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 1/6] i.MX drivers update for 6.4
Date: Sat, 8 Apr 2023 18:19:23 +0800 [thread overview]
Message-ID: <20230408101928.280271-1-shawnguo@kernel.org> (raw)
The following changes since commit fe15c26ee26efa11741a7b632e9f23b01aca4cc6:
Linux 6.3-rc1 (2023-03-05 14:52:03 -0800)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/shawnguo/linux.git tags/imx-drivers-6.4
for you to fetch changes up to 816aec03a043af6d0234c3e770bead2c772ef4eb:
soc: imx: imx8m-blk-ctrl: reordering the fields (2023-03-27 09:52:41 +0800)
----------------------------------------------------------------
i.MX drivers update for 6.4:
- Use dev_err_probe() for imx-scu driver to silences EPROBE_DEFER
messages.
- Add LVDS LPI2C and PWM power domains for scu-pd driver.
- A series from Jindong Yue to support module build of imx8m soc driver.
- Update imx8m-blk-ctrl driver to scan child nodes for binding drivers.
- Reorder structure members in imx8m-blk-ctrl driver by following
clang-analyzer suggestion.
- Update imx-weim bus driver to use helper function for "ranges"
parsing.
----------------------------------------------------------------
Alexander Stein (1):
firmware: imx: scu: use dev_err_probe
Clark Wang (1):
firmware: imx: scu-pd: add missed lvds lpi2c and pwm power domains
Jindong Yue (7):
soc: imx: imx8mp-blk-ctrl: Use dev_pm_domain_attach_by_name
soc: imx: imx8mp-blk-ctrl: Fix typo of imx8m_blk_ctrl_of_match
soc: imx: imx8mp-blk-ctrl: Add MODULE_LICENSE
soc: imx: imx8m-blk-ctrl: Use dev_pm_domain_attach_by_name
soc: imx: imx8m-blk-ctrl: Add MODULE_LICENSE
soc: imx8m: Add MODULE_LICENSE
soc: imx8m: Support building imx8m soc driver as module
Marek Vasut (1):
soc: imx: imx8m-blk-ctrl: Scan subnodes and bind drivers to them
Peng Fan (1):
soc: imx: imx8m-blk-ctrl: reordering the fields
Rob Herring (1):
bus: imx-weim: Remove open coded "ranges" parsing
drivers/bus/imx-weim.c | 19 ++++++++++---------
drivers/firmware/imx/imx-scu.c | 5 ++---
drivers/firmware/imx/scu-pd.c | 4 ++++
drivers/soc/imx/Kconfig | 2 +-
drivers/soc/imx/imx8m-blk-ctrl.c | 11 ++++++++---
drivers/soc/imx/imx8mp-blk-ctrl.c | 5 +++--
drivers/soc/imx/soc-imx8m.c | 1 +
7 files changed, 29 insertions(+), 18 deletions(-)
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next reply other threads:[~2023-04-08 10:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-08 10:19 Shawn Guo [this message]
2023-04-08 10:19 ` [GIT PULL 2/6] i.MX SoC changes for 6.4 Shawn Guo
2023-04-08 10:19 ` [GIT PULL 3/6] i.MX dt-bindings update " Shawn Guo
2023-04-12 1:46 ` Shawn Guo
2023-04-08 10:19 ` [GIT PULL 4/6] i.MX arm32 device tree changes " Shawn Guo
2023-04-08 10:19 ` [GIT PULL 5/6] i.MX arm64 " Shawn Guo
2023-04-08 10:19 ` [GIT PULL 6/6] i.MX defconfig updates " 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=20230408101928.280271-1-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).