From: Shawn Guo <shawnguo@kernel.org>
To: soc@kernel.org, arm@kernel.org
Cc: Fabio Estevam <festevam@gmail.com>,
Stefan Agner <stefan@agner.ch>, Li Yang <leoyang.li@nxp.com>,
kernel@pengutronix.de, linux-imx@nxp.com,
linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] i.MX fixes for 5.19, round 2
Date: Wed, 29 Jun 2022 10:12:44 +0800 [thread overview]
Message-ID: <20220629021244.GL819983@dragon> (raw)
The following changes since commit 7c7eaeefb0ae226da9233d5db265652d900e1fcb:
soc: imx: imx8m-blk-ctrl: fix display clock for LCDIF2 power domain (2022-06-14 11:53:42 +0800)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/shawnguo/linux.git tags/imx-fixes-5.19-2
for you to fetch changes up to 8630354f42bef90f51e003a7ce62b69aceb735ca:
arm64: dts: imx8mp-icore-mx8mp-edim2.2: correct pad settings (2022-06-27 15:55:41 +0800)
----------------------------------------------------------------
i.MX fixes for 5.19, round 2:
- Fix the SDIO description for imx7d-smegw01 board to ensure there is
no communication made at 1.8V.
- Fix pgc_ispdwp power-domain clock, which should be
IMX8MP_CLK_MEDIA_ISP_ROOT.
- Re-enable framebuffer support in mxs_defconfig to fix a Kconfig
regression.
- A series from Peng Fan (and Sherry Sun) fixing various pads on i.MX8MP
based boards to leave reserved bits untouched.
----------------------------------------------------------------
Fabio Estevam (2):
ARM: dts: imx7d-smegw01: Fix the SDIO description
ARM: mxs_defconfig: Enable the framebuffer
Peng Fan (14):
arm64: dts: imx8mp: correct clock of pgc_ispdwp
arm64: dts: imx8mp-evk: correct mmc pad settings
arm64: dts: imx8mp-evk: correct gpio-led pad settings
arm64: dts: imx8mp-evk: correct vbus pad settings
arm64: dts: imx8mp-evk: correct eqos pad settings
arm64: dts: imx8mp-evk: correct vbus pad settings
arm64: dts: imx8mp-evk: correct I2C5 pad settings
arm64: dts: imx8mp-evk: correct I2C1 pad settings
arm64: dts: imx8mp-evk: correct I2C3 pad settings
arm64: dts: imx8mp-venice-gw74xx: correct pad settings
arm64: dts: imx8mp-phyboard-pollux-rdk: correct uart pad settings
arm64: dts: imx8mp-phyboard-pollux-rdk: correct eqos pad settings
arm64: dts: imx8mp-phyboard-pollux-rdk: correct i2c2 & mmc settings
arm64: dts: imx8mp-icore-mx8mp-edim2.2: correct pad settings
Sherry Sun (1):
arm64: dts: imx8mp-evk: correct the uart2 pinctl value
arch/arm/boot/dts/imx7d-smegw01.dts | 4 +-
arch/arm/configs/mxs_defconfig | 1 +
arch/arm64/boot/dts/freescale/imx8mp-evk.dts | 88 ++++++++--------
.../dts/freescale/imx8mp-icore-mx8mp-edimm2.2.dts | 40 +++----
.../dts/freescale/imx8mp-phyboard-pollux-rdk.dts | 48 ++++-----
.../boot/dts/freescale/imx8mp-venice-gw74xx.dts | 116 ++++++++++-----------
arch/arm64/boot/dts/freescale/imx8mp.dtsi | 2 +-
7 files changed, 149 insertions(+), 150 deletions(-)
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
reply other threads:[~2022-06-29 2:13 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=20220629021244.GL819983@dragon \
--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).