From: Thomas Gleixner <tglx@linutronix.de>
To: Marc Zyngier <marc.zyngier@arm.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
jeffy <jeffy.chen@rock-chips.com>,
Brian Norris <briannorris@chromium.org>,
dianders@chromium.org, tfiga@chromium.org
Subject: Re: [patch 1/2] genirq: Handle NOAUTOEN interrupt setup proper
Date: Wed, 31 May 2017 17:18:38 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.20.1705311715020.2356@nanos> (raw)
In-Reply-To: <333511ca-9c5d-1a78-1c29-ebd172d6fe2f@arm.com>
On Wed, 31 May 2017, Marc Zyngier wrote:
> On 31/05/17 10:58, Thomas Gleixner wrote:
> > #define __irqd_to_state(d) ACCESS_PRIVATE((d)->common, state_use_accessors)
> > @@ -329,6 +330,11 @@ static inline void irqd_clr_activated(st
> > __irqd_to_state(d) &= ~IRQD_ACTIVATED;
> > }
> >
> > +static inline bool irqd_is_started_up(struct irq_data *d)
>
> nit: since we have set/clr_started, consider making this is_started
> (without the up)? Or add the _up to clr/set?
Sure.
> > +{
> > + return __irqd_to_state(d) & IRQD_IRQ_STARTED_UP;
> > +}
> > +
> > #undef __irqd_to_state
> >
> > static inline irq_hw_number_t irqd_to_hwirq(struct irq_data *d)
> > --- a/kernel/irq/chip.c
> > +++ b/kernel/irq/chip.c
> > @@ -185,37 +185,71 @@ static void irq_state_set_masked(struct
> > irqd_set(&desc->irq_data, IRQD_IRQ_MASKED);
> > }
> >
> > +static void irq_state_clr_started(struct irq_desc *desc)
> > +{
> > + irqd_clear(&desc->irq_data, IRQD_IRQ_STARTED_UP);
> > +}
> > +
> > +static void irq_state_set_started(struct irq_desc *desc)
> > +{
> > + irqd_set(&desc->irq_data, IRQD_IRQ_STARTED_UP);
> > +}
> > +
> > int irq_startup(struct irq_desc *desc, bool resend)
> > {
> > int ret = 0;
> >
> > - irq_state_clr_disabled(desc);
> > + if (irqd_is_started_up(&desc->irq_data))
> > + return 0;
> > +
>
> How about:
> if (irqd_is_started_up(&desc->irq_data)) {
> irq_enable(desc);
> return 0;
Why would we do that? I rather have a WARN_ON() there as this should never
happen.
> > + /*
> > + * This must be called even if the interrupt was never started up,
> > + * because the activation can happen before the interrupt is
> > + * available for request/startup. It has it's own state tracking so
> > + * it's safe to call it unconditonally.
>
> unconditionally?
Oops.
> > extern int irq_startup(struct irq_desc *desc, bool resend);
> > extern void irq_shutdown(struct irq_desc *desc);
> > +extern void irq_enable_or_startup(struct irq_desc *desc);
> > extern void irq_enable(struct irq_desc *desc);
> > extern void irq_disable(struct irq_desc *desc);
> > extern void irq_percpu_enable(struct irq_desc *desc, unsigned int cpu);
> > --- a/kernel/irq/manage.c
> > +++ b/kernel/irq/manage.c
> > @@ -533,7 +533,7 @@ void __enable_irq(struct irq_desc *desc)
> > goto err_out;
> > /* Prevent probing on this irq: */
> > irq_settings_set_noprobe(desc);
> > - irq_enable(desc);
> > + irq_enable_or_startup(desc);
>
> and make this irq_startup(desc, false)?
Ah, now I see where you were heading with that irq_startup()
modification. Makes sense, but let me think about it.
Thanks,
tglx
next prev parent reply other threads:[~2017-05-31 15:18 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-31 9:58 [patch 0/2] genirq: Handle NOAUTOEN interrupts correctly Thomas Gleixner
2017-05-31 9:58 ` [patch 1/2] genirq: Handle NOAUTOEN interrupt setup proper Thomas Gleixner
2017-05-31 13:54 ` Marc Zyngier
2017-05-31 15:18 ` Thomas Gleixner [this message]
2017-06-04 12:47 ` [tip:irq/core] " tip-bot for Thomas Gleixner
2017-05-31 9:58 ` [patch 2/2] genirq: Warn when IRQ_NOAUTOEN is used with shared interrupts Thomas Gleixner
2017-06-04 12:48 ` [tip:irq/core] " tip-bot for Thomas Gleixner
2017-09-06 6:00 ` [2/2] " Paul Burton
2017-09-06 8:16 ` Thomas Gleixner
2017-09-06 14:01 ` Paul Burton
2017-09-06 14:14 ` Thomas Gleixner
2017-09-07 1:18 ` Paul Burton
2017-09-07 23:25 ` [RFC PATCH v1 0/9] Support shared percpu interrupts; clean up MIPS hacks Paul Burton
2017-09-07 23:25 ` [RFC PATCH v1 1/9] genirq: Allow shared interrupt users to opt into IRQ_NOAUTOEN Paul Burton
2017-09-07 23:25 ` [RFC PATCH v1 2/9] genirq: Support shared per_cpu_devid interrupts Paul Burton
2017-09-25 21:06 ` Thomas Gleixner
2017-09-26 12:00 ` Thomas Gleixner
2017-10-19 14:08 ` Thomas Gleixner
2017-09-07 23:25 ` [RFC PATCH v1 3/9] genirq: Introduce irq_is_percpu_devid() Paul Burton
2017-09-07 23:25 ` [RFC PATCH v1 4/9] MIPS: Remove perf_irq interrupt sharing fallback Paul Burton
2017-09-07 23:25 ` [RFC PATCH v1 5/9] MIPS: Remove perf_irq Paul Burton
2017-09-07 23:25 ` [RFC PATCH v1 6/9] MIPS: perf: percpu_devid interrupt support Paul Burton
2017-10-19 14:12 ` Thomas Gleixner
2017-09-07 23:25 ` [RFC PATCH v1 7/9] MIPS: cevt-r4k: " Paul Burton
2017-09-07 23:25 ` [RFC PATCH v1 8/9] irqchip: mips-cpu: Set timer, FDC & perf interrupts percpu_devid Paul Burton
2017-09-07 23:25 ` [RFC PATCH v1 9/9] irqchip: mips-gic: Remove gic_all_vpes_local_irq_controller Paul Burton
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=alpine.DEB.2.20.1705311715020.2356@nanos \
--to=tglx@linutronix.de \
--cc=briannorris@chromium.org \
--cc=dianders@chromium.org \
--cc=jeffy.chen@rock-chips.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marc.zyngier@arm.com \
--cc=tfiga@chromium.org \
/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®