From: Linus Walleij <linus.walleij@linaro.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Javier Martinez Canillas <javier.martinez@collabora.co.uk>,
"linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>
Subject: [GIT PULL] GPIO fixes for v3.12
Date: Sat, 5 Oct 2013 20:35:44 +0200 [thread overview]
Message-ID: <CACRpkdZBzFTtoFHTiFS8HXXFy_6cmuMTTTv6C-VLubc64NgsQA@mail.gmail.com> (raw)
Hi Linus,
here are two GPIO fixes for v3.12, both dealing with setting up
IRQs properly on the OMAP for the device tree boot path.
The subject as such is pretty tricky and we're still discussing how
we want to handle this long-term, but this fix is widely ACKed
and tested.
In the absence of linux-next I've done some additional builds and
tests to make sure nothing is wrecked.
Please pull it in!
Yours,
Linus Walleij
The following changes since commit 272b98c6455f00884f0350f775c5342358ebb73f:
Linux 3.12-rc1 (2013-09-16 16:17:51 -0400)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/linusw/linux-gpio.git
tags/gpio-v3.12-2
for you to fetch changes up to fac7fa162a19100298d5d91359960037dc5bfca9:
gpio/omap: auto-setup a GPIO when used as an IRQ (2013-10-01 13:16:02 +0200)
----------------------------------------------------------------
Fixes for the GPIO tree for v3.12:
- Two patches for the OMAP driver, dealing with setting up IRQs
properly on the device tree boot path.
----------------------------------------------------------------
Javier Martinez Canillas (2):
gpio/omap: maintain GPIO and IRQ usage separately
gpio/omap: auto-setup a GPIO when used as an IRQ
drivers/gpio/gpio-omap.c | 158 ++++++++++++++++++++++++++++++-----------------
1 file changed, 101 insertions(+), 57 deletions(-)
reply other threads:[~2013-10-05 18:35 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=CACRpkdZBzFTtoFHTiFS8HXXFy_6cmuMTTTv6C-VLubc64NgsQA@mail.gmail.com \
--to=linus.walleij@linaro.org \
--cc=javier.martinez@collabora.co.uk \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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;
as well as URLs for NNTP newsgroup(s).