summaryrefslogtreecommitdiff
path: root/drivers/core/root.c
diff options
context:
space:
mode:
authorSimon Glass <sjg@chromium.org>2017-04-04 19:00:19 (GMT)
committerSimon Glass <sjg@chromium.org>2017-04-13 20:44:49 (GMT)
commit5a8a8045a928702d9b3fb6f73a4e9717040e09a9 (patch)
tree366c083a209b5c46bbb039179ee694e822654f23 /drivers/core/root.c
parentea168e3351cdb9a738ebfa4ad931a81b2f6d48dd (diff)
downloadu-boot-5a8a8045a928702d9b3fb6f73a4e9717040e09a9.tar.xz
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 'drivers/core/root.c')
0 files changed, 0 insertions, 0 deletions