From: peng.fan@nxp.com
To: shawnguo@kernel.org, sboyd@kernel.org, s.hauer@pengutronix.de,
linus.walleij@linaro.org, arnd@arndb.de
Cc: kernel@pengutronix.de, festevam@gmail.com, linux-imx@nxp.com,
aisheng.dong@nxp.com, stefan@agner.ch, Anson.Huang@nxp.com,
abel.vesa@nxp.com, linux-clk@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-gpio@vger.kernel.org,
Peng Fan <peng.fan@nxp.com>
Subject: [PATCH 0/3] imx: drop dependency on ARM64
Date: Fri, 13 Mar 2020 11:27:13 +0800 [thread overview]
Message-ID: <1584070036-26447-1-git-send-email-peng.fan@nxp.com> (raw)
From: Peng Fan <peng.fan@nxp.com>
It is possible to run aarch32 linux on aarch64 hardware, but
with the ARM64 dependency, we are not able to build those drivers
for ARM32.
Select ARM_GIC_V3 for i.MX8M is to enable the gic-v3 driver for i.MX8M
I did a basic boot test on i.MX8MM EVK board. A few ATF changes
to make psci smp work still needed.
Peng Fan (3):
pinctrl: freescale: drop the dependency on ARM64 for i.MX8M
clk: imx: drop the dependency on ARM64 for i.MX8M
soc: imx: select ARM_GIC_V3 for i.MX8M
drivers/clk/imx/Kconfig | 8 ++++----
drivers/pinctrl/freescale/Kconfig | 8 ++++----
drivers/soc/imx/Kconfig | 1 +
3 files changed, 9 insertions(+), 8 deletions(-)
--
2.16.4
next reply other threads:[~2020-03-13 3:33 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-13 3:27 peng.fan [this message]
2020-03-13 3:27 ` [PATCH 1/3] pinctrl: freescale: drop the dependency on ARM64 for i.MX8M peng.fan
2020-03-13 10:09 ` Arnd Bergmann
2020-03-25 23:23 ` Linus Walleij
2020-03-13 3:27 ` [PATCH 2/3] clk: imx: " peng.fan
2020-03-13 10:09 ` Arnd Bergmann
2020-03-16 17:01 ` Stephen Boyd
2020-04-14 13:37 ` Shawn Guo
2020-03-13 3:27 ` [PATCH 3/3] soc: imx: select ARM_GIC_V3 " peng.fan
2020-03-13 10:11 ` Arnd Bergmann
2020-03-16 6:43 ` Peng Fan
2020-03-16 8:05 ` Arnd Bergmann
2020-03-17 1:43 ` Peng Fan
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=1584070036-26447-1-git-send-email-peng.fan@nxp.com \
--to=peng.fan@nxp.com \
--cc=Anson.Huang@nxp.com \
--cc=abel.vesa@nxp.com \
--cc=aisheng.dong@nxp.com \
--cc=arnd@arndb.de \
--cc=festevam@gmail.com \
--cc=kernel@pengutronix.de \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=sboyd@kernel.org \
--cc=shawnguo@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).