devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sascha Hauer <s.hauer@pengutronix.de>
To: linux-gpio@vger.kernel.org
Cc: devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
	Linus Walleij <linus.walleij@linaro.org>,
	Bartosz Golaszewski <brgl@bgdev.pl>,
	kernel@pengutronix.de, Serge Semin <fancer.lancer@gmail.com>,
	Sascha Hauer <s.hauer@pengutronix.de>
Subject: [PATCH v4 0/2] gpio: Add gpio-latch driver
Date: Thu,  6 Oct 2022 10:30:29 +0200	[thread overview]
Message-ID: <20221006083031.2259006-1-s.hauer@pengutronix.de> (raw)

This round includes the changes suggested by Serge: Instead of hammering
the GPIOs as fast as we can we now have device tree properties to limit
the speed so that slower hardware can work with the driver.

Sascha

Sascha Hauer (2):
  gpio: Add gpio latch driver
  dt-bindings: gpio: Add gpio-latch binding document

 .../devicetree/bindings/gpio/gpio-latch.yaml  |  94 ++++++++
 drivers/gpio/Kconfig                          |   6 +
 drivers/gpio/Makefile                         |   1 +
 drivers/gpio/gpio-latch.c                     | 220 ++++++++++++++++++
 4 files changed, 321 insertions(+)
 create mode 100644 Documentation/devicetree/bindings/gpio/gpio-latch.yaml
 create mode 100644 drivers/gpio/gpio-latch.c

-- 
2.30.2


             reply	other threads:[~2022-10-06  8:30 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-06  8:30 Sascha Hauer [this message]
2022-10-06  8:30 ` [PATCH v4 1/2] gpio: Add gpio latch driver Sascha Hauer
2022-10-06  9:15   ` Serge Semin
2022-10-06 12:26     ` Sascha Hauer
2022-10-06 12:45       ` Serge Semin
2022-10-06  8:30 ` [PATCH v4 2/2] dt-bindings: gpio: Add gpio-latch binding document Sascha Hauer
2022-10-06 18:53   ` Rob Herring

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=20221006083031.2259006-1-s.hauer@pengutronix.de \
    --to=s.hauer@pengutronix.de \
    --cc=brgl@bgdev.pl \
    --cc=devicetree@vger.kernel.org \
    --cc=fancer.lancer@gmail.com \
    --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).