From: Nicolas Ferre <nicolas.ferre@atmel.com>
To: Arnd Bergmann <arnd@arndb.de>, Olof Johansson <olof@lixom.net>,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
Linux Kernel list <linux-kernel@vger.kernel.org>
Cc: Jean-Christophe PLAGNIOL-VILLARD <plagnioj@jcrosoft.com>,
Ludovic Desroches <ludovic.desroches@atmel.com>,
Chris Ball <cjb@laptop.org>,
linux-mmc@vger.kernel.org
Subject: [GIT PULL] at91: fixes for 3.7-rc7
Date: Mon, 19 Nov 2012 17:31:17 +0100 [thread overview]
Message-ID: <50AA5ED5.8090901@atmel.com> (raw)
Arnd, Olof,
Here is another "fixes" pull request for AT91. It enables the sd/mmc driver
for Device Tree enabled platforms. Those patches where part of a series that
was split in two for reaching upstream: the MMC part is already in Linus' tree
and this is the arm-soc part.
I have placed these patches on top of the fixes that you already have for AT91.
The following changes since commit 641f3ce64b050961d454a0716bb6dbf528315aac:
ARM: at91/usbh: fix overcurrent gpio setup (2012-11-16 10:46:29 +0100)
are available in the git repository at:
git://github.com/at91linux/linux-at91.git tags/at91-fixes
for you to fetch changes up to 83ce1c55cfb639438c2516cb05f3b8ee472023e5:
ARM: at91/dts: add nodes for atmel hsmci controllers for atmel boards (2012-11-19 17:02:40 +0100)
----------------------------------------------------------------
Add entries for enabling the use of sd/mmc driver on AT91.
Those entries where missing for device tree use on these
platforms.
----------------------------------------------------------------
Ludovic Desroches (3):
ARM: at91: add clocks for DT entries
ARM: at91/dts: add nodes for atmel hsmci controllers for atmel SOCs
ARM: at91/dts: add nodes for atmel hsmci controllers for atmel boards
arch/arm/boot/dts/at91sam9260.dtsi | 9 +++++++++
arch/arm/boot/dts/at91sam9263.dtsi | 18 ++++++++++++++++++
arch/arm/boot/dts/at91sam9263ek.dts | 10 ++++++++++
arch/arm/boot/dts/at91sam9g20ek_2mmc.dts | 12 ++++++++++++
arch/arm/boot/dts/at91sam9g20ek_common.dtsi | 9 +++++++++
arch/arm/boot/dts/at91sam9g25ek.dts | 18 ++++++++++++++++++
arch/arm/boot/dts/at91sam9g45.dtsi | 18 ++++++++++++++++++
arch/arm/boot/dts/at91sam9m10g45ek.dts | 19 +++++++++++++++++++
arch/arm/boot/dts/at91sam9n12.dtsi | 9 +++++++++
arch/arm/boot/dts/at91sam9n12ek.dts | 9 +++++++++
arch/arm/boot/dts/at91sam9x5.dtsi | 18 ++++++++++++++++++
arch/arm/mach-at91/at91sam9260.c | 1 +
arch/arm/mach-at91/at91sam9263.c | 2 ++
arch/arm/mach-at91/at91sam9g45.c | 2 ++
arch/arm/mach-at91/at91sam9n12.c | 1 +
arch/arm/mach-at91/at91sam9x5.c | 2 ++
16 files changed, 157 insertions(+)
--
Nicolas Ferre
next reply other threads:[~2012-11-19 16:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-19 16:31 Nicolas Ferre [this message]
2012-11-19 16:52 ` [GIT PULL] at91: fixes for 3.7-rc7 Olof Johansson
2012-11-19 17:29 ` Nicolas Ferre
2012-11-20 8:59 ` [GIT PULL v2] " Nicolas Ferre
2012-11-21 7:03 ` Olof Johansson
2012-11-21 11:25 ` Nicolas Ferre
2012-11-20 18:47 ` [GIT PULL] " Linus Walleij
2012-11-20 20:00 ` Jean-Christophe PLAGNIOL-VILLARD
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=50AA5ED5.8090901@atmel.com \
--to=nicolas.ferre@atmel.com \
--cc=arnd@arndb.de \
--cc=cjb@laptop.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=ludovic.desroches@atmel.com \
--cc=olof@lixom.net \
--cc=plagnioj@jcrosoft.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).