[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20190718013100.GB6962@lunn.ch>
Date: Thu, 18 Jul 2019 03:31:00 +0200
From: Andrew Lunn <andrew@...n.ch>
To: Rob Herring <robh+dt@...nel.org>
Cc: josua@...id-run.com, netdev <netdev@...r.kernel.org>,
stable <stable@...r.kernel.org>,
"David S. Miller" <davem@...emloft.net>,
Mark Rutland <mark.rutland@....com>
Subject: Re: [PATCH 1/4] dt-bindings: allow up to four clocks for orion-mdio
On Tue, Jul 09, 2019 at 04:03:28PM -0600, Rob Herring wrote:
> On Mon, Jul 8, 2019 at 8:41 PM Andrew Lunn <andrew@...n.ch> wrote:
> >
> > > > Optional properties:
> > > > - interrupts: interrupt line number for the SMI error/done interrupt
> > > > -- clocks: phandle for up to three required clocks for the MDIO instance
> > > > +- clocks: phandle for up to four required clocks for the MDIO instance
> > >
> > > This needs to enumerate exactly what the clocks are. Shouldn't there
> > > be an additional clock-names value too?
> >
> > Hi Rob
> >
> > The driver does not care what they are called. It just turns them all
> > on, and turns them off again when removed.
>
> That's fine for the driver to do, but this is the hardware description.
>
> It's not just what they are called, but how many too. Is 1 clock in
> the DT valid? 0? It would be unusual for a given piece of h/w to
> function with a variable number of clocks.
Hi Rob
The orion5x has 0 clocks. kirkwood, dove, Armada XP, 370 375, 380
has 1 clock. Armada 37xx has 4.
So yes, 1 clock is valid. 0 clocks is also valid. The piece of
hardware itself does not care how many clocks are feeding it, so long
as they are all turned on.
Andrew
Powered by blists - more mailing lists