On Tue Jan 24, 2023 at 4:25 PM CET, Bryan O'Donoghue wrote:
> On 24/01/2023 14:48, Luca Weiss wrote:
> > On Fri Jan 20, 2023 at 5:49 PM CET, Bryan O'Donoghue wrote:
> >> On 20/01/2023 13:13, Luca Weiss wrote:
> >>> + camcc: clock-controller@ad00000 {
> >>> + compatible = "qcom,sm6350-camcc";
> >>> + reg = <0 0x0ad00000 0 0x16000>;
> >>> + clocks = <&rpmhcc RPMH_CXO_CLK>;
> >>> + #clock-cells = <1>;
> >>> + #reset-cells = <1>;
> >>> + #power-domain-cells = <1>;
> >>> + };
> >>
> >> Should you include
> >>
> >> required-opps = <&rpmhpd_opp_low_svs>;
> >>
> >> ?
> >
> > I don't know, it works without. But doesn't this property not just
> > affect power-domains? I haven't passed any here.
> >
>
> Should you have a TITAN_TOP pd though ?
Can I reference <&camcc TITAN_TOP_GDSC> from itself? I know that having
it on is required to turn on at least some clocks (maybe all clocks).
But from what I understand how power domains are normally handled, the
driver core enables them before the driver is probed, so self
referencing wouldn't work.
And at least no other SoC upstream references TITAN_TOP_GDSC in camcc.
Regards
Luca
>
> ---
> bod
