From: Matthias Kaehlcke <mka@chromium.org>
To: Douglas Anderson <dianders@chromium.org>
Cc: Felipe Balbi <felipe.balbi@linux.intel.com>,
Minas Harutyunyan <hminas@synopsys.com>,
linux-rockchip@lists.infradead.org,
Stefan Wahren <stefan.wahren@i2se.com>,
tfiga@chromium.org, groeck@chromium.org,
Martin Schiller <ms@dev.tdt.de>,
stable@vger.kernel.org,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] usb: dwc2: host: Fix wMaxPacketSize handling (fix webcam regression)
Date: Mon, 3 Jun 2019 15:44:17 -0700 [thread overview]
Message-ID: <20190603224417.GN40515@google.com> (raw)
In-Reply-To: <20190531200412.129429-1-dianders@chromium.org>
On Fri, May 31, 2019 at 01:04:12PM -0700, Douglas Anderson wrote:
> In commit abb621844f6a ("usb: ch9: make usb_endpoint_maxp() return
> only packet size") the API to usb_endpoint_maxp() changed. It used to
> just return wMaxPacketSize but after that commit it returned
> wMaxPacketSize with the high bits (the multiplier) masked off. If you
> wanted to get the multiplier it was now up to your code to call the
> new usb_endpoint_maxp_mult() which was introduced in
> commit 541b6fe63023 ("usb: add helper to extract bits 12:11 of
> wMaxPacketSize").
>
> Prior to the API change most host drivers were updated, but no update
> was made to dwc2. Presumably it was assumed that dwc2 was too
> simplistic to use the multiplier and thus just didn't support a
> certain class of USB devices. However, it turns out that dwc2 did use
> the multiplier and many devices using it were working quite nicely.
> That means that many USB devices have been broken since the API
> change. One such device is a Logitech HD Pro Webcam C920.
>
> Specifically, though dwc2 didn't directly call usb_endpoint_maxp(), it
> did call usb_maxpacket() which in turn called usb_endpoint_maxp().
>
> Let's update dwc2 to work properly with the new API.
>
> Fixes: abb621844f6a ("usb: ch9: make usb_endpoint_maxp() return only packet size")
> Cc: stable@vger.kernel.org
> Signed-off-by: Douglas Anderson <dianders@chromium.org>
I'm not really familiar with the dwc2 driver, but this looks
reasonable to me. FWIW:
Reviewed-by: Matthias Kaehlcke <mka@chromium.org>
next prev parent reply other threads:[~2019-06-03 22:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-31 20:04 [PATCH] usb: dwc2: host: Fix wMaxPacketSize handling (fix webcam regression) Douglas Anderson
2019-05-31 20:04 ` Douglas Anderson
2019-06-03 22:44 ` Matthias Kaehlcke [this message]
2019-06-06 8:06 ` Minas Harutyunyan
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=20190603224417.GN40515@google.com \
--to=mka@chromium.org \
--cc=dianders@chromium.org \
--cc=felipe.balbi@linux.intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=groeck@chromium.org \
--cc=hminas@synopsys.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=linux-usb@vger.kernel.org \
--cc=ms@dev.tdt.de \
--cc=stable@vger.kernel.org \
--cc=stefan.wahren@i2se.com \
--cc=tfiga@chromium.org \
/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.