[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAMRc=MfH8ZuA2pK3bzSw5mitsFE9wUnoD4iG4Tg8_83SJm-poQ@mail.gmail.com>
Date: Mon, 1 Jul 2024 10:41:34 +0200
From: Bartosz Golaszewski <brgl@...ev.pl>
To: Linus Walleij <linus.walleij@...aro.org>, Thomas Gleixner <tglx@...utronix.de>
Cc: linux-gpio@...r.kernel.org, linux-kernel@...r.kernel.org,
Bartosz Golaszewski <bartosz.golaszewski@...aro.org>
Subject: Re: [PATCH v2 0/2] gpio: sim: lock simulated GPIOs as interrupts
On Mon, Jun 24, 2024 at 11:39 AM Bartosz Golaszewski <brgl@...ev.pl> wrote:
>
> From: Bartosz Golaszewski <bartosz.golaszewski@...aro.org>
>
> I realized that the gpio-sim module doesn't lock the GPIOs as interrupts
> when they are requested from the irq_sim. This leads to users being able
> to change the direction of GPIOs that should remain as inputs to output.
> This series extends the irq_sim interface and allows users to supply
> callbacks that will be executed to inform users about interrupts being
> requested and released so that they can act accordingly. The gpio-sim is
> made to use this new API and lock GPIOs as interrupts when needed.
>
> Thomas: if this is fine with you, can you Ack it so that I can take it
> through the GPIO tree for the next merge window?
>
> Changes since v1:
> - drop the notifier in favor of specific callbacks
>
> Bartosz Golaszewski (2):
> genirq/irq_sim: add an extended irq_sim initializer
> gpio: sim: lock GPIOs as interrupts when they are requested
>
> drivers/gpio/gpio-sim.c | 25 ++++++++++++++++-
> include/linux/irq_sim.h | 17 ++++++++++++
> kernel/irq/irq_sim.c | 60 ++++++++++++++++++++++++++++++++++++++---
> 3 files changed, 98 insertions(+), 4 deletions(-)
>
> --
> 2.43.0
>
Without any objections, I'd like to take it through the GPIO tree by
the end of this week.
Bart
Powered by blists - more mailing lists