From: Ikjoon Jang <firstname.lastname@example.org>
To: Johan Hovold <email@example.com>
"GustavoA . R . Silva" <firstname.lastname@example.org>,
Nicolas Boichat <email@example.com>
Subject: Re: [PATCH v4 2/2] usb: overridable hub bInterval by device node
Date: Fri, 6 Dec 2019 11:57:30 +0800 [thread overview]
Message-ID: <CAATdQgBK4gWvR06YJ3Z_y5NeqLKYY7Ajc0KG78rG2deR3Ga11A@mail.gmail.com> (raw)
On Thu, Dec 5, 2019 at 10:26 PM Johan Hovold <firstname.lastname@example.org> wrote:
> On Thu, Dec 05, 2019 at 03:32:38PM +0800, Ikjoon Jang wrote:
> > On Wed, Dec 4, 2019 at 3:55 PM Johan Hovold <email@example.com> wrote:
> > > But related to my question above, why do you need to do this during
> > > enumeration? Why not just set the lower interval value in the hub
> > > driver?
> > Because I want device tree's bInterval to be checked against the same rules
> > defined in usb_parse_endpoint(). e.g. although hardware says its maximum
> > is 255, but the practical limit is still 0 to 16, so the code can
> > print warnings when bInterval from device node is too weird.
> But that could be handled refactoring the code in question or similar.
Yes, that should be worked. I can't exactly figure out how to refactor
the code for now, but maybe parsed endpoint descriptors are being
checked with default hard wired bInterval value and after that
an overridden value should be checked again.
Actually I don't care about the details of software policies. I just want
all devices to be handled in the same manner without any further
> The fundamental problem here is that you're using devicetree, which is
> supposed to only describe the hardware, to encode policy which should be
> deferred to user space.
The hub hardware has a default bInterval inside which is actually
adjustable. So I can think setting bInterval is to describe the hardware
rather than policy.
> So I think you need to figure out an interface that allows user space to
> set the polling interval for any hub at runtime instead.
Changing the interval at runtime is an another way to solve the
power consumption problem, but it's not so easy. At least xhci needs
to restart an endpoint and no devices are changing the interval after
next prev parent reply other threads:[~2019-12-06 3:57 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-03 10:15 [PATCH v4 2/2] usb: overridable hub bInterval by device node Ikjoon Jang
2019-12-03 15:23 ` Alan Stern
2019-12-04 7:07 ` Ikjoon Jang
2019-12-03 16:53 ` Johan Hovold
2019-12-04 7:04 ` Ikjoon Jang
2019-12-04 7:55 ` Johan Hovold
2019-12-05 7:32 ` Ikjoon Jang
2019-12-05 14:26 ` Johan Hovold
2019-12-06 3:57 ` Ikjoon Jang [this message]
2019-12-06 15:00 ` Alan Stern
2019-12-09 3:47 ` Ikjoon Jang
2019-12-06 15:26 ` Johan Hovold
2019-12-09 4:05 ` Ikjoon Jang
2019-12-10 15:02 ` Johan Hovold
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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).