On Fri, 17 Dec 2010, Oleg Kutkov wrote: > Hello. > I have usb modem based on new Qualcomm cpu - qsc6085 (i can't find any > datasheet). > This device support autosuspend and everytime go to sleep after 20 > minutes of inactivity. After that i can't resume it. pppd only say > that "no carrier". Now, only unplug and plug device again... You didn't say what version of the Linux kernel you are using. > lsusb say: > Bus 001 Device 085: ID 19d2:fff1 ONDA Communication S.p.A. > > Modem has 5 ports: ttyUSB0, ttyUSB1, ttyUSB2, ttyUSB3, ttyUSB4. > > I go to sysfs and try to disable autosuspend: > > /sys/bus/usb/devices # ls > 1-0:1.0 1-1:1.0 1-1.5:1.0 1-1.5:1.2 1-1.5:1.4 2-0:1.0 2-1.1 > 2-1.1:1.0 2-1.7 2-1.8 usb1 1-1 1-1.5 1-1.5:1.1 > 1-1.5:1.3 1-1.5:1.5 2-1 2-1:1.0 2-1.1:1.1 2-1.7:1.0 > 2-1.8:1.0 usb2 > Our device is 1-1.5:1.0 - 1-1.5:1.4 Actually the device is 1-1.5 -- those other things are interfaces. > # ls 1-1.5:1.0 > bAlternateSetting bInterfaceProtocol driver ep_82 power ttyUSB0 > bInterfaceClass bInterfaceSubClass ep_02 interface subsystem uevent > bInterfaceNumber bNumEndpoints ep_81modalias supports_autosuspend > > # cat supports_autosuspend Did you leave out a "cd 1-1.5:1.0" above? > 1 > > # ls power/ > control runtime_active_time runtime_status runtime_suspended_time wakeup > > # cat runtime_status > active > > #cat control > What happened here? The "control" file can never be empty. Is this a copy & paste error? (Notice there's no ' ' after the '#' above.) What do you see in /sys/bus/usb/devices/1-1.5/power/control? That's the file and directory you should be looking in. And what's in /sys/bus/usb/devices/1-1.5/power/autosuspend? > # cat runtime_active_time > 864568 > > This value is growing up. > > What strange - runtime_status is everytime "active", even if device is sleeps. Maybe the device isn't suspended but has put itself to sleep somehow. > I try (device is still alive) for every 1-1.5:1.X: > # echo "on" > ./control > # cat control > on > > Looks like everything OK. Waiting... > And evice is suspended... How do you know the device is suspended? > This is a problem on device driver (because closed chip) or hardware problem ? I don't think this is connected with the USB stack. 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
