public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: Nikolaos Pasaloukos <nikolaos.pasaloukos@blaize.com>
To: Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	James Cowgill <james.cowgill@blaize.com>,
	Matt Redfearn <matthew.redfearn@blaize.com>,
	Neil Jones <neil.jones@blaize.com>,
	Linus Walleij <linus.walleij@linaro.org>,
	Bartosz Golaszewski <brgl@bgdev.pl>,
	Matt Redfearn <matthew.redfearn@blaize.com>,
	Catalin Marinas <catalin.marinas@arm.com>,
	Will Deacon <will@kernel.org>
Cc: "devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>,
	Nikolaos Pasaloukos <nikolaos.pasaloukos@blaize.com>
Subject: [PATCH v2 0/3] Add support for Blaize BLZP1600 GPIO driver
Date: Thu, 27 Mar 2025 11:27:03 +0000	[thread overview]
Message-ID: <20250327-kernel-upstreaming-add_gpio_support-v2-0-bbe51f8d66da@blaize.com> (raw)

This patchset adds a GPIO driver for the VeriSilicon APB v0.2
hardware. This controller is used in the Blaize BLZP1600
SoC for its GPIO interface. It is essential for upstream
support since it is used to provide signals for the
Ethernet, USB, SD and many other interfaces.

Adds the GPIO interface to the Blaize BLZP1600 SoC devicetree.

The hardware itself consists of 32 I/O pins. It has
programmable interrupt generation capability on the pins.
The interrupts can be edge or level triggered and it
includes a de-bounce circuit.

Signed-off-by: Nikolaos Pasaloukos <nikolaos.pasaloukos@blaize.com>
---
Changes in v2:
- No longer adds VeriSilicon as a vendor.
- Renamed the driver from vsi,apb-gpio to blaize,blzp1600-gpio
  Changed the driver function prefix to address the new name
  Removed IRQ_DOMAIN_HIERARCHY from Kconfig
- Builds the driver as a module by default
- Link to v1: https://lore.kernel.org/r/20250212-kernel-upstreaming-add_gpio_support-v1-0-080e724a21f3@blaize.com

---
Nikolaos Pasaloukos (3):
      dt-bindings: Document Blaize BLZP1600 GPIO driver
      gpio: Enable Blaize BLZP1600 GPIO support
      arm64: dts: blaize-blzp1600: Enable GPIO support

 .../bindings/gpio/blaize,blzp1600-gpio.yaml        |  77 ++++++
 MAINTAINERS                                        |  10 +
 arch/arm64/boot/dts/blaize/blaize-blzp1600-cb2.dts |  36 +++
 arch/arm64/boot/dts/blaize/blaize-blzp1600.dtsi    |  12 +
 drivers/gpio/Kconfig                               |  11 +
 drivers/gpio/Makefile                              |   1 +
 drivers/gpio/gpio-blzp1600.c                       | 283 +++++++++++++++++++++
 7 files changed, 430 insertions(+)
---
base-commit: fe2280d094f95105a361dc88e07b1009d4cfeca6
change-id: 20250117-kernel-upstreaming-add_gpio_support-b4ce05eff7a5

Best regards,
-- 
Nikolaos Pasaloukos <nikolaos.pasaloukos@blaize.com>


             reply	other threads:[~2025-03-27 11:33 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-27 11:27 Nikolaos Pasaloukos [this message]
2025-03-27 11:27 ` [PATCH v2 1/3] dt-bindings: Document Blaize BLZP1600 GPIO driver Nikolaos Pasaloukos
2025-03-27 16:52   ` Conor Dooley
2025-03-28 10:01   ` Neil Jones
2025-04-07 12:05     ` Bartosz Golaszewski
2025-03-27 11:27 ` [PATCH v2 2/3] gpio: Enable Blaize BLZP1600 GPIO support Nikolaos Pasaloukos
2025-03-27 11:27 ` [PATCH v2 3/3] arm64: dts: blaize-blzp1600: Enable " Nikolaos Pasaloukos
2025-04-24 13:55   ` Nikolaos Pasaloukos
2025-04-07 12:02 ` (subset) [PATCH v2 0/3] Add support for Blaize BLZP1600 GPIO driver 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=20250327-kernel-upstreaming-add_gpio_support-v2-0-bbe51f8d66da@blaize.com \
    --to=nikolaos.pasaloukos@blaize.com \
    --cc=brgl@bgdev.pl \
    --cc=catalin.marinas@arm.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=james.cowgill@blaize.com \
    --cc=krzk+dt@kernel.org \
    --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=matthew.redfearn@blaize.com \
    --cc=neil.jones@blaize.com \
    --cc=robh@kernel.org \
    --cc=will@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