On 25/01/2023 23:49, Stephen Boyd wrote:
Quoting Dmitry Baryshkov (2023-01-10 22:03:56)
Convert the clock driver to specify parent data rather than parent
names, to actually bind using 'clock-names' specified in the DTS rather
than global clock names. Use parent_hws where possible to refer parent
clocks directly, skipping the lookup.
Note, the system names for xo clocks were changed from "xo" to
"xo_board" to follow the example of other platforms. This switches the
clocks to use DT-provided "xo_board" clock instead of manually
registered "xo" clock and allows us to drop qcom_cc_register_board_clk()
call from the driver at some point.
Should probably also mention that using the firmware path will mean the
RPM control of XO could be involved and so suspend may no longer achieve
XO shutdown or it will stop working. In case bisect lands here we'll
know from the commit text that this likely broke power management.
As you've seen from the DT changes, this series is a pure rework, no
switching to RPM's XO clock.
In the same way change the looked up system "sleep_clk_src" clock to
"sleep_clk", which is registered from DT.
Reviewed-by: Konrad Dybcio <konrad.dybcio@xxxxxxxxxx>
Signed-off-by: Dmitry Baryshkov <dmitry.baryshkov@xxxxxxxxxx>
---
Reviewed-by: Stephen Boyd <sboyd@xxxxxxxxxx>
--
With best wishes
Dmitry
