mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Will Newton" <will.newton@gmail.com>
To: me@felipebalbi.com
Cc: linux-usb@vger.kernel.org,
	"Linux Kernel list" <linux-kernel@vger.kernel.org>,
	leoli@freescale.com
Subject: Re: [PATCH] fsl_usb2_udc: Add a wmb before priming endpoint.
Date: Thu, 5 Jun 2008 13:00:03 +0100	[thread overview]
Message-ID: <87a5b0800806050500pa48f081j75fa58e696ed8cc8@mail.gmail.com> (raw)
In-Reply-To: <20080603172415.GB29125@kedavra.cpe.vivax.com.br>

On Tue, Jun 3, 2008 at 6:24 PM, Felipe Balbi <me@felipebalbi.com> wrote:
> On Tue, Jun 03, 2008 at 04:20:25PM +0100, Will Newton wrote:
>> Add a wmb to fsl_queue_td before priming the endpoint. This ensures that the
>> modifications to the QH are seen by the hardware.
>>
>> Signed-off-by: Will Newton <will.newton@gmail.com>
>> ---
>>  drivers/usb/gadget/fsl_usb2_udc.c |    2 ++
>>  1 files changed, 2 insertions(+), 0 deletions(-)
>>
>> diff --git a/drivers/usb/gadget/fsl_usb2_udc.c
>> b/drivers/usb/gadget/fsl_usb2_udc.c
>> index 1868754..dd06a5b 100644
>> --- a/drivers/usb/gadget/fsl_usb2_udc.c
>> +++ b/drivers/usb/gadget/fsl_usb2_udc.c
>> @@ -653,6 +653,8 @@ static int fsl_queue_td(struct fsl_ep *ep, struct
>> fsl_req *req)
>>                       | EP_QUEUE_HEAD_STATUS_HALT));
>>       dQH->size_ioc_int_sts &= temp;
>>
>> +     wmb();
>
> checkpatch.pl will complain that there's not comment above the memory
> barrier. Could you just add it and in one line summarize why wmb()??

Yes, I'll do that and resend the patch along with the rest of the series I have.

My checkpatch does not seem to complain about the missing comment btw.

      reply	other threads:[~2008-06-05 12:00 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-03 15:20 Will Newton
2008-06-03 17:24 ` Felipe Balbi
2008-06-05 12:00   ` Will Newton [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=87a5b0800806050500pa48f081j75fa58e696ed8cc8@mail.gmail.com \
    --to=will.newton@gmail.com \
    --cc=leoli@freescale.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=me@felipebalbi.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®