From: heiko@sntech.de (Heiko Stübner)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v5 0/5] ARM: rockchip: add smp functionality
Date: Tue, 22 Oct 2013 16:08:44 +0200 [thread overview]
Message-ID: <201310221608.45192.heiko@sntech.de> (raw)
In-Reply-To: <201310221600.13562.heiko@sntech.de>
gaah, there I just learned about the arm at kernel.org address and still didn't
remember when digging up this old recipient list - which of course resulted in
Kevin not being included.
Additionally I also had the old devicetree list included.
So I'll do it again shortly :-)
Sorry for the noise
Heiko
Am Dienstag, 22. Oktober 2013, 16:00:13 schrieb Heiko St?bner:
> This series enables the use of the additional cores on Rockchip
> Cortex-A9 SoCs.
>
> To achieve this, add the scu, the needed sram and power-management-unit.
>
> Tested on both a BQ Curie2 (rk3066a / dual core) and
> on a Radxa Rock (rk3188 / quad core).
>
> changes since v4:
> - rebase on top of the recent rk3188 board support
> - implement suggestion from Matt Sealey in moving the sram-limit from
> marking reserved regions to marking available regions - hopefully
> I got the usage right :-)
> - remove __CPUINIT as suggested by Fabio Estevam
>
> changes since v3:
> - address comments from Rob Herring:
> - split the gathering of the reserve-data into a separate loop
> - spelling and style fixes
> - first patch only included for reference, already part of the
> char-misc git tree
>
> changes since v2:
> - rework the sram allocation following the suggestion from Philipp Zabel
>
> changes since v1:
> - add reserved block feature for mmio-sram, to not use two logical
> sram nodes
> - the sram content is kept intact while the device is running, so
> copying the trampoline is only needed once
>
> Heiko Stuebner (5):
> misc: sram: add ability to limit used sram areas
> ARM: rockchip: add snoop-control-unit
> ARM: rockchip: add sram dt nodes and documentation
> ARM: rockchip: add power-management-unit dt node
> ARM: rockchip: add smp bringup code
>
> .../devicetree/bindings/arm/rockchip/pmu.txt | 16 ++
> .../devicetree/bindings/arm/rockchip/smp-sram.txt | 24 +++
> Documentation/devicetree/bindings/misc/sram.txt | 8 +
> arch/arm/boot/dts/rk3066a.dtsi | 6 +
> arch/arm/boot/dts/rk3188.dtsi | 6 +
> arch/arm/boot/dts/rk3xxx.dtsi | 10 +
> arch/arm/mach-rockchip/Kconfig | 1 +
> arch/arm/mach-rockchip/Makefile | 1 +
> arch/arm/mach-rockchip/core.h | 22 +++
> arch/arm/mach-rockchip/headsmp.S | 30 ++++
> arch/arm/mach-rockchip/platsmp.c | 195
> ++++++++++++++++++++ arch/arm/mach-rockchip/rockchip.c |
> 2 +
> drivers/misc/sram.c | 51 ++++-
> 13 files changed, 368 insertions(+), 6 deletions(-)
> create mode 100644 Documentation/devicetree/bindings/arm/rockchip/pmu.txt
> create mode 100644
> Documentation/devicetree/bindings/arm/rockchip/smp-sram.txt create mode
> 100644 arch/arm/mach-rockchip/core.h
> create mode 100644 arch/arm/mach-rockchip/headsmp.S
> create mode 100644 arch/arm/mach-rockchip/platsmp.c
prev parent reply other threads:[~2013-10-22 14:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-22 14:00 [PATCH v5 0/5] ARM: rockchip: add smp functionality Heiko Stübner
2013-10-22 14:01 ` [PATCH v5 1/5] misc: sram: add ability to limit used sram areas Heiko Stübner
2013-10-22 14:01 ` [PATCH v5 2/5] ARM: rockchip: add snoop-control-unit Heiko Stübner
2013-10-22 14:08 ` Heiko Stübner [this message]
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=201310221608.45192.heiko@sntech.de \
--to=heiko@sntech.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox