From: khilman@kernel.org (Kevin Hilman)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v10 0/4] This suspend patch is only support cut off the power of cpu and some external
Date: Mon, 01 Dec 2014 17:26:26 -0800 [thread overview]
Message-ID: <7hmw763kql.fsf@deeprootsystems.com> (raw)
In-Reply-To: <CAD=FV=XuQk17CTNKJY++J+w9Ab9_OUX0ca0A99m7yKPAWSs2=w@mail.gmail.com> (Doug Anderson's message of "Mon, 1 Dec 2014 17:07:39 -0800")
Doug Anderson <dianders@chromium.org> writes:
> Hi,
>
> On Mon, Dec 1, 2014 at 2:08 PM, Doug Anderson <dianders@chromium.org> wrote:
>> Hi,
>>
>> On Mon, Dec 1, 2014 at 11:51 AM, Kevin Hilman <khilman@kernel.org> wrote:
>>> Chris Zhong <zyw@rock-chips.com> writes:
>>>
>>>> devices, since we still lack power_domain driver, so the other power rail
>>>> of rk3288 need keep power on.
>>>> I have tested it on rk3288-evb board, atop next-20141112. goto suspend by type
>>>> "echo mem > /sys/power/state", vdd_cpu is about 0mv by measuring, so it can be
>>>> determined in sleep mode, then press power button to wakeup it.
>>>
>>> I tested this on top of today's linux-next (next-20141201) and it
>>> suspends, but doesn't wake up from any of the button presses. What
>>> wakeup sources are configured for the rk3288-evb-rk808?
>>
>> Just to close the loop (I talked with Kevin over IM about this, too):
>>
>> I have a huge description of how I tested this as part of my patch at
>> <https://patchwork.kernel.org/patch/5414941/>. Chris: I think Kevin
>> has asked you several times to include information like this in your
>> cover letter. Please, please, please can you try to remember to do
>> this?
>
> Talked to Chris offline. He said that in his tests the other patches
> weren't needed, so he didn't list any other patches. Things just
> worked for him. ...so I guess he did post the instructions that
> worked for him. Sorry for the complaint. Possibly things are
> different on "next-20141112" and that's where Chris said he tested.
This series doesn't apply cleanly to next-20141112. Manually applying
(with fuzz), it boots but I have the same results: it suspends, but none
of the buttons wake it up.
Kevin
next prev parent reply other threads:[~2014-12-02 1:26 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-01 8:52 [PATCH v10 0/4] This suspend patch is only support cut off the power of cpu and some external Chris Zhong
2014-12-01 8:52 ` [PATCH v10 1/4] ARM: rockchip: add suspend and resume for RK3288 Chris Zhong
2014-12-01 8:52 ` [PATCH v10 3/4] ARM: dts: add RK3288 suspend support Chris Zhong
2014-12-01 8:52 ` [PATCH v10 4/4] ARM: dts: rockchip: add suspend settings for rk3288-evb-rk808 Chris Zhong
2014-12-01 22:19 ` Doug Anderson
2014-12-01 19:51 ` [PATCH v10 0/4] This suspend patch is only support cut off the power of cpu and some external Kevin Hilman
2014-12-01 22:08 ` Doug Anderson
2014-12-02 1:07 ` Doug Anderson
2014-12-02 1:26 ` Kevin Hilman [this message]
2014-12-03 13:55 ` Chris Zhong
2014-12-03 19:23 ` Kevin Hilman
2014-12-07 23:46 ` Heiko Stübner
2014-12-02 1:18 ` Chris Zhong
2015-01-02 20:57 ` 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=7hmw763kql.fsf@deeprootsystems.com \
--to=khilman@kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).