From: Jim Liu <jim.t90615@gmail.com>
To: JJLIU0@nuvoton.com, krzysztof.kozlowski+dt@linaro.org,
linus.walleij@linaro.org, andy@kernel.org,
benjaminfair@google.com, brgl@bgdev.pl, jim.t90615@gmail.com,
robh@kernel.org
Cc: linux-gpio@vger.kernel.org, openbmc@lists.ozlabs.org,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org
Subject: [PATCH v7 0/3] Add Nuvoton NPCM SGPIO feature
Date: Wed, 1 Nov 2023 10:51:07 +0800 [thread overview]
Message-ID: <20231101025110.1704543-1-jim.t90615@gmail.com> (raw)
This SGPIO controller is for NUVOTON NPCM7xx and NPCM8xx SoC.
Nuvoton NPCM SGPIO module is combine serial to parallel IC (HC595)
and parallel to serial IC (HC165), and use APB3 clock to control it.
This interface has 4 pins (D_out , D_in, S_CLK, LDSH).
NPCM7xx/NPCM8xx have two sgpio module each module can support up
to 64 output pins,and up to 64 input pin, the pin is only for gpi or gpo.
GPIO pins have sequential, First half is gpo and second half is gpi.
Jim Liu (3):
dt-bindings: gpio: add NPCM sgpio driver bindings
arm: dts: nuvoton: npcm: Add sgpio feature
gpio: nuvoton: Add Nuvoton NPCM sgpio driver
.../bindings/gpio/nuvoton,sgpio.yaml | 86 +++
.../dts/nuvoton/nuvoton-common-npcm7xx.dtsi | 24 +
drivers/gpio/Kconfig | 8 +
drivers/gpio/Makefile | 1 +
drivers/gpio/gpio-npcm-sgpio.c | 649 ++++++++++++++++++
5 files changed, 768 insertions(+)
create mode 100644 Documentation/devicetree/bindings/gpio/nuvoton,sgpio.yaml
create mode 100644 drivers/gpio/gpio-npcm-sgpio.c
--
2.25.1
next reply other threads:[~2023-11-01 2:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-01 2:51 Jim Liu [this message]
2023-11-01 2:51 ` [PATCH v7 1/3] dt-bindings: gpio: add NPCM sgpio driver bindings Jim Liu
2023-11-01 2:51 ` [PATCH v7 2/3] arm: dts: nuvoton: npcm: Add sgpio feature Jim Liu
2023-11-01 2:51 ` [PATCH v7 3/3] gpio: nuvoton: Add Nuvoton NPCM sgpio driver Jim Liu
2023-11-02 12:23 ` Andy Shevchenko
2023-11-02 12:49 ` Linus Walleij
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=20231101025110.1704543-1-jim.t90615@gmail.com \
--to=jim.t90615@gmail.com \
--cc=JJLIU0@nuvoton.com \
--cc=andy@kernel.org \
--cc=benjaminfair@google.com \
--cc=brgl@bgdev.pl \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=openbmc@lists.ozlabs.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).