From: Stephen Warren <swarren@wwwdotorg.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH V2] usb: ci_udc: Allocate the qTD list directly
Date: Tue, 01 Jul 2014 09:16:26 -0600 [thread overview]
Message-ID: <53B2D0CA.4060701@wwwdotorg.org> (raw)
In-Reply-To: <201407011713.16627.marex@denx.de>
On 07/01/2014 09:13 AM, Marek Vasut wrote:
> On Tuesday, July 01, 2014 at 05:03:17 PM, Stephen Warren wrote:
>> On 06/30/2014 06:04 PM, Marek Vasut wrote:
>>> Instead of weird allocation of ci_drv->items_mem and then even weirder
>>> distribution of offsets in this memory area into ci_drv->items array,
>>> just allocate ci_drv->items as a big slab of aligned memory (replaces
>>> ci_drv->items_mem) and let ci_get_qtd() do the distribution of offsets
>>> in this memory area.
>>
>> As I mentioned on IRC, this patch isn't correct.
>>
>> The existing code ensures that each pair of QTDs are correctly aligned,
>> hence the slight complexity. The new code only actively ensures that the
>> first QTD is correctly aligned; the subsequent QTDs will only be
>> correctly aligned if the sizeof the QTD structure is an exact multiple
>> of the alignment requirements. In practice, it is on my system at least,
>> but that may not be generally true.
>
> It is on every system with 32b cachelines.
Sure.
> On system with 64b cachelines, you
> won't be able to use one endpoint as both in and out, which I don't think is
> doable now either.
Yes, the 2nd QTD in each pair isn't correctly aligned at present for
64byte cachelines. I was thinking about sending a patch to fix that
(perhaps theoretical) issue.
Actually, I wonder if that's related to J?rg's issue at all; his system
has the cache line size set to 64 even though that's incorrect, perhaps
that influences the behaviour of the cache code...
next prev parent reply other threads:[~2014-07-01 15:16 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-30 23:53 [U-Boot] [PATCH] usb: ci_udc: Allocate the qTD list directly Marek Vasut
2014-06-30 23:55 ` Marek Vasut
2014-07-01 0:04 ` [U-Boot] [PATCH V2] " Marek Vasut
2014-07-01 6:51 ` Jörg Krause
2014-07-01 10:17 ` Marek Vasut
2014-07-01 11:03 ` Jörg Krause
2014-07-01 11:19 ` Marek Vasut
2014-07-01 11:22 ` Jörg Krause
2014-07-01 11:35 ` Marek Vasut
2014-07-01 11:48 ` Jörg Krause
2014-07-01 22:34 ` Jörg Krause
2014-07-01 22:36 ` Stephen Warren
2014-07-01 22:47 ` Jörg Krause
2014-07-01 22:51 ` Stephen Warren
2014-07-01 22:57 ` Jörg Krause
2014-07-01 23:10 ` Stephen Warren
2014-07-01 15:03 ` Stephen Warren
2014-07-01 15:13 ` Marek Vasut
2014-07-01 15:16 ` Stephen Warren [this message]
2014-07-01 15:22 ` Marek Vasut
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=53B2D0CA.4060701@wwwdotorg.org \
--to=swarren@wwwdotorg.org \
--cc=u-boot@lists.denx.de \
/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