linux-gpio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bartosz Golaszewski <brgl@bgdev.pl>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Linus Walleij <linus.walleij@linaro.org>,
	linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org,
	Bartosz Golaszewski <bartosz.golaszewski@linaro.org>
Subject: [GIT PULL] gpio: fixes for v6.8-rc1
Date: Thu, 18 Jan 2024 13:53:15 +0100	[thread overview]
Message-ID: <20240118125315.16778-1-brgl@bgdev.pl> (raw)

From: Bartosz Golaszewski <bartosz.golaszewski@linaro.org>

Linus,

Please pull the following set of fixes for the upcoming RC. Apart from
some regular driver fixes there's a relatively big revert of the locking
changes that were introduced to GPIOLIB in this merge window. This is
needed because it turned out that some legacy GPIO interfaces - that need
to translate a number from the global GPIO numberspace to the address of
the relevant descriptor, thus running a GPIO device lookup and taking the
GPIO device list lock - are still used in old code from atomic context
resulting in "scheduling while atomic" errors.

I'll try to make the read-only part of the list access entirely lockless
using SRCU but this will take some time so let's go back to the old global
spinlock for now.

Please pull,
Bartosz Golaszewski

The following changes since commit 576db73424305036a6aa9e40daf7109742fbb1df:

  Merge tag 'gpio-updates-for-v6.8-rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/brgl/linux (2024-01-12 13:35:31 -0800)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/brgl/linux.git tags/gpio-fixes-for-v6.8-rc1

for you to fetch changes up to efb8235bfdbe661c460f803150b50840a73b5f03:

  gpiolib: revert the attempt to protect the GPIO device list with an rwsem (2024-01-17 09:52:37 +0100)

----------------------------------------------------------------
gpio fixes for v6.8-rc1

- revert the changes aiming to use a read-write semaphore to protect the
  list of GPIO devices due to calls to legacy API taking that lock from
  atomic context in old code
- fix inverted logic in DEFINE_FREE() for GPIO device references
- check the return value of bgpio_init() in gpio-mlxbf3
- fix node address in the DT bindings example for gpio-xilinx
- fix signedness bug in gpio-rtd
- fix kernel-doc warnings in gpio-en7523

----------------------------------------------------------------
Bartosz Golaszewski (1):
      gpiolib: revert the attempt to protect the GPIO device list with an rwsem

Dan Carpenter (1):
      gpio: rtd: Fix signedness bug in probe

Lukas Wunner (1):
      gpiolib: Fix scope-based gpio_device refcounting

Michal Simek (1):
      dt-bindings: gpio: xilinx: Fix node address in gpio

Randy Dunlap (1):
      gpio: EN7523: fix kernel-doc warnings

Su Hui (1):
      gpio: mlxbf3: add an error code check in mlxbf3_gpio_probe

 .../devicetree/bindings/gpio/xlnx,gpio-xilinx.yaml |   2 +-
 drivers/gpio/gpio-en7523.c                         |   6 +-
 drivers/gpio/gpio-mlxbf3.c                         |   2 +
 drivers/gpio/gpio-rtd.c                            |  15 ++-
 drivers/gpio/gpiolib-sysfs.c                       |  45 +++----
 drivers/gpio/gpiolib-sysfs.h                       |   6 -
 drivers/gpio/gpiolib.c                             | 135 +++++++++++----------
 drivers/gpio/gpiolib.h                             |   2 -
 include/linux/gpio/driver.h                        |   2 +-
 9 files changed, 114 insertions(+), 101 deletions(-)

             reply	other threads:[~2024-01-18 12:53 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-18 12:53 Bartosz Golaszewski [this message]
2024-01-19  1:08 ` [GIT PULL] gpio: fixes for v6.8-rc1 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=20240118125315.16778-1-brgl@bgdev.pl \
    --to=brgl@bgdev.pl \
    --cc=bartosz.golaszewski@linaro.org \
    --cc=linus.walleij@linaro.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;
as well as URLs for NNTP newsgroup(s).