lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Thu, 6 Mar 2014 14:58:52 +0530
From:	Jagdish Gedia <>
To:	Peter Chen <>
Cc:	"" <>,
	"" <>
Subject: Re: USB remote wakeup through gpio interrupt

Hi Peter,

My usb device is not capable of giving interrupt when it finishes
using usb. So i dont have any idea where can i call pm_runtime_put for
my usb device?

the other thing is that, earlier you have told, waking up usb device
through interrupt is same as writing "on" to ../power/control , but i
think writing "on" to ../power/control will disable the autosuspend
for usb device in future, but i want autosuspend to be enabled for my
usb device always. Will using pm_runtime_get and pm_runtime_put cause
the disable of autosuspend for usb device?

Jagdish Gediya

On Thu, Mar 6, 2014 at 2:53 PM, Jagdish Gedia <> wrote:
> Hi Alan,
> As you have told, i have executed pm_request_resume() function from my
> interrupt handler, and it is waking up my USB device. I have
> implemented all this functionality in class driver(cdc-acm.c).
> but what is happening is after 2-3 times, ausosuspend is getting
> disable for my device. I want autosuspend to be enabled for usb device
> forever. Do pm_request_resume function causes this behavior?
> Thanks,
> Jagdish Gediya
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

Powered by blists - more mailing lists