On Fri, 8 Sep 2017, Mike Simms wrote: > Hi Alan yes it says the same "unsupported" and all other values are > the same too. I included them in brackets in my post. Yes it is odd. > I don't know if the usbmon traces show anything useful. To me it's > gobbledygook. Where are the usbmon traces? > On 8 Sep 2017 9:35 p.m., Alan Stern <stern@xxxxxxxxxxxxxxxxxxx> wrote: > > On Fri, 8 Sep 2017, Jiri Kosina wrote: > > > On Fri, 8 Sep 2017, Mike Simms wrote: > > > > > Thanks for getting back to me, > > > > > > 4.11.11-300.fc26.x86_64 and 4.12.9-300.fc26.x86_64 > > > are showing identical settings - autosuspend definitely on for > > > device /sys/bus/usb/devices/2-1.3/2-1.3:1.0/0003:046D:C52B.0001/power > > > > > > it shows in the powertop UI as good for both kernels and > > > > > > Folder contents are autosuspend_delay_ms (can't open), control (auto), > > > runtime_active_time (0), runtime_status (unsupported), > > The "unsupported" means that runtime suspend is disabled. (Don't ask > me why it doesn't say "disabled" instead.) That is suspicious in > itself. Drivers don't normally disable runtime suspend for more than > very short time intervals. > > Does the runtime_status file really say "unsupported" in both kernels? > > > > runtime_suspended_time (0) > > > > Alright, that means that both kernels are allowed to autosuspend the > > device, but apparently only 4.12 actually does so. Could you please > > confirm that with usbmon traces? > > In addition to usbmon traces, it would be good to look at the settings > under /sys/bus/usb/devices/2-1.3/2-1.3:1.0/power/. It's unlikely that > they have changed between 4.11 and 4.12, but it doesn't hurt to check. Did you do this? Alan Stern -- To unsubscribe from this list: send the line "unsubscribe linux-input" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
