On 02/28/2017 09:42 AM, Javier Martinez Canillas wrote:
> Hello Shuah,
>
> The subject line isn't consistent with what's used for exynos_defconfig
> changes, please use instead:
>
> ARM: exynos_defconfig: Increase CONFIG_CMA_SIZE_MBYTES to 96
>
oops - I meant o make it exynos_defconfig
> On 02
On Tue, Feb 28, 2017 at 09:52:33AM -0700, Shuah Khan wrote:
> On 02/28/2017 09:42 AM, Javier Martinez Canillas wrote:
> > Hello Shuah,
> >
> > The subject line isn't consistent with what's used for exynos_defconfig
> > changes, please use instead:
> >
> > ARM: exynos_defconfig: Increase CONFIG_CM
Hello Shuah,
The subject line isn't consistent with what's used for exynos_defconfig
changes, please use instead:
ARM: exynos_defconfig: Increase CONFIG_CMA_SIZE_MBYTES to 96
On 02/27/2017 09:23 PM, Shuah Khan wrote:
> Current CMA size of 64 Mbytes is right on the edge of being too small
> for s
Current CMA size of 64 Mbytes is right on the edge of being too small
for some display managers. 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 solves the problem.
Change CONFIG_CMA_SIZE_MB
4 matches
Mail list logo