From: Felipe Balbi <balbi@kernel.org>
To: Thinh Nguyen <thinh.nguyen@synopsys.com>,
linux-usb@vger.kernel.org, devicetree@vger.kernel.org,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>
Cc: John Youn <john.youn@synopsys.com>
Subject: [v6,2/3] usb: dwc3: Add disabling of start_transfer failure quirk
Date: Wed, 14 Nov 2018 13:41:25 +0200 [thread overview]
Message-ID: <87va4zj38a.fsf@linux.intel.com> (raw)
Thinh Nguyen <thinh.nguyen@synopsys.com> writes:
> DWC_usb31 peripheral v1.70a-ea06 and prior needs a SW workaround for
> isoc START TRANSFER command failure. However, some affected versions may
> have RTL patches to fix this without a SW workaround. Add this quirk to
> disable the SW workaround when it is not needed.
>
> Synopsys STAR 9001202023: Wrong microframe number for isochronous IN
> endpoints.
>
> Signed-off-by: Thinh Nguyen <thinhn@synopsys.com>
unfortunately, does't apply to testing/next. Could you rebase??
checking file Documentation/devicetree/bindings/usb/dwc3.txt
Hunk #1 FAILED at 37.
1 out of 1 hunk FAILED
(patch 1/3 is applied, though)
WARNING: multiple messages have this Message-ID (diff)
From: Felipe Balbi <balbi@kernel.org>
To: Thinh Nguyen <thinh.nguyen@synopsys.com>,
linux-usb@vger.kernel.org, devicetree@vger.kernel.org,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>
Cc: John Youn <john.youn@synopsys.com>
Subject: Re: [PATCH v6 2/3] usb: dwc3: Add disabling of start_transfer failure quirk
Date: Wed, 14 Nov 2018 13:41:25 +0200 [thread overview]
Message-ID: <87va4zj38a.fsf@linux.intel.com> (raw)
In-Reply-To: <ead428b935b52df74dbe386185e1b8298b0135b4.1541707248.git.thinhn@synopsys.com>
[-- Attachment #1: Type: text/plain, Size: 698 bytes --]
Thinh Nguyen <thinh.nguyen@synopsys.com> writes:
> DWC_usb31 peripheral v1.70a-ea06 and prior needs a SW workaround for
> isoc START TRANSFER command failure. However, some affected versions may
> have RTL patches to fix this without a SW workaround. Add this quirk to
> disable the SW workaround when it is not needed.
>
> Synopsys STAR 9001202023: Wrong microframe number for isochronous IN
> endpoints.
>
> Signed-off-by: Thinh Nguyen <thinhn@synopsys.com>
unfortunately, does't apply to testing/next. Could you rebase??
checking file Documentation/devicetree/bindings/usb/dwc3.txt
Hunk #1 FAILED at 37.
1 out of 1 hunk FAILED
(patch 1/3 is applied, though)
--
balbi
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
next reply other threads:[~2018-11-14 11:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-14 11:41 Felipe Balbi [this message]
2018-11-14 11:41 ` [PATCH v6 2/3] usb: dwc3: Add disabling of start_transfer failure quirk Felipe Balbi
-- strict thread matches above, loose matches on Subject: below --
2018-11-15 7:00 [v6,2/3] " Thinh Nguyen
2018-11-15 7:00 ` [PATCH v6 2/3] " Thinh Nguyen
2018-11-11 22:32 [v6,2/3] " Rob Herring
2018-11-11 22:32 ` [PATCH v6 2/3] " Rob Herring
2018-11-08 20:06 [v6,2/3] " Thinh Nguyen
2018-11-08 20:06 ` [PATCH v6 2/3] " Thinh Nguyen
2018-11-08 20:06 [PATCH v6 0/3] usb: dwc3: Workaround isoc start_transfer failure Thinh Nguyen
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=87va4zj38a.fsf@linux.intel.com \
--to=balbi@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=john.youn@synopsys.com \
--cc=linux-usb@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=robh+dt@kernel.org \
--cc=thinh.nguyen@synopsys.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.