Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932653AbaLAWIn (ORCPT ); Mon, 1 Dec 2014 17:08:43 -0500 Received: from mail-vc0-f169.google.com ([209.85.220.169]:42951 "EHLO mail-vc0-f169.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932636AbaLAWIk (ORCPT ); Mon, 1 Dec 2014 17:08:40 -0500 MIME-Version: 1.0 In-Reply-To: <7htx1f409k.fsf@deeprootsystems.com> References: <1417423940-1669-1-git-send-email-zyw@rock-chips.com> <7htx1f409k.fsf@deeprootsystems.com> Date: Mon, 1 Dec 2014 14:08:38 -0800 X-Google-Sender-Auth: Rv2OwldyI-3Y0XExuS5SiDr13-U Message-ID: Subject: Re: [PATCH v10 0/4] This suspend patch is only support cut off the power of cpu and some external From: Doug Anderson To: Kevin Hilman Cc: Chris Zhong , =?UTF-8?Q?Heiko_St=C3=BCbner?= , Mike Turquette , Ian Campbell , Russell King , Rob Herring , Pawel Moll , Mark Rutland , Linus Walleij , "open list:ARM/Rockchip SoC..." , "devicetree@vger.kernel.org" , "linux-kernel@vger.kernel.org" , Kumar Gala , Tony Xie , "linux-arm-kernel@lists.infradead.org" Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi, On Mon, Dec 1, 2014 at 11:51 AM, Kevin Hilman wrote: > Chris Zhong 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 . 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? For those that don't want to click on my link, I'll include the relevant bits here: --- Total patches atop that version of Linux were: 1. https://patchwork.kernel.org/patch/5051881/ - clocksource: arch_timer: Allow the device tree to specify uninitialized timer registers 2. https://patchwork.kernel.org/patch/5363671/ - clocksource: arch_timer: Fix code to use physical timers when requested 3. https://patchwork.kernel.org/patch/5382141/ - ARM: dts: rk3288: add arm,cpu-registers-not-fw-configured 4. Revert (b77d439 ARM: dts: rockchip: temporarily disable smp on rk3288) 5. https://patchwork.kernel.org/patch/5325111/ - usb: dwc2: resume root hub when device detect with suspend state 6. https://patchwork.kernel.org/patch/5410611/ - ARM: rockchip: add suspend and resume for RK3288 7. https://patchwork.kernel.org/patch/5410621/ - ARM: rockchip: Add pmu-sram binding 8. https://patchwork.kernel.org/patch/5410631/ - ARM: dts: add RK3288 suspend support 9. https://patchwork.kernel.org/patch/5410641/ - ARM: dts: rockchip: add suspend settings for rk3288-evb-rk808 It looks like my pinctrl patches might be dropped due to cross dependency problems, so tomorrow's linux-next will probably also need (https://patchwork.kernel.org/patch/5344551/ - pinctrl: rockchip: Handle wakeup pins). I've also got a local hack to the Rockchip "pm.c" to replace the usage of "PMU_ARMINT_WAKEUP_EN" with 0x0e. There seems to be some sort of ARM Interrupt waking us up all the time right when we go to sleep and the above will hack it so that only GPIOs + SDMMC Card Detect can wake us up. Someone should track down what's going on there, but for now I've used the hack to prove that the basic code actually works. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/