diff options
| author | Konrad Dybcio <konrad.dybcio@oss.qualcomm.com> | 2025-03-27 02:47:06 +0100 |
|---|---|---|
| committer | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2025-06-19 15:40:14 +0200 |
| commit | 8c3ece5ca8361b7404a396e3e8748e797be79ef7 (patch) | |
| tree | d15cb6c1b33768584fe135f0bf5530ee7cc94e2a /tools/perf/scripts/python | |
| parent | d0c194350c4d65445a74d61fb51bf6e74c615045 (diff) | |
arm64: dts: qcom: msm8998: Remove mdss_hdmi_phy phandle argument
[ Upstream commit 7ebdb205d4b9dd839a93a9b8975ce8ccf86b882a ]
The node has #clock-cells = <0>, as it only provides a single clock
output.
This leads to a turbo sneaky bug, where the dt checker shows that we
have additional clocks in the array:
clock-controller@c8c0000: clocks: [[3, 0], [39, 178], [156, 1],
[156, 0], [157, 1], [157, 0], [158], [0], [0], [0], [39, 184]]
is too long
..which happens due to dtc interpreting <&mdss_hdmi_phy 0> as
<&mdss_hdmi_phy>, <0> after taking cells into account.
Remove the superfluous argument to both silence the warning and fix
the index-based lookup of subsequent entries in "clocks".
Fixes: 2150c87db80c ("arm64: dts: qcom: msm8998: add HDMI nodes")
Reviewed-by: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
Signed-off-by: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
Link: https://lore.kernel.org/r/20250327-topic-more_dt_bindings_fixes-v2-4-b763d958545f@oss.qualcomm.com
Signed-off-by: Bjorn Andersson <andersson@kernel.org>
Signed-off-by: Sasha Levin <sashal@kernel.org>
Diffstat (limited to 'tools/perf/scripts/python')
0 files changed, 0 insertions, 0 deletions
