summaryrefslogtreecommitdiffstats
path: root/configs/bcm968380gerg_ram_defconfig
diff options
context:
space:
mode:
authorMasahiro Yamada <yamada.masahiro@socionext.com>2018-08-24 19:30:15 +0900
committerTom Rini <trini@konsulko.com>2018-08-31 11:59:44 -0400
commite3332e1a1a04534225801c2710c6faef4809641c (patch)
tree8e1777b9ee2feb63c12ae19d7bd1aa01032bd4a9 /configs/bcm968380gerg_ram_defconfig
parent4b0a2d3aabeba4df186113ef0c5edc25cec6001b (diff)
downloadu-boot-e3332e1a1a04534225801c2710c6faef4809641c.tar.gz
u-boot-e3332e1a1a04534225801c2710c6faef4809641c.tar.xz
u-boot-e3332e1a1a04534225801c2710c6faef4809641c.zip
Make kmalloc'ed memory really DMA-safe
In Linux, the memory returned by kmalloc() is DMA-capable. However, it is not true in U-Boot. At a glance, kmalloc() in U-Boot returns address aligned with ARCH_DMA_MINALIGN. However, it never pads the allocated memory. This half-way house is completely useless because calling kmalloc() and malloc() in this order causes a cache sharing problem. Change the implementation to call malloc_cache_aligned(), which allocates really DMA-capable memory. Signed-off-by: Masahiro Yamada <yamada.masahiro@socionext.com>
Diffstat (limited to 'configs/bcm968380gerg_ram_defconfig')
0 files changed, 0 insertions, 0 deletions