From: Felipe Balbi <felipe.balbi@linux.intel.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v2] usb: dwc3: Allocate and flush dwc->ep0_trb in a cache aligned manner
Date: Mon, 16 Oct 2017 16:55:03 +0300 [thread overview]
Message-ID: <87inffkxjc.fsf@linux.intel.com> (raw)
In-Reply-To: <72a54562-4437-a008-37bc-f11b2440aecc@denx.de>
Hi,
Marek Vasut <marex@denx.de> writes:
> On 10/16/2017 07:21 AM, Faiz Abbas wrote:
>> A flush of the cache is required before any outbound DMA access can
>> take place. The minimum size that can be flushed from the cache is
>> one cache line size. Therefore, any buffer allocated for DMA should
>> be in multiples of cache line size.
>>
>> Thus, allocate memory for ep0_trb in multiples of cache line size.
>>
>> Also, when local variable trb is assigned to dwc->ep0_trb[1] and used
>> to flush cache, it leads to cache misaligned messages as only the base
>> address dwc->ep0_trb is cache aligned.
>>
>> Therefore, flush cache using ep0_trb_addr which is always cache aligned.
>>
>> Signed-off-by: Faiz Abbas <faiz_abbas@ti.com>
>
> SGTM, Felipe, can you review this please ?
is cache maintenance done correctly in u-boot? Isn't the whole idea of a
coherent memory area that is is non-cacheable, non-bufferable memory?
Also, why isn't the API itself guaranteeing alignment requirements?
--
balbi
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 832 bytes
Desc: not available
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20171016/777e9c49/attachment.sig>
next prev parent reply other threads:[~2017-10-16 13:55 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-16 5:21 [U-Boot] [PATCH v2] usb: dwc3: Allocate and flush dwc->ep0_trb in a cache aligned manner Faiz Abbas
2017-10-16 10:12 ` Marek Vasut
2017-10-16 13:55 ` Felipe Balbi [this message]
2017-10-16 14:15 ` Faiz Abbas
2017-10-16 14:20 ` Felipe Balbi
2017-10-16 14:41 ` Marek Vasut
2017-10-16 14:50 ` Faiz Abbas
2017-10-16 14:51 ` Felipe Balbi
2017-10-16 15:22 ` Marek Vasut
2017-10-17 5:25 ` Faiz Abbas
2017-10-17 10:01 ` Marek Vasut
2017-10-17 11:10 ` Faiz Abbas
2017-10-17 11:14 ` 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=87inffkxjc.fsf@linux.intel.com \
--to=felipe.balbi@linux.intel.com \
--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 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.