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 V2 0/9] Support i.MX8 SoCs pinctrl drivers built as module
Date: Mon, 8 Jun 2020 22:37:27 +0800 [thread overview]
Message-ID: <1591627056-19022-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, and it also supports building i.MX
common pinctrl driver and i.MX SCU common pinctrl driver as module.
Compared to V1, the changes are as below:
- Separate the i.MX and i.MX SCU common pinctrl driver to 2 patches;
- Support building i.MX and i.MX SCU common pinctrl driver as module too.
Anson Huang (9):
pinctrl: imx: Support building SCU pinctrl driver as module
pinctrl: imx: Support building i.MX pinctrl driver 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 | 18 +++++++++---------
drivers/pinctrl/freescale/pinctrl-imx.c | 4 ++++
drivers/pinctrl/freescale/pinctrl-imx.h | 2 +-
drivers/pinctrl/freescale/pinctrl-imx8dxl.c | 9 +++------
drivers/pinctrl/freescale/pinctrl-imx8mm.c | 10 ++++------
drivers/pinctrl/freescale/pinctrl-imx8mn.c | 10 ++++------
drivers/pinctrl/freescale/pinctrl-imx8mp.c | 10 ++++------
drivers/pinctrl/freescale/pinctrl-imx8mq.c | 9 ++++-----
drivers/pinctrl/freescale/pinctrl-imx8qm.c | 9 +++------
drivers/pinctrl/freescale/pinctrl-imx8qxp.c | 9 +++------
drivers/pinctrl/freescale/pinctrl-scu.c | 6 ++++++
11 files changed, 45 insertions(+), 51 deletions(-)
--
2.7.4
next reply other threads:[~2020-06-08 14:48 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-08 14:37 Anson Huang [this message]
2020-06-08 14:37 ` [PATCH V2 1/9] pinctrl: imx: Support building SCU pinctrl driver " Anson Huang
2020-06-08 14:37 ` [PATCH V2 2/9] pinctrl: imx: Support building i.MX " Anson Huang
2020-06-08 20:10 ` kernel test robot
2020-06-08 14:37 ` [PATCH V2 3/9] pinctrl: imx8mm: Support building " Anson Huang
2020-06-08 14:37 ` [PATCH V2 4/9] pinctrl: imx8mn: " Anson Huang
2020-06-08 14:37 ` [PATCH V2 5/9] pinctrl: imx8mq: " Anson Huang
2020-06-08 14:37 ` [PATCH V2 6/9] pinctrl: imx8mp: " Anson Huang
2020-06-08 14:37 ` [PATCH V2 7/9] pinctrl: imx8qxp: " Anson Huang
2020-06-08 14:37 ` [PATCH V2 8/9] pinctrl: imx8qm: " Anson Huang
2020-06-08 14:37 ` [PATCH V2 9/9] pinctrl: imx8dxl: " Anson Huang
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=1591627056-19022-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
all inboxes | Powered by JetHome®