On Friday 08 February 2008, Sarah Sharp wrote: > Ah, I see why you would want to turn off remote wakeup on those ports. > However, > I don't see that function actually does what the comment says. AFAIK, writing > 1 to the registers represented by PORT_RWC_BITS only clears the port status > bits > related to current port events. It doesn't stop new events from being > interpreted as remote wakeup events in the future.
If the root hub *does* support power switching, writing just PORT_RWC_BITS disables power ... > You would have to clear the > PORT_WK* bits to turn off remote wakeup for a port. Am I misreading > something? > > It doesn't matter much, since the fix worked, but it was very confusing to > compare the ehci_turn_off_all_ports() and ehci_port_power(). Were you going to develop a patch to resolve those issues? - Dave - To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
