Re: lan78xx: About 8000 usb interrupts per second when idle

2019-04-14 Thread Lukas Wunner
On Tue, Apr 09, 2019 at 09:28:16AM +, Minas Harutyunyan wrote: > Am 09.04.19 um 08:54 schrieb Jisheng Zhang: > > The second one: 8000 usb interrupts per second when idle. > > This is abnormal. any idea? Is it due to the lan78xx? > > dwc2 in host mode enable SOF interrupts if any periodic EP ar

Re: Possible regression between 4.9 and 4.13

2017-08-29 Thread Lukas Wunner
On Tue, Aug 29, 2017 at 05:51:38PM +0200, Greg Kroah-Hartman wrote: > On Tue, Aug 29, 2017 at 05:34:56PM +0200, Lukas Wunner wrote: > > On Tue, Aug 29, 2017 at 04:47:25PM +0200, Greg Kroah-Hartman wrote: > > > On Tue, Aug 29, 2017 at 03:38:52PM +0200, Lukas Wunner wrote: >

Re: Possible regression between 4.9 and 4.13

2017-08-29 Thread Lukas Wunner
On Tue, Aug 29, 2017 at 04:28:53PM +0300, Mathias Nyman wrote: > This tight check was originally done to detect pci hotplug removed > hosts as soon as possible. In Mason's case, the parent of the XHCI controller isn't a hotplug port, see this lspci output: https://www.spinics.net/lists/linux-usb/

Re: Possible regression between 4.9 and 4.13

2017-08-29 Thread Lukas Wunner
On Tue, Aug 29, 2017 at 04:47:25PM +0200, Greg Kroah-Hartman wrote: > On Tue, Aug 29, 2017 at 03:38:52PM +0200, Lukas Wunner wrote: > > On Tue, Aug 29, 2017 at 04:28:53PM +0300, Mathias Nyman wrote: > > > Then again it might be a bit too drastic to kill xhci just because > &

Re: Possible regression between 4.9 and 4.13

2017-08-29 Thread Lukas Wunner
On Tue, Aug 29, 2017 at 04:28:53PM +0300, Mathias Nyman wrote: > Then again it might be a bit too drastic to kill xhci just because > we read 0x once from a mmio xhci register. Maybe we should > return an error a couple times before actually tearing down xhci. > > This tight check was orig

Re: Thunderbolt adapter fails to instantiate USB and device enumeration if already connected at boot time

2017-01-03 Thread Lukas Wunner
On Mon, Jan 02, 2017 at 02:45:00PM -0700, Chris Murphy wrote: > On Mon, Jan 2, 2017 at 2:28 PM, Alan Stern wrote: > > Considering that the failed boot log contains no USB messages at all, > > and no messages referring to PCI bus :37 (the bus associated with > > the adapter), this certainly loo

Re: USB hot-plug not working (ASUS TP301UA-C4028T)

2016-10-20 Thread Lukas Wunner
On Tue, Oct 11, 2016 at 11:18:28AM -0400, Alan Stern wrote: > On Sat, 8 Oct 2016, Lukas Wunner wrote: > > The PCI core already calls pm_runtime_get_sync() before invoking the > > ->probe hook of a driver (see local_pci_probe()). Drivers need to > > explicitly release a ru

Re: USB hot-plug not working (ASUS TP301UA-C4028T)

2016-10-08 Thread Lukas Wunner
On Thu, Oct 06, 2016 at 10:42:14AM -0400, Alan Stern wrote: > On Wed, 5 Oct 2016, Lukas Wunner wrote: > > On Wed, Oct 05, 2016 at 01:54:01PM -0500, Bjorn Helgaas wrote: > > > On Wed, Oct 05, 2016 at 10:45:22AM -0400, Alan Stern wrote: > > > > In short, Pierre'

Re: USB hot-plug not working (ASUS TP301UA-C4028T)

2016-10-05 Thread Lukas Wunner
On Wed, Oct 05, 2016 at 01:54:01PM -0500, Bjorn Helgaas wrote: > On Wed, Oct 05, 2016 at 10:45:22AM -0400, Alan Stern wrote: > > In short, Pierre's USB host controller doesn't send wakeup signals from > > runtime suspend, because the firmware limits the runtime-suspend state > > to D0 and the contr

Re: kmem_cache_alloc fail with unable to handle paging request after pci hotplug remove.

2016-07-05 Thread Lukas Wunner
On Tue, Jul 05, 2016 at 11:00:21AM +0800, AceLan Kao wrote: > These are logs from my machine. > > *** Before plug-in the USB key > > u@u-XPS-13-9xxx:~$ sudo lspci - -s 00:1c.0 > 00:1c.0 PCI bridge: Intel Corporation Device 9d10 (rev f1) (prog-if 00 > [Normal decode]) [...] > L

Re: kmem_cache_alloc fail with unable to handle paging request after pci hotplug remove.

2016-07-04 Thread Lukas Wunner
On Mon, Jul 04, 2016 at 06:04:42PM +0300, Mathias Nyman wrote: > On 04.07.2016 17:25, Rafael J. Wysocki wrote: > > On Mon, Jul 4, 2016 at 4:26 PM, Mathias Nyman > > wrote: > > > AceLan Kao can get his DELL XPS 13 laptop to hang by plugging/un-plugging > > > a USB 3.1 key via thunderbolt port. > >