On Thu, 21 Aug 2014, Johan Hovold wrote:
> > It's not really super-nice, but if no other way around it has been found
> > to be possible in USB core, I am willing to take this.
>
> Agreed, it's not that nice, but I'm not aware of any other way to
> prevent the device firmware from disconnecting.
On Wed, Aug 20, 2014 at 08:20:43AM -0500, Jiri Kosina wrote:
> On Mon, 14 Jul 2014, Johan Hovold wrote:
>
> > From 8101c0dfd42a232f1d2872de4f412d8d61d5646f Mon Sep 17 00:00:00 2001
> > From: Johan Hovold
> > Date: Mon, 14 Jul 2014 18:43:31 +0200
> > Subject: [PATCH] HID: usbhid: add HID_QUIRK_IN
On Mon, 14 Jul 2014, Johan Hovold wrote:
> From 8101c0dfd42a232f1d2872de4f412d8d61d5646f Mon Sep 17 00:00:00 2001
> From: Johan Hovold
> Date: Mon, 14 Jul 2014 18:43:31 +0200
> Subject: [PATCH] HID: usbhid: add HID_QUIRK_IN
>
> Add quirk to submit the interrupt-in urb already at start() rather t
[ +CC: Jiri and linux-input ]
On Wed, Jul 09, 2014 at 03:07:33PM +0200, Johan Hovold wrote:
> On Mon, Jul 07, 2014 at 10:34:30PM -0700, Greg Kroah-Hartman wrote:
> > On Mon, Jul 07, 2014 at 11:24:42AM +0200, Johan Hovold wrote:
>
> > > I ended up getting the same laptop so now I'm facing the same
On Mon, Jul 07, 2014 at 10:34:30PM -0700, Greg Kroah-Hartman wrote:
> On Mon, Jul 07, 2014 at 11:24:42AM +0200, Johan Hovold wrote:
> > I ended up getting the same laptop so now I'm facing the same problem
> > with repeated disconnects (especially during resume, which is really
> > annoying as it
On Mon, Jul 07, 2014 at 11:24:42AM +0200, Johan Hovold wrote:
> On Sun, Jun 01, 2014 at 10:43:21AM -0700, Greg Kroah-Hartman wrote:
> > On Sun, Jun 01, 2014 at 12:21:55PM -0400, Alan Stern wrote:
> > > On Sun, 1 Jun 2014, Bjørn Mork wrote:
> > >
> > > > Greg KH writes:
> > > >
> > > > > Ok, here
On Sun, Jun 01, 2014 at 10:43:21AM -0700, Greg Kroah-Hartman wrote:
> On Sun, Jun 01, 2014 at 12:21:55PM -0400, Alan Stern wrote:
> > On Sun, 1 Jun 2014, Bjørn Mork wrote:
> >
> > > Greg KH writes:
> > >
> > > > Ok, here's the dump for when the device keeps disconnecting itself from
> > > > the
On Sun, 1 Jun 2014, Greg KH wrote:
> > It doesn't look to me like a crash. It looks more like the driver is
> > missing.
>
> Doh, I had based my kernel config on my desktop, and it didn't have the
> hid multitouch driver enabled.
>
> Turning that on and, wow, it works! Thanks for pointing out
On Sun, Jun 01, 2014 at 12:21:55PM -0400, Alan Stern wrote:
> On Sun, 1 Jun 2014, Bjørn Mork wrote:
>
> > Greg KH writes:
> >
> > > Ok, here's the dump for when the device keeps disconnecting itself from
> > > the bus (no call to check_highspeed() anymore).
> > >
> > > Things go better, but then
On Sun, 1 Jun 2014, Bjørn Mork wrote:
> Greg KH writes:
>
> > Ok, here's the dump for when the device keeps disconnecting itself from
> > the bus (no call to check_highspeed() anymore).
> >
> > Things go better, but then the device just goes quiet, and resets. Any
> > ideas? I'll dig further t
Greg KH writes:
> Ok, here's the dump for when the device keeps disconnecting itself from
> the bus (no call to check_highspeed() anymore).
>
> Things go better, but then the device just goes quiet, and resets. Any
> ideas? I'll dig further this evening...
>
> 8800d906a0c0 2610372685 S Ci:2
On Sat, May 31, 2014 at 08:54:52AM -0700, Greg KH wrote:
> On Sat, May 31, 2014 at 04:45:01PM +0200, Bjørn Mork wrote:
> > Greg KH writes:
> >
> > > 8800da9be6c0 3444255124 S Ci:2:067:0 s 80 06 0100 0012 18 <
> > > 8800da9be6c0 3444255418 C Ci:2:067:0 0 18 = 12010002 0008
> > >
On Sat, May 31, 2014 at 04:45:01PM +0200, Bjørn Mork wrote:
> Greg KH writes:
>
> > 8800da9be6c0 3444255124 S Ci:2:067:0 s 80 06 0100 0012 18 <
> > 8800da9be6c0 3444255418 C Ci:2:067:0 0 18 = 12010002 0008 f3048900
> > 1300040e 0001
>
> So you are successfully reading the devic
Greg KH writes:
> 8800da9be6c0 3444255124 S Ci:2:067:0 s 80 06 0100 0012 18 <
> 8800da9be6c0 3444255418 C Ci:2:067:0 0 18 = 12010002 0008 f3048900
> 1300040e 0001
So you are successfully reading the device descriptor in hub_port_init()
> 88020b7a76c0 3444255485 S Ci:2:067:
On Fri, May 30, 2014 at 09:30:36PM -0700, Greg KH wrote:
> On Wed, Oct 16, 2013 at 08:49:34AM -0700, Sarah Sharp wrote:
> > On Fri, Oct 04, 2013 at 11:39:47AM -0500, Drew Von Spreecken wrote:
> > > Sarah, I've enabled debugging for the module if it helps... Log attached.
> >
> > Hi Drew,
> >
> >
On Wed, Oct 16, 2013 at 08:49:34AM -0700, Sarah Sharp wrote:
> On Fri, Oct 04, 2013 at 11:39:47AM -0500, Drew Von Spreecken wrote:
> > Sarah, I've enabled debugging for the module if it helps... Log attached.
>
> Hi Drew,
>
> > On 09/30/2013 06:19 PM, Sarah Sharp wrote:
> > >Hi Drew!
> > >
> > >I
On Fri, Oct 04, 2013 at 11:39:47AM -0500, Drew Von Spreecken wrote:
> Sarah, I've enabled debugging for the module if it helps... Log attached.
Hi Drew,
> On 09/30/2013 06:19 PM, Sarah Sharp wrote:
> >Hi Drew!
> >
> >I'm the xHCI driver maintainer, and it helps to Cc me on issues with USB
> >devi
Hi Drew!
I'm the xHCI driver maintainer, and it helps to Cc me on issues with USB
devices under xHCI hosts.
On Sun, Sep 29, 2013 at 11:14:47AM -0500, Drew Von Spreecken wrote:
> I have an Elan touchscreen that is causing USB resets and errors at
> boot and intermittently during use. The touchscre
I have an Elan touchscreen that is causing USB resets and errors at boot
and intermittently during use. The touchscreen works as expected but
messages are still being logged to kern.log.
It appears to get detected correctly:
Bus 001 Device 002: ID 8087:8000 Intel Corp.
Bus 001 Device 001: ID 1
19 matches
Mail list logo
