From: Sergei Shtylyov <sshtylyov@ru.mvista.com>
To: Mike Frysinger <vapier@gentoo.org>
Cc: linux-usb@vger.kernel.org, Felipe Balbi <felipe.balbi@nokia.com>,
linux-kernel@vger.kernel.org,
uclinux-dist-devel@blackfin.uclinux.org,
Sonic Zhang <sonic.zhang@analog.com>,
Cliff Cai <cliff.cai@analog.com>
Subject: Re: [PATCH 05/11] USB: musb: add notes for Blackfin anomalies
Date: Thu, 17 Sep 2009 16:33:47 +0400 [thread overview]
Message-ID: <4AB22CAB.1080905@ru.mvista.com> (raw)
In-Reply-To: <1253144325-1203-5-git-send-email-vapier@gentoo.org>
Hello.
Mike Frysinger wrote:
> From: Sonic Zhang <sonic.zhang@analog.com>
> Add some helpful notes about how the driver works around different
> anomalies that exist in the on-chip host controller.
>
> Signed-off-by: Sonic Zhang <sonic.zhang@analog.com>
> Signed-off-by: Cliff Cai <cliff.cai@analog.com>
> Signed-off-by: Mike Frysinger <vapier@gentoo.org>
Grammar and style nipicking follows... :-)
> diff --git a/drivers/usb/musb/blackfin.h b/drivers/usb/musb/blackfin.h
> index a240c1e..de62962 100644
> --- a/drivers/usb/musb/blackfin.h
> +++ b/drivers/usb/musb/blackfin.h
> @@ -14,6 +14,35 @@
> * Blackfin specific definitions
> */
>
> +/* Anomalies notes:
> + *
> + * 05000450 - USB DMA Mode 1 Short Packet Data Corruption:
> + * MUSB driver is designed to transfer buffer of N * maxpacket size
> + * in DMA mode 1 and leave rest data to the next transfer in DMA
> + * mode 0, so we never transmit a short packet in DMA mode 1.
> + *
> + * 05000463 - This anomaly doesn't affect this driver,Since it
No comma needed here, and why capitalize "since"?
> + * never uses L1 or L2 memory as data destination.
> + *
> + * 05000464 - This anomaly doesn't affect this driver,Since it
Same here...
> + * never uses L1 or L2 memory as data source.
> + *
> + * 05000465 - Actually,the anomaly still can be seen when SCLK
> + * is over 100 MHz,and there is no way to workaround
> + * for bulk endpoints,because the wMaxPackSize of bulk
> + * is less than or equal to 512,while the fifo size of
Shouldn't there be spaces after commas?
> + * endpoint 5,6,7 is 1024,the double buffer mode is
Either comma doesn't fit here, or "so" is needed after it...
> + * enabled automatically when these endpoints are used
> + * for bulk OUT.
> + *
> + * 05000466 - This anomaly doesn't affect this driver,Since it
No comma or uppercase needed...
> + * never mixs concurrent DMA and core accesses to the
"Mixes"...
> + * TX endpoint FIFOs.
WBR, Sergei
next prev parent reply other threads:[~2009-09-17 12:31 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-16 23:38 [PATCH 01/11] USB: musb: tweak musb_read_fifo() to avoid unused warnings Mike Frysinger
2009-09-16 23:38 ` [PATCH 02/11] USB: musb: kill compile warning for Blackfin systems Mike Frysinger
2009-09-16 23:38 ` [PATCH 03/11] USB: musb: kill some useless comments in Blackfin driver Mike Frysinger
2009-09-16 23:38 ` [PATCH 04/11] USB: musb: update Blackfin processor dependency Mike Frysinger
2009-09-16 23:38 ` [PATCH 05/11] USB: musb: add notes for Blackfin anomalies Mike Frysinger
2009-09-17 12:33 ` Sergei Shtylyov [this message]
2009-09-17 16:25 ` [PATCH 05/12 v2] " Mike Frysinger
2009-09-16 23:38 ` [PATCH 06/11] USB: musb: add work around for Blackfin anomaly 05000456 Mike Frysinger
2009-09-16 23:38 ` [PATCH 07/11] USB: musb: fix musb_platform_set_mode() definition Mike Frysinger
2009-09-16 23:38 ` [PATCH 08/11] USB: musb: clear the Blackfin interrupt pending bits early in the ISR Mike Frysinger
2009-09-16 23:38 ` [PATCH 09/11] USB: musb: error out when anomaly 05000380 is applicable Mike Frysinger
2009-09-16 23:38 ` [PATCH 10/11] USB: musb: Blackfin code needs NOP_USB_XCEIV too Mike Frysinger
2009-09-16 23:38 ` [PATCH 11/11] USB: musb: fix printf warning in debug code Mike Frysinger
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=4AB22CAB.1080905@ru.mvista.com \
--to=sshtylyov@ru.mvista.com \
--cc=cliff.cai@analog.com \
--cc=felipe.balbi@nokia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=sonic.zhang@analog.com \
--cc=uclinux-dist-devel@blackfin.uclinux.org \
--cc=vapier@gentoo.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.