From: Oliver Neukum <oneukum@suse.com>
To: Jisheng Zhang <Jisheng.Zhang@synaptics.com>,
Minas Harutyunyan <minas.harutyunyan@synopsys.com>
Cc: Douglas Anderson <dianders@chromium.org>,
Stefan Wahren <stefan.wahren@i2se.com>,
"linux-rpi-kernel@lists.infradead.org"
<linux-rpi-kernel@lists.infradead.org>,
Woojung Huh <woojung.huh@microchip.com>,
"linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>
Subject: Re: lan78xx: About 8000 usb interrupts per second when idle
Date: Wed, 10 Apr 2019 12:08:48 +0200 [thread overview]
Message-ID: <1554890928.21725.6.camel@suse.com> (raw)
In-Reply-To: <20190410172917.23cb7d0e@xhacker.debian>
On Mi, 2019-04-10 at 09:37 +0000, Jisheng Zhang wrote:
> On Tue, 9 Apr 2019 09:28:16 +0000 Minas Harutyunyan wrote:
Hi,
> > dwc2 in host mode enable SOF interrupts if any periodic EP are in use.
> > So, 8000 interrupts per second is expectant behavior.
>
> Makes sense. 8 microframes each 1ms, so 8*1000 = 8000 interrupts/s
The remedy for that would be using autosuspend. That just tells us that
support for autosuspend is not optional.
Regards
Oliver
next prev parent reply other threads:[~2019-04-10 10:08 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 ` lan78xx: About 8000 usb interrupts per second when idle Stefan Wahren
2019-04-09 9:28 ` Minas Harutyunyan
2019-04-10 9:37 ` Jisheng Zhang
2019-04-10 10:08 ` Oliver Neukum [this message]
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=1554890928.21725.6.camel@suse.com \
--to=oneukum@suse.com \
--cc=Jisheng.Zhang@synaptics.com \
--cc=dianders@chromium.org \
--cc=linux-rpi-kernel@lists.infradead.org \
--cc=linux-usb@vger.kernel.org \
--cc=minas.harutyunyan@synopsys.com \
--cc=stefan.wahren@i2se.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).