From: Thinh Nguyen <Thinh.Nguyen@synopsys.com>
To: Anurag Kumar Vulisha <anurag.kumar.vulisha@xilinx.com>,
"balbi@kernel.org" <balbi@kernel.org>,
"gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>
Cc: "linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Thinh.Nguyen@synopsys.com" <Thinh.Nguyen@synopsys.com>,
"v.anuragkumar@gmail.com" <v.anuragkumar@gmail.com>
Subject: Re: [PATCH v4 4/8] usb: dwc3: implement stream transfer timeout
Date: Thu, 13 Sep 2018 21:24:00 +0000 [thread overview]
Message-ID: <30102591E157244384E984126FC3CB4F544AECB6@us01wembx1.internal.synopsys.com> (raw)
In-Reply-To: 1536418986-16609-5-git-send-email-anurag.kumar.vulisha@xilinx.com
Hi Anurag,
On 9/8/2018 8:03 AM, Anurag Kumar Vulisha wrote:
> According to dwc3 databook when streams are used, it may be possible
> for the host and device become out of sync, where device may wait for
> host to issue prime transcation and host may wait for device to issue
> erdy. To avoid such deadlock, timeout needs to be implemented. After
> timeout occurs, device will first stop transfer and restart the transfer
> again. This patch does the same.
>
> Signed-off-by: Anurag Kumar Vulisha <anurag.kumar.vulisha@xilinx.com>
> Reviewed-by: Thinh Nguyen <thinhn@synopsys.com>
> ---
> Chnages in v4:
> 1. Added description for stream timeout timer as suggested by
> "Thinh Nguyen"
>
> Changes in v3:
> 1. Added the changes suggested by "Thinh Nguyen"
>
> Changes in v2:
> 1. Changed STREAM_TIMEOUT to STREAM_TIMEOUT_MS as suggested by
> "Andy Shevchenko"
> ---
> drivers/usb/dwc3/core.h | 7 +++++++
> drivers/usb/dwc3/gadget.c | 45 +++++++++++++++++++++++++++++++++++++++++++++
> 2 files changed, 52 insertions(+)
>
> diff --git a/drivers/usb/dwc3/core.h b/drivers/usb/dwc3/core.h
> index 5bfb625..f62e8c4 100644
> --- a/drivers/usb/dwc3/core.h
> +++ b/drivers/usb/dwc3/core.h
> @@ -633,6 +633,11 @@ struct dwc3_event_buffer {
>
> #define DWC3_TRB_NUM 256
>
> +/*
> + * Timeout value in msecs used by stream_timeout_timer when streams are enabled
> + */
> +#define STREAM_TIMEOUT_MS 50
> +
> /**
> * struct dwc3_ep - device side endpoint representation
> * @endpoint: usb endpoint
> @@ -656,6 +661,7 @@ struct dwc3_event_buffer {
> * @name: a human readable name e.g. ep1out-bulk
> * @direction: true for TX, false for RX
> * @stream_capable: true when streams are enabled
> + * @stream_timeout_timer: timeout timer used by bulk streams
> */
> struct dwc3_ep {
> struct usb_ep endpoint;
> @@ -705,6 +711,7 @@ struct dwc3_ep {
>
> unsigned direction:1;
> unsigned stream_capable:1;
> + struct timer_list stream_timeout_timer;
> };
>
> enum dwc3_phy {
> diff --git a/drivers/usb/dwc3/gadget.c b/drivers/usb/dwc3/gadget.c
> index 13ea282..306d4c5 100644
> --- a/drivers/usb/dwc3/gadget.c
> +++ b/drivers/usb/dwc3/gadget.c
> @@ -254,6 +254,7 @@ int dwc3_send_gadget_generic_command(struct dwc3 *dwc, unsigned cmd, u32 param)
> }
>
> static int __dwc3_gadget_wakeup(struct dwc3 *dwc);
> +static void stream_timeout_function(struct timer_list *arg);
>
> /**
> * dwc3_send_gadget_ep_cmd - issue an endpoint command
> @@ -574,6 +575,17 @@ static int dwc3_gadget_set_ep_config(struct dwc3_ep *dep, unsigned int action)
> | DWC3_DEPCFG_STREAM_EVENT_EN
> | DWC3_DEPCFG_XFER_COMPLETE_EN;
> dep->stream_capable = true;
> +
> + /*
> + * When BULK streams are enabled it may be possible for the host
> + * and device become out of sync, where device may wait for host
> + * to issue prime transcation and host may wait for device to
> + * issue ERDY. To avoid such deadlock, timeout needs to be
> + * implemented. After timeout occurs, device will first stop
> + * transfer and restart the transfer again.
> + */
> + timer_setup(&dep->stream_timeout_timer,
> + stream_timeout_function, 0);
> }
>
> if (!usb_endpoint_xfer_control(desc))
> @@ -730,6 +742,9 @@ static int __dwc3_gadget_ep_disable(struct dwc3_ep *dep)
>
> trace_dwc3_gadget_ep_disable(dep);
>
> + if (dep->stream_capable)
> + del_timer(&dep->stream_timeout_timer);
> +
> dwc3_remove_requests(dwc, dep);
>
> /* make sure HW endpoint isn't stalled */
> @@ -1257,6 +1272,12 @@ static int __dwc3_gadget_kick_transfer(struct dwc3_ep *dep)
> return ret;
> }
>
> + if (starting && dep->stream_capable) {
> + dep->stream_timeout_timer.expires = jiffies +
> + msecs_to_jiffies(STREAM_TIMEOUT_MS);
> + add_timer(&dep->stream_timeout_timer);
> + }
> +
> return 0;
> }
>
> @@ -2403,6 +2424,13 @@ static void dwc3_gadget_endpoint_transfer_in_progress(struct dwc3_ep *dep,
> stop = true;
> }
>
> + /*
> + * Delete the timer that was started in __dwc3_gadget_kick_transfer()
> + * for stream capable endpoints.
> + */
> + if (dep->stream_capable)
> + del_timer(&dep->stream_timeout_timer);
> +
> dwc3_gadget_ep_cleanup_completed_requests(dep, event, status);
>
> if (stop) {
> @@ -2487,6 +2515,11 @@ static void dwc3_endpoint_interrupt(struct dwc3 *dwc,
> }
> break;
> case DWC3_DEPEVT_STREAMEVT:
> + if (event->status == DEPEVT_STREAMEVT_FOUND)
> + del_timer(&dep->stream_timeout_timer);
> + else
> + dev_dbg(dwc->dev, "unable to find suitable stream");
This debug message is already printed in the driver tracepoint. There's
no need to print it here. Also, I don't think Felipe will accept adding
new dev_dbg() after removing all of them and converting them to tracepoints.
Thinh
next prev parent reply other threads:[~2018-09-13 21:24 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-08 15:02 [PATCH v4 0/8] usb: dwc3: Fix broken BULK stream support to dwc3 gadget driver Anurag Kumar Vulisha
2018-09-08 15:02 ` [PATCH v4 1/8] usb: dwc3: Correct the logic for checking TRB full in __dwc3_prepare_one_trb() Anurag Kumar Vulisha
2018-09-08 15:03 ` [PATCH v4 2/8] usb: dwc3: update stream id in depcmd Anurag Kumar Vulisha
2018-09-08 15:03 ` [PATCH v4 3/8] usb: dwc3: make controller clear transfer resources after complete Anurag Kumar Vulisha
2018-09-08 15:03 ` [PATCH v4 4/8] usb: dwc3: implement stream transfer timeout Anurag Kumar Vulisha
2018-09-13 21:24 ` Thinh Nguyen [this message]
2018-09-15 13:20 ` Anurag Kumar Vulisha
2018-09-08 15:03 ` [PATCH v4 5/8] usb: dwc3: don't issue no-op trb for stream capable endpoints Anurag Kumar Vulisha
2018-09-08 15:03 ` [PATCH v4 6/8] usb: dwc3: check for requests in started list " Anurag Kumar Vulisha
2018-09-10 20:13 ` Thinh Nguyen
2018-09-10 22:50 ` Thinh Nguyen
2018-09-08 15:03 ` [PATCH v4 7/8] usb: dwc3: Check for IOC/LST bit in both event->status and TRB->ctrl fields Anurag Kumar Vulisha
2018-09-08 15:03 ` [PATCH v4 8/8] usb: dwc3: Check MISSED ISOC bit only for ISOC endpoints Anurag Kumar Vulisha
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=30102591E157244384E984126FC3CB4F544AECB6@us01wembx1.internal.synopsys.com \
--to=thinh.nguyen@synopsys.com \
--cc=anurag.kumar.vulisha@xilinx.com \
--cc=balbi@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=v.anuragkumar@gmail.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;
as well as URLs for NNTP newsgroup(s).