From: "Thomas Dahlmann" <thomas.dahlmann@amd.com>
To: "Oliver Neukum" <oliver@neukum.org>
Cc: linux-usb-devel@lists.sourceforge.net,
"Jordan Crouse" <jordan.crouse@amd.com>,
linux-mips@linux-mips.org, linux-kernel@vger.kernel.org,
info-linux@ldcmail.amd.com
Subject: Re: [linux-usb-devel] [PATCH] UDC support for MIPS/AU1200 and Geode/CS5536
Date: Tue, 10 Jan 2006 12:02:09 +0100 [thread overview]
Message-ID: <43C39431.6020308@amd.com> (raw)
In-Reply-To: <200601092344.55988.oliver@neukum.org>
Oliver Neukum wrote:
>Am Montag, 9. Januar 2006 19:03 schrieb Jordan Crouse:
>
>
>>>From the "two-birds-one-stone" department, I am pleased to present USB UDC
>>support for both the MIPS Au1200 SoC and the Geode CS5535 south bridge.
>>Also, coming soon (in the next few days), OTG, which has been removed from
>>the usb_host patch, and put into its own patch (as per David's comments).
>>
>>This patch is against current linux-mips git, but it should apply for Linus's
>>tree as well.
>>
>>Regards,
>>Jordan
>>
>>
>>
>+ VDBG("udc_read_bytes(): %d bytes\n", bytes);
>+
>+ /* dwords first */
>+ for (i = 0; i < bytes / UDC_DWORD_BYTES; i++) {
>+ *((u32*) (buf + (i<<2))) = readl(dev->rxfifo);
>+ }
>
>Is there any reason you don't increment by 4?
>
> Regards
> Oliver
>
>
>
>
>
The loop is for reading dwords only, so "i < bytes / UDC_DWORD_BYTES" cuts
off remaining 1,2 or 3 bytes which are handled by the next loop.
But you are right, incrementing by 4 may look better, as
for (i = 0; i < bytes - bytes % UDC_DWORD_BYTES; i+=4) {
*((u32*) (buf + i)) = readl(dev->rxfifo);
}
Thanks,
Thomas
next prev parent reply other threads:[~2006-01-10 11:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20060109180356.GA8855@cosmic.amd.com>
2006-01-09 18:21 ` UDC support for MIPS/AU1200 and Geode/CS5536 Jordan Crouse
2006-01-09 22:44 ` [linux-usb-devel] [PATCH] " Oliver Neukum
2006-01-10 11:02 ` Thomas Dahlmann [this message]
2006-01-10 13:16 ` David Vrabel
2006-01-10 13:40 ` Oliver Neukum
2006-01-13 10:08 ` Thomas Dahlmann
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=43C39431.6020308@amd.com \
--to=thomas.dahlmann@amd.com \
--cc=info-linux@ldcmail.amd.com \
--cc=jordan.crouse@amd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=linux-usb-devel@lists.sourceforge.net \
--cc=oliver@neukum.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