From: Sascha Hauer <s.hauer@pengutronix.de>
To: linux-gpio@vger.kernel.org
Cc: linux-kernel@vger.kernel.org,
Linus Walleij <linus.walleij@linaro.org>,
Bartosz Golaszewski <brgl@bgdev.pl>,
kernel@pengutronix.de, Sascha Hauer <s.hauer@pengutronix.de>
Subject: [PATCH 0/2] gpio: Add gpio-latch driver
Date: Thu, 25 Aug 2022 11:41:30 +0200 [thread overview]
Message-ID: <20220825094132.1268174-1-s.hauer@pengutronix.de> (raw)
This adds a gpio-driver which multiplexes existing GPIOs using latches.
Uwe asked [1] if that would be accectable as a new gpio driver, and here
is the result. For a better description what this is all about have a
look at the drawings in the patches.
The driver is pretty much straight forward. The only thing I wasn't sure
about is in which category in Kconfig the driver should be sorted in. I
decided for "Virtual GPIO drivers" which is not an exact match, but the
best I could find in the existing categories.
Sascha
[1] https://lore.kernel.org/all/CACRpkdaBO=JzokGUF6uXZc7ASVD7LjqBxTLGwX-FShM=A9gw9A@mail.gmail.com/t/
Sascha Hauer (2):
gpio: Add gpio latch driver
dt-bindings: gpio: Add gpio-latch binding document
.../devicetree/bindings/gpio/gpio-latch.yaml | 83 ++++++++
drivers/gpio/Kconfig | 6 +
drivers/gpio/Makefile | 1 +
drivers/gpio/gpio-latch.c | 188 ++++++++++++++++++
4 files changed, 278 insertions(+)
create mode 100644 Documentation/devicetree/bindings/gpio/gpio-latch.yaml
create mode 100644 drivers/gpio/gpio-latch.c
--
2.30.2
next reply other threads:[~2022-08-25 9:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-25 9:41 Sascha Hauer [this message]
2022-08-25 9:41 ` [PATCH 1/2] gpio: Add gpio latch driver Sascha Hauer
2022-08-26 5:53 ` Marco Felsch
2022-08-29 14:21 ` Sascha Hauer
2022-08-26 13:41 ` Linus Walleij
2022-08-25 9:41 ` [PATCH 2/2] dt-bindings: gpio: Add gpio-latch binding document Sascha Hauer
2022-08-26 13:37 ` Linus Walleij
2022-08-29 14:40 ` Sascha Hauer
2022-08-31 12:40 ` Linus Walleij
2022-09-01 7:53 ` Sascha Hauer
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=20220825094132.1268174-1-s.hauer@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=brgl@bgdev.pl \
--cc=kernel@pengutronix.de \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.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 NNTP newsgroup(s).