From: Marc Zyngier <maz@kernel.org>
To: Talel Shenhar <talel@amazon.com>
Cc: <tglx@linutronix.de>, <jason@lakedaemon.net>,
<linux-kernel@vger.kernel.org>, <dwmw@amazon.co.uk>,
<benh@kernel.crashing.org>, <hhhawa@amazon.com>,
<ronenk@amazon.com>, <jonnyc@amazon.com>, <hanochu@amazon.com>,
<barakw@amazon.com>
Subject: Re: [PATCH 1/1] irqchip: al-fic: add support for irq retrigger
Date: Mon, 09 Sep 2019 10:40:45 +0100 [thread overview]
Message-ID: <86d0g9st7m.wl-maz@kernel.org> (raw)
In-Reply-To: <1568018358-18985-1-git-send-email-talel@amazon.com>
On Mon, 09 Sep 2019 09:39:18 +0100,
Talel Shenhar <talel@amazon.com> wrote:
Hi Talel,
>
> Introduce interrupts retrigger support for Amazon's Annapurna Labs Fabric
> Interrupt Controller.
>
> Signed-off-by: Talel Shenhar <talel@amazon.com>
> ---
> drivers/irqchip/irq-al-fic.c | 12 ++++++++++++
> 1 file changed, 12 insertions(+)
>
> diff --git a/drivers/irqchip/irq-al-fic.c b/drivers/irqchip/irq-al-fic.c
> index 1a57cee..0b0a737 100644
> --- a/drivers/irqchip/irq-al-fic.c
> +++ b/drivers/irqchip/irq-al-fic.c
> @@ -15,6 +15,7 @@
>
> /* FIC Registers */
> #define AL_FIC_CAUSE 0x00
> +#define AL_FIC_SET_CAUSE 0x08
> #define AL_FIC_MASK 0x10
> #define AL_FIC_CONTROL 0x28
>
> @@ -126,6 +127,16 @@ static void al_fic_irq_handler(struct irq_desc *desc)
> chained_irq_exit(irqchip, desc);
> }
>
> +static int al_fic_irq_retrigger(struct irq_data *data)
> +{
> + struct irq_chip_generic *gc = irq_data_get_irq_chip_data(data);
> + struct al_fic *fic = gc->private;
> +
> + writel_relaxed(BIT(data->hwirq), fic->base + AL_FIC_SET_CAUSE);
> +
> + return 1;
> +}
> +
> static int al_fic_register(struct device_node *node,
> struct al_fic *fic)
> {
> @@ -159,6 +170,7 @@ static int al_fic_register(struct device_node *node,
> gc->chip_types->chip.irq_unmask = irq_gc_mask_clr_bit;
> gc->chip_types->chip.irq_ack = irq_gc_ack_clr_bit;
> gc->chip_types->chip.irq_set_type = al_fic_irq_set_type;
> + gc->chip_types->chip.irq_retrigger = al_fic_irq_retrigger;
> gc->chip_types->chip.flags = IRQCHIP_SKIP_SET_WAKE;
> gc->private = fic;
Looks good to me. Is this a fix or a new feature? If the former, I can
queue it up for -rc1.
M.
--
Jazz is not dead, it just smells funny.
next prev parent reply other threads:[~2019-09-09 9:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-09 8:39 [PATCH 1/1] irqchip: al-fic: add support for irq retrigger Talel Shenhar
2019-09-09 9:40 ` Marc Zyngier [this message]
2019-09-09 10:18 ` [UNVERIFIED SENDER] " Shenhar, Talel
2019-10-14 18:38 ` [tip: irq/urgent] irqchip/al-fic: Add " tip-bot2 for Talel Shenhar
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=86d0g9st7m.wl-maz@kernel.org \
--to=maz@kernel.org \
--cc=barakw@amazon.com \
--cc=benh@kernel.crashing.org \
--cc=dwmw@amazon.co.uk \
--cc=hanochu@amazon.com \
--cc=hhhawa@amazon.com \
--cc=jason@lakedaemon.net \
--cc=jonnyc@amazon.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ronenk@amazon.com \
--cc=talel@amazon.com \
--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