From: Shuah Khan Date: Tue, 28 Feb 2017 19:12:21 +0000 (-0700) Subject: ARM: exynos_defconfig: Increase CONFIG_CMA_SIZE_MBYTES to 96 X-Git-Url: https://git.stricted.de/?a=commitdiff_plain;h=fd2694a112d6b53eba8d8e182fef0dccdab6c9e8;p=GitHub%2Fmoto-9609%2Fandroid_kernel_motorola_exynos9610.git ARM: exynos_defconfig: Increase CONFIG_CMA_SIZE_MBYTES to 96 Current CMA size of 64 Mbytes is right on the edge of being small when several drivers need to allocate large CMA buffers. For example, if the s5p-mfc driver needs to pre-allocate CMA memory to decode a H.264 1080p video, then there won't be enough CMA memory left for other drivers, such as the exynos-drm driver that may need to allocate GEM buffers for the display manager. Increasing CMA size to 96 Mbytes in exynos_defconfig addresses use-cases such as these. Suggested-by: Marek Szyprowski Signed-off-by: Shuah Khan Reviewed-by: Javier Martinez Canillas Signed-off-by: Krzysztof Kozlowski --- diff --git a/arch/arm/configs/exynos_defconfig b/arch/arm/configs/exynos_defconfig index ed38259ce65e..6dc661c4a2c1 100644 --- a/arch/arm/configs/exynos_defconfig +++ b/arch/arm/configs/exynos_defconfig @@ -53,7 +53,7 @@ CONFIG_RFKILL_REGULATOR=y CONFIG_DEVTMPFS=y CONFIG_DEVTMPFS_MOUNT=y CONFIG_DMA_CMA=y -CONFIG_CMA_SIZE_MBYTES=64 +CONFIG_CMA_SIZE_MBYTES=96 CONFIG_BLK_DEV_LOOP=y CONFIG_BLK_DEV_CRYPTOLOOP=y CONFIG_BLK_DEV_RAM=y