Commit 4c50185e authored by Sushaanth Srirangapathi's avatar Sushaanth Srirangapathi Committed by Kamal Mostafa

fbdev: da8xx-fb: fix videomodes of lcd panels

commit 713fced8 upstream.

Commit 028cd86b ("video: da8xx-fb: fix the polarities of the
hsync/vsync pulse") fixes polarities of HSYNC/VSYNC pulse but
forgot to update known_lcd_panels[] which had sync values
according to old logic. This breaks LCD at least on DA850 EVM.

This patch fixes this issue and I have tested this for panel
"Sharp_LK043T1DG01" using DA850 EVM board.

Fixes: 028cd86b ("video: da8xx-fb: fix the polarities of the hsync/vsync pulse")
Signed-off-by: default avatarSushaanth Srirangapathi <sushaanth.s@ti.com>
Signed-off-by: default avatarTomi Valkeinen <tomi.valkeinen@ti.com>
Signed-off-by: default avatarKamal Mostafa <kamal@canonical.com>
parent ee08b7fb
...@@ -209,8 +209,7 @@ static struct fb_videomode known_lcd_panels[] = { ...@@ -209,8 +209,7 @@ static struct fb_videomode known_lcd_panels[] = {
.lower_margin = 2, .lower_margin = 2,
.hsync_len = 0, .hsync_len = 0,
.vsync_len = 0, .vsync_len = 0,
.sync = FB_SYNC_CLK_INVERT | .sync = FB_SYNC_CLK_INVERT,
FB_SYNC_HOR_HIGH_ACT | FB_SYNC_VERT_HIGH_ACT,
}, },
/* Sharp LK043T1DG01 */ /* Sharp LK043T1DG01 */
[1] = { [1] = {
...@@ -224,7 +223,7 @@ static struct fb_videomode known_lcd_panels[] = { ...@@ -224,7 +223,7 @@ static struct fb_videomode known_lcd_panels[] = {
.lower_margin = 2, .lower_margin = 2,
.hsync_len = 41, .hsync_len = 41,
.vsync_len = 10, .vsync_len = 10,
.sync = FB_SYNC_HOR_HIGH_ACT | FB_SYNC_VERT_HIGH_ACT, .sync = 0,
.flag = 0, .flag = 0,
}, },
[2] = { [2] = {
...@@ -239,7 +238,7 @@ static struct fb_videomode known_lcd_panels[] = { ...@@ -239,7 +238,7 @@ static struct fb_videomode known_lcd_panels[] = {
.lower_margin = 10, .lower_margin = 10,
.hsync_len = 10, .hsync_len = 10,
.vsync_len = 10, .vsync_len = 10,
.sync = FB_SYNC_HOR_HIGH_ACT | FB_SYNC_VERT_HIGH_ACT, .sync = 0,
.flag = 0, .flag = 0,
}, },
[3] = { [3] = {
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment