linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Linus Walleij <linus.walleij@linaro.org>
To: Sascha Hauer <s.hauer@pengutronix.de>
Cc: linux-gpio@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org, Bartosz Golaszewski <brgl@bgdev.pl>,
	kernel@pengutronix.de, Serge Semin <fancer.lancer@gmail.com>
Subject: Re: [PATCH v5 1/2] gpio: Add gpio latch driver
Date: Mon, 17 Oct 2022 10:50:44 +0200	[thread overview]
Message-ID: <CACRpkdapjEt8g7zMw8smvJVpvf3TFNNH8hJge1cSp==qYcU2ZA@mail.gmail.com> (raw)
In-Reply-To: <20221007114647.2723457-2-s.hauer@pengutronix.de>

On Fri, Oct 7, 2022 at 1:47 PM Sascha Hauer <s.hauer@pengutronix.de> wrote:

> This driver implements a GPIO multiplexer based on latches connected to
> other GPIOs. A set of data GPIOs is connected to the data input of
> multiple latches. The clock input of each latch is driven by another
> set of GPIOs. With two 8-bit latches 10 GPIOs can be multiplexed into
> 16 GPIOs. GPOs might be a better term as in fact the multiplexed pins
> are output only.
>
> Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>

This looks fine to me!
Reviewed-by: Linus Walleij <linus.walleij@linaro.org>

Yours,
Linus Walleij

  parent reply	other threads:[~2022-10-17  8:52 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-07 11:46 [PATCH v5 0/2] gpio: Add gpio-latch driver Sascha Hauer
2022-10-07 11:46 ` [PATCH v5 1/2] gpio: Add gpio latch driver Sascha Hauer
2022-10-07 16:29   ` Serge Semin
2022-10-17  8:50   ` Linus Walleij [this message]
2022-10-07 11:46 ` [PATCH v5 2/2] dt-bindings: gpio: Add gpio-latch binding document Sascha Hauer
2022-10-07 16:33   ` Serge Semin
2022-10-17  8:51   ` Linus Walleij
2022-10-25  9:39 ` [PATCH v5 0/2] gpio: Add gpio-latch driver Bartosz Golaszewski

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='CACRpkdapjEt8g7zMw8smvJVpvf3TFNNH8hJge1cSp==qYcU2ZA@mail.gmail.com' \
    --to=linus.walleij@linaro.org \
    --cc=brgl@bgdev.pl \
    --cc=devicetree@vger.kernel.org \
    --cc=fancer.lancer@gmail.com \
    --cc=kernel@pengutronix.de \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=s.hauer@pengutronix.de \
    /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).