From: heiko@sntech.de (Heiko Stübner)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 3/3] ARM: rockchip: enable PMU_GPIOINT_WAKEUP_EN when entering shallow suspend
Date: Thu, 06 Aug 2015 13:10:55 +0200 [thread overview]
Message-ID: <3564263.VnOXW7qXSg@diego> (raw)
In-Reply-To: <CAD=FV=W0L_0iM+15BAUfTA2ij5Ac90aVW9JZYyDhHMDNT2ZUMg@mail.gmail.com>
Am Mittwoch, 5. August 2015, 18:55:52 schrieb Doug Anderson:
> Heiko,
>
> On Tue, Aug 4, 2015 at 3:51 PM, Heiko St?bner <heiko@sntech.de> wrote:
> > PMU_GPIOINT_WAKEUP_EN seems needed when entering the shallow suspend
> > (with logic staying on) but does not seem to be needed for the deep
> > suspend for unknown reasons.
> > Testing revealed that this setting really is necessary to reliably
> > resume the veyron devices from suspend.
> >
> > Reported-by: Chris Zhong <zyw@rock-chips.com>
> > Signed-off-by: Heiko Stuebner <heiko@sntech.de>
> > ---
> >
> > arch/arm/mach-rockchip/pm.c | 9 ++++++---
> > arch/arm/mach-rockchip/pm.h | 1 +
> > 2 files changed, 7 insertions(+), 3 deletions(-)
>
> Very odd, but OK by me...
Hopefully we'll get an explaination from the ic-people soon-ish.
> Hopefully we'll eventually end up being
> able to use deep suspend on mainline. That'd be nice, wouldn't it?
hehe ... yep, one of the big remaining projects :-)
next prev parent reply other threads:[~2015-08-06 11:10 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-04 22:50 [PATCH v3 1/3] ARM: rockchip: rename osc_switch_to_32k variable Heiko Stübner
2015-08-04 22:51 ` [PATCH v3 2/3] ARM: rockchip: set correct stabilization thresholds in suspend Heiko Stübner
2015-08-05 10:41 ` Chris Zhong
2015-08-06 1:54 ` Doug Anderson
2015-08-04 22:51 ` [PATCH v3 3/3] ARM: rockchip: enable PMU_GPIOINT_WAKEUP_EN when entering shallow suspend Heiko Stübner
2015-08-05 10:51 ` Chris Zhong
2015-08-06 1:55 ` Doug Anderson
2015-08-06 11:10 ` Heiko Stübner [this message]
2015-08-05 10:36 ` [PATCH v3 1/3] ARM: rockchip: rename osc_switch_to_32k variable Chris Zhong
2015-08-05 23:45 ` Doug Anderson
2015-08-06 11:11 ` Heiko Stübner
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=3564263.VnOXW7qXSg@diego \
--to=heiko@sntech.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox