Re: [PATCH v2] ARM: exynos_defconfig: increase CONFIG_CMA_SIZE_MBYTES to 96

2017-03-07 Thread Krzysztof Kozlowski
On Tue, Feb 28, 2017 at 12:12:21PM -0700, Shuah Khan wrote: > 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,

Re: [PATCH v2] ARM: exynos_defconfig: increase CONFIG_CMA_SIZE_MBYTES to 96

2017-03-07 Thread Krzysztof Kozlowski
On Tue, Feb 28, 2017 at 12:12:21PM -0700, Shuah Khan wrote: > 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,

Re: [PATCH v2] ARM: exynos_defconfig: increase CONFIG_CMA_SIZE_MBYTES to 96

2017-03-01 Thread Krzysztof Kozlowski
On Wed, Mar 01, 2017 at 11:08:52AM -0700, Shuah Khan wrote: > On 03/01/2017 10:09 AM, Krzysztof Kozlowski wrote: > > On Tue, Feb 28, 2017 at 12:12:21PM -0700, Shuah Khan wrote: > >> Current CMA size of 64 Mbytes is right on the edge of being small when > >> several drivers need to allocate large

Re: [PATCH v2] ARM: exynos_defconfig: increase CONFIG_CMA_SIZE_MBYTES to 96

2017-03-01 Thread Krzysztof Kozlowski
On Wed, Mar 01, 2017 at 11:08:52AM -0700, Shuah Khan wrote: > On 03/01/2017 10:09 AM, Krzysztof Kozlowski wrote: > > On Tue, Feb 28, 2017 at 12:12:21PM -0700, Shuah Khan wrote: > >> Current CMA size of 64 Mbytes is right on the edge of being small when > >> several drivers need to allocate large

Re: [PATCH v2] ARM: exynos_defconfig: increase CONFIG_CMA_SIZE_MBYTES to 96

2017-03-01 Thread Shuah Khan
On 03/01/2017 10:09 AM, Krzysztof Kozlowski wrote: > On Tue, Feb 28, 2017 at 12:12:21PM -0700, Shuah Khan wrote: >> 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

Re: [PATCH v2] ARM: exynos_defconfig: increase CONFIG_CMA_SIZE_MBYTES to 96

2017-03-01 Thread Shuah Khan
On 03/01/2017 10:09 AM, Krzysztof Kozlowski wrote: > On Tue, Feb 28, 2017 at 12:12:21PM -0700, Shuah Khan wrote: >> 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

Re: [PATCH v2] ARM: exynos_defconfig: increase CONFIG_CMA_SIZE_MBYTES to 96

2017-03-01 Thread Krzysztof Kozlowski
On Tue, Feb 28, 2017 at 12:12:21PM -0700, Shuah Khan wrote: > 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 Everything looks good but I

Re: [PATCH v2] ARM: exynos_defconfig: increase CONFIG_CMA_SIZE_MBYTES to 96

2017-03-01 Thread Krzysztof Kozlowski
On Tue, Feb 28, 2017 at 12:12:21PM -0700, Shuah Khan wrote: > 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 Everything looks good but I

[PATCH v2] ARM: exynos_defconfig: increase CONFIG_CMA_SIZE_MBYTES to 96

2017-02-28 Thread Shuah Khan
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

[PATCH v2] ARM: exynos_defconfig: increase CONFIG_CMA_SIZE_MBYTES to 96

2017-02-28 Thread Shuah Khan
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