From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-qk0-f193.google.com ([209.85.220.193]:56611 "EHLO mail-qk0-f193.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752702AbdKHPcJ (ORCPT ); Wed, 8 Nov 2017 10:32:09 -0500 MIME-Version: 1.0 In-Reply-To: <1510154134-1248-3-git-send-email-ulf.hansson@linaro.org> References: <1510154134-1248-1-git-send-email-ulf.hansson@linaro.org> <1510154134-1248-3-git-send-email-ulf.hansson@linaro.org> From: Geert Uytterhoeven Date: Wed, 8 Nov 2017 16:32:08 +0100 Message-ID: Subject: Re: [PATCH 2/3] PM / core: Add WAKEUP_POWERED driver flag To: Ulf Hansson Cc: "Rafael J . Wysocki" , Linux PM list , Kevin Hilman , Viresh Kumar , Geert Uytterhoeven , Simon Horman , Niklas Soderlund , Linux-Renesas Content-Type: text/plain; charset="UTF-8" Sender: linux-renesas-soc-owner@vger.kernel.org List-ID: On Wed, Nov 8, 2017 at 4:15 PM, Ulf Hansson wrote: > For some bus types and PM domains, it's not sufficient to only check the > return value from device_may_wakeup(), to fully understand how to treat the > device during system suspend. > > In particular, sometimes the device may need to stay in full power state, > to have wakeup signals enabled for it. Therefore, define and document a > WAKEUP_POWERED flag, to enable drivers to instruct bus types and PM domains > exactly about that. > > During __device_suspend() in the PM core, let's make sure to also propagate > the setting of the flag to the parent device, when wakeup signals are > enabled and unless the parent has the "ignore_children" flag set. This > makes it also consistent with how the existing "wakeup_path" flag is being > assigned. > > Signed-off-by: Ulf Hansson Reviewed-by: Geert Uytterhoeven Gr{oetje,eeting}s, Geert -- Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org In personal conversations with technical people, I call myself a hacker. But when I'm talking to journalists I just say "programmer" or something like that. -- Linus Torvalds