From: Marc Zyngier <marc.zyngier@arm.com>
To: Bartosz Golaszewski <brgl@bgdev.pl>
Cc: "Linus Walleij" <linus.walleij@linaro.org>,
"Thomas Gleixner" <tglx@linutronix.de>,
"Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>,
linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org,
"Bartosz Golaszewski" <bgolaszewski@baylibre.com>
Subject: Re: [PATCH v6 1/7] irq/irq_sim: add irq_set_type() callback
Date: Tue, 19 Feb 2019 16:14:49 +0000 [thread overview]
Message-ID: <20190219161449.26e99a2b@why.wild-wind.fr.eu.org> (raw)
In-Reply-To: <20190219160650.9614-2-brgl@bgdev.pl>
On Tue, 19 Feb 2019 17:06:44 +0100
Bartosz Golaszewski <brgl@bgdev.pl> wrote:
> From: Bartosz Golaszewski <bgolaszewski@baylibre.com>
>
> Implement the irq_set_type() callback and call irqd_set_trigger_type()
> internally so that users interested in the configured trigger type can
> later retrieve it using irqd_get_trigger_type(). We only support edge
> trigger types.
>
> Signed-off-by: Bartosz Golaszewski <bgolaszewski@baylibre.com>
> ---
> kernel/irq/irq_sim.c | 12 ++++++++++++
> 1 file changed, 12 insertions(+)
>
> diff --git a/kernel/irq/irq_sim.c b/kernel/irq/irq_sim.c
> index 98a20e1594ce..b992f88c5613 100644
> --- a/kernel/irq/irq_sim.c
> +++ b/kernel/irq/irq_sim.c
> @@ -25,10 +25,22 @@ static void irq_sim_irqunmask(struct irq_data *data)
> irq_ctx->enabled = true;
> }
>
> +static int irq_sim_set_type(struct irq_data *data, unsigned int type)
> +{
> + /* We only support rising and falling edge trigger types. */
> + if (type & ~IRQ_TYPE_EDGE_BOTH)
> + return -EINVAL;
> +
> + irqd_set_trigger_type(data, type);
> +
> + return 0;
> +}
> +
> static struct irq_chip irq_sim_irqchip = {
> .name = "irq_sim",
> .irq_mask = irq_sim_irqmask,
> .irq_unmask = irq_sim_irqunmask,
> + .irq_set_type = irq_sim_set_type,
> };
>
> static void irq_sim_handle_irq(struct irq_work *work)
Acked-by: Marc Zyngier <marc.zyngier@arm.com>
M.
--
Without deviation from the norm, progress is not possible.
next prev parent reply other threads:[~2019-02-19 16:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-19 16:06 [PATCH v6 0/7] gpio: mockup: improve the user-space testing interface Bartosz Golaszewski
2019-02-19 16:06 ` [PATCH v6 1/7] irq/irq_sim: add irq_set_type() callback Bartosz Golaszewski
2019-02-19 16:14 ` Marc Zyngier [this message]
2019-02-19 16:36 ` Bartosz Golaszewski
2019-02-19 16:06 ` [PATCH v6 2/7] gpio: mockup: add locking Bartosz Golaszewski
2019-02-19 16:06 ` [PATCH v6 3/7] gpio: mockup: implement get_multiple() Bartosz Golaszewski
2019-02-19 16:06 ` [PATCH v6 4/7] gpio: mockup: don't create the debugfs link named after the label Bartosz Golaszewski
2019-02-19 16:06 ` [PATCH v6 5/7] gpio: mockup: change the type of 'offset' to unsigned int Bartosz Golaszewski
2019-02-19 16:06 ` [PATCH v6 6/7] gpio: mockup: change the signature of unlocked get/set helpers Bartosz Golaszewski
2019-02-19 16:06 ` [PATCH v6 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=20190219161449.26e99a2b@why.wild-wind.fr.eu.org \
--to=marc.zyngier@arm.com \
--cc=bgolaszewski@baylibre.com \
--cc=brgl@bgdev.pl \
--cc=linus.walleij@linaro.org \
--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
all inboxes | Powered by JetHome®