From: Joel Stanley <joel@jms.id.au>
To: Arnd Bergmann <arnd@arndb.de>, Olof Johansson <olof@lixom.net>,
arm <arm@kernel.org>
Cc: linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] ARM: aspeed: devicetree for 4.11
Date: Wed, 18 Jan 2017 09:50:02 +1100 [thread overview]
Message-ID: <CACPK8XffqYCRipx+KzxyH0z-5=t53ezPjRv+MxOj7-tj2kbG2A@mail.gmail.com> (raw)
Hello Arnd and Olof,
Please pull the Aspeed devicetree ...tree for 4.11.
The following changes since commit 7ce7d89f48834cefece7804d38fc5d85382edf77:
Linux 4.10-rc1 (2016-12-25 16:13:08 -0800)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/joel/aspeed.git
tags/aspeed-4.11-devicetree
for you to fetch changes up to 8f9bafbb92c0308cf8d33536803c822e14bed4d7:
ARM: dts: aspeed: Add Romulus BMC platform (2017-01-10 21:55:46 +1100)
----------------------------------------------------------------
Aspeed devicetree updates for 4.11
This introduces the first OpenPower Power9 BMC system, Romulus. Romulus is
based on the ast2500 SoC from Aspeed.
These commits also add newly upstreamed drivers to the Palmetto BMC and ast2500
eval board. We now have working network, ipmi bt, gpio and pinmux on
all platforms.
ARM: dts: aspeed: Add Romulus BMC platform
ARM: dts: aspeed: Add ftgmac100 to g4 and g5 platforms
ARM: dts: aspeed: Correct palmetto device tree
ARM: dts: aspeed: Reserve framebuffer memory
ARM: dts: aspeed-g5: Add gpio controller to devicetree
ARM: dts: aspeed-g5: Add syscon and pin controller nodes
ARM: dts: aspeed-g5: Add LPC Controller node
ARM: dts: aspeed-g5: Add SoC Display Controller node
ARM: dts: aspeed-g4: Add gpio controller to devicetree
ARM: dts: aspeed-g4: Add syscon and pin controller nodes
----------------------------------------------------------------
Andrew Jeffery (6):
ARM: dts: aspeed-g4: Add syscon and pin controller nodes
ARM: dts: aspeed-g4: Add gpio controller to devicetree
ARM: dts: aspeed-g5: Add SoC Display Controller node
ARM: dts: aspeed-g5: Add LPC Controller node
ARM: dts: aspeed-g5: Add syscon and pin controller nodes
ARM: dts: aspeed-g5: Add gpio controller to devicetree
Cyril Bur (2):
ARM: dts: aspeed: Reserve framebuffer memory
ARM: dts: aspeed: Correct palmetto device tree
Joel Stanley (2):
ARM: dts: aspeed: Add ftgmac100 to g4 and g5 platforms
ARM: dts: aspeed: Add Romulus BMC platform
arch/arm/boot/dts/Makefile | 1 +
arch/arm/boot/dts/aspeed-ast2500-evb.dts | 14 +
arch/arm/boot/dts/aspeed-bmc-opp-palmetto.dts | 24 +-
arch/arm/boot/dts/aspeed-bmc-opp-romulus.dts | 45 ++
arch/arm/boot/dts/aspeed-g4.dtsi | 776 +++++++++++++++++++++++
arch/arm/boot/dts/aspeed-g5.dtsi | 879 ++++++++++++++++++++++++++
6 files changed, 1737 insertions(+), 2 deletions(-)
create mode 100644 arch/arm/boot/dts/aspeed-bmc-opp-romulus.dts
next reply other threads:[~2017-01-17 22:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-17 22:50 Joel Stanley [this message]
2017-01-19 0:27 ` [GIT PULL] ARM: aspeed: devicetree for 4.11 Olof Johansson
2017-01-19 2:59 ` Joel Stanley
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='CACPK8XffqYCRipx+KzxyH0z-5=t53ezPjRv+MxOj7-tj2kbG2A@mail.gmail.com' \
--to=joel@jms.id.au \
--cc=arm@kernel.org \
--cc=arnd@arndb.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=olof@lixom.net \
/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).