From: Shawn Guo <shawnguo@kernel.org>
To: soc@kernel.org, arm@kernel.org
Cc: Shawn Guo <shawnguo@kernel.org>, Stefan Agner <stefan@agner.ch>,
Li Yang <leoyang.li@nxp.com>,
linux-imx@nxp.com, kernel@pengutronix.de,
Fabio Estevam <festevam@gmail.com>,
linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL 4/6] i.MX device tree changes for 5.8
Date: Sat, 23 May 2020 11:25:14 +0800 [thread overview]
Message-ID: <20200523032516.11016-4-shawnguo@kernel.org> (raw)
In-Reply-To: <20200523032516.11016-1-shawnguo@kernel.org>
The following changes since commit 8f3d9f354286745c751374f5f1fcafee6b3f3136:
Linux 5.7-rc1 (2020-04-12 12:35:55 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/shawnguo/linux.git tags/imx-dt-5.8
for you to fetch changes up to 103515d91832bb837159c37f0cb69d59d68a1dc2:
ARM: dts: imx53-cx9020: Group port definitions for the dvi-converter (2020-05-20 10:57:14 +0800)
----------------------------------------------------------------
i.MX device tree changes for 5.8:
- A series from Anson Huang updating SRC devices to match bindings
schema definition.
- Correct CPU supply name and add cpu1 supply for i.MX7D.
- Convert thermal device to use nvmem interface to get fuse data
for imx6qdl and imx6sl.
- A series from Tim Harvey to update imx6qdl-gw devices, adding support
of LSM9DS1 IIO imu/magn, USB OTG, bcm4330-bt, etc.
- Add input MUX for ENET2 MDIO into IMX7D pin functions.
- Misc random device addition or update.
----------------------------------------------------------------
Andreas Kemnade (1):
ARM: dts: e60k02: add interrupt for PMIC
Anson Huang (9):
ARM: dts: imx7: Correct CPU supply name
ARM: dts: imx7d: Add cpu1 supply
ARM: dts: imx51: Add src node interrupt
ARM: dts: imx53: Add src node interrupt
ARM: dts: imx6qdl: Use nvmem interface to get fuse data
ARM: dts: imx6sl: Use nvmem interface to get fuse data
ARM: dts: imx: make src node name generic
ARM: dts: imx50: Add src node interrupt
ARM: dts: imx5: make src node name generic
Fabio Estevam (1):
ARM: dts: imx50: Remove unused iomuxc-gpr node
Igor Opaniuk (1):
ARM: dts: colibri: introduce device trees with UHS-I support
Kuldeep Singh (1):
arm: dts: ls1021atwr: Add QSPI node properties
Marek Vasut (1):
ARM: dts: imx6q-dhcom: Add DH 560-200 display unit support
Ricardo Cañuelo (1):
ARM: dts: imx53-cx9020: Group port definitions for the dvi-converter
Russell King (1):
ARM: dts: imx6-sr-som: add ethernet PHY configuration
Steffen Trumtrar (1):
ARM: dts: imx7d-pinfunc: add input mux for ENET2 mdio
Tim Harvey (5):
ARM: dts: imx6qdl-gw552x: add USB OTG support
ARM: dts: imx6qdl-gw560x: add lsm9ds1 iio imu/magn support
ARM: dts: imx6qdl-gw5904: add lsm9ds1 iio imu/magn support
ARM: dts: imx6qdl-gw5910: add support for bcm4330-bt
ARM: dts: imx6qdl-gw5910: fix wlan regulator
arch/arm/boot/dts/Makefile | 1 +
arch/arm/boot/dts/e60k02.dtsi | 2 +
arch/arm/boot/dts/imx50.dtsi | 8 +-
arch/arm/boot/dts/imx51.dtsi | 3 +-
arch/arm/boot/dts/imx53-cx9020.dts | 25 ++---
arch/arm/boot/dts/imx53.dtsi | 3 +-
arch/arm/boot/dts/imx6dl-colibri-v1_1-eval-v3.dts | 31 ++++++
arch/arm/boot/dts/imx6q-dhcom-pdk2.dts | 115 +++++++++++++++++++++-
arch/arm/boot/dts/imx6qdl-colibri-v1_1-uhs.dtsi | 44 +++++++++
arch/arm/boot/dts/imx6qdl-colibri.dtsi | 11 ++-
arch/arm/boot/dts/imx6qdl-gw552x.dtsi | 14 +++
arch/arm/boot/dts/imx6qdl-gw560x.dtsi | 31 ++++++
arch/arm/boot/dts/imx6qdl-gw5904.dtsi | 31 ++++++
arch/arm/boot/dts/imx6qdl-gw5910.dtsi | 35 +++----
arch/arm/boot/dts/imx6qdl-sr-som.dtsi | 11 +++
arch/arm/boot/dts/imx6qdl.dtsi | 13 ++-
arch/arm/boot/dts/imx6sl.dtsi | 13 ++-
arch/arm/boot/dts/imx6sx.dtsi | 2 +-
arch/arm/boot/dts/imx6ul.dtsi | 2 +-
arch/arm/boot/dts/imx7-tqma7.dtsi | 2 +-
arch/arm/boot/dts/imx7d-cl-som-imx7.dts | 4 +
arch/arm/boot/dts/imx7d-colibri.dtsi | 4 +
arch/arm/boot/dts/imx7d-nitrogen7.dts | 4 +
arch/arm/boot/dts/imx7d-pinfunc.h | 2 +-
arch/arm/boot/dts/imx7d-sdb.dts | 4 +
arch/arm/boot/dts/imx7d-tqma7.dtsi | 4 +
arch/arm/boot/dts/imx7d-zii-rmu2.dts | 2 +-
arch/arm/boot/dts/imx7d-zii-rpu2.dts | 2 +-
arch/arm/boot/dts/imx7s.dtsi | 2 +-
arch/arm/boot/dts/ls1021a-twr.dts | 14 +++
30 files changed, 384 insertions(+), 55 deletions(-)
create mode 100644 arch/arm/boot/dts/imx6dl-colibri-v1_1-eval-v3.dts
create mode 100644 arch/arm/boot/dts/imx6qdl-colibri-v1_1-uhs.dtsi
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2020-05-23 3:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-23 3:25 [GIT PULL 1/6] i.MX drivers update for 5.8 Shawn Guo
2020-05-23 3:25 ` [GIT PULL 2/6] i.MX SoC changes " Shawn Guo
2020-05-23 3:25 ` [GIT PULL 3/6] i.MX bindings change " Shawn Guo
2020-05-23 3:25 ` Shawn Guo [this message]
2020-05-23 3:25 ` [GIT PULL 5/6] i.MX arm64 device tree changes " Shawn Guo
2020-05-23 3:25 ` [GIT PULL 6/6] i.MX defconfig update " Shawn Guo
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=20200523032516.11016-4-shawnguo@kernel.org \
--to=shawnguo@kernel.org \
--cc=arm@kernel.org \
--cc=festevam@gmail.com \
--cc=kernel@pengutronix.de \
--cc=leoyang.li@nxp.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=soc@kernel.org \
--cc=stefan@agner.ch \
/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).