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 N MiB 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 <m.szyprow...@samsung.com> Signed-off-by: Shuah Khan <shua...@osg.samsung.com> Reviewed-by: Javier Martinez Canillas <jav...@osg.samsung.com> --- Changes since v1: Fix short and long commit log. Reason for this patch: With the proposed s5p_mfc patch series that pre-allocate buffers, when display manager starts, it fails to get GEM buffers. Increasing the CMA size to 96 solved the problem. arch/arm/configs/exynos_defconfig | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/arch/arm/configs/exynos_defconfig b/arch/arm/configs/exynos_defconfig index 742baf0..2541414 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 -- 2.7.4
