From: olof@lixom.net (Olof Johansson)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/2] ARM: ux500: add an SMP enablement type and move cpu nodes
Date: Thu, 6 Aug 2015 10:10:52 +0200 [thread overview]
Message-ID: <20150806081052.GB16520@localhost> (raw)
In-Reply-To: <1438586801-30115-1-git-send-email-linus.walleij@linaro.org>
On Mon, Aug 03, 2015 at 09:26:41AM +0200, Linus Walleij wrote:
> The "cpus" node cannot be inside the "soc" node, while this
> works for the CoreSight blocks, the early boot code will look
> for "cpus" directly under the root node, so this is a hard
> convention. So move the CPU nodes.
>
> Augment the "reg" property to match what is actually in the
> hardware: 0x300 and 0x301 respectively.
>
> Then add an SMP enablement type to be used by the SMP init
> code, "ste,dbx500-smp".
>
> Signed-off-by: Linus Walleij <linus.walleij@linaro.org>
> ---
> Hi ARM SoC people: please apply this as a fix for v4.2
> as it is prerequisite for 2/2 which is a more proper fix
> for the secondary CPU boot regression addressed by the
> fixed remappings patch.
Applied, thanks.
-Olof
next prev parent reply other threads:[~2015-08-06 8:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-03 7:26 [PATCH 1/2] ARM: ux500: add an SMP enablement type and move cpu nodes Linus Walleij
2015-08-06 8:10 ` Olof Johansson [this message]
2015-10-20 4:52 ` Kevin Hilman
2015-10-22 12:24 ` Linus Walleij
2015-10-22 22:13 ` Kevin Hilman
2015-10-22 22:17 ` Kevin Hilman
2015-10-22 22:59 ` Kevin Hilman
-- strict thread matches above, loose matches on Subject: below --
2015-07-31 12:22 Linus Walleij
2015-07-31 12:22 ` 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=20150806081052.GB16520@localhost \
--to=olof@lixom.net \
--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.