From: Bartosz Golaszewski <brgl@bgdev.pl>
To: "Linus Walleij" <linus.walleij@linaro.org>,
"Thomas Gleixner" <tglx@linutronix.de>,
"Marc Zyngier" <marc.zyngier@arm.com>,
"Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
Cc: linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org,
Bartosz Golaszewski <bgolaszewski@baylibre.com>
Subject: [PATCH v3 0/7] gpio: mockup: improve the user-space testing interface
Date: Tue, 12 Feb 2019 14:15:53 +0100 [thread overview]
Message-ID: <20190212131600.18960-1-brgl@bgdev.pl> (raw)
From: Bartosz Golaszewski <bgolaszewski@baylibre.com>
Hi Marc,
this is a trimmed down version of the previous series. All irq_sim patches
from the previous implementation were dropped. The only change in irq_sim now
is addition of the irq_sim_get_type() helper. We store the irq type in the
irq_set_type() callback and allow users to retrieve it with the new function.
The entire logic handling the line state now lives directly in the only user
that needs it - the GPIO testing module. Since the GPIO user API only supports
edge interrupts, level types are not supported. This functionality is only
needed for user-space tests. The testing module tracks the line state and makes
sure to avoid impossible situations (like firing a rising edge interrupt if
the line is being driven low).
Other gpio-mockup patches are unchanged - the only change in patch 7 is the
line state tracking.
v1 -> v2:
- instead of providing the irq_sim_get_type() helper, move the irq type
logic into the simulator and provide a helper that allows users to specify
the type of the fired interrupt
v2 -> v3:
- switch back to having irq_sim_type() and put the line state logic into the
GPIO testing module
Bartosz Golaszewski (7):
irq/irq_sim: provide irq_sim_get_type()
gpio: mockup: add locking
gpio: mockup: implement get_multiple()
gpio: mockup: don't create the debugfs link named after the label
gpio: mockup: change the type of 'offset' to unsigned int
gpio: mockup: change the signature of unlocked get/set helpers
gpio: mockup: rework debugfs interface
drivers/gpio/gpio-mockup.c | 188 +++++++++++++++++++++++++++++++------
include/linux/irq_sim.h | 2 +
kernel/irq/irq_sim.c | 23 +++++
3 files changed, 186 insertions(+), 27 deletions(-)
--
2.20.1
next reply other threads:[~2019-02-12 13:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-12 13:15 Bartosz Golaszewski [this message]
2019-02-12 13:15 ` [PATCH v3 1/7] irq/irq_sim: provide irq_sim_get_type() Bartosz Golaszewski
2019-02-14 10:27 ` Marc Zyngier
2019-02-12 13:15 ` [PATCH v3 2/7] gpio: mockup: add locking Bartosz Golaszewski
2019-02-12 13:15 ` [PATCH v3 3/7] gpio: mockup: implement get_multiple() Bartosz Golaszewski
2019-02-12 13:15 ` [PATCH v3 4/7] gpio: mockup: don't create the debugfs link named after the label Bartosz Golaszewski
2019-02-12 13:15 ` [PATCH v3 5/7] gpio: mockup: change the type of 'offset' to unsigned int Bartosz Golaszewski
2019-02-12 13:15 ` [PATCH v3 6/7] gpio: mockup: change the signature of unlocked get/set helpers Bartosz Golaszewski
2019-02-12 13:16 ` [PATCH v3 7/7] gpio: mockup: rework debugfs interface 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=20190212131600.18960-1-brgl@bgdev.pl \
--to=brgl@bgdev.pl \
--cc=bgolaszewski@baylibre.com \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marc.zyngier@arm.com \
--cc=tglx@linutronix.de \
--cc=u.kleine-koenig@pengutronix.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).