[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAJZ5v0gJQHUMEXTbvb0q6rmW-1xuRWAwGMmo_CCE8mYj-xf5QA@mail.gmail.com>
Date: Mon, 17 Jul 2017 23:03:09 +0200
From: "Rafael J. Wysocki" <rafael@...nel.org>
To: Pavel Machek <pavel@....cz>,
Florian Fainelli <f.fainelli@...il.com>
Cc: Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
"Rafael J. Wysocki" <rjw@...ysocki.net>,
Alexandre Belloni <alexandre.belloni@...e-electrons.com>,
"Rafael J. Wysocki" <rafael@...nel.org>,
Ulf Hansson <ulf.hansson@...aro.org>,
Daniel Lezcano <daniel.lezcano@...aro.org>,
linux-pm <linux-pm@...r.kernel.org>,
Thibaud Cornic <thibaud_cornic@...madesigns.com>,
JB <jb_lescher@...madesigns.com>, Mason <slash.tmp@...e.fr>,
Kevin Hilman <khilman@...nel.org>,
Linux ARM <linux-arm-kernel@...ts.infradead.org>
Subject: Re: [PATCH v2] PM / suspend: Add suspend_target_state()
On Mon, Jul 17, 2017 at 10:16 PM, Pavel Machek <pavel@....cz> wrote:
> Hi!
>
>> Have the core suspend/resume framework store the system-wide suspend
>> state (suspend_state_t) we are about to enter, and expose it to drivers
>> via suspend_target_state() in order to retrieve that. The state is
>> assigned in suspend_devices_and_enter().
>
> Do we really want to have variable + inline functions that just read
> that variable?
Florian, Pavel is right, you can simply export the variable.
Anything accessing it should go under CONFIG_PM_SLEEP anyway.
Thanks,
Rafael
Powered by blists - more mailing lists