On 19/07/2012 13:35, Benoît Thébaudeau wrote:
> bad_cache_range actually returned true if the range was OK, but it was used
> according to its name, which resulted in all valid dcache range
> invalidate/flush
> operations being dropped. Hence, most DMA transfers resulted in garbage data.
>
> This
bad_cache_range actually returned true if the range was OK, but it was used
according to its name, which resulted in all valid dcache range invalidate/flush
operations being dropped. Hence, most DMA transfers resulted in garbage data.
This patch renames this function according to what it does, and
2 matches
Mail list logo