[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20111003170503.GI23811@sirena.org.uk>
Date: Mon, 3 Oct 2011 18:05:03 +0100
From: Mark Brown <broonie@...nsource.wolfsonmicro.com>
To: Russell King - ARM Linux <linux@....linux.org.uk>
Cc: jeremy.kerr@...onical.com, paul@...an.com,
linaro-dev@...ts.linaro.org, linus.walleij@...ricsson.com,
tglx@...utronix.de, patches@...aro.org,
linux-arm-kernel@...ts.infradead.org, magnus.damm@...il.com,
linux-kernel@...r.kernel.org, eric.miao@...aro.org,
grant.likely@...retlab.ca, dsaxena@...aro.org,
amit.kucheria@...aro.org, skannan@...cinc.com,
arnd.bergmann@...aro.org, sboyd@...inc.com,
richard.zhao@...aro.org, shawn.guo@...escale.com,
Mike Turquette <mturquette@...com>
Subject: Re: [PATCH v2 1/7] clk: Add a generic clock infrastructure
On Mon, Oct 03, 2011 at 05:43:09PM +0100, Russell King - ARM Linux wrote:
> On Mon, Oct 03, 2011 at 05:31:08PM +0100, Mark Brown wrote:
[Not being many off-SoC clocks]
> > I dunno, I get the impression that some of this is due to the current
> > limitations of the clock API rather than due to a lack of clocks -
> > perhaps that's specific to the applications I look at, though.
> > applications
> The clk API per-se has nothing to do with how clocks are registered.
> There are two things that are the clk API:
Right, it's consumer side only which is the limitation I'm talking about
- at the minute it's only possible to use the clk API for on-SoC clocks
(or at least clocks that the SoC cares about), we don't have a clock API
for cross platform clock providers. I don't know if getting a cross
platform implementation will change that situation much.
--
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