public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Heiko Schocher <hs@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] ELF_RELOC causes strange I-cache issues
Date: Thu, 21 Oct 2010 12:50:01 +0200	[thread overview]
Message-ID: <4CC01AD9.60207@denx.de> (raw)
In-Reply-To: <4CC01719.30706@free.fr>

Hello Albert,

Albert ARIBAUD wrote:
> Le 21/10/2010 12:11, Reinhard Meyer a ?crit :
>> Hello,
>>
>> observation here:
>>
>> ICACHE is always ON. No crash with "usb read 21000000 0 1000"
>> Sorry that I can't reproduce the problem here, not even with 10000
>> blocks.
>> (tried a few dozen times)
>> (ARM926EJS - AT91SAM9XE)
>> (based on TOT 3ed16071b006dbda65070a4143db74da469f6e30 of 35h ago)
>>
>> But with DCACHE ON, the USB Stick is not found - maybe a timing problem:
>>
>> TOP9000>  dc off
>> Data (writethrough) Cache is OFF
>> TOP9000>  usb reset
>> (Re)start USB...
>> USB:   scanning bus for devices... 2 USB Device(s) found
>>         scanning bus for storage devices... 1 Storage Device(s) found
>> TOP9000>  dc on
>> Data (writethrough) Cache is ON
>> TOP9000>  usb reset
>> (Re)start USB...
>> USB:   scanning bus for devices... ERROR: CTL:TIMEOUT
>> 2 USB Device(s) found
>>         scanning bus for storage devices... 0 Storage Device(s) found
>> TOP9000>
>>
>>
>> Reinhard
> 
> If the USB controller uses DMA, then the DCache issue probably has to do
> with making sure to flush the (relevant lines of) cache before
> memory-to-device DMAs and to invalidate the (again, relevant lines of)
> cache after device-to-memory DMAs.

Yep. I think if you want to use dcache here, you have to activate
CONFIG_EHCI_DCACHE and implement the flush_dcache_range(),
invalidate_dcache_range(), flush_invalidate() functions for
your plattform, if not implemented yet.

> And I suggest we move this dcache issue to its own discussion thread.

Yep.

bye,
Heiko
-- 
DENX Software Engineering GmbH,     MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany

  parent reply	other threads:[~2010-10-21 10:50 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-20 18:49 [U-Boot] ELF_RELOC causes strange I-cache issues Wolfgang Denk
2010-10-20 20:12 ` Albert ARIBAUD
2010-10-20 20:54   ` Wolfgang Denk
2010-10-20 22:20     ` Joakim Tjernlund
2010-10-21  9:18     ` Albert Aribaud
2010-10-21  9:51       ` Heiko Schocher
2010-10-21 10:11         ` Reinhard Meyer
2010-10-21 10:34           ` Albert ARIBAUD
2010-10-21 10:49             ` Reinhard Meyer
2010-10-21 10:50             ` Heiko Schocher [this message]
2010-10-21 11:03             ` Stefan Roese
2010-10-21 10:54           ` Wolfgang Denk
2010-10-21 10:56         ` Albert ARIBAUD
2010-10-21 11:36           ` Wolfgang Denk
2010-10-21 11:45             ` Wolfgang Denk
2010-10-21 11:52               ` Stefano Babic
2010-10-21 11:53           ` Wolfgang Denk
2010-10-21 12:00           ` Wolfgang Denk
2010-10-21 12:53             ` Albert ARIBAUD
2010-10-21 11:28         ` Joakim Tjernlund
2010-10-21 10:05       ` Wolfgang Denk
2010-10-22 12:23 ` [U-Boot] [PATCH] ehci-hcd.c: fix hanging under higher load Wolfgang Denk
2010-10-22 19:51   ` Remy Bohmer
2010-10-22 12:26 ` [U-Boot] ELF_RELOC causes strange I-cache issues Wolfgang Denk
2010-10-22 13:19   ` Albert ARIBAUD
2010-10-22 13:28     ` Wolfgang Denk

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=4CC01AD9.60207@denx.de \
    --to=hs@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox