From: Geert Uytterhoeven <geert+renesas@glider.be>
To: Linus Walleij <linus.walleij@linaro.org>,
Alexandre Courbot <gnurou@gmail.com>
Cc: linux-gpio@vger.kernel.org, linux-sh@vger.kernel.org,
Geert Uytterhoeven <geert+renesas@glider.be>
Subject: [PATCH 0/3] gpio: rcar: Fix wake up using gpio-keys with PM domain
Date: Wed, 18 Mar 2015 18:41:06 +0000 [thread overview]
Message-ID: <1426704069-26389-1-git-send-email-geert+renesas@glider.be> (raw)
Hi,
This patch series contains a few cleanups and updates for the Renesas
R-Car GPIO driver, and fixes wake-up from s2ram using gpio-keys when
using a PM Domain to manage the module clock.
It was tested on r8a7791/koelsch.
Thanks!
Geert Uytterhoeven (3):
gpio: rcar: Use local variable gpio_chip in gpio_rcar_probe()
gpio: rcar: Add more register documentation
gpio: rcar: Prevent module clock disable when wake-up is enabled
drivers/gpio/gpio-rcar.c | 63 +++++++++++++++++++++++++++++++++++-------------
1 file changed, 46 insertions(+), 17 deletions(-)
--
1.9.1
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
next reply other threads:[~2015-03-18 18:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-18 18:41 Geert Uytterhoeven [this message]
2015-03-18 18:41 ` [PATCH 1/3] gpio: rcar: Use local variable gpio_chip in gpio_rcar_probe() Geert Uytterhoeven
2015-03-26 9:18 ` Linus Walleij
2015-03-18 18:41 ` [PATCH 2/3] gpio: rcar: Add more register documentation Geert Uytterhoeven
2015-03-26 9:19 ` Linus Walleij
2015-03-18 18:41 ` [PATCH 3/3] gpio: rcar: Prevent module clock disable when wake-up is enabled Geert Uytterhoeven
2015-03-26 9:26 ` 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=1426704069-26389-1-git-send-email-geert+renesas@glider.be \
--to=geert+renesas@glider.be \
--cc=gnurou@gmail.com \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-sh@vger.kernel.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).