On Sat, Sep 6, 2008 at 6:01 AM, arun c <arunedarath@xxxxxxxxxxxxxxxxxxxx> wrote:
> This patch fixes the irq error warnings from omapfb which
> was stalling the console.
>
> Only the below 2 errors are coming now
>
> omapfb omapfb: irq error status 00e2
> omapfb omapfb: irq error status 00c0
>
> Signed-off-by: Arun C <arunedarath@xxxxxxxxxxxxxxxxxxxx>
> ---
> drivers/video/omap/lcd_omap2evm.c | 6 +++---
> 1 files changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/video/omap/lcd_omap2evm.c
> b/drivers/video/omap/lcd_omap2evm.c
> index 8a0105e..c58f2d0 100644
> --- a/drivers/video/omap/lcd_omap2evm.c
> +++ b/drivers/video/omap/lcd_omap2evm.c
> @@ -130,11 +130,11 @@ struct lcd_panel omap2evm_panel = {
> .x_res = LCD_XRES,
> .y_res = LCD_YRES,
> .hsw = 3,
> - .hfp = 0,
> + .hfp = 10,
> .hbp = 28,
> .vsw = 2,
> - .vfp = 1,
> - .vbp = 0,
> + .vfp = 3,
> + .vbp = 1,
>
> .pixel_clock = LCD_PIXCLOCK_MAX,
>
> --
> 1.5.3.4
>
Please ignore this patch as of now.
The problem is whenever I add support for new device the
error(omapfb irq errors) is coming again. There was no issues
until we added support for nand. After nand support error
messages began to appear and this patch solved it.
Today I added support for touch screen and the errors
came again. I had to adjust the above values(hbp, hfp, vbp, vfp)
again to resolve the issues.
I am thinking that I will send the final stable values after
adding full support for OMAP2EVM.
Do anybody know how to optimize (hsw, hfp, hbp, vsw, vbp,
vfp) values?
Regards,
Arun C
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
