[pandaboard] omapfb not accepting 720p mode

[pandaboard] omapfb not accepting 720p mode

[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

Greets,
Tobias

Re: [pandaboard] omapfb not accepting 720p mode

[Archit Taneja]

Hi,

On Saturday 26 October 2013 09:01 PM, Tobias Jakobi wrote:
> 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

Re: [pandaboard] omapfb not accepting 720p mode

[Tobias Jakobi]

Archit Taneja wrote:
> 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

Re: [pandaboard] omapfb not accepting 720p mode

[Archit Taneja]

Hi,

On Monday 28 October 2013 03:04 PM, Tobias Jakobi wrote:
> Archit Taneja wrote:
>> 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.

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