From: Linus Walleij <linus.walleij@linaro.org>
To: Anson Huang <Anson.Huang@nxp.com>
Cc: Dong Aisheng <aisheng.dong@nxp.com>,
Fabio Estevam <festevam@gmail.com>,
Shawn Guo <shawnguo@kernel.org>, Stefan Agner <stefan@agner.ch>,
Sascha Hauer <kernel@pengutronix.de>,
Sascha Hauer <s.hauer@pengutronix.de>,
"open list:GPIO SUBSYSTEM" <linux-gpio@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Linux ARM <linux-arm-kernel@lists.infradead.org>,
NXP Linux Team <Linux-imx@nxp.com>
Subject: Re: [PATCH V6 0/9] Support i.MX8 SoCs pinctrl drivers built as module
Date: Tue, 7 Jul 2020 10:02:08 +0200 [thread overview]
Message-ID: <CACRpkdYYJfA9uur0R+9ONkEk1pEABJnzrPe7U0VX4-QVQHgLcQ@mail.gmail.com> (raw)
In-Reply-To: <1592979844-18833-1-git-send-email-Anson.Huang@nxp.com>
On Wed, Jun 24, 2020 at 8:35 AM Anson Huang <Anson.Huang@nxp.com> wrote:
> 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
Patches applied to the pinctrl devel branch for v5.9.
Yours,
Linus Walleij
prev parent reply other threads:[~2020-07-07 8:02 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-24 6:23 [PATCH V6 0/9] Support i.MX8 SoCs pinctrl drivers built as module Anson Huang
2020-06-24 6:23 ` [PATCH V6 1/9] pinctrl: imx: Support i.MX8 SoCs pinctrl driver " 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 [this message]
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=CACRpkdYYJfA9uur0R+9ONkEk1pEABJnzrPe7U0VX4-QVQHgLcQ@mail.gmail.com \
--to=linus.walleij@linaro.org \
--cc=Anson.Huang@nxp.com \
--cc=Linux-imx@nxp.com \
--cc=aisheng.dong@nxp.com \
--cc=festevam@gmail.com \
--cc=kernel@pengutronix.de \
--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).