mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Bartosz Golaszewski <bartosz.golaszewski@oss.qualcomm.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Linus Walleij <linusw@kernel.org>,
	linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org,
	brgl@kernel.org,
	Bartosz Golaszewski <bartosz.golaszewski@oss.qualcomm.com>
Subject: [GIT PULL] gpio fixes for v7.2-rc2
Date: Fri,  3 Jul 2026 09:59:03 +0200	[thread overview]
Message-ID: <20260703075903.5102-1-bartosz.golaszewski@oss.qualcomm.com> (raw)

Linus,

Please pull the following set of GPIO fixes for the next RC.

Thanks,
Bartosz

The following changes since commit dc59e4fea9d83f03bad6bddf3fa2e52491777482:

  Linux 7.2-rc1 (2026-06-28 12:01:31 -0700)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/brgl/linux.git tags/gpio-fixes-for-v7.2-rc2

for you to fetch changes up to 9777530157e7b82fd994327ff878c4245dadc931:

  pinctrl: meson: restore non-sleeping GPIO access (2026-07-01 09:26:40 +0200)

----------------------------------------------------------------
gpio fixes for v7.2-rc2

- check the return value of gpiochip_add_data() in gpio-mvebu and
  gpio-htc-egpio
- avoid locking context issues with GPIO drivers using the shared GPIO
  proxy by only allowing sleeping operations (atomic GPIO ops don't
  really make sense in shared context anyway)
- with the above: restoe non-sleeping GPIO access in pinctrl-meson
- fix return value on OOM in gpio-timberdale
- fix interrupt handling in gpio-mt7621
- support both A and B variants of NCT6126D in gpio-f7188x

----------------------------------------------------------------
Bartosz Golaszewski (1):
      Merge tag 'v7.2-rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux into gpio/for-current

Paul Louvel (1):
      gpio-f7188x: Add support for NCT6126D version B

Pengpeng Hou (2):
      gpio: mvebu: fail probe if gpiochip registration fails
      gpio: htc-egpio: use managed gpiochip registration

Sergio Paracuellos (3):
      gpio: mt7621: avoid corruption of shared interrupt trigger state
      gpio: mt7621: more robust management of IRQ domain teardown
      gpio: mt7621: be sure IRQ domain is created before exposing GPIO chips

Viacheslav Bocharov (2):
      gpio: shared-proxy: always serialize with a sleeping mutex
      pinctrl: meson: restore non-sleeping GPIO access

Vladimir Zapolskiy (1):
      gpio: timberdale: Return -ENOMEM on dynamic memory allocation in probe

 drivers/gpio/gpio-f7188x.c            |  6 ++-
 drivers/gpio/gpio-htc-egpio.c         |  6 ++-
 drivers/gpio/gpio-mt7621.c            | 25 ++++++------
 drivers/gpio/gpio-mvebu.c             |  5 ++-
 drivers/gpio/gpio-shared-proxy.c      | 76 +++++++++++++----------------------
 drivers/gpio/gpio-timberdale.c        |  2 +-
 drivers/gpio/gpiolib-shared.c         |  9 +----
 drivers/gpio/gpiolib-shared.h         | 28 +------------
 drivers/pinctrl/meson/pinctrl-meson.c |  2 +-
 9 files changed, 60 insertions(+), 99 deletions(-)

             reply	other threads:[~2026-07-03  7:59 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-03  7:59 Bartosz Golaszewski [this message]
2026-07-03 15:55 ` pr-tracker-bot

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=20260703075903.5102-1-bartosz.golaszewski@oss.qualcomm.com \
    --to=bartosz.golaszewski@oss.qualcomm.com \
    --cc=brgl@kernel.org \
    --cc=linusw@kernel.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.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

all inboxes | Powered by JetHome®