From: Anson Huang <Anson.Huang@nxp.com>
To: aisheng.dong@nxp.com, festevam@gmail.com, shawnguo@kernel.org,
stefan@agner.ch, kernel@pengutronix.de, linus.walleij@linaro.org,
s.hauer@pengutronix.de, linux-gpio@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Cc: Linux-imx@nxp.com
Subject: [PATCH V6 0/9] Support i.MX8 SoCs pinctrl drivers built as module
Date: Wed, 24 Jun 2020 14:23:55 +0800 [thread overview]
Message-ID: <1592979844-18833-1-git-send-email-Anson.Huang@nxp.com> (raw)
There are more and mroe requirements that SoC specific modules should be built
as module in order to support generic kernel image, such as Android GKI concept.
This patch series supports i.MX8 SoCs pinctrl drivers to be built as module,
including i.MX8MQ/MM/MN/MP/QXP/QM/DXL SoCs, i.MX common pinctrl driver and i.MX
SCU common pinctrl driver as still built-in.
Compared to V5, the changes are as below:
- Keep i.MX common pinctrl libary built in, ONLY i.MX SoC pinctrl driver
support built as module.
Anson Huang (9):
pinctrl: imx: Support i.MX8 SoCs pinctrl driver built as module
pinctrl: imx: scu: Support i.MX8 SCU SoCs pinctrl driver built as
module
pinctrl: imx8mm: Support building as module
pinctrl: imx8mn: Support building as module
pinctrl: imx8mq: Support building as module
pinctrl: imx8mp: Support building as module
pinctrl: imx8qxp: Support building as module
pinctrl: imx8qm: Support building as module
pinctrl: imx8dxl: Support building as module
drivers/pinctrl/freescale/Kconfig | 14 +++++++-------
drivers/pinctrl/freescale/pinctrl-imx.c | 2 ++
drivers/pinctrl/freescale/pinctrl-imx8dxl.c | 5 +++++
drivers/pinctrl/freescale/pinctrl-imx8mm.c | 6 ++++++
drivers/pinctrl/freescale/pinctrl-imx8mn.c | 6 ++++++
drivers/pinctrl/freescale/pinctrl-imx8mp.c | 6 ++++++
drivers/pinctrl/freescale/pinctrl-imx8mq.c | 6 ++++++
drivers/pinctrl/freescale/pinctrl-imx8qm.c | 5 +++++
drivers/pinctrl/freescale/pinctrl-imx8qxp.c | 5 +++++
drivers/pinctrl/freescale/pinctrl-scu.c | 4 ++++
10 files changed, 52 insertions(+), 7 deletions(-)
--
2.7.4
next reply other threads:[~2020-06-24 6:35 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-24 6:23 Anson Huang [this message]
2020-06-24 6:23 ` [PATCH V6 1/9] pinctrl: imx: Support i.MX8 SoCs pinctrl driver built as module Anson Huang
2020-06-24 6:23 ` [PATCH V6 2/9] pinctrl: imx: scu: Support i.MX8 SCU " Anson Huang
2020-06-24 6:23 ` [PATCH V6 3/9] pinctrl: imx8mm: Support building " Anson Huang
2020-06-24 6:23 ` [PATCH V6 4/9] pinctrl: imx8mn: " Anson Huang
2020-06-24 6:24 ` [PATCH V6 5/9] pinctrl: imx8mq: " Anson Huang
2020-06-24 6:24 ` [PATCH V6 6/9] pinctrl: imx8mp: " Anson Huang
2020-06-24 6:24 ` [PATCH V6 7/9] pinctrl: imx8qxp: " Anson Huang
2020-06-24 6:24 ` [PATCH V6 8/9] pinctrl: imx8qm: " Anson Huang
2020-06-24 6:24 ` [PATCH V6 9/9] pinctrl: imx8dxl: " Anson Huang
2020-06-24 7:18 ` [PATCH V6 0/9] Support i.MX8 SoCs pinctrl drivers built " Aisheng Dong
2020-07-07 8:02 ` Linus Walleij
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=1592979844-18833-1-git-send-email-Anson.Huang@nxp.com \
--to=anson.huang@nxp.com \
--cc=Linux-imx@nxp.com \
--cc=aisheng.dong@nxp.com \
--cc=festevam@gmail.com \
--cc=kernel@pengutronix.de \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=s.hauer@pengutronix.de \
--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).