On Thu, 20 Dec 2012, Frank Schäfer wrote: > > Yes runtime suspend works (tested with a mouse) and lspci -vv doesn't > > change. > > > > With > > /sys/devices/pci0000:00/0000:00:02.0/usb2/2-9/power: > > control = on > > runtime_status = active > > > > 00:02.0 USB controller: NVIDIA Corporation MCP61 USB 1.1 Controller (rev > > a2) (prog-if 10 [OHCI]) > > Subsystem: ASUSTeK Computer Inc. Device 8234 > > Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- > > ParErr- Stepping- SERR- FastB2B- DisINTx- > > Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- > > <TAbort- <MAbort- >SERR- <PERR- INTx- > > Latency: 0 (750ns min, 250ns max) > > Interrupt: pin A routed to IRQ 23 > > Region 0: Memory at fe02f000 (32-bit, non-prefetchable) [size=4K] > > Capabilities: [44] Power Management version 2 > > Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA > > PME(D0+,D1+,D2+,D3hot+,D3cold+) > > Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME- > > Kernel driver in use: ohci_hcd > > > > > > => set control to 'auto' > > > > runtime_status = active > > > > 00:02.0 USB controller: NVIDIA Corporation MCP61 USB 1.1 Controller (rev > > a2) (prog-if 10 [OHCI]) > > Subsystem: ASUSTeK Computer Inc. Device 8234 > > Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- > > ParErr- Stepping- SERR- FastB2B- DisINTx- > > Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- > > <TAbort- <MAbort- >SERR- <PERR- INTx- > > Latency: 0 (750ns min, 250ns max) > > Interrupt: pin A routed to IRQ 23 > > Region 0: Memory at fe02f000 (32-bit, non-prefetchable) [size=4K] > > Capabilities: [44] Power Management version 2 > > Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA > > PME(D0+,D1+,D2+,D3hot+,D3cold+) > > Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME- > > Kernel driver in use: ohci_hcd > > > > > > => after ~2s the device suspends > > > > runtime_status = suspended > > > > 00:02.0 USB controller: NVIDIA Corporation MCP61 USB 1.1 Controller (rev > > a2) (prog-if 10 [OHCI]) > > Subsystem: ASUSTeK Computer Inc. Device 8234 > > Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- > > ParErr- Stepping- SERR- FastB2B- DisINTx- > > Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- > > <TAbort- <MAbort- >SERR- <PERR- INTx- > > Latency: 0 (750ns min, 250ns max) > > Interrupt: pin A routed to IRQ 23 > > Region 0: Memory at fe02f000 (32-bit, non-prefetchable) [size=4K] > > Capabilities: [44] Power Management version 2 > > Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA > > PME(D0+,D1+,D2+,D3hot+,D3cold+) > > Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME- > > Kernel driver in use: ohci_hcd > > > > Of course I checked that the host controller suspends, too. The lspci output above shows that the host controller is _not_ suspended. Or at least, that's what it looks like -- maybe for some reason the runtime suspend code didn't put the controller into D3. It would help to see the dmesg output from a kernel with CONFIG_USB_DEBUG enabled. What do you get in /sys/devices/pci0000:00/0000:00:02.0/power/ ? > I also checked if lspci changes after unplugging the mouse, but that's > not the case. Alan Stern -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
