mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
To: Andrew Goodbody <andrew.goodbody@cambrionix.com>,
	"b-liu@ti.com" <b-liu@ti.com>
Cc: "gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>,
	"linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"stable@vger.kernel.org" <stable@vger.kernel.org>
Subject: Re: [PATCH V2 2/2] usb: musb: Stop bulk endpoint while queue is rotated
Date: Mon, 23 May 2016 16:40:17 +0300	[thread overview]
Message-ID: <c63488a8-321d-49f4-8efa-67c8d8dad488@cogentembedded.com> (raw)
In-Reply-To: <6b25b4a5cc104ea0adc5bd006040529b@SEHSTE15D2BE2.hs20.net>

On 5/23/2016 4:26 PM, Andrew Goodbody wrote:

>>> Ensure that the endpoint is stopped by clearing REQPKT before clearing
>>> DATAERR_NAKTIMEOUT before rotating the queue on the dedicated bulk
>>> endpoint.
>>> This addresses an issue where a race could result in the endpoint
>>> receiving data before it was reprogrammed resulting in a warning about
>>> such data from musb_rx_reinit before it was thrown away.
>>> The data thrown away was a valid packet that had been correctly ACKed
>>> which meant the host and device got out of sync.
>>>
>>> Signed-off-by: Andrew Goodbody <andrew.goodbody@cambrionix.com>
>>> Cc: stable@vger.kernel.org
>>> ---
>>> V2 added comment about clearing REQPKT before DATAERR_NAKTIMEOUT
>>>
>>>  drivers/usb/musb/musb_host.c | 6 ++++++
>>>  1 file changed, 6 insertions(+)
>>>
>>> diff --git a/drivers/usb/musb/musb_host.c
>>> b/drivers/usb/musb/musb_host.c index 2966596..676cb98 100644
>>> --- a/drivers/usb/musb/musb_host.c
>>> +++ b/drivers/usb/musb/musb_host.c
>>> @@ -997,6 +997,12 @@ static void musb_bulk_nak_timeout(struct musb
>> *musb, struct musb_hw_ep *ep,
>>>  		/* clear nak timeout bit */
>>>  		rx_csr = musb_readw(epio, MUSB_RXCSR);
>>>  		rx_csr |= MUSB_RXCSR_H_WZC_BITS;
>>> +		/*
>>> +		 * Need to stop the transaction by clearing REQPKT before
>>
>>     Transcation? Maybe transfer?
>
> The quote from the TRM is "If the DATAERR_NAKTIMEOUT bit is set, the controller can be directed either to continue trying this transaction (until it times out again) by clearing the DATAERR_NAKTIMEOUT bit or to abort the transaction by clearing REQPKT bit before clearing the DATAERR_NAKTIMEOUT bit."
> So 'transaction' is correct.

    OK.

>>> +		 * DATAERR_NAKTIMEOUT ref TRM section 16.3.8.2.2.1.2
>>
>>     Which TRM? Do you understand that the MUSB core is used by multiple
>> SoCs?
>> I'd recommend referring just to the "abstract" manual or the MUSB
>> programmer's guide (section 9.2.2 if you want an exact ref.).

> That would be the AM335x Sitara Processors TRM. I don't have the MUSB programmer's guide, is it available online somewhere?

    AFAIK, no.

> I do not understand what you mean by the "abstract" manual.

    Just saying "the manual" or "the manuals".

> Would you be OK with "ref MUSB Programmer's Guide section 9.2.2"

    Yes. However, that spec calls the bit just "NAK Timeout" in this context, 
not DATAERR_NAKTIMEOUT. Overall, this spec. uses CamelCase for the register 
bit names (I recall dbrownell complaining over that and uppercase all the bit 
names in my patches :-).

> Andrew
>
>> [...]

MBR, Sergei

  reply	other threads:[~2016-05-23 13:40 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-23 12:00 [PATCH V2 0/2] usb: musb: fix dropped packets Andrew Goodbody
2016-05-23 12:00 ` [PATCH V2 1/2] usb: musb: Ensure rx reinit occurs for shared_fifo endpoints Andrew Goodbody
2016-05-23 12:00 ` [PATCH V2 2/2] usb: musb: Stop bulk endpoint while queue is rotated Andrew Goodbody
2016-05-23 12:38   ` Sergei Shtylyov
2016-05-23 13:26     ` Andrew Goodbody
2016-05-23 13:40       ` Sergei Shtylyov [this message]
2016-05-23 14:37         ` Sergei Shtylyov
2016-05-23 15:19           ` Andrew Goodbody
2016-05-23 16:46             ` Sergei Shtylyov

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=c63488a8-321d-49f4-8efa-67c8d8dad488@cogentembedded.com \
    --to=sergei.shtylyov@cogentembedded.com \
    --cc=andrew.goodbody@cambrionix.com \
    --cc=b-liu@ti.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=stable@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

all inboxes | Powered by JetHome®