On 31 March 2015 at 22:31, Dmitry Torokhov wrote:
> On Tue, Mar 31, 2015 at 06:14:49PM +0200, Tomeu Vizoso wrote:
>> So ancestor devices can remain runtime-suspended when the system goes
>> into a sleep state, they and all of their descendant devices need to
>> have runtime PM enabled.
>
> I am
On 31 March 2015 at 22:31, Dmitry Torokhov dmitry.torok...@gmail.com wrote:
On Tue, Mar 31, 2015 at 06:14:49PM +0200, Tomeu Vizoso wrote:
So ancestor devices can remain runtime-suspended when the system goes
into a sleep state, they and all of their descendant devices need to
have runtime PM
On Tue, Mar 31, 2015 at 06:14:49PM +0200, Tomeu Vizoso wrote:
> So ancestor devices can remain runtime-suspended when the system goes
> into a sleep state, they and all of their descendant devices need to
> have runtime PM enabled.
I am confused. Input devices are not runtime-PM-enabled, so what
So ancestor devices can remain runtime-suspended when the system goes
into a sleep state, they and all of their descendant devices need to
have runtime PM enabled.
Signed-off-by: Tomeu Vizoso
---
drivers/input/evdev.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/drivers/input/evdev.c
So ancestor devices can remain runtime-suspended when the system goes
into a sleep state, they and all of their descendant devices need to
have runtime PM enabled.
Signed-off-by: Tomeu Vizoso tomeu.viz...@collabora.com
---
drivers/input/evdev.c | 3 +++
1 file changed, 3 insertions(+)
diff
On Tue, Mar 31, 2015 at 06:14:49PM +0200, Tomeu Vizoso wrote:
So ancestor devices can remain runtime-suspended when the system goes
into a sleep state, they and all of their descendant devices need to
have runtime PM enabled.
I am confused. Input devices are not runtime-PM-enabled, so what
6 matches
Mail list logo