On Fri, Jan 5, 2018 at 6:12 PM, Ulf Hansson wrote:
> On 5 January 2018 at 13:57, Rafael J. Wysocki wrote:
>> On Tue, Jan 2, 2018 at 5:08 PM, Ulf Hansson wrote:
>>> Currently the wakeup_path status flag becomes propagated from a child
>>> device to its parent device at __device_suspend(). This al
On 5 January 2018 at 13:57, Rafael J. Wysocki wrote:
> On Tue, Jan 2, 2018 at 5:08 PM, Ulf Hansson wrote:
>> Currently the wakeup_path status flag becomes propagated from a child
>> device to its parent device at __device_suspend(). This allows a driver
>> dealing with a parent device to act on t
On Tue, Jan 2, 2018 at 5:08 PM, Ulf Hansson wrote:
> Currently the wakeup_path status flag becomes propagated from a child
> device to its parent device at __device_suspend(). This allows a driver
> dealing with a parent device to act on the flag from its ->suspend()
> callback.
>
> However, in si
Currently the wakeup_path status flag becomes propagated from a child
device to its parent device at __device_suspend(). This allows a driver
dealing with a parent device to act on the flag from its ->suspend()
callback.
However, in situations when the wakeup_path status flag needs to be set
from
