[opensuse-kernel] Correct USB quirk for this device ?
Hi: I have one device called "entropy key" http://www.entropykey.co.uk/ 9: USB 00.0: 10200 Modem [Created at usb.122] Unique ID: hhw5.xbUS5LcXf33 Parent ID: FZIx.RTX9xWW_uz4 SysFS ID: /devices/pci0000:00/0000:00:1d.2/usb8/8-1/8-1:1.0 SysFS BusID: 8-1:1.0 Hardware Class: modem Model: "Simtec Electronics Entropy Key" Hotplug: USB Vendor: usb 0x20df "Simtec Electronics" Device: usb 0x0001 "Entropy Key" Revision: "2.00" Serial ID: "M/9uBjBLNzE3QSFD" Driver: "cdc_acm" Driver Modules: "cdc_acm" Device File: /dev/ttyACM0 Device Files: /dev/ttyACM0, /dev/serial/by-id/usb-Simtec_Electronics_Entropy_Key_M_9uBjBLNzE3QSFD-if00, /dev/serial/by-path/pci-0000:00:1d.2-usb-0:1:1.0 Speed: 12 Mbps Module Alias: "usb:v20DFp0001d0200dc02dsc00dp00ic02isc02ip01" Driver Info #0: Driver Status: cdc_acm is active Driver Activation Cmd: "modprobe cdc_acm" Config Status: cfg=no, avail=yes, need=no, active=unknown Attached to: #18 (Hub) which works just fine most of the time, except that it has never-ever recovered after suspend/resume, the only way to make it "live again" is plug/unplug the device after resume, or with an pm script #!/bin/bash . /usr/lib/pm-utils/functions case "$1" in hibernate|suspend) stopservice ekeyd modunload cdc-acm ;; thaw|resume) modreload cdc-acm restartservice ekeyd ;; *) ;; esac exit 0 and well, that's really *really* ugly. Looking at the USB quirks list, looks like this device needs USB_QUIRK_RESET_RESUME, I am not a kernel developer so Im not sure about if this is correct. will be cool if someone can add the quirk if it is the correct one or point me to the right approach. ;) -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kernel+owner@opensuse.org
On 05/07/2012 09:58 PM, Cristian Rodríguez wrote:
Looking at the USB quirks list, looks like this device needs USB_QUIRK_RESET_RESUME, I am not a kernel developer so Im not sure about if this is correct.
will be cool if someone can add the quirk if it is the correct one or point me to the right approach. ;)
I have no idea if that is the correct quirk, but if it is, you should apply the attached patch to the kernel source, and rebuild. If it works, then you should report back here, and I'll push it upstream. Larry
On 07/05/12 23:23, Larry Finger wrote:
On 05/07/2012 09:58 PM, Cristian Rodríguez wrote:
Looking at the USB quirks list, looks like this device needs USB_QUIRK_RESET_RESUME, I am not a kernel developer so Im not sure about if this is correct.
will be cool if someone can add the quirk if it is the correct one or point me to the right approach. ;)
I have no idea if that is the correct quirk, but if it is, you should apply the attached patch to the kernel source, and rebuild.
If it works, then you should report back here, and I'll push it upstream.
I already have such patch locally but have not tested it yet ;) -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kernel+owner@opensuse.org
Am 08.05.2012 05:23, schrieb Larry Finger:
I have no idea if that is the correct quirk, but if it is, you should apply the attached patch to the kernel source, and rebuild.
The patch looks wrong (applies USB_QUIRK_RESET_RESUME to "BUILDWIN Photo Frame" which had USB_QUIRK_HONOR_BNUMINTERFACES before). :-) -- Stefan Seyfried "Dispatch war rocket Ajax to bring back his body!" -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kernel+owner@opensuse.org
On 05/08/2012 02:22 AM, Stefan Seyfried wrote:
Am 08.05.2012 05:23, schrieb Larry Finger:
I have no idea if that is the correct quirk, but if it is, you should apply the attached patch to the kernel source, and rebuild.
The patch looks wrong (applies USB_QUIRK_RESET_RESUME to "BUILDWIN Photo Frame" which had USB_QUIRK_HONOR_BNUMINTERFACES before). :-)
Yes, I messed it up. Cristian: I presume your version is correct. Once it is tested, then send it upstream to Greg Kroah-Hartman <gregkh@linuxfoundation.org> with Cc to linux-kernel@vger.kernel.org and linux-usb@vger.kernel.org. The E-mail should have a subject something like "[PATCH] usb: Add reset-resume quirk for ...." with the body containing a short description of why the patch is necessary. Follow this section with a line that says "Signed-off-by: NAME <E-MAIL ADDRESS>". The official set of rules is located at Documentation/SubmittingPatches in the source tree. Larry -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kernel+owner@opensuse.org
El 08/05/12 11:13, Larry Finger escribió:
The patch looks wrong (applies USB_QUIRK_RESET_RESUME to "BUILDWIN Photo Frame" which had USB_QUIRK_HONOR_BNUMINTERFACES before). :-)
Yes, I messed it up.
Cristian: I presume your version is correct. Once it is tested,
Yes, my patch is ok, Im building a kernel now for testing. -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kernel+owner@opensuse.org
El 08/05/12 12:37, Cristian Rodríguez escribió:
El 08/05/12 11:13, Larry Finger escribió:
The patch looks wrong (applies USB_QUIRK_RESET_RESUME to "BUILDWIN Photo Frame" which had USB_QUIRK_HONOR_BNUMINTERFACES before). :-)
Yes, I messed it up.
Cristian: I presume your version is correct. Once it is tested,
Yes, my patch is ok, Im building a kernel now for testing.
Though my patch is correct and actually applies the quirk to the device and hence it reset on resume, it does not fix the problem :-| Only removing the module AND restarting the service helps ( skipping any of those steps fails) The curious thing is that during normal operation, If I unplug the device, the userspace daemon correctly says the device is gone and when plugged once again it reports "OK" and continues working normally. -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kernel+owner@opensuse.org
participants (3)
-
Cristian Rodríguez -
Larry Finger -
Stefan Seyfried