[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAATdQgBSPHyhWsAvLE=_Fd990exgaZ+Dzftad7++ZjzGsSkmJA@mail.gmail.com>
Date: Tue, 19 Nov 2019 12:05:28 +0800
From: Ikjoon Jang <ikjn@...omium.org>
To: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Cc: linux-usb@...r.kernel.org, devicetree@...r.kernel.org,
linux-kernel@...r.kernel.org, Rob Herring <robh+dt@...nel.org>,
Mark Rutland <mark.rutland@....com>,
Alan Stern <stern@...land.harvard.edu>,
Suwan Kim <suwan.kim027@...il.com>,
"Gustavo A . R . Silva" <gustavo@...eddedor.com>,
Johan Hovold <johan@...nel.org>,
Nicolas Boitchat <drinkcat@...omium.org>
Subject: Re: [PATCH 0/2] usb: override hub device bInterval with device node
On Sun, Nov 17, 2019 at 3:14 PM Greg Kroah-Hartman
<gregkh@...uxfoundation.org> wrote:
>
> On Sun, Nov 17, 2019 at 11:31:49AM +0800, Ikjoon Jang wrote:
> > This patchset enables hard wired hub device to use different bInterval
> > from its descriptor when the hub has a combined device node.
>
> If it is a hard-wired hub, why can't you change that interval in the
> firmware for that hub as you (as a platform owner) have control over
> that?
yes, actually that's the best option, but the hub devices were shipped with
mask ROM we can't change the descriptors.
>
> thanks,
>
> greg k-h
Powered by blists - more mailing lists