There are two problems with the upstream camcc implementation at the moment which this series addresses. 1. The camcc block has two power-domains MXC and MMCX however, the yaml description doesn't include MXC. 2. The code for the GDSC definitions for x1e80100 camcc fails to list the titan_top_gdsc as the parent GDSC of the other GDSCs. This series addresses both of those bugs. There is currently no upstream camcc dtsi for x1e80100 so the yaml change won't affect the ABI. Signed-off-by: Bryan O'Donoghue <bryan.odonoghue@xxxxxxxxxx> --- Changes in v2: - Incorporates Krzysztof's comment on removing "phandle" description - Added Konrad's RB - Moves the location of the allOf Editing the dtsi to test the yaml constraints showed the power-domains were not being picked up but putting the allOf before the required fixed that. - Listed the 8450, 8560 and 8280 under "-items" as testing shows adding too many power-domains to the dtsi was not being picked up by the automated checkers. - Tested with Too many power-domains in sm8450 Zero power-domains in 8550 Too few power-domains in x1e80100 - Link to v1: https://lore.kernel.org/r/20240311-linux-next-camcc-fixes-v1-0-d126ae0b9350@xxxxxxxxxx --- Bryan O'Donoghue (2): dt-bindings: clock: qcom: Fix x1e80100 camcc power-domain declaration clk: qcom: camcc-x1e80100: Set titan_top_gdsc as the parent GDSC of subordinate GDSCs .../bindings/clock/qcom,sm8450-camcc.yaml | 37 ++++++++++++++++++---- drivers/clk/qcom/camcc-x1e80100.c | 7 ++++ 2 files changed, 38 insertions(+), 6 deletions(-) --- base-commit: 8ffc8b1bbd505e27e2c8439d326b6059c906c9dd change-id: 20240310-linux-next-camcc-fixes-a68322916421 Best regards, -- Bryan O'Donoghue <bryan.odonoghue@xxxxxxxxxx>
