From: Felipe Balbi <balbi@ti.com>
To: <changbin.du@intel.com>, <johnyoun@synopsys.com>
Cc: <gregkh@linuxfoundation.org>, <linux-usb@vger.kernel.org>,
<linux-kernel@vger.kernel.org>,
"Du, Changbin" <changbin.du@intel.com>
Subject: Re: [PATCH] usb: dwc2: fix transfer stop programming for out endpoint
Date: Wed, 16 Dec 2015 10:57:59 -0600 [thread overview]
Message-ID: <8760zyfi08.fsf@saruman.tx.rr.com> (raw)
In-Reply-To: <1449214703-30795-1-git-send-email-changbin.du@intel.com>
[-- Attachment #1: Type: text/plain, Size: 1824 bytes --]
Hi,
changbin.du@intel.com writes:
> From: "Du, Changbin" <changbin.du@intel.com>
>
> To stop an out endpoint, software should set sets the Global OUT NAK,
> but not the Global Non-periodic IN NAK. This driver bug leads the out-ep
> failed be in disabled state with below error.
>
> dwc2_hsotg_ep_stop_xfr: timeout DOEPCTL.EPDisable
>
> Signed-off-by: Du, Changbin <changbin.du@intel.com>
John, is this patch okay to apply ?
> ---
> drivers/usb/dwc2/gadget.c | 10 +++++-----
> 1 file changed, 5 insertions(+), 5 deletions(-)
>
> diff --git a/drivers/usb/dwc2/gadget.c b/drivers/usb/dwc2/gadget.c
> index 0abf73c..92a182f 100644
> --- a/drivers/usb/dwc2/gadget.c
> +++ b/drivers/usb/dwc2/gadget.c
> @@ -2911,15 +2911,15 @@ static void dwc2_hsotg_ep_stop_xfr(struct dwc2_hsotg *hsotg,
> "%s: timeout DIEPINT.NAKEFF\n", __func__);
> } else {
> /* Clear any pending nak effect interrupt */
> - dwc2_writel(GINTSTS_GINNAKEFF, hsotg->regs + GINTSTS);
> + dwc2_writel(GINTSTS_GOUTNAKEFF, hsotg->regs + GINTSTS);
>
> - __orr32(hsotg->regs + DCTL, DCTL_SGNPINNAK);
> + __orr32(hsotg->regs + DCTL, DCTL_SGOUTNAK);
>
> /* Wait for global nak to take effect */
> if (dwc2_hsotg_wait_bit_set(hsotg, GINTSTS,
> - GINTSTS_GINNAKEFF, 100))
> + GINTSTS_GOUTNAKEFF, 100))
> dev_warn(hsotg->dev,
> - "%s: timeout GINTSTS.GINNAKEFF\n", __func__);
> + "%s: timeout GINTSTS.GOUTNAKEFF\n", __func__);
> }
>
> /* Disable ep */
> @@ -2944,7 +2944,7 @@ static void dwc2_hsotg_ep_stop_xfr(struct dwc2_hsotg *hsotg,
> /* TODO: Flush shared tx fifo */
> } else {
> /* Remove global NAKs */
> - __bic32(hsotg->regs + DCTL, DCTL_SGNPINNAK);
> + __bic32(hsotg->regs + DCTL, DCTL_SGOUTNAK);
> }
> }
>
> --
> 2.5.0
>
--
balbi
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 818 bytes --]
next prev parent reply other threads:[~2015-12-16 16:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-04 7:38 [PATCH] usb: dwc2: fix transfer stop programming for out endpoint changbin.du
2015-12-16 16:57 ` Felipe Balbi [this message]
2015-12-16 21:34 ` John Youn
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=8760zyfi08.fsf@saruman.tx.rr.com \
--to=balbi@ti.com \
--cc=changbin.du@intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=johnyoun@synopsys.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
/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