[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <568A5970.2000201@ti.com>
Date: Mon, 4 Jan 2016 13:37:20 +0200
From: Tomi Valkeinen <tomi.valkeinen@...com>
To: Pali Rohár <pali.rohar@...il.com>
CC: Ivaylo Dimitrov <ivo.g.dimitrov.75@...il.com>, <tony@...mide.com>,
<linux@....linux.org.uk>, <pavel@....cz>,
<linux-omap@...r.kernel.org>, <linux-kernel@...r.kernel.org>,
Ivaylo Dimitrov <freemangordon@....bg>
Subject: Re: [PATCH] ARM: omapfb: Add early framebuffer memory allocator
Hi,
On 01/01/16 14:01, Pali Rohár wrote:
> Hi Tomi! Can you review this patch? It is waiting here for two years!
>
> On Thursday 26 December 2013 00:12:39 Ivaylo Dimitrov wrote:
>> From: Ivaylo Dimitrov <freemangordon@....bg>
>>
>> On memory limited devices, CMA fails easily when asked to allocate
>> big chunks of memory like framebuffer memory needed for video
>> playback.
>>
>> Add boot parameter "omapfb_memsize" which allocates memory to be used
>> as dma coherent memory, so dma_alloc_attrs won't hit CMA allocator
>> when trying to allocate memory for the framebuffers
We probably need exactly the same for omapdrm, as omapfb is on the way
to being deprecated. And sounds to me that we probably need similar for
other devices which try to do large allocations (camera? video decoders?).
So I really think this should be somehow be a general option for any device.
I also wonder if CMA can be improved to not need anything like this? If
you just increase the CMA area, won't that increase the chances CMA will
work?
Tomi
Download attachment "signature.asc" of type "application/pgp-signature" (820 bytes)
Powered by blists - more mailing lists