From: Russell King - ARM Linux <linux@arm.linux.org.uk>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: Hans de Goede <hdegoede@redhat.com>,
LKML <linux-kernel@vger.kernel.org>,
Carlo Caione <carlo.caione@gmail.com>
Subject: Re: [PATCH] irq: Add a new IRQF_ACK_BEFORE_UNMASK irq flag
Date: Wed, 12 Mar 2014 10:45:23 +0000 [thread overview]
Message-ID: <20140312104523.GE21483@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <alpine.DEB.2.02.1403120944270.18573@ionos.tec.linutronix.de>
On Wed, Mar 12, 2014 at 11:38:24AM +0100, Thomas Gleixner wrote:
> If the interrupt chip has this behaviour then handle_level_irq as the
> flow handler is the wrong thing to start with because it always acks
> before calling the handler.
This sounds like the situation with the Dove PMC irqchip too, except
that it has the additional complication that "acking" any interrupt is
potentially distructive to other pending interrupts, so should be done
as infrequently as possible.
> +void unmask_threaded_irq(struct irq_desc *desc)
> +{
> + struct irq_chip *chip = desc->irq_data.chip;
> +
> + if (chip->flags & IRQCHIP_EOI_THREADED)
> + chip->irq_eoi(&desc->irq_data);
> +
> + if (chip->irq_unmask) {
> + desc->irq_data.chip->irq_unmask(&desc->irq_data);
ITYM:
chip->irq_unmask(&desc->irq_data);
--
FTTC broadband for 0.8mile line: now at 9.7Mbps down 460kbps up... slowly
improving, and getting towards what was expected from it.
next prev parent reply other threads:[~2014-03-12 10:45 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-11 23:13 Hans de Goede
2014-03-12 8:55 ` Hans de Goede
2014-03-12 10:38 ` Thomas Gleixner
2014-03-12 10:45 ` Russell King - ARM Linux [this message]
2014-03-12 10:48 ` Thomas Gleixner
2014-03-12 17:08 ` Hans de Goede
2014-03-12 22:16 ` Thomas Gleixner
2014-03-13 13:09 ` Sebastian Andrzej Siewior
2014-03-13 13:32 ` Thomas Gleixner
2014-03-13 13:37 ` Sebastian Andrzej Siewior
2014-03-13 14:32 ` [PATCH] irq: Add a new IRQF_ACK_BEFORE_UNMASK irq flagq Thomas Gleixner
2014-03-13 16:20 ` Hans de Goede
2014-03-13 16:24 ` Thomas Gleixner
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=20140312104523.GE21483@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--cc=carlo.caione@gmail.com \
--cc=hdegoede@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--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
all inboxes | Powered by JetHome®