[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <533ABCEC.8040701@codethink.co.uk>
Date: Tue, 01 Apr 2014 14:19:40 +0100
From: Ben Dooks <ben.dooks@...ethink.co.uk>
To: Greg KH <gregkh@...uxfoundation.org>,
Sylwester Nawrocki <s.nawrocki@...sung.com>
CC: devicetree@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org, mturquette@...aro.org,
linux@....linux.org.uk, robh+dt@...nel.org,
grant.likely@...aro.org, mark.rutland@....com,
galak@...eaurora.org, kyungmin.park@...sung.com,
sw0312.kim@...sung.com, m.szyprowski@...sung.com,
t.figa@...sung.com, laurent.pinchart@...asonboard.com,
s.hauer@...gutronix.de
Subject: Re: [PATCH RFC v4 2/2] clk: Add handling of clk parent and rate assigned
from DT
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.
--
Ben Dooks http://www.codethink.co.uk/
Senior Engineer Codethink - Providing Genius
--
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