linux-gpio.vger.kernel.org archive mirror
 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 0/5] gpio: notify user-space about config changes in the kernel
Date: Sun, 6 Oct 2024 21:29:34 +0800	[thread overview]
Message-ID: <20241006132934.GA179594@rigel> (raw)
In-Reply-To: <20241004-gpio-notify-in-kernel-events-v1-0-8ac29e1df4fe@linaro.org>

On Fri, Oct 04, 2024 at 04:43:21PM +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.
>
> Signed-off-by: Bartosz Golaszewski <bartosz.golaszewski@linaro.org>

Patches 1-3 look good to me.

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

for those three.

> ---
> Bartosz Golaszewski (5):
>       gpiolib: use v2 defines for line state change events
>       gpiolib: unify two loops initializing GPIO descriptors
>       gpio: cdev: update flags at once when reconfiguring from user-space
>       gpiolib: simplify notifying user-space about line requests
>       gpiolib: notify user-space about in-kernel line state changes
>
>  drivers/gpio/gpiolib-cdev.c |  88 +++++++++++++++++------------------
>  drivers/gpio/gpiolib.c      | 110 ++++++++++++++++++++++++++++++++++++--------
>  drivers/gpio/gpiolib.h      |   9 +++-
>  3 files changed, 141 insertions(+), 66 deletions(-)
> ---
> base-commit: 58ca61c1a866bfdaa5e19fb19a2416764f847d75
> change-id: 20240924-gpio-notify-in-kernel-events-07cd912153e8
>
> Best regards,
> --
> Bartosz Golaszewski <bartosz.golaszewski@linaro.org>
>

  parent reply	other threads:[~2024-10-06 13:29 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-04 14:43 [PATCH 0/5] gpio: notify user-space about config changes in the kernel Bartosz Golaszewski
2024-10-04 14:43 ` [PATCH 1/5] gpiolib: use v2 defines for line state change events Bartosz Golaszewski
2024-10-04 14:43 ` [PATCH 2/5] gpiolib: unify two loops initializing GPIO descriptors Bartosz Golaszewski
2024-10-09 16:09   ` Linus Walleij
2024-10-04 14:43 ` [PATCH 3/5] gpio: cdev: update flags at once when reconfiguring from user-space Bartosz Golaszewski
2024-10-09 16:10   ` Linus Walleij
2024-10-04 14:43 ` [PATCH 4/5] gpiolib: simplify notifying user-space about line requests Bartosz Golaszewski
2024-10-05  3:46   ` Kent Gibson
2024-10-05  9:34     ` Bartosz Golaszewski
2024-10-05  9:49       ` Kent Gibson
2024-10-04 14:43 ` [PATCH 5/5] gpiolib: notify user-space about in-kernel line state changes Bartosz Golaszewski
2024-10-05  7:46   ` Kent Gibson
2024-10-05  9:42     ` Bartosz Golaszewski
2024-10-05  9:54       ` Kent Gibson
2024-10-05 18:45         ` Bartosz Golaszewski
2024-10-05 19:11           ` Kent Gibson
2024-10-06 13:29 ` Kent Gibson [this message]
2024-10-08  8:22 ` (subset) [PATCH 0/5] 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=20241006132934.GA179594@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 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).