All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stefan Wahren <stefan.wahren@i2se.com>
To: Jisheng Zhang <Jisheng.Zhang@synaptics.com>,
	Minas Harutyunyan <hminas@synopsys.com>
Cc: "linux-rpi-kernel@lists.infradead.org" 
	<linux-rpi-kernel@lists.infradead.org>,
	"linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>,
	Douglas Anderson <dianders@chromium.org>,
	Woojung Huh <woojung.huh@microchip.com>
Subject: lan78xx: About 8000 usb interrupts per second when idle
Date: Tue, 9 Apr 2019 09:18:03 +0200	[thread overview]
Message-ID: <3cda1098-e0ad-42ac-af96-c85eba480556@i2se.com> (raw)
In-Reply-To: <20190409144655.753d3bd9@xhacker.debian>

Hi Minas,

Am 09.04.19 um 08:54 schrieb Jisheng Zhang:
> On Mon, 8 Apr 2019 16:05:51 +0800 Jisheng Zhang wrote:
>
>> Hi Stefan,
>>
>> On Mon, 8 Apr 2019 09:57:14 +0200 Stefan Wahren wrote:
>>
>>>
>>> Hi Jisheng,
>>>
>>>
>>> thanks for sending this patch.  I already reported this issue last year
>>> [1], but Microchip wasn't able to provide a fix.
>>>
>>> I will give it a try.
>>>   
>>>> The second one: 8000 usb interrupts per second when idle. This is abnormal.
>>>> any idea? Is it due to the lan78xx?    
>>> Does this downstream patch [2] improve your situation?  
>> Thanks a lot. Will try the patch tonight.
> I tried this patch, it doesn't help. One more observation: if I
> ifconfig eth0 down, I can still get 8000 usb interrupts per second. Not sure
> whether this is usb issue or not.

Jisheng reports a lot of USB interrupts while the lan78xx driver on
Raspberry Pi 3B+ is in idle.

Any suggestions to narrow this down?

Stefan

>
> Thanks
>

       reply	other threads:[~2019-04-09  7:18 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20190408143443.335f7e93@xhacker.debian>
     [not found] ` <002929b7-9a0d-6d92-4e03-18a6748c6708@i2se.com>
     [not found]   ` <20190408160551.03911b27@xhacker.debian>
     [not found]     ` <20190409144655.753d3bd9@xhacker.debian>
2019-04-09  7:18       ` Stefan Wahren [this message]
2019-04-09  9:28         ` lan78xx: About 8000 usb interrupts per second when idle Minas Harutyunyan
2019-04-10  9:37           ` Jisheng Zhang
2019-04-10 10:08             ` Oliver Neukum
2019-04-14 19:46           ` Lukas Wunner
2019-04-15  0:53             ` Woojung.Huh
2019-04-15 17:35             ` Doug Anderson
2019-04-15 18:15               ` Alan Stern
2019-04-14 21:51 Paul Zimmerman

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3cda1098-e0ad-42ac-af96-c85eba480556@i2se.com \
    --to=stefan.wahren@i2se.com \
    --cc=Jisheng.Zhang@synaptics.com \
    --cc=dianders@chromium.org \
    --cc=hminas@synopsys.com \
    --cc=linux-rpi-kernel@lists.infradead.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=woojung.huh@microchip.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.