From: Gregory CLEMENT <gregory.clement@bootlin.com>
To: Arnd Bergmann <arnd@arndb.de>, Olof Johansson <olof@lixom.net>,
<arm@kernel.org>,
soc@kernel.org
Cc: Andrew Lunn <andrew@lunn.ch>, Jason Cooper <jason@lakedaemon.net>,
linux-arm-kernel@lists.infradead.org,
Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>
Subject: [GIT PULL v2] ARM: mvebu: dt for v5.10 (#1)
Date: Mon, 05 Oct 2020 15:01:25 +0200 [thread overview]
Message-ID: <87v9foesii.fsf@BL-laptop> (raw)
Hi,
Here is the second try of the first pull request for dt for mvebu for v5.10.
Gregory
The following changes since commit 9123e3a74ec7b934a4a099e98af6a61c2f80bbf5:
Linux 5.9-rc1 (2020-08-16 13:04:57 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/gclement/mvebu.git tags/mvebu-dt-5.10-1
for you to fetch changes up to e4af6e19d05dbe93595440d5bb9136b47fd9f8cc:
ARM: dts: Add i2c0 pinctrl information for 98dx3236 (2020-09-24 10:25:17 +0200)
----------------------------------------------------------------
mvebu dt for 5.10 (part 1)
- Add support for MikroTik CRS3xx switches
- Clean-up kirkwood device tree: replace "ok" by "okay"
- Improve device tree for PCA953x gpio expander nodes
- 98dx3236 SoCs:
- remove non-existent i2c1
- add i2c0 pinctrl information
----------------------------------------------------------------
Adrian Schmutzler (1):
ARM: dts: kirkwood: replace status value "ok" by "okay"
Chris Packham (2):
ARM: dts: Remove non-existent i2c1 from 98dx3236
ARM: dts: Add i2c0 pinctrl information for 98dx3236
Krzysztof Kozlowski (2):
ARM: dts: dove: fix PCA95xx GPIO expander properties on A510
ARM: dts: armada: align GPIO hog names with dtschema
Luka Kovacic (3):
ARM: dts: mvebu: Add CRS326-24G-2S board
ARM: dts: mvebu: Add CRS305-1G-4S board
ARM: dts: mvebu: Add CRS328-4C-20S-4S board
arch/arm/boot/dts/Makefile | 6 ++
arch/arm/boot/dts/armada-388-clearfog.dts | 4 +-
arch/arm/boot/dts/armada-388-clearfog.dtsi | 10 +-
arch/arm/boot/dts/armada-388-helios4.dts | 6 +-
arch/arm/boot/dts/armada-xp-98dx3236.dtsi | 12 ++-
arch/arm/boot/dts/armada-xp-crs305-1g-4s-bit.dts | 43 +++++++++
arch/arm/boot/dts/armada-xp-crs305-1g-4s.dts | 17 ++++
arch/arm/boot/dts/armada-xp-crs305-1g-4s.dtsi | 104 +++++++++++++++++++++
arch/arm/boot/dts/armada-xp-crs326-24g-2s-bit.dts | 43 +++++++++
arch/arm/boot/dts/armada-xp-crs326-24g-2s.dts | 17 ++++
arch/arm/boot/dts/armada-xp-crs326-24g-2s.dtsi | 104 +++++++++++++++++++++
.../boot/dts/armada-xp-crs328-4c-20s-4s-bit.dts | 43 +++++++++
arch/arm/boot/dts/armada-xp-crs328-4c-20s-4s.dts | 17 ++++
arch/arm/boot/dts/armada-xp-crs328-4c-20s-4s.dtsi | 104 +++++++++++++++++++++
arch/arm/boot/dts/dove-sbc-a510.dts | 1 +
arch/arm/boot/dts/kirkwood-dockstar.dts | 2 +-
arch/arm/boot/dts/kirkwood-dreamplug.dts | 2 +-
arch/arm/boot/dts/kirkwood-goflexnet.dts | 2 +-
.../arm/boot/dts/kirkwood-guruplug-server-plus.dts | 2 +-
arch/arm/boot/dts/kirkwood-iconnect.dts | 2 +-
arch/arm/boot/dts/kirkwood-iomega_ix2_200.dts | 2 +-
arch/arm/boot/dts/kirkwood-nsa3x0-common.dtsi | 2 +-
arch/arm/boot/dts/kirkwood.dtsi | 4 +-
23 files changed, 525 insertions(+), 24 deletions(-)
create mode 100644 arch/arm/boot/dts/armada-xp-crs305-1g-4s-bit.dts
create mode 100644 arch/arm/boot/dts/armada-xp-crs305-1g-4s.dts
create mode 100644 arch/arm/boot/dts/armada-xp-crs305-1g-4s.dtsi
create mode 100644 arch/arm/boot/dts/armada-xp-crs326-24g-2s-bit.dts
create mode 100644 arch/arm/boot/dts/armada-xp-crs326-24g-2s.dts
create mode 100644 arch/arm/boot/dts/armada-xp-crs326-24g-2s.dtsi
create mode 100644 arch/arm/boot/dts/armada-xp-crs328-4c-20s-4s-bit.dts
create mode 100644 arch/arm/boot/dts/armada-xp-crs328-4c-20s-4s.dts
create mode 100644 arch/arm/boot/dts/armada-xp-crs328-4c-20s-4s.dtsi
--
Gregory Clement, Bootlin
Embedded Linux and Kernel engineering
http://bootlin.com
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
reply other threads:[~2020-10-05 13:03 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=87v9foesii.fsf@BL-laptop \
--to=gregory.clement@bootlin.com \
--cc=andrew@lunn.ch \
--cc=arm@kernel.org \
--cc=arnd@arndb.de \
--cc=jason@lakedaemon.net \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=olof@lixom.net \
--cc=sebastian.hesselbarth@gmail.com \
--cc=soc@kernel.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