From: Billy Tsai <billy_tsai@aspeedtech.com>
To: <linus.walleij@linaro.org>, <brgl@bgdev.pl>, <robh@kernel.org>,
<krzk+dt@kernel.org>, <conor+dt@kernel.org>, <joel@jms.id.au>,
<andrew@codeconstruct.com.au>, <linux-gpio@vger.kernel.org>,
<devicetree@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-aspeed@lists.ozlabs.org>, <linux-kernel@vger.kernel.org>,
<BMC-SW@aspeedtech.com>
Subject: [PATCH v1 0/2] Add Aspeed G7 gpio support
Date: Wed, 21 Aug 2024 15:07:38 +0800 [thread overview]
Message-ID: <20240821070740.2378602-1-billy_tsai@aspeedtech.com> (raw)
The Aspeed 7th generation SoC features two GPIO controllers: one with 12
GPIO pins and another with 216 GPIO pins. The main difference from the
previous generation is that the control logic has been updated to support
per-pin control, allowing each pin to have its own 32-bit register for
configuring value, direction, interrupt type, and more.
Billy Tsai (2):
dt-bindings: gpio: aspeed,ast2400-gpio: Support ast2700
gpio: Add G7 Aspeed gpio controller driver
.../bindings/gpio/aspeed,ast2400-gpio.yaml | 46 +-
drivers/gpio/Kconfig | 7 +
drivers/gpio/Makefile | 1 +
drivers/gpio/gpio-aspeed-g7.c | 831 ++++++++++++++++++
4 files changed, 884 insertions(+), 1 deletion(-)
create mode 100644 drivers/gpio/gpio-aspeed-g7.c
--
2.25.1
next reply other threads:[~2024-08-21 7:07 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-21 7:07 Billy Tsai [this message]
2024-08-21 7:07 ` [PATCH v1 1/2] dt-bindings: gpio: aspeed,ast2400-gpio: Support ast2700 Billy Tsai
2024-08-21 8:51 ` Krzysztof Kozlowski
2024-09-02 8:23 ` Billy Tsai
2024-08-21 7:07 ` [PATCH v1 2/2] gpio: Add G7 Aspeed gpio controller driver Billy Tsai
2024-08-21 12:10 ` Bartosz Golaszewski
2024-08-26 9:59 ` Billy Tsai
2024-08-21 20:51 ` kernel test robot
2024-08-21 23:13 ` kernel test robot
2024-08-22 1:31 ` Andrew Jeffery
2024-08-27 2:45 ` Billy Tsai
2024-08-28 1:18 ` Andrew Jeffery
2024-08-28 5:35 ` Billy Tsai
2024-08-22 9:16 ` kernel test robot
2024-08-26 8:37 ` Linus Walleij
2024-08-26 10:56 ` [PATCH " Markus Elfring
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=20240821070740.2378602-1-billy_tsai@aspeedtech.com \
--to=billy_tsai@aspeedtech.com \
--cc=BMC-SW@aspeedtech.com \
--cc=andrew@codeconstruct.com.au \
--cc=brgl@bgdev.pl \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=joel@jms.id.au \
--cc=krzk+dt@kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-aspeed@lists.ozlabs.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@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