From: "Ивайло Димитров" <freemangordon@abv.bg>
To: tomi.valkeinen@ti.com
Cc: pali.rohar@gmail.com, pc+n900@asdf.org, linux-kernel@vger.kernel.org
Subject: OMAPFB: CMA allocation failures
Date: Sat, 12 Oct 2013 17:43:08 +0300 (EEST) [thread overview]
Message-ID: <950342286.150022.1381588988533.JavaMail.apache@mail83.abv.bg> (raw)
Hi Tomi,
patch http://lists.infradead.org/pipermail/linux-arm-kernel/2012-November/131269.html modifies
omapfb driver to use DMA API to allocate framebuffer memory instead of preallocating VRAM.
With this patch I see a lot of:
Jan 1 06:33:27 Nokia-N900 kernel: [ 2054.879577] cma: dma_alloc_from_contiguous(cma c05f5844, count 192, align 8)
Jan 1 06:33:27 Nokia-N900 kernel: [ 2054.914215] cma: dma_alloc_from_contiguous(): memory range at c07df000 is busy, retrying
Jan 1 06:33:27 Nokia-N900 kernel: [ 2054.933502] cma: dma_alloc_from_contiguous(): memory range at c07e1000 is busy, retrying
Jan 1 06:33:27 Nokia-N900 kernel: [ 2054.940032] cma: dma_alloc_from_contiguous(): memory range at c07e3000 is busy, retrying
Jan 1 06:33:27 Nokia-N900 kernel: [ 2054.966644] cma: dma_alloc_from_contiguous(): memory range at c07e5000 is busy, retrying
Jan 1 06:33:27 Nokia-N900 kernel: [ 2054.976867] cma: dma_alloc_from_contiguous(): memory range at c07e7000 is busy, retrying
Jan 1 06:33:27 Nokia-N900 kernel: [ 2055.038055] cma: dma_alloc_from_contiguous(): memory range at c07e9000 is busy, retrying
Jan 1 06:33:27 Nokia-N900 kernel: [ 2055.038116] cma: dma_alloc_from_contiguous(): returned (null)
Jan 1 06:33:27 Nokia-N900 kernel: [ 2055.038146] omapfb omapfb: failed to allocate framebuffer
errors while trying to play a video on N900 with Maemo 5 (Fremantle) on top of linux-3.12rc1.
It is deffinitely the CMA that fails to allocate the memory most of the times, but I wonder
how reliable CMA is to be used in omapfb. I even reserved 64MB for CMA, but that made no
difference. If CMA is disabled, the memory allocation still fails as obviously it is highly
unlikely there will be such a big chunk of continuous free memory on RAM limited device like
N900.
One obvious solution is to just revert the removal of VRAM memory allocator, but that would
mean I'll have to maintain a separate tree with all the implications that brings.
What would you advise on how to deal with the issue?
Regards,
Ivo
next reply other threads:[~2013-10-12 14:48 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-12 14:43 Ивайло Димитров [this message]
2013-10-14 6:04 ` OMAPFB: CMA allocation failures Tomi Valkeinen
-- strict thread matches above, loose matches on Subject: below --
2013-10-15 6:49 Ивайло Димитров
2013-10-15 7:36 ` Tomi Valkeinen
2013-10-28 7:37 ` Minchan Kim
2013-10-16 6:33 Ивайло Димитров
2013-10-23 21:59 Ивайло Димитров
2013-10-24 7:00 ` Tomi Valkeinen
2013-10-29 12:47 Ивайло Димитров
2013-10-30 5:53 ` Minchan Kim
2013-10-30 12:19 ` Tomi Valkeinen
2013-11-05 19:55 Ивайло Димитров
[not found] <1847426616.52843.1383681351015.JavaMail.apache@mail83.abv.bg>
2013-11-30 10:00 ` Ivajlo Dimitrov
2013-12-05 11:25 ` Tomi Valkeinen
2013-12-06 8:31 ` Ivajlo Dimitrov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=950342286.150022.1381588988533.JavaMail.apache@mail83.abv.bg \
--to=freemangordon@abv.bg \
--cc=linux-kernel@vger.kernel.org \
--cc=pali.rohar@gmail.com \
--cc=pc+n900@asdf.org \
--cc=tomi.valkeinen@ti.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).