[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: [PATCH] ppc32: Rework power management take #3



> > The attached patch fixes this for me by moving the wakeup in the
> > finish() callback. Maybe making post_freeze to be called in the first
> > place would be a more correct fix...
> 
> Yes.
> 
> > The attached patch also fixes the kernel/power core to use PLATFORM
> > instead of SHUTDOWN as the sleep mode... 
> 
> Ok, good, I'll have a look, thanks.

I also have issues with the integrated USB bluetooth controller.

When suspending to ram all works ok.

When resuming from suspend to disk, this USB device doesn't answer
anymore. It doesn't matter if I remove the modules (hci_usb) before
sleeping and reload them after, it just doesn't work anymore.

The only log I have is:
	hci_usb_intr_rx_submit: hci0 intr rx submit failed urb de5791f4 err -90

I don't really understand how suspend/resume is supposed to work for USB
devices.

When resuming, I see disconnect/reconnect messages from ehci_hcd
corresponding to my external usb mouse:
	ehci_hcd 0001:10:1b.2: park 0
	ehci_hcd 0001:10:1b.2: USB 2.0 restarted, EHCI 1.00, driver 10 Dec 2004
	usb 4-1: USB disconnect, address 3
	usb 4-1: new low speed USB device using ohci_hcd and address 4
	input: USB HID v1.10 Mouse [Logitech USB Mouse] on usb-0001:10:1b.1-1

But no other USB messages. However, this Powerbook has a USB keyboard,
which works ok after the resume. Even stranger, the USB keyboard and the
bluetooth controller are on the same USB bus:

	Bus 004 Device 005: ID 046d:c00c Logitech, Inc. Optical Wheel Mouse
	Bus 004 Device 001: ID 0000:0000
	Bus 003 Device 001: ID 0000:0000
	Bus 002 Device 007: ID 05ac:8205 Apple Computer, Inc.
			       ^^^^^^^^^ this one is the bluetooth controller
	Bus 002 Device 006: ID 05ac:020f Apple Computer, Inc.
			       ^^^^^^^^^ this is the keyboard
	Bus 002 Device 001: ID 0000:0000
	Bus 001 Device 001: ID 0000:0000

I have no idea if this is Powerbook specific, so I start by posting this
here, but linux-usb may be more appropriate...

Stelian.
-- 
Stelian Pop <stelian@popies.net>



Reply to: