[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <7ha804lr2a.fsf@baylibre.com>
Date: Thu, 02 Nov 2017 14:59:25 +0100
From: Kevin Hilman <khilman@...libre.com>
To: Geert Uytterhoeven <geert+renesas@...der.be>
Cc: "Rafael J . Wysocki" <rjw@...ysocki.net>,
Ulf Hansson <ulf.hansson@...aro.org>,
Simon Horman <horms@...ge.net.au>,
Magnus Damm <magnus.damm@...il.com>,
Matthias Brugger <matthias.bgg@...il.com>,
Heiko Stuebner <heiko@...ech.de>, linux-pm@...r.kernel.org,
linux-mediatek@...ts.infradead.org,
linux-rockchip@...ts.infradead.org,
linux-renesas-soc@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2 1/5] PM / Domains: Allow genpd users to specify default active wakeup behavior
Geert Uytterhoeven <geert+renesas@...der.be> writes:
> It is quite common for PM Domains to require slave devices to be kept
> active during system suspend if they are to be used as wakeup sources.
> To enable this, currently each PM Domain or driver has to provide its
> own gpd_dev_ops.active_wakeup() callback.
>
> Introduce a new flag GENPD_FLAG_ACTIVE_WAKEUP to consolidate this.
> If specified, all slave devices configured as wakeup sources will be
> kept active during system suspend.
>
> PM Domains that need more fine-grained controls, based on the slave
> device, can still provide their own callbacks, as before.
>
> Signed-off-by: Geert Uytterhoeven <geert+renesas@...der.be>
Reviewed-by: Kevin Hilman <khilman@...libre.com>
Powered by blists - more mailing lists