From: maxime.ripard@free-electrons.com (Maxime Ripard)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 2/4] pinctrl: sunxi: Move setting of mux to irq type from unmask to request_resources
Date: Tue, 17 Jun 2014 22:34:30 +0200 [thread overview]
Message-ID: <20140617203430.GC19730@lukather> (raw)
In-Reply-To: <1402691764-17562-3-git-send-email-hdegoede@redhat.com>
On Fri, Jun 13, 2014 at 10:36:02PM +0200, Hans de Goede wrote:
> With level triggered interrupt mask / unmask will get called for each
> interrupt, doing the somewhat expensive mux setting on each unmask thus is
> not a good idea. Instead add a request_resources callback and do it there.
>
> Signed-off-by: Hans de Goede <hdegoede@redhat.com>
Acked-by: Maxime Ripard <maxime.ripard@free-electrons.com>
Thanks!
Maxime
--
Maxime Ripard, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20140617/3d3df746/attachment.sig>
next prev parent reply other threads:[~2014-06-17 20:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-13 20:36 [PATCH v2 0/4] pinctrl: sunxi: Properly handle level triggered gpio irqs Hans de Goede
2014-06-13 20:36 ` [PATCH v2 1/4] pinctrl: sunxi: Add IRQCHIP_SKIP_SET_WAKE flag for pinctrl irq chip Hans de Goede
2014-06-13 20:36 ` [PATCH v2 2/4] pinctrl: sunxi: Move setting of mux to irq type from unmask to request_resources Hans de Goede
2014-06-17 20:34 ` Maxime Ripard [this message]
2014-06-13 20:36 ` [PATCH v2 3/4] pinctrl: sunxi: Properly handle level triggered gpio interrupts Hans de Goede
2014-06-13 20:36 ` [PATCH v2 4/4] pinctrl: sunxi: Define enable / disable irq callbacks for level triggered irqs Hans de Goede
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=20140617203430.GC19730@lukather \
--to=maxime.ripard@free-electrons.com \
--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.