From: "A.s. Dong" <aisheng.dong@nxp.com>
To: "linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>
Cc: "A.s. Dong" <aisheng.dong@nxp.com>,
"dongas86@gmail.com" <dongas86@gmail.com>,
"linus.walleij@linaro.org" <linus.walleij@linaro.org>,
"stefan@agner.ch" <stefan@agner.ch>,
dl-linux-imx <linux-imx@nxp.com>,
"kernel@pengutronix.de" <kernel@pengutronix.de>,
Fabio Estevam <fabio.estevam@nxp.com>,
"shawnguo@kernel.org" <shawnguo@kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: [PATCH V3 0/2] pinctrl: imx: add imx8qxp pinctrl support
Date: Wed, 17 Oct 2018 06:04:41 +0000 [thread overview]
Message-ID: <1539756011-32559-1-git-send-email-aisheng.dong@nxp.com> (raw)
This patch series adds i.MX8QXP pinctrl support which is based on
the pad service provided by SCU firmware.
Note it depends on SCU APIs patch set which has already been merged by Shawn.
So suppose this patch series can go through shawn's tree.
Note the binding part is also merged into scu binding doc according to
Rob's suggestion.
https://www.spinics.net/lists/arm-kernel/msg680738.html
v2->v3:
* Pad name update (add IMX8QXP prefix)
v1->v2:
* scu firmware headfile path update
* structure name and api usage update
* move SCU Pad API implementation into driver
* add binding headfile pad-imx8qxp.h
Dong Aisheng (2):
pinctrl: fsl: add scu based pinctrl support
pinctrl: imx: add imx8qxp driver
drivers/pinctrl/freescale/Kconfig | 11 +
drivers/pinctrl/freescale/Makefile | 2 +
drivers/pinctrl/freescale/pinctrl-imx.c | 425 ++++++++++------
drivers/pinctrl/freescale/pinctrl-imx.h | 67 ++-
drivers/pinctrl/freescale/pinctrl-imx8qxp.c | 232 +++++++++
drivers/pinctrl/freescale/pinctrl-scu.c | 121 +++++
include/dt-bindings/pinctrl/pads-imx8qxp.h | 751 ++++++++++++++++++++++++++++
7 files changed, 1439 insertions(+), 170 deletions(-)
create mode 100644 drivers/pinctrl/freescale/pinctrl-imx8qxp.c
create mode 100644 drivers/pinctrl/freescale/pinctrl-scu.c
create mode 100644 include/dt-bindings/pinctrl/pads-imx8qxp.h
--
2.7.4
next reply other threads:[~2018-10-17 6:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-17 6:04 A.s. Dong [this message]
2018-10-17 6:04 ` [PATCH V3 1/2] pinctrl: fsl: add scu based pinctrl support A.s. Dong
2018-10-17 6:04 ` [PATCH V3 2/2] pinctrl: imx: add imx8qxp driver A.s. Dong
2018-10-30 12:01 ` [PATCH V3 0/2] pinctrl: imx: add imx8qxp pinctrl support Linus Walleij
2018-10-30 14:03 ` A.s. Dong
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=1539756011-32559-1-git-send-email-aisheng.dong@nxp.com \
--to=aisheng.dong@nxp.com \
--cc=dongas86@gmail.com \
--cc=fabio.estevam@nxp.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-imx@nxp.com \
--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).