Hello Maxime,
On Mon, Apr 01, 2019 at 10:22:42AM +0200, Maxime Ripard wrote:
> Hi,
>
> On Thu, Mar 28, 2019 at 12:31:59PM +0100, megous@xxxxxxxxxx wrote:
> > From: Ondrej Jirman <megous@xxxxxxxxxx>
> >
> > A83T DTSI has cpu clocks defined only on the first CPU in each cluster.
> > We can bring down any CPU in the cluster, so we need to define clock
> > for each CPU, so that the system knows what clock to use if the first
> > CPU is down.
> >
> > Signed-off-by: Ondrej Jirman <megous@xxxxxxxxxx>
> > ---
> > arch/arm/boot/dts/sun8i-a83t.dtsi | 12 ++++++++++++
> > 1 file changed, 12 insertions(+)
> >
> > diff --git a/arch/arm/boot/dts/sun8i-a83t.dtsi b/arch/arm/boot/dts/sun8i-a83t.dtsi
> > index 7a40b7d77ec0..1b0b025b9250 100644
> > --- a/arch/arm/boot/dts/sun8i-a83t.dtsi
> > +++ b/arch/arm/boot/dts/sun8i-a83t.dtsi
> > @@ -73,6 +73,8 @@
> > };
> >
> > cpu@1 {
> > + clocks = <&ccu CLK_C0CPUX>;
>
> Usually we'll have the compatible first
I'll re-order it.
> > + clock-names = "cpu";
>
> And that's not documented anywhere?
Cpufreq doesn't use CPU clock names, except for the mediatek cpufreq driver.
It's not docummented explicitly, except it's used as part of examples in
bindings/opp/opp.txt.
I guess I can safely drop it, but other will probably keep using it, because
it's part of the examples.
thank you and regards,
Ondrej
> Maxime
>
> --
> Maxime Ripard, Bootlin
> Embedded Linux and Kernel engineering
> https://bootlin.com
