Doug Anderson <dianders at chromium.org> writes: > Hi, > > On Mon, Dec 1, 2014 at 2:08 PM, Doug Anderson <dianders at chromium.org> wrote: >> Hi, >> >> On Mon, Dec 1, 2014 at 11:51 AM, Kevin Hilman <khilman at kernel.org> wrote: >>> Chris Zhong <zyw at 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
