Messages in this thread | | | From | "Rafael J. Wysocki" <> | Date | Tue, 19 Dec 2017 12:19:20 +0100 | Subject | Re: [PATCH 3/4] PM / core: Direct DPM_FLAG_SMART_SUSPEND optimization |
| |
On Tue, Dec 19, 2017 at 12:13 PM, Rafael J. Wysocki <rafael@kernel.org> wrote: > On Tue, Dec 19, 2017 at 8:38 AM, Ulf Hansson <ulf.hansson@linaro.org> wrote: >> On 10 December 2017 at 01:00, Rafael J. Wysocki <rjw@rjwysocki.net> wrote: >>> From: Rafael J. Wysocki <rafael.j.wysocki@intel.com> >>>
[cut]
> >> Moreover, what happens when/if a driver that has deployed this >> solution, starts being used on a new SoC and then additional >> operations during system suspend becomes required (for example >> pinctrls that needs to be put in a system sleep state)? Then >> everything falls apart, doesn't it? > > Then you runtime-resume the device in ->suspend() and the remaining > callbacks will run for you just fine.
BTW, I guess you'll need a middle layer in that case anyway so that the driver doesn't have to distinguish between platforms it has to work with which makes the argument somewhat moot.
Thanks, Rafael
| |