From: Shawn Guo <shawnguo@kernel.org>
To: soc@kernel.org, arm@kernel.org
Cc: Shawn Guo <shawnguo@kernel.org>,
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 2/4] i.MX drivers change for 6.1
Date: Sun, 18 Sep 2022 17:28:04 +0800 [thread overview]
Message-ID: <20220918092806.2152700-2-shawnguo@kernel.org> (raw)
In-Reply-To: <20220918092806.2152700-1-shawnguo@kernel.org>
Hi,
This is the i.MX drivers changeset for 6.1. It's built on top of
imx/bindings branch (tag imx-bindings-6.1) to resolve the dependency
on DT bindings header. Please consider to pull, thanks!
Shawn
The following changes since commit 64e61a940d96184d294f431848a28765f44525fa:
dt-bindings: arm: imx: update fsl.yaml for imx8dxl (2022-09-17 16:25:50 +0800)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/shawnguo/linux.git tags/imx-drivers-6.1
for you to fetch changes up to e9aa77d413c903ba4cf7da3fe0b419cae5b97a81:
soc: imx: add i.MX93 media blk ctrl driver (2022-09-17 16:31:06 +0800)
----------------------------------------------------------------
i.MX drivers change for 6.1:
- Update i.MX8MP blk-ctrl driver to handle PCIe PHY reset bit.
- Add interconnect support into i.MX8MP blk-ctrl driver, so that i.MX8MP
NoC can be set up properly after related power domain is up.
- Add blk-ctrl support for i.MX8MP HDMI HDCP/HRV and VPU block.
- Add i.MX93 SRC power domain and MEDIA blk-ctrl driver.
- Update imx8m-blk-ctrl driver to use genpd_xlate_onecell.
----------------------------------------------------------------
Lucas Stach (1):
soc: imx: imx8mp-blk-ctrl: handle PCIe PHY resets
Peng Fan (7):
soc: imx: add icc paths for i.MX8MP media blk ctrl
soc: imx: add icc paths for i.MX8MP hsio/hdmi blk ctrl
soc: imx: add i.MX8MP HDMI blk ctrl HDCP/HRV_MWR
soc: imx: imx8m-blk-ctrl: add i.MX8MP VPU blk ctrl
soc: imx: imx8m-blk-ctrl: Use genpd_xlate_onecell
soc: imx: add i.MX93 SRC power domain driver
soc: imx: add i.MX93 media blk ctrl driver
drivers/soc/imx/Kconfig | 8 +
drivers/soc/imx/Makefile | 2 +
drivers/soc/imx/imx8m-blk-ctrl.c | 96 +++++++--
drivers/soc/imx/imx8mp-blk-ctrl.c | 89 ++++++--
drivers/soc/imx/imx93-blk-ctrl.c | 436 ++++++++++++++++++++++++++++++++++++++
drivers/soc/imx/imx93-pd.c | 164 ++++++++++++++
drivers/soc/imx/imx93-src.c | 33 +++
7 files changed, 800 insertions(+), 28 deletions(-)
create mode 100644 drivers/soc/imx/imx93-blk-ctrl.c
create mode 100644 drivers/soc/imx/imx93-pd.c
create mode 100644 drivers/soc/imx/imx93-src.c
next prev parent reply other threads:[~2022-09-18 9:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-18 9:28 [GIT PULL 1/4] i.MX DT bindings update for 6.1 Shawn Guo
2022-09-18 9:28 ` Shawn Guo [this message]
2022-09-18 9:28 ` [GIT PULL 3/4] i.MX device tree change " Shawn Guo
2022-09-18 9:28 ` [GIT PULL 4/4] i.MX arm64 device tree update " Shawn Guo
2022-09-23 14:52 ` [GIT PULL 1/4] i.MX DT bindings " patchwork-bot+linux-soc
2022-09-23 16:20 ` patchwork-bot+linux-soc
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=20220918092806.2152700-2-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).