Skip to contentSkip to conversation

omapfb not accepting 720p mode

pandaboard Tobias Jakobi 2 participants 4 messages Oct 26, 2013 – Oct 28, 2013

lore
Share & tools
lore
#1 lore raw

Hi,

Quoted 5 lines · Tobias Jakobi

Hello,

the kernel bugtracker doesn't let me put this address into CC, so here manually:
https://bugzilla.kernel.org/show_bug.cgi?id=63781

The issue seems like we can't allocate buffers for 720p.

Can you make sure if CONFIG_DMA_CMA is set in your config? And you could set CMA_SIZE_MBYTES to a larger valuem say 50M.

Archit

#2 lore raw
Quoted 7 lines · Archit Taneja

The issue seems like we can't allocate buffers for 720p.

Can you make sure if CONFIG_DMA_CMA is set in your config? And you could set CMA_SIZE_MBYTES to a larger valuem say 50M.

Archit

Hello Archit,

yes, CMA is activated and with my latest config I've got 32MB allocated. I'll try to further increase the amount and check some other (larger) resolutions with don't require CVT (1280x1024 e.g.).

Also I may be wrong, but isn't allocation done after the parsing? The first message "cannot parse default modes" comes from omapfb_parse_def_modes returning an error. Which could be triggered by either the mode syntax being messed up (not the case for me I think), kstrdup failing (not very likely) or omapfb_set_def_mode failing. And from what I can see, omapfb_set_def_mode does some timing calculations/conversions, sets these timings and nothing more.

The allocation part is triggered by omapfb_create_framebuffers, so after omapfb_parse_def_modes.

Greets,
Tobias

#3 lore raw

Hi,

Quoted 14 lines · Tobias Jakobi
Quoted 7 lines · Archit Taneja

The issue seems like we can't allocate buffers for 720p.

Can you make sure if CONFIG_DMA_CMA is set in your config? And you could set CMA_SIZE_MBYTES to a larger valuem say 50M.

Archit

Hello Archit,

yes, CMA is activated and with my latest config I've got 32MB allocated. I'll try to further increase the amount and check some other (larger) resolutions with don't require CVT (1280x1024 e.g.).

Quoted 7 lines

Also I may be wrong, but isn't allocation done after the parsing? The first message "cannot parse default modes" comes from omapfb_parse_def_modes returning an error. Which could be triggered by either the mode syntax being messed up (not the case for me I think), kstrdup failing (not very likely) or omapfb_set_def_mode failing. And from what I can see, omapfb_set_def_mode does some timing calculations/conversions, sets these timings and nothing more.

You are right about the allocation coming after parsing the modes.

The problem is that our naming conventions for displays had changed sometime back. Could you change the name 'hdmi' to 'connector-hdmi', like below:

connector-hdmi:mode-string

Archit