From: linus.walleij@linaro.org (Linus Walleij)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 3/4] pinctrl: sunxi: Properly handle level triggered gpio interrupts
Date: Fri, 4 Jul 2014 23:35:21 +0200 [thread overview]
Message-ID: <CACRpkdbYOCUO1KiRGE7dEeo3cycafns2qLrHhdw=ujNjPDHfUg@mail.gmail.com> (raw)
In-Reply-To: <1404051062-24079-4-git-send-email-hdegoede@redhat.com>
On Sun, Jun 29, 2014 at 4:11 PM, Hans de Goede <hdegoede@redhat.com> wrote:
> For level triggered gpio interrupts we need to use handle_fasteoi_irq,
> like we do with the irq-sunxi-nmi driver. This is necessary to give threaded
> interrupt handlers a chance to actuall clear the source of the interrupt
> (which may involve sleeping waiting for i2c / spi / mmc transfers), before
> acknowledging the interrupt.
>
> Signed-off-by: Hans de Goede <hdegoede@redhat.com>
Patch applied with Maxime's ACK.
Yours,
Linus Walleij
next prev parent reply other threads:[~2014-07-04 21:35 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-29 14:10 [PATCH v3 0/4] pinctrl: sunxi: Properly handle level triggered gpio irqs Hans de Goede
2014-06-29 14:10 ` [PATCH v3 1/4] pinctrl: sunxi: Add IRQCHIP_SKIP_SET_WAKE flag for pinctrl irq chip Hans de Goede
2014-07-04 21:32 ` Linus Walleij
2014-06-29 14:11 ` [PATCH v3 2/4] pinctrl: sunxi: Move setting of mux to irq type from unmask to request_resources Hans de Goede
2014-07-04 21:33 ` Linus Walleij
2014-06-29 14:11 ` [PATCH v3 3/4] pinctrl: sunxi: Properly handle level triggered gpio interrupts Hans de Goede
2014-07-01 14:41 ` Maxime Ripard
2014-07-04 21:35 ` Linus Walleij [this message]
2014-06-29 14:11 ` [PATCH v3 4/4] pinctrl: sunxi: Define enable / disable irq callbacks for level triggered irqs Hans de Goede
2014-07-01 14:45 ` Maxime Ripard
2014-07-04 21:39 ` Linus Walleij
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='CACRpkdbYOCUO1KiRGE7dEeo3cycafns2qLrHhdw=ujNjPDHfUg@mail.gmail.com' \
--to=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.