From: nicolas.ferre@atmel.com (Nicolas Ferre)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] at91: soc updates for 3.14 #1
Date: Mon, 9 Dec 2013 10:57:39 +0100 [thread overview]
Message-ID: <1386583059-22281-1-git-send-email-nicolas.ferre@atmel.com> (raw)
Arnd, Olof, Kevin,
This pull-request is for addition of sama5d36 and its Evaluation Kit. The
patches are stacked on the "cleanup" material already in arm-soc tree
(at91/sama5-ccf) like all other AT91 pull-requests for 3.14.
Thanks, best regards,
The following changes since commit b46e837d8ef1f3c777bbf9513e2cdb5d87d6c374:
ARM: at91/dt: remove old clk material (2013-12-02 15:31:29 +0100)
are available in the git repository at:
git://github.com/at91linux/linux-at91.git tags/at91-soc
for you to fetch changes up to 0a72922b8dab2a1ce9cc977e9b1850556b48b4aa:
ARM: at91: sama5d3/dt: add sama5d36ek dts files (2013-12-09 09:50:53 +0100)
----------------------------------------------------------------
First soc pull-request for 3.14
Addition of the sama5d36 SoC as a member of the sama5d3 family
- SoC code and Device Tree file
- Evaluation Kit (EK board) Device Tree file
----------------------------------------------------------------
Josh Wu (2):
ARM: at91: sama5d3: add support for sama5d36 chip
ARM: at91: sama5d3/dt: add sama5d36ek dts files
arch/arm/boot/dts/Makefile | 2 ++
arch/arm/boot/dts/sama5d3.dtsi | 2 +-
arch/arm/boot/dts/sama5d36.dtsi | 20 +++++++++++++
arch/arm/boot/dts/sama5d36ek.dts | 53 +++++++++++++++++++++++++++++++++++
arch/arm/mach-at91/Kconfig | 2 +-
arch/arm/mach-at91/include/mach/cpu.h | 3 +-
arch/arm/mach-at91/setup.c | 4 +++
7 files changed, 83 insertions(+), 3 deletions(-)
create mode 100644 arch/arm/boot/dts/sama5d36.dtsi
create mode 100644 arch/arm/boot/dts/sama5d36ek.dts
--
Nicolas Ferre
next reply other threads:[~2013-12-09 9:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-09 9:57 Nicolas Ferre [this message]
2013-12-10 19:34 ` [GIT PULL] at91: soc updates for 3.14 #1 Kevin Hilman
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=1386583059-22281-1-git-send-email-nicolas.ferre@atmel.com \
--to=nicolas.ferre@atmel.com \
--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).