From: Thinh Nguyen <Thinh.Nguyen@synopsys.com>
To: Mayank Rana <quic_mrana@quicinc.com>,
"peter.chen@kernel.org" <peter.chen@kernel.org>,
"balbi@kernel.org" <balbi@kernel.org>,
"gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>,
John Youn <John.Youn@synopsys.com>,
"quic_jackp@quicinc.com" <quic_jackp@quicinc.com>,
"quic_wcheng@quicinc.com" <quic_wcheng@quicinc.com>
Subject: Re: [PATCH] usb: dwc3: Fix ep0 handling when getting reset while doing control transfer
Date: Wed, 25 May 2022 03:52:40 +0000 [thread overview]
Message-ID: <ba6285cb-f9ff-8047-ad53-1f4534517b66@synopsys.com> (raw)
In-Reply-To: <ac4a59de-2eae-cab3-4b28-b89582978648@synopsys.com>
Thinh Nguyen wrote:
> Mayank Rana wrote:
>> @@ -3766,6 +3768,27 @@ static void dwc3_gadget_reset_interrupt(struct dwc3 *dwc)
>> }
>>
>> dwc3_reset_gadget(dwc);
>> +
>> + /*
>> + * From SNPS databook section 8.1.2, the EP0 should be in setup
>> + * phase. So ensure that EP0 is in setup phase by issuing a stall
>> + * and restart if EP0 is not in setup phase.
>> + */
>
> We should not issue End Transfer to control endpoint unless it's error
> case such as invalid direction. The databook also specify under section
> USB reset initialization to not send End Transfer to control endpoint.
>
>> + if (dwc->ep0state != EP0_SETUP_PHASE) {
>> + unsigned int dir;
>> +
>> + dir = !!dwc->ep0_expect_in;
>> + if (dwc->ep0state == EP0_DATA_PHASE)
>> + dwc3_ep0_end_control_data(dwc, dwc->eps[dir]);
>> + else
>> + dwc3_ep0_end_control_data(dwc, dwc->eps[!dir]);
On second thought, it seems cleaner to do this though the behavior is
undefined.
Do you have the driver tracepoint log capture of this scenario? It'd be
great if I can also review it.
Thanks!
Thinh
prev parent reply other threads:[~2022-05-25 3:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-04 19:36 Mayank Rana
2022-05-25 0:40 ` Thinh Nguyen
2022-05-25 3:52 ` Thinh Nguyen [this message]
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=ba6285cb-f9ff-8047-ad53-1f4534517b66@synopsys.com \
--to=thinh.nguyen@synopsys.com \
--cc=John.Youn@synopsys.com \
--cc=balbi@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=peter.chen@kernel.org \
--cc=quic_jackp@quicinc.com \
--cc=quic_mrana@quicinc.com \
--cc=quic_wcheng@quicinc.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®