From: Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>
To: "Antoine Ténart" <antoine.tenart@free-electrons.com>
Cc: alexandre.belloni@free-electrons.com,
thomas.petazzoni@free-electrons.com, zmxu@marvell.com,
jszhang@marvell.com, linux-arm-kernel@lists.infradead.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 1/5] ARM: berlin: add SMP support
Date: Wed, 25 Jun 2014 17:00:02 +0200 [thread overview]
Message-ID: <53AAE3F2.9060809@gmail.com> (raw)
In-Reply-To: <1401897826-11711-2-git-send-email-antoine.tenart@free-electrons.com>
On 06/04/2014 06:03 PM, Antoine Ténart wrote:
> Adds SMP support for Berlin SoCs. Secondary CPUs are reset, then
> execute the instruction we put in the reset exception register, setting
> the pc at the address contained in the software reset address register,
> which is the physical address of the Berlin secondary startup.
>
> This implementation avoid using the pen lock mechanism.
>
> Signed-off-by: Antoine Ténart <antoine.tenart@free-electrons.com>
Applied to berlin/soc with Andrew's Reviewed-by.
Thanks!
next prev parent reply other threads:[~2014-06-25 15:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-04 16:03 [PATCH v2 0/5] ARM: Berlin: SMP support Antoine Ténart
2014-06-04 16:03 ` [PATCH v2 1/5] ARM: berlin: add " Antoine Ténart
2014-06-25 15:00 ` Sebastian Hesselbarth [this message]
2014-06-04 16:03 ` [PATCH v2 2/5] Documentation: bindings: add the Berlin CPU control doc Antoine Ténart
[not found] ` <1401897826-11711-3-git-send-email-antoine.tenart-wi1+55ScJUtKEb57/3fJTNBPR1lH4CV8@public.gmane.org>
2014-06-25 15:00 ` Sebastian Hesselbarth
2014-06-04 16:03 ` [PATCH v2 3/5] Documentation: bindings: add the marvell, berlin-smp CPU enable method Antoine Ténart
2014-06-04 16:03 ` [PATCH v2 4/5] ARM: dts: berlin: add SMP related nodes and properties for BG2 Antoine Ténart
2014-06-04 16:03 ` [PATCH v2 5/5] ARM: dts: berlin: add SMP related nodes and properties for BG2Q Antoine Ténart
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=53AAE3F2.9060809@gmail.com \
--to=sebastian.hesselbarth@gmail.com \
--cc=alexandre.belloni@free-electrons.com \
--cc=antoine.tenart@free-electrons.com \
--cc=devicetree@vger.kernel.org \
--cc=jszhang@marvell.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=thomas.petazzoni@free-electrons.com \
--cc=zmxu@marvell.com \
/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).