From: Billy Tsai <billy_tsai@aspeedtech.com>
To: <trini@konsulko.com>, <ryan_chen@aspeedtech.com>,
<chiawei_wang@aspeedtech.com>, <BMC-SW@aspeedtech.com>,
<joel@jms.id.au>, <billy_tsai@aspeedtech.com>,
<fr0st61te@gmail.com>, <clamor95@gmail.com>,
<marek.vasut+renesas@mailbox.org>, <michal.simek@amd.com>,
<paul.barker.ct@bp.renesas.com>, <piotr.wojtaszczyk@timesys.com>,
<andre.przywara@arm.com>, <jim.t90615@gmail.com>,
<kabel@kernel.org>, <caleb.connolly@linaro.org>,
<sjg@chromium.org>, <ye.li@nxp.com>, <pbrobinson@gmail.com>,
<u-boot@lists.denx.de>
Subject: [PATCH v1 0/3] Support Aspeed SGPIO controller
Date: Wed, 16 Oct 2024 16:59:52 +0800 [thread overview]
Message-ID: <20241016085955.314236-1-billy_tsai@aspeedtech.com> (raw)
AST2600 SoC has 2 SGPIO master interfaces one with 128 pins another one
with 80 pins, AST2500/AST2400 SoC has 1 SGPIO master interface that
supports up to 80 pins.
Billy Tsai (3):
gpio: Add Aspeed SGPIO driver
ARM: dts: ast2500: Add SGPIO to device tree
ARM: dts: ast2600: Add SGPIO to device tree
arch/arm/dts/ast2500-evb.dts | 5 +
arch/arm/dts/ast2500.dtsi | 20 ++
arch/arm/dts/ast2600-evb.dts | 10 +
arch/arm/dts/ast2600.dtsi | 40 +++
drivers/gpio/Kconfig | 7 +
drivers/gpio/Makefile | 1 +
drivers/gpio/gpio-aspeed-sgpio.c | 310 +++++++++++++++++++++++
drivers/pinctrl/aspeed/pinctrl_ast2500.c | 1 +
drivers/pinctrl/aspeed/pinctrl_ast2600.c | 10 +
9 files changed, 404 insertions(+)
create mode 100644 drivers/gpio/gpio-aspeed-sgpio.c
--
2.25.1
next reply other threads:[~2024-10-16 9:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-16 8:59 Billy Tsai [this message]
2024-10-16 8:59 ` [PATCH v1 1/3] gpio: Add Aspeed SGPIO driver Billy Tsai
2024-10-16 8:59 ` [PATCH v1 2/3] ARM: dts: ast2500: Add SGPIO to device tree Billy Tsai
2024-10-16 8:59 ` [PATCH v1 3/3] ARM: dts: ast2600: " Billy Tsai
2024-10-29 22:28 ` [PATCH v1 0/3] Support Aspeed SGPIO controller Tom Rini
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=20241016085955.314236-1-billy_tsai@aspeedtech.com \
--to=billy_tsai@aspeedtech.com \
--cc=BMC-SW@aspeedtech.com \
--cc=andre.przywara@arm.com \
--cc=caleb.connolly@linaro.org \
--cc=chiawei_wang@aspeedtech.com \
--cc=clamor95@gmail.com \
--cc=fr0st61te@gmail.com \
--cc=jim.t90615@gmail.com \
--cc=joel@jms.id.au \
--cc=kabel@kernel.org \
--cc=marek.vasut+renesas@mailbox.org \
--cc=michal.simek@amd.com \
--cc=paul.barker.ct@bp.renesas.com \
--cc=pbrobinson@gmail.com \
--cc=piotr.wojtaszczyk@timesys.com \
--cc=ryan_chen@aspeedtech.com \
--cc=sjg@chromium.org \
--cc=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
--cc=ye.li@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