diff options
| author | Janorkar, Mayuresh <mayur@ti.com> | 2011-02-22 07:35:13 -0600 |
|---|---|---|
| committer | Tomi Valkeinen <tomi.valkeinen@ti.com> | 2011-03-11 15:46:23 +0200 |
| commit | 371e2081447ce2bc6a25c20b513b9ba33cf5769e (patch) | |
| tree | 07d87df8133912e361d398590574c37d98d82fde /arch | |
| parent | 09dc89cb3123d102e1615fab9e3d65a70402d061 (diff) | |
OMAPFB: Adding a check for timings in set_def_mode
When omapfb.mode is passed through bootargs, when omapfb is setting mode,
it would check if timings passed are fine for panel attached to it.
It makes use of check_timing API provided by the panel.
In current code if check_timing API is not available for attached panel,
OMAPFB would return -EINVAL and BPP sent via bootargs will not have any effect.
In case of panels like TAAL panel, omapfb or any other driver should not be allowed to
change the timings. So bpps sent via bootargs will not have an effect.
In such case we can check only the x_res and y_res with the panels resolution
and if they match go ahead and set the bpps.
The bpp value sent via bootarg would have an effect.
Signed-off-by: Mayuresh Janorkar <mayur@ti.com>
Signed-off-by: Tomi Valkeinen <tomi.valkeinen@ti.com>
Diffstat (limited to 'arch')
0 files changed, 0 insertions, 0 deletions