[U-Boot] [RFC] command/cache: Add flush_cache command

[Tom Rini <trini@ti.com>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 03/22/2013 02:30 AM, Albert ARIBAUD wrote:
> Hi Scott,
> 
>> Perhaps it could be, or the application could be altered to 
>> release secondary cores through the spin table.  I don't think 
>> that excuses a situation where some ways of putting a blob of 
>> bytes into RAM flush the cache (to the extent the architecture 
>> requires it for the blob of bytes to be executable) and others 
>> don't, and there's no way to do it manually.
> 
> AFAIU there is.
> 
>> Would you remove the "go" command entirely?  I think that would 
>> be a mistake.
> 
> I do not see why you are talking about removing the "go" command. 
> In the 'worst' scenario (from an effort perspective), it would
> have to be do a flush and possibly cache disable before branching
> to the payload; in the 'best' scenario, it needs not be modified at
> all.

It seems like we're going around and around with one point not being
addressed.  When using 'go', how do you know the size to flush?  And
since Scott is talking about performance testing apps, the cache
should not be disabled (unless we expect all standalone apps to enable
the cache, in which case we need to provide something in the jump
table to make that easy and document this change).

- -- 
Tom
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQIcBAEBAgAGBQJRTEvnAAoJENk4IS6UOR1WHZEP/3YU+LOnwSP9TRarsg2gtH2I
jfgb31qqQ1RZjF0rYawxfJdYyhJPYVkyHIlsLHBUq7onB2Y5VGwO0PkbDoImroBt
Fy8V/th1oW9NzmvrcDe9fUiisGQzvH4glgtBhKDp+a1XGuXkyLUE+C6lkJzzZ5kp
XzSqHKSER3yOC1nUhZMyYAgy0u5sFQreH+smTz7Tt+3kOtSMj73dbSm5w9dfifMS
Med82eVUWJGS+1ZjAe0NNGHZHFmIHd+o7hQkrkpzH8H+uOBOZQkgD9xD5fiat2Nc
2rMNfuvcvHeLAgwNcSOEQwIcr/EHLKb3OyXQop7qw4XLvxTtQ23Dw/HLvkRFYWMg
A82SUd9GVrBrVd9WtTpNxbDGZ1xttKOHP0zB9BhazpFP9rLCVpWvIPWMExooAboe
dYWBNmosiHcL0J2dfE3ep5tz+/FWkbHYPUCZ/MOs9avd7PEzT8IGp0OU7mpPYXRQ
2RuLhvc8SIW7PlKV8NL69/FrliYxNsxML3+eLMl0IjlW4lGJdSbL0HaIw7Lsftb5
8dEVrfmE2ftzLs2LbjoC12PHdGuYNsQoM/Kvwbvq8s8Bl8wzhXzcSOCf1YKLrXRG
7l9oBYX5oEiBdYAfEq7De1bODyravoJ6R1ledaz5CrRuQptChDhl4z3aZaKU0Mos
WK5aeCrPTJYSOVSNCdUJ
=TtQR
-----END PGP SIGNATURE-----