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 1/6] i.MX drivers update for 5.7
Date: Wed, 18 Mar 2020 13:19:13 +0800 [thread overview]
Message-ID: <20200318051918.32579-1-shawnguo@kernel.org> (raw)
The following changes since commit bb6d3fb354c5ee8d6bde2d576eb7220ea09862b9:
Linux 5.6-rc1 (2020-02-09 16:08:48 -0800)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/shawnguo/linux.git tags/imx-drivers-5.7
for you to fetch changes up to 2a52651292ad9e642d205ce2ece2686d3b3395a7:
soc: imx: drop COMPILE_TEST for IMX_SCU_SOC (2020-03-16 11:44:40 +0800)
----------------------------------------------------------------
i.MX drivers update for 5.7:
- Update SCU power domain driver to include PD ranges for audio, CM40
I2C and INTMUX, also enlarge PD range for mu_b.
- Remove IMX_SC_RPC_SVC_ABORT from SCU API, as it was added by mistake.
- Increase build test coverage for i.MX8M SoC and IMX_SCU driver.
- Improve i.MX GPC power up sequencing to ensure that the reset is
properly propagated through the peripheral devices in the power
domain.
----------------------------------------------------------------
Anson Huang (1):
firmware: imx: add COMPILE_TEST for IMX_SCU driver
Daniel Baluta (1):
firmware: imx: scu-pd: Add missing audio PD ranges
Joakim Zhang (1):
firmware: imx: scu-pd: add power domain for I2C and INTMUX in CM40 SS
Leonard Crestez (2):
soc: imx: gpcv2: include linux/sizes.h
firmware: imx: Remove IMX_SC_RPC_SVC_ABORT
Lucas Stach (1):
soc: imx: gpc: fix power up sequencing
Peng Fan (2):
soc: imx: increase build coverage for imx8m soc driver
soc: imx: drop COMPILE_TEST for IMX_SCU_SOC
Sebastien Fagard (1):
firmware: imx: scu-pd: enlarge PD range for mu_b
drivers/firmware/imx/Kconfig | 2 +-
drivers/firmware/imx/scu-pd.c | 13 ++++++++++++-
drivers/soc/Makefile | 2 +-
drivers/soc/imx/Kconfig | 11 ++++++++++-
drivers/soc/imx/Makefile | 2 +-
drivers/soc/imx/gpc.c | 24 +++++++++++++-----------
drivers/soc/imx/gpcv2.c | 1 +
drivers/soc/imx/{soc-imx8.c => soc-imx8m.c} | 0
include/linux/firmware/imx/ipc.h | 1 -
9 files changed, 39 insertions(+), 17 deletions(-)
rename drivers/soc/imx/{soc-imx8.c => soc-imx8m.c} (100%)
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next reply other threads:[~2020-03-18 5:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-18 5:19 Shawn Guo [this message]
2020-03-18 5:19 ` [GIT PULL 2/6] i.MX SoC changes for 5.7 Shawn Guo
2020-03-18 5:19 ` [GIT PULL 3/6] i.MX DT bindings update " Shawn Guo
2020-03-18 5:19 ` [GIT PULL 4/6] i.MX arm DTS changes " Shawn Guo
2020-03-18 5:19 ` [GIT PULL 5/6] i.MX arm64 DTS update " Shawn Guo
2020-03-18 5:19 ` [GIT PULL 6/6] i.MX defconfig changes " 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=20200318051918.32579-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).