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/5] i.MX drivers change for 5.9
Date: Mon, 20 Jul 2020 16:55:32 +0800 [thread overview]
Message-ID: <20200720085536.24138-1-shawnguo@kernel.org> (raw)
The following changes since commit b3a9e3b9622ae10064826dccb4f7a52bd88c7407:
Linux 5.8-rc1 (2020-06-14 12:45:04 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/shawnguo/linux.git tags/imx-drivers-5.9
for you to fetch changes up to d82bcef5157de1368c08244a846ab968b3e5cb7e:
soc: imx: select ARM_GIC_V3 for i.MX8M (2020-07-13 16:42:32 +0800)
----------------------------------------------------------------
i.MX drivers change for 5.9:
- Update SCU irq code to call pm_system_wakeup() in general MU IRQ
handler, so that system can be waked up when MU IRQ arrives.
- Move i.MX SCU soc driver into imx firmware folder to get it
initialized from i.MX SCU firmware driver.
- Clean up soc-imx-scu driver a bit by using devm_kasprintf().
- Correct postfix setting for cm40 power domain in scu-pd driver.
- Add resource management support for IMX_SCU firmware driver.
- Add more cm4 resources to i.MX SCU power domain driver.
- Select ARM_GIC_V3 from SOC_IMX8M for being able to use GICv3 driver
in AARCH32 mode Linux on AARCH64 hardware.
----------------------------------------------------------------
Anson Huang (2):
firmware: imx: make sure MU irq can wake up system from suspend mode
firmware: imx: Move i.MX SCU soc driver into imx firmware folder
Peng Fan (5):
soc: imx: scu: use devm_kasprintf
firmware: imx: scu-pd: fix cm40 power domain
firmware: imx: add resource management api
firmware: imx: scu-pd: add more cm4 resources
soc: imx: select ARM_GIC_V3 for i.MX8M
arch/arm64/configs/defconfig | 1 -
drivers/firmware/imx/Makefile | 2 +-
drivers/firmware/imx/imx-scu-irq.c | 2 +
.../soc-imx-scu.c => firmware/imx/imx-scu-soc.c} | 83 +++++-----------------
drivers/firmware/imx/imx-scu.c | 4 ++
drivers/firmware/imx/rm.c | 45 ++++++++++++
drivers/firmware/imx/scu-pd.c | 14 +++-
drivers/soc/imx/Kconfig | 10 +--
drivers/soc/imx/Makefile | 1 -
include/linux/firmware/imx/sci.h | 2 +
include/linux/firmware/imx/svc/rm.h | 69 ++++++++++++++++++
11 files changed, 153 insertions(+), 80 deletions(-)
rename drivers/{soc/imx/soc-imx-scu.c => firmware/imx/imx-scu-soc.c} (57%)
create mode 100644 drivers/firmware/imx/rm.c
create mode 100644 include/linux/firmware/imx/svc/rm.h
_______________________________________________
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-07-20 8:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-20 8:55 Shawn Guo [this message]
2020-07-20 8:55 ` [GIT PULL 2/5] i.MX DT bindings for 5.9 Shawn Guo
2020-07-20 8:55 ` [GIT PULL 3/5] i.MX device tree update " Shawn Guo
2020-07-20 8:55 ` [GIT PULL 4/5] i.MX arm64 " Shawn Guo
2020-07-20 8:55 ` [GIT PULL 5/5] i.MX defconfig " 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=20200720085536.24138-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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.