Hi,
I'm trying to make remote wake up working on a 2.6.15-rc7 kernel and
got a couple of questions related to that.
First I noticed hc->can_wakeup that should be initialized in
hcd->start method. It's used by core to know if the hcd support remote
wake up, is that correct ? If so whatever its value, an attached
device (that supports remote wakup of course) can wake up the
hcd...BTW, what's is the difference between hc->can_wakeup and
hc->remote_wakeup ?
OK, let's assume I have suspended a mouse device. If I move it, it
wakes up the hcd. The hcd got an interrupt and in the interrupt
handler I only raise the C_PORT_SUSPEND field in the port status
change bits. Khubd notices this change and only asks for the root hub
to clear the C_PORT_SUSPEND bit. Should I resume the bus when clearing
this bit ?
I looked at sl811's implementation but I actually don't understand how
it works. Here's how I have understood it: a remote wakup is detected
by an interrupt (I guess it's SL11H_INTMASK_RD one). Then the handler
raise the C_PORT_SUSPEND field and executes:
if (irqstat) {
if (sl811->port1 & (1 << USB_PORT_FEAT_ENABLE))
start_transfer(sl811);
ret = IRQ_HANDLED;
if (retries--)
goto retry;
}
which do actually nothing as far I can see...Khubd detects the field
C_PORT_SUSPEND and clears it but it's do nothing interesting on the
bus...where am I wrong in this interpretation ?
Happy new year,
--
Franck
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_idv37&alloc_id865&op=click
_______________________________________________
[email protected]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
