[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAATdQgBRSJVjpCawa3eZXHLex-gWqdJrmQ6xriu11ok49UmNwg@mail.gmail.com>
Date: Wed, 4 Dec 2019 10:46:17 +0800
From: Ikjoon Jang <ikjn@...omium.org>
To: Johan Hovold <johan@...nel.org>
Cc: linux-usb@...r.kernel.org, devicetree@...r.kernel.org,
GregKroah-Hartman <gregkh@...uxfoundation.org>,
RobHerring <robh+dt@...nel.org>,
MarkRutland <mark.rutland@....com>,
AlanStern <stern@...land.harvard.edu>,
SuwanKim <suwan.kim027@...il.com>,
"GustavoA . R . Silva" <gustavo@...eddedor.com>,
linux-kernel@...r.kernel.org,
Nicolas Boichat <drinkcat@...omium.org>
Subject: Re: [PATCH v4 0/2] usb: override hub device bInterval with device
On Wed, Dec 4, 2019 at 12:40 AM Johan Hovold <johan@...nel.org> wrote:
>
> On Tue, Dec 03, 2019 at 06:15:21PM +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.
> >
> > When we know reducing autosuspend delay for built-in HIDs is better for
> > power saving, we can reduce it to the optimal value. But if a parent hub
> > has a long bInterval, mouse lags a lot from more frequent autosuspend.
> > So this enables overriding bInterval for a hard wired hub device only
> > when we know that reduces the power consumption.
> >
> > Changes in v4
> > - use of_property_read_u32() instead of of_property_read_u8()
>
> What changed in the previous versions?
changes in the previous versions:
v4: use of_property_read_u32() instead of of_property_read_u8()
v3: errata fixed "hub, interval" --> "hub,interval"
v2: do not use unlikely() macro, commit message
>
> Johan
Powered by blists - more mailing lists