summaryrefslogtreecommitdiff
path: root/include/uapi/linux
diff options
context:
space:
mode:
authorIvan Vecera <ivecera@redhat.com>2026-01-14 15:27:24 +0300
committerJakub Kicinski <kuba@kernel.org>2026-01-19 23:04:53 +0300
commitb1f99cc8863847676d4a7329ffb668a030150d99 (patch)
tree9f8436bcafa6d13fdea1fc9abcf947b7ffe0c53f /include/uapi/linux
parentd321d505edb64286bae0e464574d0fd553e31adc (diff)
downloadlinux-b1f99cc8863847676d4a7329ffb668a030150d99.tar.xz
dpll: add dpll_device op to get supported modes
Currently, the DPLL subsystem assumes that the only supported mode is the one currently active on the device. When dpll_msg_add_mode_supported() is called, it relies on ops->mode_get() and reports that single mode to userspace. This prevents users from discovering other modes the device might be capable of. Add a new callback .supported_modes_get() to struct dpll_device_ops. This allows drivers to populate a bitmap indicating all modes supported by the hardware. Update dpll_msg_add_mode_supported() to utilize this new callback: * if ops->supported_modes_get is defined, use it to retrieve the full bitmap of supported modes. * if not defined, fall back to the existing behavior: retrieve the current mode via ops->mode_get and set the corresponding bit in the bitmap. Finally, iterate over the bitmap and add a DPLL_A_MODE_SUPPORTED netlink attribute for every set bit, accurately reporting the device's capabilities to userspace. Reviewed-by: Vadim Fedorenko <vadim.fedorenko@linux.dev> Signed-off-by: Ivan Vecera <ivecera@redhat.com> Link: https://patch.msgid.link/20260114122726.120303-2-ivecera@redhat.com Signed-off-by: Jakub Kicinski <kuba@kernel.org>
Diffstat (limited to 'include/uapi/linux')
0 files changed, 0 insertions, 0 deletions