From: "Antoine Ténart" <antoine.tenart@free-electrons.com>
To: sebastian.hesselbarth@gmail.com
Cc: thomas.petazzoni@free-electrons.com, zmxu@marvell.com,
devicetree@vger.kernel.org,
"Antoine Ténart" <antoine.tenart@free-electrons.com>,
linux-kernel@vger.kernel.org,
alexandre.belloni@free-electrons.com, jszhang@marvell.com,
linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 0/5] ARM: Berlin: SMP support
Date: Wed, 4 Jun 2014 18:03:41 +0200 [thread overview]
Message-ID: <1401897826-11711-1-git-send-email-antoine.tenart@free-electrons.com> (raw)
This series adds the SMP support for Marvell Berlin BG2 and BG2Q.
This implementation takes advantage of the reset exception register and
the software reset address register to make the CPUs execute the Berlin
secondary startup when being reset. This has the advantage of not using
the pen lock mechanism.
Patch 3 depends on Alex Elder effort to properly document CPU enable
methods: https://patchwork.kernel.org/patch/4138211/
Changes since v1:
- added a proper enable-method documentation
- s/reseted/reset/ and s/register/vector/
- removed unneeded 'select SMP'
Antoine Ténart (5):
ARM: berlin: add SMP support
Documentation: bindings: add the Berlin CPU control doc
Documentation: bindings: add the marvell,berlin-smp CPU enable method
ARM: dts: berlin: add SMP related nodes and properties for BG2
ARM: dts: berlin: add SMP related nodes and properties for BG2Q
.../arm/cpu-enable-method/marvell,berlin-smp | 41 +++++++++
.../devicetree/bindings/arm/marvell,berlin.txt | 16 ++++
arch/arm/boot/dts/berlin2.dtsi | 11 +++
arch/arm/boot/dts/berlin2q.dtsi | 11 +++
arch/arm/mach-berlin/Kconfig | 3 +
arch/arm/mach-berlin/Makefile | 3 +-
arch/arm/mach-berlin/headsmp.S | 30 +++++++
arch/arm/mach-berlin/platsmp.c | 99 ++++++++++++++++++++++
8 files changed, 213 insertions(+), 1 deletion(-)
create mode 100644 Documentation/devicetree/bindings/arm/cpu-enable-method/marvell,berlin-smp
create mode 100644 arch/arm/mach-berlin/headsmp.S
create mode 100644 arch/arm/mach-berlin/platsmp.c
--
1.9.1
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next reply other threads:[~2014-06-04 16:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-04 16:03 Antoine Ténart [this message]
2014-06-04 16:03 ` [PATCH v2 1/5] ARM: berlin: add SMP support Antoine Ténart
2014-06-25 15:00 ` Sebastian Hesselbarth
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=1401897826-11711-1-git-send-email-antoine.tenart@free-electrons.com \
--to=antoine.tenart@free-electrons.com \
--cc=alexandre.belloni@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=sebastian.hesselbarth@gmail.com \
--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).