]> git.ipfire.org Git - thirdparty/kernel/linux.git/commit
Merge branch 'dpll-zl3073x-include-current-frequency-in-supported-frequencies-list'
authorJakub Kicinski <kuba@kernel.org>
Sat, 7 Feb 2026 04:44:24 +0000 (20:44 -0800)
committerJakub Kicinski <kuba@kernel.org>
Sat, 7 Feb 2026 04:44:24 +0000 (20:44 -0800)
commit5826eec8710c214f02f253c165d66a230f5a86c3
treed693603aae6594071a4446309a6d62f0d1320f49
parenta14d9317904559a6948946de05bf9fb6f2a34fba
parent85a9aaac4a38a7ce68f30bd7678fca4e8c687fe2
Merge branch 'dpll-zl3073x-include-current-frequency-in-supported-frequencies-list'

Ivan Vecera says:

====================
dpll: zl3073x: Include current frequency in supported frequencies list

This series ensures that the current operating frequency of a DPLL pin
is always reported in its supported frequencies list.

Problem:
When a ZL3073x DPLL pin is registered, its supported frequencies are
read from the firmware node's "supported-frequencies-hz" property.
However, if the firmware node is missing, or doesn't include the
current operating frequency, the pin reports a frequency that isn't
in its supported list. This inconsistency can confuse userspace tools
that expect the current frequency to be among the supported values.

Solution:
Always include the current pin frequency as the first entry in the
supported frequencies list, followed by any additional frequencies
from the firmware node (with duplicates filtered out).

Patch 1 refactors the output pin frequency calculation into a reusable
helper function zl3073x_dev_output_pin_freq_get(), which mirrors the
existing zl3073x_dev_ref_freq_get() for input pins.

Patch 2 modifies zl3073x_pin_props_get() to obtain the current
frequency early and place it at index 0 of the supported frequencies
array, ensuring it is always present regardless of firmware node
contents.
====================

Link: https://patch.msgid.link/20260205154350.3180465-1-ivecera@redhat.com
Signed-off-by: Jakub Kicinski <kuba@kernel.org>