diff options
| author | Simon Glass <sjg@chromium.org> | 2017-04-04 13:00:19 -0600 |
|---|---|---|
| committer | Simon Glass <sjg@chromium.org> | 2017-04-13 14:44:49 -0600 |
| commit | 5a8a8045a928702d9b3fb6f73a4e9717040e09a9 (patch) | |
| tree | 366c083a209b5c46bbb039179ee694e822654f23 /tools | |
| parent | ea168e3351cdb9a738ebfa4ad931a81b2f6d48dd (diff) | |
| download | u-boot-5a8a8045a928702d9b3fb6f73a4e9717040e09a9.zip u-boot-5a8a8045a928702d9b3fb6f73a4e9717040e09a9.tar.gz u-boot-5a8a8045a928702d9b3fb6f73a4e9717040e09a9.tar.bz2 | |
dm: core: Ensure DMA regions start up with the cache clean
There is a strange interaction with drivers which use DMA if the cache
starts off in a dirty state. Buffer space which the driver reads (but has
not previously written) can contain zero bytes from alloc_priv(). This can
cause corruption of the memory used by DMA for incoming data.
Fix this and add a comment to explain the problem.
This allows the dwc2 driver to work correctly with driver model, for
example.
Signed-off-by: Simon Glass <sjg@chromium.org>
Diffstat (limited to 'tools')
0 files changed, 0 insertions, 0 deletions