Re: [Bugme-new] [Bug 12447] New: usbtouchscreen submits URB too quickly if built in to kernel

Re: [Bugme-new] [Bug 12447] New: usbtouchscreen submits URB too quickly if built in to kernel

[Andrew Morton]

(switched to email.  Please respond via emailed reply-to-all, not via the
bugzilla web interface).

On Wed, 14 Jan 2009 08:29:31 -0800 (PST) bugme-daemon-590EEB7GvNiWaY/ihj7yzEB+6BGkLq7r@public.gmane.org wrote:

> http://bugzilla.kernel.org/show_bug.cgi?id=12447
> 
>            Summary: usbtouchscreen submits URB too quickly if built in to
>                     kernel
>            Product: Drivers
>            Version: 2.5
>      KernelVersion: 2.6.27
>           Platform: All
>         OS/Version: Linux
>               Tree: Mainline
>             Status: NEW
>           Severity: normal
>           Priority: P1
>          Component: Input Devices
>         AssignedTo: drivers_input-devices-ztI5WcYan/vQLgFONoPN62D2FQJk+8+b@public.gmane.org
>         ReportedBy: david.hagood-15hjz6xD4c1Wk0Htik3J/w@public.gmane.org
> 
> 
> Latest working kernel version: (unknown)
> Earliest failing kernel version: (unknown)
> Distribution: Debian/x86 (Lenny), Debian/ARM (OMAP, Lenny)
> Hardware Environment: x86, Beagleboard
> Software Environment: Debian Lenny, X
> Problem Description:
> If the usbtouchscreen driver is built in to the kernel and a Microtouch systems
> touchscreen (USB ID 0596:0001) is plugged in, the initialization of the driver
> fails with the following logged:
> 
> usbtouchscreen: usbtouch_irq - usb_submit_urb failed with result: -19           
> usb 1-1.3: new full speed USB device using musb_hdrc and address 11             
> usb 1-1.3: configuration #1 chosen from 1 choice                                
> input: 3M 3M USB Touchscreen - EX II as /class/input/input10
> 
> If the driver is compiled as a module and is not loaded into the kernel, the
> initialization works - dmesg output is:
> 
> usb 1-1.3: new full speed USB device using musb_hdrc and address 12             
> usb 1-1.3: configuration #1 chosen from 1 choice                                
> input: 3M 3M USB Touchscreen - EX II as /class/input/input11                    
> usbcore: registered new interface driver usbtouchscreen
> 
> If the screen is unplugged and plugged in again, the result is the same as if
> the module is built in. If the screen is unplugged, the usbtouchscreen module
> removed, and the screen plugged in, it works.
> 
> I would conjecture that a delay is needed after the insertion to allow the
> hardware to stabilize.
> 
> Steps to reproduce:
> Build the usbtouchscreen driver as a built-in driver.
> Insure touchscreen hardware is NOT plugged in.
> Reboot into new kernel, wait for system up.
> Connect touchscreen hardware.
> 
> Expected results: hardware device found, initialized, /dev/input/event[n]
> created.
> Actual results: Hardware found, URB submission error, no dev entry created.
> 
> Build driver as module.
> Insure touchscreen hardware is NOT plugged in.
> Reboot into new kernel, wait for system up.
> Connect touchscreen hardware.
> 
> Expected results: hardware device found, drivers modprobed, initialized,
> /dev/input/event[n] created.
> Actual results: as expected.
> 
> Remove device, wait 5 seconds, re-connect hardware.
> 
> Expected results: hardware device found, initialized, /dev/input/event[n]
> created.
> Actual results: Hardware found, URB submission error, no dev entry created.
> 
> Remove hardware, rmmod usbtouchscreen driver, reconnect hardware.
> 
> Expected results: hardware device found, drivers modprobed, initialized,
> /dev/input/event[n] created.
> Actual results: as expected.
> 
> NOTE: This happens both on the x86 and the ARM environment.
> 

Is this a USB thing, or an input thing?
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: [Bugme-new] [Bug 12447] New: usbtouchscreen submits URB too quickly if built in to kernel

[David Hagood]

On Wed, 2009-01-14 at 10:28 -0800, Andrew Morton wrote:
> (switched to email.  Please respond via emailed reply-to-all, not via the
> bugzilla web interface).
> 
OK, you asked for it - no fair complaining about the email wart that I
can do nothing about.

> On Wed, 14 Jan 2009 08:29:31 -0800 (PST) bugme-daemon@bugzilla.kernel.org wrote:
> 
> Is this a USB thing, or an input thing?
> 

I'm not sure I understand the question. The problem is in the
usbtouchscreen kernel module, which is an input module.

The problem is NOT at the X layer (read: user space), but in the kernel
driver.

Did that answer the question?

(and here comes the wart - this gets added by our mail servers, and I
cannot do anything about it. The intended distribution of the email is
the world, so it has no application....)

Notice: This e-mail is intended solely for use of the individual or entity to which it is addressed and may contain information that is proprietary, privileged, company confidential and/or exempt from disclosure under applicable law. If the reader is not the intended recipient or agent responsible for delivering the message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited.  If this communication has been transmitted from a U.S. location it may also contain data subject to the International Traffic in Arms Regulations or U.S. Export Administration Regulations and cannot be disseminated, distributed or copied to foreign nationals, residing in the U.S. or abroad, without the prior approval of the U.
 S. Department of State or appropriate export licensing authority. If you have received this communication in error, please notify the sender by reply e-mail or collect telephone call and del
 ete or destroy all copies of this e-mail message, any physical copies made of this e-mail message and/or any file attachment(s).

Re: [Bugme-new] [Bug 12447] New: usbtouchscreen submits URB too quickly if built in to kernel

[Andrew Morton]

On Wed, 14 Jan 2009 17:08:28 -0600
David Hagood <david.hagood@aeroflex.com> wrote:

> On Wed, 2009-01-14 at 10:28 -0800, Andrew Morton wrote:
> > (switched to email.  Please respond via emailed reply-to-all, not via the
> > bugzilla web interface).
> > 
> OK, you asked for it - no fair complaining about the email wart that I
> can do nothing about.

It happens.

> > On Wed, 14 Jan 2009 08:29:31 -0800 (PST) bugme-daemon@bugzilla.kernel.org wrote:
> > 
> > Is this a USB thing, or an input thing?
> > 
> 
> I'm not sure I understand the question. The problem is in the
> usbtouchscreen kernel module, which is an input module.
> 
> The problem is NOT at the X layer (read: user space), but in the kernel
> driver.
> 
> Did that answer the question?

The question was asked of the USB and input developers ;) It's unclear
(to me) which subsystem would need fixing to make this work properly.

Re: [Bugme-new] [Bug 12447] New: usbtouchscreen submits URB too quickly if built in to kernel

[Dmitry Torokhov]

On Wed, Jan 14, 2009 at 03:13:36PM -0800, Andrew Morton wrote:
> On Wed, 14 Jan 2009 17:08:28 -0600
> David Hagood <david.hagood@aeroflex.com> wrote:
> 
> > On Wed, 2009-01-14 at 10:28 -0800, Andrew Morton wrote:
> > > (switched to email.  Please respond via emailed reply-to-all, not via the
> > > bugzilla web interface).
> > > 
> > OK, you asked for it - no fair complaining about the email wart that I
> > can do nothing about.
> 
> It happens.
> 
> > > On Wed, 14 Jan 2009 08:29:31 -0800 (PST) bugme-daemon@bugzilla.kernel.org wrote:
> > > 
> > > Is this a USB thing, or an input thing?
> > > 
> > 
> > I'm not sure I understand the question. The problem is in the
> > usbtouchscreen kernel module, which is an input module.
> > 
> > The problem is NOT at the X layer (read: user space), but in the kernel
> > driver.
> > 
> > Did that answer the question?
> 
> The question was asked of the USB and input developers ;) It's unclear
> (to me) which subsystem would need fixing to make this work properly.
> 

I suppose this is device-specific and will have to be worked around in
the driver buy resubmitting request a few times until it "sticks".

-- 
Dmitry

Re: [Bugme-new] [Bug 12447] New: usbtouchscreen submits URB too quickly if built in to kernel

[Dmitry Torokhov]

On Wednesday 14 January 2009 20:43:39 Dmitry Torokhov wrote:
> On Wed, Jan 14, 2009 at 03:13:36PM -0800, Andrew Morton wrote:
> > On Wed, 14 Jan 2009 17:08:28 -0600
> >
> > David Hagood <david.hagood-15hjz6xD4c1Wk0Htik3J/w@public.gmane.org> wrote:
> > > On Wed, 2009-01-14 at 10:28 -0800, Andrew Morton wrote:
> > > > (switched to email.  Please respond via emailed reply-to-all, not via
> > > > the bugzilla web interface).
> > >
> > > OK, you asked for it - no fair complaining about the email wart that I
> > > can do nothing about.
> >
> > It happens.
> >
> > > > On Wed, 14 Jan 2009 08:29:31 -0800 (PST)
> > > > bugme-daemon-590EEB7GvNiWaY/ihj7yzEB+6BGkLq7r@public.gmane.org wrote:
> > > >
> > > > Is this a USB thing, or an input thing?
> > >
> > > I'm not sure I understand the question. The problem is in the
> > > usbtouchscreen kernel module, which is an input module.
> > >
> > > The problem is NOT at the X layer (read: user space), but in the kernel
> > > driver.
> > >
> > > Did that answer the question?
> >
> > The question was asked of the USB and input developers ;) It's unclear
> > (to me) which subsystem would need fixing to make this work properly.
>
> I suppose this is device-specific and will have to be worked around in
> the driver buy resubmitting request a few times until it "sticks".

Hmm, I take it back... the message comes from the IRQ routine; that
means we were able to submit IRQ at least once. Plus we do send a
few control messages for mtouch. So I don't understand why it would
start returning -ENODEV out of sudden.

-- 
Dmitry
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: [Bugme-new] [Bug 12447] New: usbtouchscreen submits URB too quickly if built in to kernel

[Alan Stern]

On Wed, 14 Jan 2009, Dmitry Torokhov wrote:

> > I suppose this is device-specific and will have to be worked around in
> > the driver buy resubmitting request a few times until it "sticks".
> 
> Hmm, I take it back... the message comes from the IRQ routine; that
> means we were able to submit IRQ at least once. Plus we do send a
> few control messages for mtouch. So I don't understand why it would
> start returning -ENODEV out of sudden.

A usbmon trace might come in useful here.  See the instructions in 
Documentation/usb/usbmon.txt.

Alan Stern

Re: [Bugme-new] [Bug 12447] New: usbtouchscreen submits URB too quickly if built in to kernel

[David Hagood]

On Thu, 2009-01-15 at 10:09 -0500, Alan Stern wrote:
> On Wed, 14 Jan 2009, Dmitry Torokhov wrote:
> 
> > > I suppose this is device-specific an
> A usbmon trace might come in useful here.  See the instructions in 
> Documentation/usb/usbmon.txt.
> 
> Alan Stern
> 

Now that i've mounted the USB monitor system, it works. Heisenberg
lives!


Notice: This e-mail is intended solely for use of the individual or entity to which it is addressed and may contain information that is proprietary, privileged, company confidential and/or exempt from disclosure under applicable law. If the reader is not the intended recipient or agent responsible for delivering the message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited.  If this communication has been transmitted from a U.S. location it may also contain data subject to the International Traffic in Arms Regulations or U.S. Export Administration Regulations and cannot be disseminated, distributed or copied to foreign nationals, residing in the U.S. or abroad, without the prior approval of the U.
 S. Department of State or appropriate export licensing authority. If you have received this communication in error, please notify the sender by reply e-mail or collect telephone call and del
 ete or destroy all copies of this e-mail message, any physical copies made of this e-mail message and/or any file attachment(s).