From: Mike Frysinger <vapier@gentoo.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] tegra: mmc: Support operation with dcache enabled
Date: Sun, 8 Jan 2012 03:42:01 -0500 [thread overview]
Message-ID: <201201080342.02878.vapier@gentoo.org> (raw)
In-Reply-To: <74CDBE0F657A3D45AFBB94109FB122FF176BE9309F@HQMAIL01.nvidia.com>
On Wednesday 21 December 2011 16:10:16 Stephen Warren wrote:
> Simon Glass wrote at Wednesday, December 21, 2011 1:03 PM:
> > When the data cache is enabled we must flush on write and invalidate
> > on read. We also check that buffers are aligned to data cache lines
> > boundaries. With recent work in U-Boot this should generally be the case
> > but the warnings will catch problems.
>
> Conceptually this seems fine, but shouldn't the MMC driver core be doing
> the cache management, so all platforms without cache coherency can
> benefit from it?
if the driver bitbangs things out (like SPI/MMC), then the core doing it would
be a waste wouldn't it ?
a better question might be how does Linux handle it ? does it force the
drivers to do it, or does the core take care of things ?
-mike
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 836 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20120108/673d84dc/attachment.pgp>
next prev parent reply other threads:[~2012-01-08 8:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-21 20:02 [U-Boot] [PATCH] tegra: mmc: Support operation with dcache enabled Simon Glass
2011-12-21 21:10 ` Stephen Warren
2012-01-08 8:42 ` Mike Frysinger [this message]
2012-01-09 2:36 ` Andy Fleming
2012-01-09 3:36 ` Andy Fleming
2012-01-09 5:31 ` Simon Glass
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=201201080342.02878.vapier@gentoo.org \
--to=vapier@gentoo.org \
--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