OMAPFB: use dma_alloc instead of omap's vram
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest0 of 5 patches 0 repliesNew
Patches in v1 No applies recorded yet
None of the 5 patches the cover letter announces are in this archive.
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [PATCH 0/5] OMAPFB: use dma_alloc instead of omap's vram
Quoted 4 lines · Tony Lindgren
Quoted 2 lines
Should we enable CMA by default in
omap2plus_defconfig? And perhaps on omap1 also?Yes if that's now needed for DSS.
DSS works fine without CMA, at least for small displays, and when fb allocation is done at boot time. So it's not a strict "need".
I'm not sure how easily FB allocations start to fail without CMA, and how much CMA helps.
I'm not even sure what's the default DMA pool size on OMAP... If it's the one set with "coherent_pool" kernel parameter, then the default seems to be 256K, which is quite small for video use. For CMA the default global area is 16M. Both can, of course, be changed with boot params or kernel config (at least for CMA).
But I think it makes sense to have CMA by default even if non-CMA kernel would work.
Tomi
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 897 bytes
Desc: OpenPGP digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20121120/85fa6eaa/attachment.sig>