mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Sascha Hauer <s.hauer@pengutronix.de>
To: Barebox List <barebox@lists.infradead.org>,
	 Sascha Hauer <s.hauer@pengutronix.de>
Subject: Re: [PATCH 0/4] make I2C GPIO expander provided buttons work
Date: Fri, 23 Feb 2024 08:32:33 +0100	[thread overview]
Message-ID: <170867355389.296878.10227878309394509588.b4-ty@pengutronix.de> (raw)
In-Reply-To: <20240221142800.1958810-1-s.hauer@pengutronix.de>


On Wed, 21 Feb 2024 15:27:56 +0100, Sascha Hauer wrote:
> The TQMa6UL board uses the gpio-keys driver with GPIOs provided by a
> PCA9554 I2C GPIO expander. This currently doesn't work as the GPIOs
> are read in a poller during an ongoing I2C transfer on the same bus.
> 
> This series fixes that by adding a slice to struct gpio_chip and
> checking its availability before using it.
> 
> [...]

Applied, thanks!

[1/4] gpio: add slice support
      https://git.pengutronix.de/cgit/barebox/commit/?id=cb046503d2c2 (link may not be stable)
[2/4] gpio: pca953x: depend on i2c slice
      https://git.pengutronix.de/cgit/barebox/commit/?id=73b7973cee7d (link may not be stable)
[3/4] input: gpio_keys: limit poll rate
      https://git.pengutronix.de/cgit/barebox/commit/?id=ff5e5b69d643 (link may not be stable)
[4/4] input: gpio_keys: only use gpios in poller when not in use
      https://git.pengutronix.de/cgit/barebox/commit/?id=b01bba2f2bea (link may not be stable)

Best regards,
-- 
Sascha Hauer <s.hauer@pengutronix.de>




      parent reply	other threads:[~2024-02-23  7:36 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-21 14:27 Sascha Hauer
2024-02-21 14:27 ` [PATCH 1/4] gpio: add slice support Sascha Hauer
2024-02-21 14:27 ` [PATCH 2/4] gpio: pca953x: depend on i2c slice Sascha Hauer
2024-02-21 14:27 ` [PATCH 3/4] input: gpio_keys: limit poll rate Sascha Hauer
2024-02-21 14:28 ` [PATCH 4/4] input: gpio_keys: only use gpios in poller when not in use Sascha Hauer
2024-02-23  7:32 ` Sascha Hauer [this message]

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=170867355389.296878.10227878309394509588.b4-ty@pengutronix.de \
    --to=s.hauer@pengutronix.de \
    --cc=barebox@lists.infradead.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