From: Shawn Guo <shawnguo@kernel.org>
To: arm@kernel.org
Cc: linux-arm-kernel@lists.infradead.org,
Shawn Guo <shawnguo@kernel.org>,
Fabio Estevam <festevam@gmail.com>,
linux-imx@nxp.com, kernel@pengutronix.de
Subject: [GIT PULL 2/7] i.MX SoC changes for 5.1
Date: Tue, 12 Feb 2019 19:21:21 +0800 [thread overview]
Message-ID: <20190212112126.572-2-shawnguo@kernel.org> (raw)
In-Reply-To: <20190212112126.572-1-shawnguo@kernel.org>
The following changes since commit bfeffd155283772bbe78c6a05dec7c0128ee500c:
Linux 5.0-rc1 (2019-01-06 17:08:20 -0800)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/shawnguo/linux.git tags/imx-soc-5.1
for you to fetch changes up to 84a2ab25b12d69914c96dd12e762f7ff912f9735:
arm64: imx8mq: select PM support (2019-02-01 15:04:32 +0800)
----------------------------------------------------------------
i.MX SoC changes for 5.1:
- Support cpuidle for i.MX7ULP, states WFI, WAIT and STOP get added.
- Support SoC revision detecting for i.MX7ULP by reading JTAG_ID
register from SIM module.
- Select PM and GPCv2 irqchip driver options for i.MX8 support, as they
are essential for building an i.MX8 based system.
- Skip build of ssi-fiq code if SND_SOC_IMX_PCM_FIQ is not enabled.
----------------------------------------------------------------
Anson Huang (2):
ARM: imx: add i.MX7ULP cpuidle support
ARM: imx: add i.MX7ULP SoC revision support
Lucas Stach (2):
arm64: imx8mq: select GPCv2 irqchip driver
arm64: imx8mq: select PM support
Stefan Agner (1):
ARM: imx: don't build ssi-fiq if not required
arch/arm/mach-imx/Makefile | 3 +-
arch/arm/mach-imx/common.h | 10 +++++++
arch/arm/mach-imx/cpuidle-imx7ulp.c | 60 +++++++++++++++++++++++++++++++++++++
arch/arm/mach-imx/cpuidle.h | 5 ++++
arch/arm/mach-imx/mach-imx7ulp.c | 46 ++++++++++++++++++++++++++++
arch/arm/mach-imx/pm-imx7ulp.c | 49 ++++++++++++++++++++++++++----
arch/arm64/Kconfig.platforms | 4 +++
7 files changed, 171 insertions(+), 6 deletions(-)
create mode 100644 arch/arm/mach-imx/cpuidle-imx7ulp.c
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2019-02-12 11:22 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-12 11:21 [GIT PULL 1/7] i.MX drivers update for 5.1 Shawn Guo
2019-02-12 11:21 ` Shawn Guo [this message]
2019-02-15 16:40 ` [GIT PULL 2/7] i.MX SoC changes " Arnd Bergmann
2019-02-12 11:21 ` [GIT PULL 3/7] i.MX DT bindings update " Shawn Guo
2019-02-15 15:08 ` Arnd Bergmann
2019-02-18 1:16 ` Shawn Guo
2019-02-12 11:21 ` [GIT PULL 4/7] i.MX device tree changes " Shawn Guo
2019-02-15 15:10 ` Arnd Bergmann
2019-02-12 11:21 ` [GIT PULL 5/7] i.MX arm64 " Shawn Guo
2019-02-15 15:11 ` Arnd Bergmann
2019-02-12 11:21 ` [GIT PULL 6/7] i.MX defconfig updates " Shawn Guo
2019-02-15 15:47 ` Arnd Bergmann
2019-02-12 11:21 ` [GIT PULL 7/7] i.MX MAINTAINERS update " Shawn Guo
2019-02-15 16:38 ` Arnd Bergmann
2019-02-15 17:03 ` Fabio Estevam
2019-02-15 16:18 ` [GIT PULL 1/7] i.MX drivers " Arnd Bergmann
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=20190212112126.572-2-shawnguo@kernel.org \
--to=shawnguo@kernel.org \
--cc=arm@kernel.org \
--cc=festevam@gmail.com \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
/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).