All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marek Vasut <marex@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] nios2: zap cache status enable and disable functions
Date: Sat, 10 Oct 2015 20:10:01 +0200	[thread overview]
Message-ID: <201510102010.01110.marex@denx.de> (raw)
In-Reply-To: <5618C086.4000706@wytron.com.tw>

On Saturday, October 10, 2015 at 09:38:46 AM, Thomas Chou wrote:
> Hi Marek,
> 
> On 10/09/2015 08:57 PM, Marek Vasut wrote:
> > On Friday, October 09, 2015 at 05:32:47 AM, Thomas Chou wrote:
> >> As the icache and dcache of nios2 are always enabled, the
> >> cmd_cache is no of use and the cache status, enable and
> >> disable functions can be removed.
> > 
> > This is no good, I want to be able to enable/disable caches to look
> > for DMA-related issues. That is, if I disable cache, the suspicious
> > driver works and if I enable cache, the driver does not work, I can
> > conclude that it's a DMA/cache-related issue.
> 
> I understand. But the hardware always enables the cache if it is
> configured in nios2 cpu.
> 
> We can bypass (partially disable) the cache using ioremap() or
> dma_alloc_coherent(). If the DMA buffer address is mangled with
> ioremap(), then it is uncached. You may use this to debug.

OK, now it's clearer to me what you mean, thanks.

Best regards,
Marek Vasut

  reply	other threads:[~2015-10-10 18:10 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-09  3:32 [U-Boot] [PATCH] nios2: zap cache status enable and disable functions Thomas Chou
2015-10-09 12:57 ` Marek Vasut
2015-10-10  7:38   ` Thomas Chou
2015-10-10 18:10     ` Marek Vasut [this message]
2015-10-13 13:19 ` 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=201510102010.01110.marex@denx.de \
    --to=marex@denx.de \
    --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.