[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20111123185518.GG31337@atomide.com>
Date: Wed, 23 Nov 2011 10:55:19 -0800
From: Tony Lindgren <tony@...mide.com>
To: Russell King - ARM Linux <linux@....linux.org.uk>
Cc: Greg KH <greg@...ah.com>, Mike Turquette <mturquette@...aro.org>,
linaro-dev@...ts.linaro.org, eric.miao@...aro.org,
grant.likely@...retlab.ca, jeremy.kerr@...onical.com,
Mike Turquette <mturquette@...com>, sboyd@...cinc.com,
magnus.damm@...il.com, dsaxena@...aro.org,
linux-arm-kernel@...ts.infradead.org, arnd.bergmann@...aro.org,
patches@...aro.org, tglx@...utronix.de, linux-omap@...r.kernel.org,
richard.zhao@...aro.org, shawn.guo@...escale.com, paul@...an.com,
linus.walleij@...ricsson.com, broonie@...nsource.wolfsonmicro.com,
linux-kernel@...r.kernel.org, amit.kucheria@...aro.org,
skannan@...cinc.com
Subject: Re: [PATCH v3 5/5] clk: export tree topology and clk data via sysfs
* Russell King - ARM Linux <linux@....linux.org.uk> [111123 09:31]:
> On Wed, Nov 23, 2011 at 08:59:04AM -0800, Tony Lindgren wrote:
> > ..let's plan on getting rid of the early usage of clocks instead so
> > you don't have the issue of deferring stuff.
>
> No - we have too many platforms already using them early to do a change
> like this - and to do such a change will force them to invent some other
> way. That's just stupid.
Not necessarily for all the systems. For omap2+ we should be able to
boot the system initially with the perf counter as the clockevent and
32KiHz always running timer. Then a dmtimer using proper clockevent
driver could take over.
> Keep the clk API as a fundamental thing which should be initialized early
> so we don't have to invent new clk APIs to get around its unavailability.
What else are you aware of that is really needed early for clocks other
than clockevent?
We've already proven that SRAM init can be moved to happen later. The
optional debug serial port is already enabled by the bootloader.
Regards,
Tony
--
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