public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Thomas Chou <thomas@wytron.com.tw>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] nios2: convert cache flush to use dm cpu data
Date: Sun, 11 Oct 2015 08:38:35 +0800	[thread overview]
Message-ID: <5619AF8B.7040306@wytron.com.tw> (raw)
In-Reply-To: <201510102018.00580.marex@denx.de>

Hi Marek,

On 10/11/2015 02:18 AM, Marek Vasut wrote:
> Then you'd also need means to allocate variables to aligned memory location
> to prevent invalid cache flush. (Linux does this with it's DMA API). We are
> much simpler and thus this abstraction is still not available. I wonder if
> the overhead of DMA API would be high or not for U-Boot.

I see most people use memalign(ARCH_DMA_MINALIGN, len) in u-boot to 
allocate DMA buffers so that they are cache aligned.

> It is even worse if the cache flush operators permit incorrect cache flushes
> or invalidations. Like I mentioned before, this can lead to hard to debug
> problems when using DMA (at least on ARM).

I would suggest debug check should be left as for debug only. The 
definition of common functions should be kept as it is more important 
than coding style.

I debugged DMA issues a lot in the past until I realized the importance 
of aligned buffers. So there should be a developer's guideline.

But it is even much more difficult when something you believed does not 
work as expected, what is taken as common sense. It will trap a lot of 
developers when they called your flush cache functions but was skipped 
just because, eg, the end of packets are not aligned which is usually 
the case.

I would suggest that, with the best of my knowledge, please change the 
range check to a debug probe, and restore the cache flush functions to 
the common definition.

Best regards,
Thomas

  reply	other threads:[~2015-10-11  0:38 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-06  8:20 [U-Boot] [PATCH] nios2: convert cache flush to use dm cpu data Thomas Chou
2015-10-08 21:39 ` Marek Vasut
2015-10-09  2:49   ` Ley Foon Tan
2015-10-09  8:00     ` Thomas Chou
2015-10-09 14:42       ` Marek Vasut
2015-10-10  5:55         ` Thomas Chou
2015-10-10  6:32           ` Thomas Chou
2015-10-10 18:18             ` Marek Vasut
2015-10-11  0:38               ` Thomas Chou [this message]
2015-10-11 12:15                 ` Marek Vasut
2015-10-12  0:34                   ` Thomas Chou
2015-10-12 10:30                     ` Marek Vasut
2015-10-12 13:12                       ` Thomas Chou
2015-10-12 13:29                         ` Marek Vasut
2015-10-12 13:49                           ` Wolfgang Denk
2015-10-13  1:04                           ` Thomas Chou
2015-10-16 23:03                             ` Marek Vasut
2015-10-17  3:22                               ` Thomas Chou
2015-10-17 11:44                                 ` Marek Vasut
2015-10-10 18:12           ` Marek Vasut
2015-10-09 14:40     ` Marek Vasut
2015-10-09 12:58 ` [U-Boot] [PATCH v2] " Thomas Chou

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=5619AF8B.7040306@wytron.com.tw \
    --to=thomas@wytron.com.tw \
    --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