From: Thomas Gleixner <tglx@linutronix.de>
To: Carlo Caione <carlo.caione@gmail.com>
Cc: linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
Maxime Ripard <maxime.ripard@free-electrons.com>,
Hans De Goede <hdegoede@redhat.com>,
emilio@elopez.com.ar, linux-sunxi@googlegroups.com,
t.figa@samsung.com
Subject: Re: [linux-sunxi] Re: [PATCH] irq: Add new flag to ack level-triggered interrupts before unmasking
Date: Fri, 7 Feb 2014 18:24:40 +0100 (CET) [thread overview]
Message-ID: <alpine.DEB.2.02.1402071721350.21991@ionos.tec.linutronix.de> (raw)
In-Reply-To: <CAOQ7t2b5qVTUXOB4iWAOoTehm=u6zxP0-zQmirSF0DvEk8KddQ@mail.gmail.com>
On Fri, 7 Feb 2014, Carlo Caione wrote:
> Yeah, no really difference between threaded and non threaded.
> For the record, from a mail exchange with Allwinner's engineers: "the
> NMI module is a signal conversion module. It catches the NMI pin's
> state and generates irq to GIC", so GIC does not really ACK anything.
> BTW being a dummy "signal conversion module" this is probably why I
> still need to clear the pending status even though my IRQ line has
> already been cleared.
A pretty useless signal conversion module it seems creating a big mess
for a single interrupt line :)
> > I'm not against having a flag, but this should be done less convoluted
> > and have proper names which make the use case clear along with a good
> > technical explanation of the flag in the comment.
>
> Ok, at this point do you think that a patch in the core could be
> useful or is it better to stick with modifying the unmask callback?
Not sure, really, but I tend to a core patch. Though we really want to
know whether the issue is threaded only or not. If it's a general
issue then this wants to go into unmask_irq() itself and not into an
extra unmask_threaded_irq() function.
Thanks,
tglx
next prev parent reply other threads:[~2014-02-07 17:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-06 21:11 Carlo Caione
2014-02-06 21:14 ` Thomas Gleixner
2014-02-06 21:21 ` [linux-sunxi] " Carlo Caione
2014-02-06 21:54 ` Thomas Gleixner
2014-02-07 10:08 ` Carlo Caione
2014-02-07 11:51 ` Thomas Gleixner
2014-02-07 15:41 ` Carlo Caione
2014-02-07 17:24 ` Thomas Gleixner [this message]
2014-02-07 22:31 ` Carlo Caione
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.02.1402071721350.21991@ionos.tec.linutronix.de \
--to=tglx@linutronix.de \
--cc=carlo.caione@gmail.com \
--cc=emilio@elopez.com.ar \
--cc=hdegoede@redhat.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sunxi@googlegroups.com \
--cc=maxime.ripard@free-electrons.com \
--cc=t.figa@samsung.com \
/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®