From: Shenwei Wang <shenwei.wang@nxp.com>
To: robh+dt@kernel.org, krzysztof.kozlowski+dt@linaro.org,
linus.walleij@linaro.org, brgl@bgdev.pl, shawnguo@kernel.org,
s.hauer@pengutronix.de, kernel@pengutronix.de,
festevam@gmail.com, linux-imx@nxp.com
Cc: devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-gpio@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
imx@lists.linux.dev, Shenwei Wang <shenwei.wang@nxp.com>
Subject: [PATCH v5 0/3] Add IMX8 SCU GPIO support
Date: Fri, 12 Aug 2022 08:30:09 -0500 [thread overview]
Message-ID: <20220812133012.7283-1-shenwei.wang@nxp.com> (raw)
The system controller (SCU) is the central unit to manage the resources
on i.MX8 platforms. The SCU firmware provides a set of APIs to access
the GPIO PINs on the SCU domain.
This patch series implements the standard GPIO driver over the SCU
firmware APIs, so that the GPIOs on the SCU domain could be accessed
like a local GPIO PINs.
Changes in V5:
- rename the file name from fsl,imx-sc-gpio to fsl,imx8qxp-sc-gpio
to match the compatible string
Changes in V4:
- remove the generic compatible of "fsl,imx-sc-gpio"
- update the gpio $ref in "fsl,scu.yaml" as the file name is changed
- update the commit comment for 0003 because the driver is moved to the
directory of "drivers/gpio"
Changes in V3:
- follow the other imx8 SCU binding rule and rename the compatible string
from fsl,imx8-scu-gpio to fsl,imx8qxp-sc-gpio
- rename the doc file from fsl,imx8-scu-gpio.yaml to fsl,imx-sc-gpio.yaml
Changes in V2:
- move the driver into the gpio directory per Krzysztof's feedback
- change the subnode description in file fsl,scu.yaml
- fix the dt_binding_check error
Shenwei Wang (3):
dt-bindings: gpio: Add imx scu gpio driver bindings
dt-bindings: firmware: imx: Add imx-scu gpio node
gpio: imx-scu: add imx-scu GPIO driver
.../devicetree/bindings/firmware/fsl,scu.yaml | 5 +
.../bindings/gpio/fsl,imx8qxp-sc-gpio.yaml | 39 +++++
drivers/gpio/Kconfig | 4 +
drivers/gpio/Makefile | 1 +
drivers/gpio/gpio-imx-scu.c | 139 ++++++++++++++++++
5 files changed, 188 insertions(+)
create mode 100644 Documentation/devicetree/bindings/gpio/fsl,imx8qxp-sc-gpio.yaml
create mode 100644 drivers/gpio/gpio-imx-scu.c
--
2.25.1
next reply other threads:[~2022-08-12 13:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-12 13:30 Shenwei Wang [this message]
2022-08-12 13:30 ` [PATCH v5 1/3] dt-bindings: gpio: Add imx scu gpio driver bindings Shenwei Wang
2022-08-12 13:33 ` Krzysztof Kozlowski
2022-08-12 13:30 ` [PATCH v5 2/3] dt-bindings: firmware: imx: Add imx-scu gpio node Shenwei Wang
2022-08-12 13:30 ` [PATCH v5 3/3] gpio: imx-scu: add imx-scu GPIO driver Shenwei Wang
2022-08-15 9:06 ` Bartosz Golaszewski
2022-08-16 10:08 ` Krzysztof Kozlowski
2022-08-22 8:51 ` [PATCH v5 0/3] Add IMX8 SCU GPIO support Linus Walleij
2022-08-31 15:21 ` Bartosz Golaszewski
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=20220812133012.7283-1-shenwei.wang@nxp.com \
--to=shenwei.wang@nxp.com \
--cc=brgl@bgdev.pl \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=imx@lists.linux.dev \
--cc=kernel@pengutronix.de \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@kernel.org \
/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).