From: tony@atomide•com (Tony Lindgren)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCH v2] ARM: OMAP: clocks: Delay clk inits atleast until slab is initialized
Date: Wed, 27 Mar 2013 09:50:08 -0700 [thread overview]
Message-ID: <20130327165007.GJ25575@atomide.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1303270456280.8161@utopia.booyaka.com>
* Paul Walmsley <paul@pwsan•com> [130326 22:01]:
> Hi
>
> On Thu, 21 Mar 2013, Rajendra Nayak wrote:
>
> > clk inits on OMAP happen quite early, even before slab is available.
> > The dependency comes from the fact that the timer init code starts to
> > use clocks and hwmod and we need clocks to be initialized by then.
> >
> > There are various problems doing clk inits this early, one is,
> > not being able to do dynamic clk registrations and hence the
> > dependency on clk-private.h. The other is, inability to debug
> > early kernel crashes without enabling DEBUG_LL and earlyprintk.
>
> ...
>
> > Reported-by: Piotr Haber <phaber@broadcom•com>
> > Reported-by: Tony Lindgren <tony@atomide•com>
> > Signed-off-by: Rajendra Nayak <rnayak@ti•com>
>
> Thanks, looks good to me. Nice patch description!
>
> Acked-by: Paul Walmsley <paul@pwsan•com>
I applied this into omap-for-v3.9-rc3/fixes, will send a pull request
for those today.
Regards,
Tony
prev parent reply other threads:[~2013-03-27 16:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-21 11:04 [PATCH v2] ARM: OMAP: clocks: Delay clk inits atleast until slab is initialized Rajendra Nayak
2013-03-21 11:18 ` Santosh Shilimkar
2013-03-21 17:59 ` Mike Turquette
2013-03-27 4:57 ` Paul Walmsley
2013-03-27 16:50 ` Tony Lindgren [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20130327165007.GJ25575@atomide.com \
--to=tony@atomide$(echo .)com \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox