Hello, since some boards need to manage GPIOs to turn on and off the LCD and since on shutdwon the driver does: #if !defined(CONFIG_FRAMEBUFFER_CONSOLE) && defined(CONFIG_LOGO) au1100fb_fb_blank(VESA_POWERDOWN, &fbdev->info); #endif fbdev->regs->lcd_control &= ~LCD_CONTROL_GO; I suggest the attached patch to do the same during boot. Note that this prevents boards support developers to add specific code before the command: fbdev->regs->lcd_control |= LCD_CONTROL_GO; but putting all these stuff into proper function au1100fb_fb_blank(). Please, let me know what do you think about it. Ciao, Rodolfo -- GNU/Linux Solutions e-mail: giometti@xxxxxxxxxxxx Linux Device Driver giometti@xxxxxxxxx Embedded Systems giometti@xxxxxxxx UNIX programming phone: +39 349 2432127
diff --git a/drivers/video/au1100fb.c b/drivers/video/au1100fb.c index 7c5fd9c..a59654b 100644 --- a/drivers/video/au1100fb.c +++ b/drivers/video/au1100fb.c @@ -110,6 +114,8 @@ static struct fb_var_screeninfo au1100fb static struct au1100fb_drv_info drv_info; +int au1100fb_fb_blank(int blank_mode, struct fb_info *fbi); + /* * Set hardware with var settings. This will enable the controller with a specific * mode, normally validated with the fb_check_var method @@ -205,7 +211,7 @@ int au1100fb_setmode(struct au1100fb_dev fbdev->regs->lcd_pwmhi = 0; /* Resume controller */ - fbdev->regs->lcd_control |= LCD_CONTROL_GO; + au1100fb_fb_blank(VESA_NO_BLANKING, &fbdev->info); return 0; }