From: Bartosz Golaszewski <brgl@bgdev.pl>
To: Linus Walleij <linus.walleij@linaro.org>,
Thomas Gleixner <tglx@linutronix.de>
Cc: linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org,
Bartosz Golaszewski <bartosz.golaszewski@linaro.org>
Subject: [PATCH v2 0/2] gpio: sim: lock simulated GPIOs as interrupts
Date: Mon, 24 Jun 2024 11:39:31 +0200 [thread overview]
Message-ID: <20240624093934.17089-1-brgl@bgdev.pl> (raw)
From: Bartosz Golaszewski <bartosz.golaszewski@linaro.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
next reply other threads:[~2024-06-24 9:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-24 9:39 Bartosz Golaszewski [this message]
2024-06-24 9:39 ` [PATCH v2 1/2] genirq/irq_sim: add an extended irq_sim initializer Bartosz Golaszewski
2024-06-26 11:48 ` Linus Walleij
2024-06-24 9:39 ` [PATCH v2 2/2] gpio: sim: lock GPIOs as interrupts when they are requested Bartosz Golaszewski
2024-06-26 11:48 ` Linus Walleij
2024-07-01 8:41 ` [PATCH v2 0/2] gpio: sim: lock simulated GPIOs as interrupts Bartosz Golaszewski
2024-07-03 12:48 ` Linus Walleij
2024-07-04 7:26 ` 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=20240624093934.17089-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=tglx@linutronix.de \
/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).