From: Linus Walleij <linus.walleij@linaro.org>
To: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
Cc: Bartosz Golaszewski <brgl@bgdev.pl>,
Thomas Gleixner <tglx@linutronix.de>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"open list:GPIO SUBSYSTEM" <linux-gpio@vger.kernel.org>,
Bartosz Golaszewski <bgolaszewski@baylibre.com>
Subject: Re: [PATCH 1/2] irq/irq_sim: provide irq_sim_fire_edge()
Date: Fri, 14 Dec 2018 15:07:37 +0100 [thread overview]
Message-ID: <CACRpkdaTNFFevE-hauMn17cXbsoddkw_Bp3WyBHbzG1+dohxew@mail.gmail.com> (raw)
In-Reply-To: <20181205132000.f7n2stv2pxldzcxu@pengutronix.de>
On Wed, Dec 5, 2018 at 2:20 PM Uwe Kleine-König
<u.kleine-koenig@pengutronix.de> wrote:
> On Wed, Dec 05, 2018 at 01:19:54PM +0100, Linus Walleij wrote:
> > > The iio testing driver only needs the trigger and relies on an irq that
> > > then calls the registerd handler. The iio driver doesn't need to tune
> > > the edge sensitivity though and if your mockup driver just only calls
> > > the fire routine if the configured sensitivity justifies that,
> > > everything should work as expected.
> >
> > Simulating edges in the generic IRQ simulator codes seems
> > generally useful to me, even if there is just one user now.
>
> I cannot imagine another potential user. Which kind of driver could use
> that that is not a gpio simulator?
I suppose anything that can generate an IRQ and wants to generate
some test IRQs where edge matters, drivers/irqchips/?
Regmap IRQ drivers/base/regmap/regmap-irq.c does support
edges, and regmap already expose all registers it handles in
debugfs, so it'd be really neat of you can also use debugfs
to insert IRQs from a device using regmap.
Yours,
Linus Walleij
next prev parent reply other threads:[~2018-12-14 14:17 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-20 13:40 [PATCH 0/2] irq/irq_sim: provide a specialized variant of irq_sim_fire() Bartosz Golaszewski
2018-11-20 13:40 ` [PATCH 1/2] irq/irq_sim: provide irq_sim_fire_edge() Bartosz Golaszewski
2018-11-20 17:17 ` Uwe Kleine-König
2018-11-21 16:34 ` Bartosz Golaszewski
2018-11-21 19:15 ` Uwe Kleine-König
2018-11-23 15:59 ` Bartosz Golaszewski
2018-11-25 21:18 ` Uwe Kleine-König
2018-11-29 18:14 ` Bartosz Golaszewski
2018-11-30 22:26 ` Linus Walleij
2018-12-02 12:29 ` Marc Zyngier
2018-12-02 17:00 ` Bartosz Golaszewski
2018-12-02 21:56 ` Uwe Kleine-König
2018-12-02 22:20 ` Bartosz Golaszewski
2018-12-03 10:23 ` Bartosz Golaszewski
2018-12-03 10:49 ` Uwe Kleine-König
2018-12-03 10:57 ` Bartosz Golaszewski
2018-12-03 11:06 ` Uwe Kleine-König
2018-12-05 12:19 ` Linus Walleij
2018-12-05 12:38 ` Bartosz Golaszewski
2018-12-05 12:55 ` Linus Walleij
2018-12-17 10:32 ` Bartosz Golaszewski
2018-12-17 12:59 ` Uwe Kleine-König
2018-12-17 13:59 ` Bartosz Golaszewski
2018-12-05 13:20 ` Uwe Kleine-König
2018-12-14 14:07 ` Linus Walleij [this message]
2018-12-17 11:19 ` Uwe Kleine-König
2018-11-20 13:40 ` [PATCH 2/2] gpio: mockup: use irq_sim_fire_edge() Bartosz Golaszewski
2018-12-03 11:09 ` Uwe Kleine-König
2018-12-11 14:15 ` Uwe Kleine-König
2018-12-11 15:38 ` 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=CACRpkdaTNFFevE-hauMn17cXbsoddkw_Bp3WyBHbzG1+dohxew@mail.gmail.com \
--to=linus.walleij@linaro.org \
--cc=bgolaszewski@baylibre.com \
--cc=brgl@bgdev.pl \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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).