logo

Could not compile stylesheet for simplistic. Using last compiled stylesheet.

no suspend to ram, if device plugged on OTG

posted in IGEPv2
Friday, March 08 2013, 04:24 PM
0
we are using igepv2 with ISEE kernel 2.6.37-5. i saw a problem,if i want to go to suspend to ram by using:

"echo -n "mem" > /sys/power/state".

if a device was plugged into OTG port (in out case 4port high speed hub) the board did not go into suspend to ram (directly woke up again):

[ 351.617797] PM: Syncing filesystems ... done.
[ 351.647033] Freezing user space processes ... (elapsed 0.01 seconds) done.
[ 351.672515] Freezing remaining freezable tasks ... (elapsed 0.02 seconds) done.
[ 351.704254] Suspending console(s) (use no_console_suspend to debug)
[ 351.714385] ADU07_usb_mcp: disconnecting usb driver from device
[ 351.714416] ADU07_usb_mcp: down adu07_mutex_boot
[ 351.714447] ADU07_usb_mcp: down adu07_mutex_command
[ 351.714447] ADU07_usb_mcp: down adu07_mutex_err_status
[ 351.714477] ADU07_usb_mcp: down adu07_mutex_data
[ 351.714813] ADU07_usb_mcp: up adu07_mutex_data
[ 351.714843] ADU07_usb_mcp: up adu07_mutex_err_status
[ 351.714843] ADU07_usb_mcp: up adu07_mutex_command
[ 351.714874] ADU07_usb_mcp: up adu07_mutex_boot
[ 351.716156] pm_op(): usb_dev_suspend+0x0/0x10 returns -16
[ 351.716186] PM: Device usb2 failed to suspend async: error -16
[ 351.716247] PM: Some devices failed to suspend
[ 351.717498] ADU07_usb_mcp: activating probe trigger in data channel thread
[ 351.718017] PM: resume of devices complete after 1.739 msecs
[ 351.718292] ADU07_usb_mcp: probing usb driver for device
[ 351.718322] ADU07_usb_mcp: VID=0x04b4 PID=0x8613 interface=0xdeac5600
[ 351.718841] ADU07_usb_mcp: got minor number 16
[ 351.718872] ADU07_usb_mcp: device is running in HIGH-SPEED mode
[ 351.718872] ADU07_usb_mcp: setting max. tlg size to 512 byte
[ 351.824218] ADU07_usb_mcp: adapting max telegram per transfer (packet size: 512 bytes / packets per tranfser: 20 packets)
[ 351.836364] Restarting tasks ... done.

i could solve the problem by changing the following in kernel config:

1.) Device Driver\USB support\USB runtime power management (autosuspend) and wakeup

2.) Driver Mode (USB Host) --->

afterwards the system went to sleep, even if a device is plugged on OTG.

[ 862.507690] PM: early resume of devices complete after 0.335 msecs
[ 862.510345] [wake_on_gpio]: handled IRQ for GPIO 318
[ 862.770294] usb 1-1: reset high speed USB device using musb-hdrc and address 5
[ 877.832885] musb_h_ep0_irq 1162: no URB for end 0
[ 877.833007] PM: resume of devices complete after 15325.195 msecs
[ 877.833312] ADU07_usb_mcp: probing usb driver for device
[ 877.833343] ADU07_usb_mcp: VID=0x1b97 PID=0x0001 interface=0xdeac5a00
[ 877.833923] ADU07_usb_mcp: got minor number 16
[ 877.833923] ADU07_usb_mcp: device is running in HIGH-SPEED mode
[ 877.833953] ADU07_usb_mcp: setting max. tlg size to 512 byte
[ 877.977905] ADU07_usb_mcp: adapting max telegram per transfer (packet size: 512 bytes / packets per tranfser: 20 packets)
[ 877.990112] Restarting tasks ...
[ 877.993774] usb 1-1: USB disconnect, address 5
[ 877.998718] usb 1-1.3: USB disconnect, address 7
[ 878.004364] pl2303 ttyUSB0: pl2303 converter now disconnected from ttyUSB0
[ 878.011718] pl2303 1-1.3:1.0: device disconnected
[ 878.065521] done.
[ 878.332885] usb 1-1: new high speed USB device using musb-hdrc and address 8
[ 878.481658] usb 1-1: New USB device found, idVendor=04cc, idProduct=1520
[ 878.488677] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[ 878.501647] hub 1-1:1.0: USB hub found
[ 878.508178] hub 1-1:1.0: 4 ports detected
[ 878.809509] usb 1-1.3: new full speed USB device using musb-hdrc and address 9
[ 878.928558] usb 1-1.3: New USB device found, idVendor=067b, idProduct=2303
[ 878.935852] usb 1-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 878.943542] usb 1-1.3: Product: USB-Serial Controller
[ 878.948852] usb 1-1.3: Manufacturer: Prolific Technology Inc.
[ 878.960998] pl2303 1-1.3:1.0: pl2303 converter detected
[ 878.971557] usb 1-1.3: pl2303 converter now attached to ttyUSB0
[ 883.484436] [wake_on_gpio]: handled IRQ for GPIO 318
[ 883.489898] ADU07_usb_mcp: starting data channel kernel thread

nevertheless, all devices beeing connected to OTG seem to be completely disconnected, not stopped and resumed (but this is OK for my application).

Question: is this OK or do the changes have any bad side effects?

Accepted Answer

Thursday, June 13 2013, 05:25 PM - #permalink
0
Do you test that issue with last 2.6.37-6 kernel release ?
The reply is currently minimized Show
Responses (0)
  • There are no replies here yet.
Your Reply

SUPPORT


This email address is being protected from spambots. You need JavaScript enabled to view it.
This email address is being protected from spambots. You need JavaScript enabled to view it.
IGEP Community Wiki
IGEP Community Forum
IGEP Community Online Chat