[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20140402080102.GK2931@tbergstrom-lnx.Nvidia.com>
Date: Wed, 2 Apr 2014 11:01:02 +0300
From: Peter De Schrijver <pdeschrijver@...dia.com>
To: Ben Dooks <ben.dooks@...ethink.co.uk>
CC: Greg KH <gregkh@...uxfoundation.org>,
Sylwester Nawrocki <s.nawrocki@...sung.com>,
"mark.rutland@....com" <mark.rutland@....com>,
"devicetree@...r.kernel.org" <devicetree@...r.kernel.org>,
"mturquette@...aro.org" <mturquette@...aro.org>,
"t.figa@...sung.com" <t.figa@...sung.com>,
"sw0312.kim@...sung.com" <sw0312.kim@...sung.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"kyungmin.park@...sung.com" <kyungmin.park@...sung.com>,
"robh+dt@...nel.org" <robh+dt@...nel.org>,
"laurent.pinchart@...asonboard.com"
<laurent.pinchart@...asonboard.com>,
"galak@...eaurora.org" <galak@...eaurora.org>,
"grant.likely@...aro.org" <grant.likely@...aro.org>,
"linux@....linux.org.uk" <linux@....linux.org.uk>,
"s.hauer@...gutronix.de" <s.hauer@...gutronix.de>,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>,
"m.szyprowski@...sung.com" <m.szyprowski@...sung.com>
Subject: Re: [PATCH RFC v4 2/2] clk: Add handling of clk parent and rate
assigned from DT
On Tue, Apr 01, 2014 at 03:19:40PM +0200, Ben Dooks wrote:
> On 31/03/14 21:06, Greg KH wrote:
> > On Mon, Mar 31, 2014 at 06:41:56PM +0200, Sylwester Nawrocki wrote:
> >> This function adds a helper function to configure clock parents and rates
> >> as specified in clock-parents, clock-rates DT properties for a consumer
> >> device and a call to it before driver is bound to a device.
> >>
> >> Signed-off-by: Sylwester Nawrocki <s.nawrocki@...sung.com>
>
> [snip]
>
> >
> > I don't understand why you need the driver core to initialize this one
> > type of thing? That should be in a driver, or in a class, or at worse
> > case, the platform code.
> >
> > What makes clocks so "unique" here?
>
> I suppose the issue here is that a lot of drivers currently use
> clocks and a number of systems have badly setup default clock trees
> at start time.
>
> Mark Brown and others have argued that the management of clocks which
> is common to all devices should not live in the driver.
Exactly, this data should be part of the clock provider DT nodes, not
of the device nodes.
Cheers,
Peter.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists