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 2/6] i.MX SoC changes for 5.8
Date: Sat, 23 May 2020 11:25:12 +0800 [thread overview]
Message-ID: <20200523032516.11016-2-shawnguo@kernel.org> (raw)
In-Reply-To: <20200523032516.11016-1-shawnguo@kernel.org>
The following changes since commit 8f3d9f354286745c751374f5f1fcafee6b3f3136:
Linux 5.7-rc1 (2020-04-12 12:35:55 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/shawnguo/linux.git tags/imx-soc-5.8
for you to fetch changes up to 52102a3ba6a617449f4b057880d73be93310a7c7:
soc: imx: move cpu code to drivers/soc/imx (2020-05-20 23:03:50 +0800)
----------------------------------------------------------------
i.MX SoC changes for 5.8:
- Add soc device support for Vybrid/VF platform.
- Move the i.MX soc device registration code from mach-imx to
drivers/soc/imx for possible future consolidation with i.MX8 code.
- A small fixup to make pcm970_sja1000_platform_data static.
----------------------------------------------------------------
Andrey Smirnov (1):
ARM: vf610: report soc info via soc device
Ma Feng (1):
ARM: imx: pcm037: make pcm970_sja1000_platform_data static
Peng Fan (3):
ARM: imx: use device_initcall for imx_soc_device_init
ARM: imx: move cpu definitions into a header
soc: imx: move cpu code to drivers/soc/imx
arch/arm/mach-imx/common.h | 1 -
arch/arm/mach-imx/cpu.c | 159 --------------------------------
arch/arm/mach-imx/mach-imx6q.c | 8 +-
arch/arm/mach-imx/mach-imx6sl.c | 8 +-
arch/arm/mach-imx/mach-imx6sx.c | 8 +-
arch/arm/mach-imx/mach-imx6ul.c | 8 +-
arch/arm/mach-imx/mach-imx7d.c | 6 --
arch/arm/mach-imx/mach-imx7ulp.c | 2 +-
arch/arm/mach-imx/mach-pcm037.c | 2 +-
arch/arm/mach-imx/mach-vf610.c | 47 ++++++++++
arch/arm/mach-imx/mxc.h | 22 +----
drivers/soc/imx/Makefile | 3 +
drivers/soc/imx/soc-imx.c | 192 +++++++++++++++++++++++++++++++++++++++
include/soc/imx/cpu.h | 36 ++++++++
14 files changed, 285 insertions(+), 217 deletions(-)
create mode 100644 drivers/soc/imx/soc-imx.c
create mode 100644 include/soc/imx/cpu.h
_______________________________________________
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:[~2020-05-23 3:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-23 3:25 [GIT PULL 1/6] i.MX drivers update for 5.8 Shawn Guo
2020-05-23 3:25 ` Shawn Guo [this message]
2020-05-23 3:25 ` [GIT PULL 3/6] i.MX bindings change " Shawn Guo
2020-05-23 3:25 ` [GIT PULL 4/6] i.MX device tree changes " Shawn Guo
2020-05-23 3:25 ` [GIT PULL 5/6] i.MX arm64 " Shawn Guo
2020-05-23 3:25 ` [GIT PULL 6/6] i.MX defconfig update " 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=20200523032516.11016-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).