From: Dirk Behme <dirk.behme@googlemail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] i.MX dcache issues
Date: Sun, 15 Jul 2012 08:56:35 +0200 [thread overview]
Message-ID: <500269A3.60105@googlemail.com> (raw)
In-Reply-To: <386549548.1363378.1342303697853.JavaMail.root@advansee.com>
On 15.07.2012 00:08, Beno?t Th?baudeau wrote:
> On Sat, Jul 14, 2012 at 11:28:03PM +0200, Beno?t Th?baudeau wrote:
>> Shouldn't the MMC/eSDHC drivers flush/invalidate the dcache ranges
>> that they use
>> for DMA operations? Not doing so would explain why stack-allocated
>> buffers are
>> more affected than buffers in unused RAM areas.
>
> That will help:
> http://git.denx.de/?p=u-boot/u-boot-mmc.git;a=commitdiff;h=e576bd90f940806b989ffd666552081f17f032c8
Are you sure that this patch does really help?
If I remember correctly (will re-check) we have this patch locally
applied. But even with this patch, we have issues so that we enabled
CONFIG_SYS_DCACHE_OFF, i.e. disabled the dcache.
The issues we observed *without* CONFIG_SYS_DCACHE_OFF: The SD card
was detected as 1-bit only (mmcinfo), while with dcache off it was
used as 4-bit. Debugging this showed that wrong configuration data was
read [1]. Having a fat partition on the card, mmc part/fatls etc
failed, too, with cache enabled.
Best regards
Dirk
[1]
http://git.denx.de/?p=u-boot.git;a=blob;f=drivers/mmc/mmc.c;h=aebe578ff6f2e0228baa3e5d010f6808ea269760;hb=HEAD#l856
mmc->scr[0]/scr[1] contained random data
next prev parent reply other threads:[~2012-07-15 6:56 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1294453568.1339613.1342208396619.JavaMail.root@advansee.com>
2012-07-14 21:28 ` [U-Boot] i.MX dcache issues Benoît Thébaudeau
2012-07-14 22:08 ` Benoît Thébaudeau
2012-07-15 6:56 ` Dirk Behme [this message]
2012-07-15 14:37 ` Benoît Thébaudeau
2012-07-16 22:30 ` Marek Vasut
2012-07-19 11:43 ` Benoît Thébaudeau
2012-07-19 11:43 ` Marek Vasut
2012-07-19 12:43 ` Stefano Babic
2012-07-19 12:47 ` Marek Vasut
2012-07-15 13:46 ` Stefano Babic
2012-07-15 13:45 ` Stefano Babic
2012-07-15 14:45 ` Benoît Thébaudeau
2012-07-16 6:13 ` Dirk Behme
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=500269A3.60105@googlemail.com \
--to=dirk.behme@googlemail.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.