diff for duplicates of <59C265B1.6020909@linux.intel.com> diff --git a/a/1.txt b/N1/1.txt index 36bae4b..1bd6f28 100644 --- a/a/1.txt +++ b/N1/1.txt @@ -1,5 +1,5 @@ -On 20.09.2017 12:24, yinbo.zhu at nxp.com wrote: -> From: "yinbo.zhu" <yinbo.zhu@nxp.com> +On 20.09.2017 12:24, yinbo.zhu-3arQi8VN3Tc@public.gmane.org wrote: +> From: "yinbo.zhu" <yinbo.zhu-3arQi8VN3Tc@public.gmane.org> > > When a transaction error (defined in Section 4.10.2.3, "USB > Transaction Error" of the xHCI Specification) occurs on the @@ -10,9 +10,9 @@ On 20.09.2017 12:24, yinbo.zhu at nxp.com wrote: > transition the endpoint to the Stopped state. In order to > restart the transfer, the driver can perform either of the > following: -> ? Ring the doorbell again, which restarts the transfer from +> • Ring the doorbell again, which restarts the transfer from > where it stopped, or -> ? Issue a Set TR (Transfer Ring) Dequeue Pointer command for +> • Issue a Set TR (Transfer Ring) Dequeue Pointer command for > the endpoint to start the transfer from a different > Transfer Ring pointer Consider the following scenario: > 1. The xHCI driver prepares a control transfer read to one @@ -49,12 +49,12 @@ into a no-op. > > Impact: When this issue occurs, the device likely responds in > one of the following ways: -> ? The device responds with a STALL because the data stage has +> • The device responds with a STALL because the data stage has > unexpectedly changed directions. The controller then generates > a Stall Error transfer event, to which software must issue a > Reset Endpoint command followed by a Set TR Dequeue Pointer > command pointing to a new Setup TRB to clear the STALL condition. -> ? The device does not respond to the inverted data stage and the +> • The device does not respond to the inverted data stage and the > transaction times out. The controller generates another USB > Transaction Error transfer event, to which software likely > performs a USB Reset to the device because it is unresponsive. @@ -98,3 +98,9 @@ It's also possible this is toggle/sequence number issue, you could try issuing a EP_SOFT_RESET endpoint reset instead. -Mathias + + +-- +To unsubscribe from this list: send the line "unsubscribe devicetree" in +the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org +More majordomo info at http://vger.kernel.org/majordomo-info.html diff --git a/a/content_digest b/N1/content_digest index c8d1033..c885e54 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -1,12 +1,23 @@ "ref\020170920092441.21292-1-yinbo.zhu@nxp.com\0" - "From\0mathias.nyman@linux.intel.com (Mathias Nyman)\0" - "Subject\0[PATCH v1] usb: host: Implement workaround for Erratum A-007463\0" + "ref\020170920092441.21292-1-yinbo.zhu-3arQi8VN3Tc@public.gmane.org\0" + "From\0Mathias Nyman <mathias.nyman-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>\0" + "Subject\0Re: [PATCH v1] usb: host: Implement workaround for Erratum A-007463\0" "Date\0Wed, 20 Sep 2017 15:57:21 +0300\0" - "To\0linux-arm-kernel@lists.infradead.org\0" + "To\0yinbo.zhu-3arQi8VN3Tc@public.gmane.org" + Rob Herring <robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org> + Mark Rutland <mark.rutland-5wv7dgnIgG8@public.gmane.org> + Russell King <linux-I+IVW8TIWO2tmTQ+vhA3Yw@public.gmane.org> + " Felipe Balbi <balbi-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>\0" + "Cc\0Greg Kroah-Hartman <gregkh-hQyY1W1yCW8ekmWlsbkhG0B+6BGkLq7r@public.gmane.org>" + Mathias Nyman <mathias.nyman-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org> + open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS <devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org> + moderated list:ARM PORT <linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org> + open list <linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org> + " open list:DESIGNWARE USB3 DRD IP DRIVER <linux-usb-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>\0" "\00:1\0" "b\0" - "On 20.09.2017 12:24, yinbo.zhu at nxp.com wrote:\n" - "> From: \"yinbo.zhu\" <yinbo.zhu@nxp.com>\n" + "On 20.09.2017 12:24, yinbo.zhu-3arQi8VN3Tc@public.gmane.org wrote:\n" + "> From: \"yinbo.zhu\" <yinbo.zhu-3arQi8VN3Tc@public.gmane.org>\n" ">\n" "> When a transaction error (defined in Section 4.10.2.3, \"USB\n" "> Transaction Error\" of the xHCI Specification) occurs on the\n" @@ -17,9 +28,9 @@ "> transition the endpoint to the Stopped state. In order to\n" "> restart the transfer, the driver can perform either of the\n" "> following:\n" - "> ? Ring the doorbell again, which restarts the transfer from\n" + "> \342\200\242 Ring the doorbell again, which restarts the transfer from\n" "> where it stopped, or\n" - "> ? Issue a Set TR (Transfer Ring) Dequeue Pointer command for\n" + "> \342\200\242 Issue a Set TR (Transfer Ring) Dequeue Pointer command for\n" "> the endpoint to start the transfer from a different\n" "> Transfer Ring pointer Consider the following scenario:\n" "> 1. The xHCI driver prepares a control transfer read to one\n" @@ -56,12 +67,12 @@ ">\n" "> Impact: When this issue occurs, the device likely responds in\n" "> one of the following ways:\n" - "> ? The device responds with a STALL because the data stage has\n" + "> \342\200\242 The device responds with a STALL because the data stage has\n" "> unexpectedly changed directions. The controller then generates\n" "> a Stall Error transfer event, to which software must issue a\n" "> Reset Endpoint command followed by a Set TR Dequeue Pointer\n" "> command pointing to a new Setup TRB to clear the STALL condition.\n" - "> ? The device does not respond to the inverted data stage and the\n" + "> \342\200\242 The device does not respond to the inverted data stage and the\n" "> transaction times out. The controller generates another USB\n" "> Transaction Error transfer event, to which software likely\n" "> performs a USB Reset to the device because it is unresponsive.\n" @@ -104,6 +115,12 @@ "It's also possible this is toggle/sequence number issue,\n" "you could try issuing a EP_SOFT_RESET endpoint reset instead.\n" "\n" - -Mathias + "-Mathias\n" + "\n" + "\n" + "--\n" + "To unsubscribe from this list: send the line \"unsubscribe devicetree\" in\n" + "the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org\n" + More majordomo info at http://vger.kernel.org/majordomo-info.html -f6116f874a24c314b79e8156956ec6875b9ce6f194822d035117d377322c5bdc +438fbbc29497b66297670b4b3c41656924b8ceccd33ae4f823db45fb4fdb73fb
diff --git a/a/1.txt b/N2/1.txt index 36bae4b..be257f0 100644 --- a/a/1.txt +++ b/N2/1.txt @@ -1,4 +1,4 @@ -On 20.09.2017 12:24, yinbo.zhu at nxp.com wrote: +On 20.09.2017 12:24, yinbo.zhu@nxp.com wrote: > From: "yinbo.zhu" <yinbo.zhu@nxp.com> > > When a transaction error (defined in Section 4.10.2.3, "USB @@ -10,9 +10,9 @@ On 20.09.2017 12:24, yinbo.zhu at nxp.com wrote: > transition the endpoint to the Stopped state. In order to > restart the transfer, the driver can perform either of the > following: -> ? Ring the doorbell again, which restarts the transfer from +> • Ring the doorbell again, which restarts the transfer from > where it stopped, or -> ? Issue a Set TR (Transfer Ring) Dequeue Pointer command for +> • Issue a Set TR (Transfer Ring) Dequeue Pointer command for > the endpoint to start the transfer from a different > Transfer Ring pointer Consider the following scenario: > 1. The xHCI driver prepares a control transfer read to one @@ -49,12 +49,12 @@ into a no-op. > > Impact: When this issue occurs, the device likely responds in > one of the following ways: -> ? The device responds with a STALL because the data stage has +> • The device responds with a STALL because the data stage has > unexpectedly changed directions. The controller then generates > a Stall Error transfer event, to which software must issue a > Reset Endpoint command followed by a Set TR Dequeue Pointer > command pointing to a new Setup TRB to clear the STALL condition. -> ? The device does not respond to the inverted data stage and the +> • The device does not respond to the inverted data stage and the > transaction times out. The controller generates another USB > Transaction Error transfer event, to which software likely > performs a USB Reset to the device because it is unresponsive. diff --git a/a/content_digest b/N2/content_digest index c8d1033..de65b09 100644 --- a/a/content_digest +++ b/N2/content_digest @@ -1,11 +1,21 @@ "ref\020170920092441.21292-1-yinbo.zhu@nxp.com\0" - "From\0mathias.nyman@linux.intel.com (Mathias Nyman)\0" - "Subject\0[PATCH v1] usb: host: Implement workaround for Erratum A-007463\0" + "From\0Mathias Nyman <mathias.nyman@linux.intel.com>\0" + "Subject\0Re: [PATCH v1] usb: host: Implement workaround for Erratum A-007463\0" "Date\0Wed, 20 Sep 2017 15:57:21 +0300\0" - "To\0linux-arm-kernel@lists.infradead.org\0" + "To\0yinbo.zhu@nxp.com" + Rob Herring <robh+dt@kernel.org> + Mark Rutland <mark.rutland@arm.com> + Russell King <linux@armlinux.org.uk> + " Felipe Balbi <balbi@kernel.org>\0" + "Cc\0Greg Kroah-Hartman <gregkh@linuxfoundation.org>" + Mathias Nyman <mathias.nyman@intel.com> + open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS <devicetree@vger.kernel.org> + moderated list:ARM PORT <linux-arm-kernel@lists.infradead.org> + open list <linux-kernel@vger.kernel.org> + " open list:DESIGNWARE USB3 DRD IP DRIVER <linux-usb@vger.kernel.org>\0" "\00:1\0" "b\0" - "On 20.09.2017 12:24, yinbo.zhu at nxp.com wrote:\n" + "On 20.09.2017 12:24, yinbo.zhu@nxp.com wrote:\n" "> From: \"yinbo.zhu\" <yinbo.zhu@nxp.com>\n" ">\n" "> When a transaction error (defined in Section 4.10.2.3, \"USB\n" @@ -17,9 +27,9 @@ "> transition the endpoint to the Stopped state. In order to\n" "> restart the transfer, the driver can perform either of the\n" "> following:\n" - "> ? Ring the doorbell again, which restarts the transfer from\n" + "> \342\200\242 Ring the doorbell again, which restarts the transfer from\n" "> where it stopped, or\n" - "> ? Issue a Set TR (Transfer Ring) Dequeue Pointer command for\n" + "> \342\200\242 Issue a Set TR (Transfer Ring) Dequeue Pointer command for\n" "> the endpoint to start the transfer from a different\n" "> Transfer Ring pointer Consider the following scenario:\n" "> 1. The xHCI driver prepares a control transfer read to one\n" @@ -56,12 +66,12 @@ ">\n" "> Impact: When this issue occurs, the device likely responds in\n" "> one of the following ways:\n" - "> ? The device responds with a STALL because the data stage has\n" + "> \342\200\242 The device responds with a STALL because the data stage has\n" "> unexpectedly changed directions. The controller then generates\n" "> a Stall Error transfer event, to which software must issue a\n" "> Reset Endpoint command followed by a Set TR Dequeue Pointer\n" "> command pointing to a new Setup TRB to clear the STALL condition.\n" - "> ? The device does not respond to the inverted data stage and the\n" + "> \342\200\242 The device does not respond to the inverted data stage and the\n" "> transaction times out. The controller generates another USB\n" "> Transaction Error transfer event, to which software likely\n" "> performs a USB Reset to the device because it is unresponsive.\n" @@ -106,4 +116,4 @@ "\n" -Mathias -f6116f874a24c314b79e8156956ec6875b9ce6f194822d035117d377322c5bdc +de140ecd67d8968ae42eac956143a16ee74c8898011aaec97cc749f06884418c
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.