From: Doug Anderson <dianders@chromium.org>
To: Heiko Stuebner <heiko@sntech.de>,
Linus Walleij <linus.walleij@linaro.org>
Cc: Sonny Rao <sonnyrao@chromium.org>,
Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Chris Zhong <zyw@rock-chips.com>,
linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org,
Doug Anderson <dianders@chromium.org>,
linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH v2 0/2] Pinctrl fixes for rockchip
Date: Wed, 19 Nov 2014 14:51:31 -0800 [thread overview]
Message-ID: <1416437493-25588-1-git-send-email-dianders@chromium.org> (raw)
These two patches fix some pinctrl issues on rockchip. The first
fixes a real issue where interrupts were being left on in
suspend/resume and waking the system up when they shouldn't. The
second fixes purely theoretical problems but seems clean.
I've tested these patches more extensively on a non-mainline tree but
have done basic compile and boot testing on mainline. I don't have
suspend/resume working so well on mainline yet, so I haven't tested
fully there.
Changes in v2:
- Spread out code (heiko)
Doug Anderson (2):
pinctrl: rockchip: Handle wakeup pins
pinctrl: rockchip: Fix enable/disable/mask/unmask
drivers/pinctrl/pinctrl-rockchip.c | 57 ++++++++++++++++++++++++++++++++++++--
1 file changed, 54 insertions(+), 3 deletions(-)
--
2.1.0.rc2.206.gedb03e5
next reply other threads:[~2014-11-19 22:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-19 22:51 Doug Anderson [this message]
2014-11-19 22:51 ` [PATCH v2 1/2] pinctrl: rockchip: Handle wakeup pins Doug Anderson
2014-11-28 8:05 ` Linus Walleij
2014-11-19 22:51 ` [PATCH v2 2/2] pinctrl: rockchip: Fix enable/disable/mask/unmask Doug Anderson
2014-11-28 8:06 ` Linus Walleij
2014-11-26 17:56 ` [PATCH v2 0/2] Pinctrl fixes for rockchip Heiko Stübner
2014-11-28 9:22 ` 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=1416437493-25588-1-git-send-email-dianders@chromium.org \
--to=dianders@chromium.org \
--cc=dmitry.torokhov@gmail.com \
--cc=heiko@sntech.de \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=sonnyrao@chromium.org \
--cc=zyw@rock-chips.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;
as well as URLs for NNTP newsgroup(s).