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>,
	Geert Uytterhoeven <geert+renesas@glider.be>
Cc: linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org,
	Bartosz Golaszewski <brgl@bgdev.pl>,
	kernel@pengutronix.de
Subject: Re: [PATCH 1/2] gpio: Add gpio latch driver
Date: Fri, 26 Aug 2022 15:41:59 +0200	[thread overview]
Message-ID: <CACRpkdZboPe5DTkO7HuouAW92cE9NC-dOZ0_zwPTRCOM+pJ8sQ@mail.gmail.com> (raw)
In-Reply-To: <20220825094132.1268174-2-s.hauer@pengutronix.de>

On Thu, Aug 25, 2022 at 11:41 AM 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>

Take a close look at the other forwarding driver:
drivers/gpio/gpio-aggregator.c

Especially (as pointed out by Marco) the sleeping/non-sleeping calls.

There was a lot of discussion around that patch before we got the
forwarding of GPIOs into a nice working shape.

Also get Geert to review this because he knows what you need to
do. :)

Yours,
Linus Walleij

  parent reply	other threads:[~2022-08-26 13:43 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-25  9:41 [PATCH 0/2] gpio: Add gpio-latch driver Sascha Hauer
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 [this message]
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=CACRpkdZboPe5DTkO7HuouAW92cE9NC-dOZ0_zwPTRCOM+pJ8sQ@mail.gmail.com \
    --to=linus.walleij@linaro.org \
    --cc=brgl@bgdev.pl \
    --cc=geert+renesas@glider.be \
    --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).