All of lore.kernel.org
 help / color / mirror / Atom feed
From: s.hauer@pengutronix.de (Sascha Hauer)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/3] mach-ux500: initialize l2x0 at arch_init time
Date: Wed, 24 Aug 2011 14:14:26 +0200	[thread overview]
Message-ID: <20110824121425.GA31404@pengutronix.de> (raw)
In-Reply-To: <CACRpkdZWwwapspVFrZNC8ReURrKVYFUDzdmEL7HiZWOjZ907jQ@mail.gmail.com>

Hi Linus,

On Wed, Aug 24, 2011 at 01:59:40PM +0200, Linus Walleij wrote:
> On Wed, Aug 24, 2011 at 12:12 PM, Kyungmin Park <kmpark@infradead.org> wrote:
> > On Wed, Aug 24, 2011 at 6:56 PM, Santosh <santosh.shilimkar@ti.com> wrote:
> >> On Wednesday 24 August 2011 02:53 PM, Linus Walleij wrote:
> >>
> >> More and more you delay L2 cache enable in boot-process,
> >> your boot-up time is going to shoot-up.
> >>
> >> Have you thought about it. Cache's should be enabled as
> >> early as possible.
> >
> > Right, after change from early_init to arch_init. it takes more time.
> 
> Hm no good. I'll drop this.
> 
> We've seen that if we try to unlock the I&D l2x0 at the
> early_initcall() as in [3/3] it will sometimes fail, like it's
> still locked down afterwards. Calling it from .init_machine()
> appears to work. So in my dumbness I moved it to
> arch_initcall() which should be equivalent. Does anyone
> have some subtle hint or experience on how to get around
> that one issue, or should I just put in a second
> arch_initcall() for just the unlocking?
> 
> Sascha, I guess Freescale should also move the l2x0 init to
> early_init() in mach-imx/cache-l2x0.c if possible. Can
> you try the below on your machine(s)?

Sure, what are you interested in? If it works reliably or if works
faster?

Sascha

> 
> diff --git a/arch/arm/mach-imx/cache-l2x0.c b/arch/arm/mach-imx/cache-l2x0.c
> index 69d1322..e5538a4 100644
> --- a/arch/arm/mach-imx/cache-l2x0.c
> +++ b/arch/arm/mach-imx/cache-l2x0.c
> @@ -53,4 +53,4 @@ static int mxc_init_l2x0(void)
> 
>         return 0;
>  }
> -arch_initcall(mxc_init_l2x0);
> +early_initcall(mxc_init_l2x0);
> 
> Yours,
> Linus Walleij
> 

-- 
Pengutronix e.K.                           |                             |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

  reply	other threads:[~2011-08-24 12:14 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-24  9:23 [PATCH 2/3] mach-ux500: initialize l2x0 at arch_init time Linus Walleij
2011-08-24  9:56 ` Santosh
2011-08-24 10:12   ` Kyungmin Park
2011-08-24 11:59     ` Linus Walleij
2011-08-24 12:14       ` Sascha Hauer [this message]
2011-08-24 12:30         ` Jason Liu

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=20110824121425.GA31404@pengutronix.de \
    --to=s.hauer@pengutronix.de \
    --cc=linux-arm-kernel@lists.infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.