All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kent Gibson <warthog618@gmail.com>
To: Bartosz Golaszewski <brgl@bgdev.pl>
Cc: Linus Walleij <linus.walleij@linaro.org>,
	linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org,
	Bartosz Golaszewski <bartosz.golaszewski@linaro.org>
Subject: Re: [PATCH v5 0/8] gpio: notify user-space about config changes in the kernel
Date: Sun, 20 Oct 2024 19:51:50 +0800	[thread overview]
Message-ID: <20241020115150.GA60526@rigel> (raw)
In-Reply-To: <20241018-gpio-notify-in-kernel-events-v5-0-c79135e58a1c@linaro.org>

On Fri, Oct 18, 2024 at 11:10:08AM +0200, Bartosz Golaszewski wrote:
> We currently only emit events on changed line config to user-space on
> changes made from user-space. Users have no way of getting notified
> about in-kernel changes. This series improves the situation and also
> contains a couple other related improvements.
>
> This is a reworked approach which gets and stores as much info (all of
> it actually, except for the pinctrl state) the moment the event occurrs
> but moves the actual queueing of the event on the kfifo to a dedicated
> high-priority, ordered workqueue.
>
> Signed-off-by: Bartosz Golaszewski <bartosz.golaszewski@linaro.org>

Reviewed-by: Kent Gibson <warthog618@gmail.com>

Cheers,
Kent.

  parent reply	other threads:[~2024-10-20 11:51 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-18  9:10 [PATCH v5 0/8] gpio: notify user-space about config changes in the kernel Bartosz Golaszewski
2024-10-18  9:10 ` [PATCH v5 1/8] gpiolib: notify user-space when a driver requests its own desc Bartosz Golaszewski
2024-10-18  9:10 ` [PATCH v5 2/8] gpiolib: unduplicate chip guard in set_config path Bartosz Golaszewski
2024-10-18  9:10 ` [PATCH v5 3/8] gpio: cdev: go back to storing debounce period in the GPIO descriptor Bartosz Golaszewski
2024-10-18  9:10 ` [PATCH v5 4/8] gpio: cdev: prepare gpio_desc_to_lineinfo() for being called from atomic Bartosz Golaszewski
2024-10-18  9:10 ` [PATCH v5 5/8] gpiolib: add a per-gpio_device line state notification workqueue Bartosz Golaszewski
2024-10-18  9:10 ` [PATCH v5 6/8] gpio: cdev: put emitting the line state events on a workqueue Bartosz Golaszewski
2025-11-13 21:11   ` Sverdlin, Alexander
2025-11-14  8:21     ` Bartosz Golaszewski
2025-11-14  9:04       ` Sverdlin, Alexander
2025-11-14 10:11         ` Bartosz Golaszewski
2025-11-14 11:57           ` Sverdlin, Alexander
2025-11-14 15:26             ` Bartosz Golaszewski
2024-10-18  9:10 ` [PATCH v5 7/8] gpiolib: switch the line state notifier to atomic Bartosz Golaszewski
2024-10-18  9:10 ` [PATCH v5 8/8] gpiolib: notify user-space about in-kernel line state changes Bartosz Golaszewski
2024-10-23 21:05   ` Mark Brown
2024-10-24  6:49     ` Bartosz Golaszewski
2024-10-24  8:15       ` Bartosz Golaszewski
2024-10-24 11:34         ` Klara Modin
2024-10-24 11:45           ` Bartosz Golaszewski
2024-10-24 11:59             ` Klara Modin
2024-10-24 13:39               ` Bartosz Golaszewski
2024-10-20 11:51 ` Kent Gibson [this message]
2024-10-22  7:02 ` [PATCH v5 0/8] gpio: notify user-space about config changes in the kernel 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=20241020115150.GA60526@rigel \
    --to=warthog618@gmail.com \
    --cc=bartosz.golaszewski@linaro.org \
    --cc=brgl@bgdev.pl \
    --cc=linus.walleij@linaro.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.