From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] vexpress: soc changes for v3.8
Date: Fri, 26 Oct 2012 13:37:16 +0000 [thread overview]
Message-ID: <201210261337.16972.arnd@arndb.de> (raw)
In-Reply-To: <1350579917.4984.19.camel@hornet>
On Thursday 18 October 2012, Pawel Moll wrote:
> Hi Arnd, Olof,
>
> Could you, please, pull the Versatile Express SOC updates for 3.8?
>
Pulled into next/soc now, sorry for the delay.
Since this adds new mfd drivers, it should really have an Ack from
Samuel, and you should keep him on Cc during the submission.
Samuel: I hope you're ok with this going through the arm-soc tree,
if not please let me know and I'll take the branch out again.
Arnd
> The following changes since commit ddffeb8c4d0331609ef2581d84de4d763607bd37:
>
> Linux 3.7-rc1 (2012-10-14 14:41:04 -0700)
>
> are available in the git repository at:
>
> git://git.linaro.org/people/pawelmoll/linux.git vexpress-soc
>
> for you to fetch changes up to f665f235c6ee31f84049920f16d1ff6e2dabc8f5:
>
> ARM: vexpress: Remove motherboard dependencies in the DTS files (2012-10-18 18:00:07 +0100)
>
> ----------------------------------------------------------------
> Pawel Moll (5):
> mfd: Versatile Express config infrastructure
> mfd: Versatile Express system registers driver
> ARM: vexpress: Add config bus components and clocks to DTs
> ARM: vexpress: Start using new Versatile Express infrastructure
> ARM: vexpress: Remove motherboard dependencies in the DTS files
>
> .../devicetree/bindings/arm/vexpress-sysreg.txt | 50 ++
> Documentation/devicetree/bindings/arm/vexpress.txt | 98 +++-
> arch/arm/boot/dts/vexpress-v2m-rs1.dtsi | 146 +++++-
> arch/arm/boot/dts/vexpress-v2m.dtsi | 146 +++++-
> arch/arm/boot/dts/vexpress-v2p-ca15-tc1.dts | 121 ++++-
> arch/arm/boot/dts/vexpress-v2p-ca15_a7.dts | 186 ++++++-
> arch/arm/boot/dts/vexpress-v2p-ca5s.dts | 84 ++-
> arch/arm/boot/dts/vexpress-v2p-ca9.dts | 136 ++++-
> arch/arm/include/asm/hardware/sp810.h | 6 -
> arch/arm/mach-vexpress/Kconfig | 4 +-
> arch/arm/mach-vexpress/Makefile | 2 +-
> arch/arm/mach-vexpress/ct-ca9x4.c | 41 +-
> arch/arm/mach-vexpress/include/mach/motherboard.h | 81 ---
> arch/arm/mach-vexpress/platsmp.c | 3 +-
> arch/arm/mach-vexpress/v2m.c | 349 ++++---------
> drivers/mfd/Kconfig | 6 +
> drivers/mfd/Makefile | 1 +
> drivers/mfd/vexpress-config.c | 277 ++++++++++
> drivers/mfd/vexpress-sysreg.c | 552 ++++++++++++++++++++
> include/linux/vexpress.h | 121 +++++
> 20 files changed, 1993 insertions(+), 417 deletions(-)
> create mode 100644 Documentation/devicetree/bindings/arm/vexpress-sysreg.txt
> create mode 100644 drivers/mfd/vexpress-config.c
> create mode 100644 drivers/mfd/vexpress-sysreg.c
> create mode 100644 include/linux/vexpress.h
>
>
>
>
next prev parent reply other threads:[~2012-10-26 13:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-18 17:05 [GIT PULL] vexpress: soc changes for v3.8 Pawel Moll
2012-10-26 13:37 ` Arnd Bergmann [this message]
2012-10-26 14:02 ` Pawel Moll
2012-10-26 16:44 ` Arnd Bergmann
2012-10-26 16:54 ` Pawel Moll
2012-10-26 17:00 ` Arnd Bergmann
2012-10-26 17:10 ` Pawel Moll
2012-10-26 17:18 ` Arnd Bergmann
2012-10-26 17:45 ` Pawel Moll
2012-10-26 19:26 ` Arnd Bergmann
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=201210261337.16972.arnd@arndb.de \
--to=arnd@arndb.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;
as well as URLs for NNTP newsgroup(s).