linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: lee.jones@linaro.org (Lee Jones)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/1] ARM: ux500: Fix u9540 booting issues
Date: Tue, 27 Nov 2012 13:03:11 +0000	[thread overview]
Message-ID: <20121127130311.GE2013@gmail.com> (raw)
In-Reply-To: <201211271236.01493.arnd@arndb.de>

On Tue, 27 Nov 2012, Arnd Bergmann wrote:

> On Tuesday 27 November 2012, Lee Jones wrote:
> 
> > The u9540 stopped booting after the v3.7 merge window due to
> > a lack of common clk support and early PRCMU initialisation.
> > In this patch we rectify these issues, placing the u9540
> > development board back into a successfully booting state.
> 
> > -       if (cpu_is_u8500_family())
> > +       if (cpu_is_u8500_family() || cpu_is_u9540())
> >                 u8500_clk_init();
> > -       else if (cpu_is_u9540())
> > -               u9540_clk_init();
> >         else if (cpu_is_u8540())
> >                 u8540_clk_init();
> 
> It certainly doesn't /look/ right, even if it works.  Can you explain why
> u8540_clk_init works and u9540_clk_init doesn't?

Because it's empty. :)

Common clk doesn't support the u9540 yet, and even when it does,
most (all?) of the clocks will be identical to the u9540 in any
case.

I believe Linus wants to apply this with a TODO, to ensure the
board is at least bootable. This whole section is in the wrong
place anyway IMHO, and needs moving out to somewhere less hacky,
rather than initialising clocks and the PRCMU from .init_irq.

-- 
Lee Jones
Linaro ST-Ericsson Landing Team Lead
Linaro.org ? Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog

  reply	other threads:[~2012-11-27 13:03 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-27  9:34 [PATCH 1/1] ARM: ux500: Fix u9540 booting issues Lee Jones
2012-11-27 12:36 ` Arnd Bergmann
2012-11-27 13:03   ` Lee Jones [this message]
2013-01-24 16:06 ` Linus Walleij

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=20121127130311.GE2013@gmail.com \
    --to=lee.jones@linaro.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).