summaryrefslogtreecommitdiff
path: root/Documentation/devicetree/bindings/clock
diff options
context:
space:
mode:
authorUdit Kumar <u-kumar1@ti.com>2024-02-13 11:26:40 +0300
committerStephen Boyd <sboyd@kernel.org>2024-02-22 08:59:48 +0300
commitad3ac13c6ec318b43e769cc9ffde67528e58e555 (patch)
treec223606f4d3800d1ad8f7fcd0a362d65b75de26b /Documentation/devicetree/bindings/clock
parent6613476e225e090cc9aad49be7fa504e290dd33d (diff)
downloadlinux-ad3ac13c6ec318b43e769cc9ffde67528e58e555.tar.xz
clk: keystone: sci-clk: Adding support for non contiguous clocks
Most of clocks and their parents are defined in contiguous range, But in few cases, there is gap in clock numbers[0]. Driver assumes clocks to be in contiguous range, and add their clock ids incrementally. New firmware started returning error while calling get_freq and is_on API for non-available clock ids. In this fix, driver checks and adds only valid clock ids. [0] https://software-dl.ti.com/tisci/esd/latest/5_soc_doc/j7200/clocks.html Section Clocks for NAVSS0_CPTS_0 Device, clock id 12-15 not present. Fixes: 3c13933c6033 ("clk: keystone: sci-clk: add support for dynamically probing clocks") Signed-off-by: Udit Kumar <u-kumar1@ti.com> Link: https://lore.kernel.org/r/20240213082640.457316-1-u-kumar1@ti.com Reviewed-by: Nishanth Menon <nm@ti.com> Signed-off-by: Stephen Boyd <sboyd@kernel.org>
Diffstat (limited to 'Documentation/devicetree/bindings/clock')
0 files changed, 0 insertions, 0 deletions