linux-gpio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andrei Stefanescu <andrei.stefanescu@oss.nxp.com>
To: Linus Walleij <linus.walleij@linaro.org>,
	Bartosz Golaszewski <brgl@bgdev.pl>,
	Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Chester Lin <chester62515@gmail.com>,
	Matthias Brugger <mbrugger@suse.com>,
	Ghennadi Procopciuc <Ghennadi.Procopciuc@nxp.com>,
	Larisa Grigore <larisa.grigore@nxp.com>
Cc: linux-gpio@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	NXP S32 Linux Team <s32@nxp.com>,
	Andrei Stefanescu <andrei.stefanescu@oss.nxp.com>
Subject: [PATCH 0/3] gpio: siul2-s32g2: add initial GPIO driver
Date: Mon, 26 Aug 2024 11:42:07 +0300	[thread overview]
Message-ID: <20240826084214.2368673-1-andrei.stefanescu@oss.nxp.com> (raw)

This patch series adds support for basic GPIO
operations(set, get, direction_output/input, set_config).

There are two SIUL2 hardware modules: SIUL2_0 and SIUL2_1.
However, this driver exports both as a single GPIO driver.
This is because the interrupt registers are located only
in SIUL2_1, even for GPIOs that are part of SIUL2_0.

There are two gaps in the GPIO ranges:
- 102-111(inclusive) are invalid
- 123-143(inclusive) are invalid

These will be excluded via the `gpio-reserved-ranges`
property.

Writing and reading GPIO values is done via the PGPDO/PGPDI
registers(Parallel GPIO Pad Data Output/Input) which are
16 bit registers, each bit corresponding to a GPIO.

Note that the PGPDO order is similar to a big-endian grouping
of two registers:
PGPDO1, PGPDO0, PGPDO3, PGPDO2, PGPDO5, PGPDO4, gap, PGPDO6.

I have other patches for this driver:
- interrupt support
- power management callbacks

which I plan to upstream after this series gets merged
in order to simplify the review process.

Andrei Stefanescu (3):
  dt-bindings: gpio: add schema for NXP S32G2/S32G3 SoCs
  drivers: gpio: siul2-s32g2: add NXP S32G2/S32G3 SoCs support
  MAINTAINERS: add MAINTAINER for S32G2 SIUL2 GPIO driver

 .../bindings/gpio/nxp,gpio-siul2-s32g2.yaml   | 134 ++++
 MAINTAINERS                                   |   2 +
 drivers/gpio/Kconfig                          |   8 +
 drivers/gpio/Makefile                         |   1 +
 drivers/gpio/gpio-siul2-s32g2.c               | 607 ++++++++++++++++++
 5 files changed, 752 insertions(+)
 create mode 100644 Documentation/devicetree/bindings/gpio/nxp,gpio-siul2-s32g2.yaml
 create mode 100644 drivers/gpio/gpio-siul2-s32g2.c

-- 
2.45.2


             reply	other threads:[~2024-08-26  8:42 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-26  8:42 Andrei Stefanescu [this message]
2024-08-26  8:42 ` [PATCH 1/3] dt-bindings: gpio: add schema for NXP S32G2/S32G3 SoCs Andrei Stefanescu
2024-08-26  9:14   ` Krzysztof Kozlowski
2024-08-26  9:36   ` Krzysztof Kozlowski
2024-08-26  8:42 ` [PATCH 2/3] drivers: gpio: siul2-s32g2: add NXP S32G2/S32G3 SoCs support Andrei Stefanescu
2024-08-26  9:10   ` Krzysztof Kozlowski
2024-08-26 14:03     ` Andrei Stefanescu
2024-08-26 14:04       ` Krzysztof Kozlowski
2024-09-06  8:43     ` Andrei Stefanescu
2024-09-06  9:39       ` Krzysztof Kozlowski
2024-09-06  9:45         ` Andrei Stefanescu
2024-09-06  9:53           ` Krzysztof Kozlowski
2024-09-06 11:50             ` Andrei Stefanescu
2024-09-06 12:02               ` Krzysztof Kozlowski
2024-08-26  9:42   ` Linus Walleij
2024-08-26 14:03     ` Andrei Stefanescu
2024-08-26 14:06   ` Andrew Lunn
2024-08-27  2:23   ` kernel test robot
2024-08-27  4:38   ` kernel test robot
2024-08-26  8:42 ` [PATCH 3/3] MAINTAINERS: add MAINTAINER for S32G2 SIUL2 GPIO driver Andrei Stefanescu

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=20240826084214.2368673-1-andrei.stefanescu@oss.nxp.com \
    --to=andrei.stefanescu@oss.nxp.com \
    --cc=Ghennadi.Procopciuc@nxp.com \
    --cc=brgl@bgdev.pl \
    --cc=chester62515@gmail.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=larisa.grigore@nxp.com \
    --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=mbrugger@suse.com \
    --cc=robh@kernel.org \
    --cc=s32@nxp.com \
    /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).