From: Scott Branden <sbranden@broadcom.com>
To: John Youn <johnyoun@synopsys.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
<linux-usb@vger.kernel.org>, Roman Bacik <rbacik@broadcom.com>
Cc: <linux-kernel@vger.kernel.org>, <bcm-kernel-feedback-list@broadcom.com>
Subject: Re: [PATCH v3 0/1] USB DWC2 parity fix in isochronous mode
Date: Wed, 23 Sep 2015 00:35:54 -0700 [thread overview]
Message-ID: <5602565A.90304@broadcom.com> (raw)
In-Reply-To: <1441934023-6557-1-git-send-email-sbranden@broadcom.com>
Hi John,
Could you please review the v3 Patch. I believe we have address all of
your comments?
On 15-09-10 06:13 PM, Scott Branden wrote:
> This patch contains a fix for a real world interop problem found
> when using the Synopsis DWC2 USB controller with isochronous audio as
> detailed in the commit message.
>
> Changes from v2:
> - created s2c_hsotg_chage_ep_iso_parity function to call function in 3 places in code
> - used hsotg->num_of_eps instead of MAX_EPS_CHANNELS
>
> Changes from v1:
> - Address code review comments as per previous responses:
> - renamed parity_set to has_correct_parity and reorder some logic
>
>
> Roman Bacik (1):
> usb: dwc2: gadget: parity fix in isochronous mode
>
> drivers/usb/dwc2/core.h | 1 +
> drivers/usb/dwc2/gadget.c | 58 ++++++++++++++++++++++++++++++++++++++++++-----
> drivers/usb/dwc2/hw.h | 1 +
> 3 files changed, 54 insertions(+), 6 deletions(-)
>
next prev parent reply other threads:[~2015-09-23 7:36 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-11 1:13 [PATCH v3 0/1] USB DWC2 parity fix in isochronous mode Scott Branden
2015-09-11 1:13 ` [PATCH v3 1/1] usb: dwc2: gadget: " Scott Branden
2015-09-23 7:35 ` Scott Branden [this message]
2015-09-23 8:11 ` [PATCH v3 0/1] USB DWC2 " John Youn
2015-09-23 8:18 ` John Youn
2015-09-23 15:39 ` Scott Branden
2015-09-23 18:05 ` John Youn
2015-09-24 4:21 ` John Youn
2015-09-24 17:28 ` Roman Bacik
2015-09-25 3:15 ` John Youn
2015-09-28 15:27 ` Roman Bacik
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=5602565A.90304@broadcom.com \
--to=sbranden@broadcom.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=gregkh@linuxfoundation.org \
--cc=johnyoun@synopsys.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=rbacik@broadcom.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 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.