From: linux@bohmer.net (Remy Bohmer)
To: linux-arm-kernel@lists.infradead.org
Subject: [patch v2 1/2] at91_udc.c read_fifo timing issue
Date: Fri, 29 Jan 2010 18:04:19 +0100 [thread overview]
Message-ID: <3efb10971001290904p74b1919aif8ff013f050123a9@mail.gmail.com> (raw)
In-Reply-To: <20100129162155.709756286@gmail.com>
Hi Harro,
2010/1/29 Harro Haan <hrhaan@gmail.com>:
> This solves the read_fifo timing issue for example seen with CDC Ethernet.
> See the comments below for more info.
>
> Signed-off-by: Harro Haan <hrhaan@gmail.com>
> ---
> ?drivers/usb/gadget/at91_udc.c | ? 46 ++++++++++++++++++++++++++++++++++++++----
> ?1 file changed, 42 insertions(+), 4 deletions(-)
>
Acked-by: Remy Bohmer <linux@bohmer.net>
next prev parent reply other threads:[~2010-01-29 17:04 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-27 16:30 [patch 0/2] at91_udc driver: read_fifo timing issue + use spinlocks Harro Haan
2010-01-27 16:30 ` [patch 1/2] at91_udc.c read_fifo timing issue Harro Haan
2010-01-27 16:30 ` [patch 2/2] at91_udc.c use spinlocks instead of local_irq_xxx Harro Haan
2010-01-27 17:37 ` H Hartley Sweeten
2010-01-28 12:52 ` Harro Haan
2010-01-29 16:20 ` [patch v2 0/2] at91_udc driver: read_fifo timing issue + use spinlocks Harro Haan
2010-01-29 16:20 ` [patch v2 1/2] at91_udc.c read_fifo timing issue Harro Haan
2010-01-29 17:04 ` Remy Bohmer [this message]
2010-01-31 20:08 ` Ryan Mallon
2010-01-31 22:34 ` Anti Sullin
2010-02-03 14:37 ` [patch v3 0/3] at91_udc: fix soft lockup, HW glitch and use spinlocks Harro Haan
2010-02-03 14:37 ` [patch v3 1/3] Fix soft lockup in at91 udc driver Harro Haan
2010-02-03 14:37 ` [patch v3 2/3] at91_udc HW glitch Harro Haan
2010-03-23 20:26 ` Andrew Victor
2010-03-25 12:03 ` Harro Haan
2010-03-25 13:09 ` Anti Sullin
2010-02-03 14:37 ` [patch v3 3/3] at91_udc.c use spinlocks instead of local_irq_xxx Harro Haan
2010-01-29 16:20 ` [patch v2 2/2] " Harro Haan
2010-01-29 17:27 ` H Hartley Sweeten
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=3efb10971001290904p74b1919aif8ff013f050123a9@mail.gmail.com \
--to=linux@bohmer.net \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).