From: Sergei Shtylyov <sshtylyov@mvista.com>
To: linux-fbdev@vger.kernel.org
Subject: Re: [PATCH] DA8XX/OMAP-L1XX: FB: Implement double buffering
Date: Wed, 24 Mar 2010 14:53:12 +0000 [thread overview]
Message-ID: <4BAA2758.8060105@mvista.com> (raw)
Hello.
Martin Ambrose wrote:
> This work includes the following:
> . Implement handler for FBIO_WAITFORVSYNC ioctl.
>
> . Allocate the data and palette buffers separately.
> A consequence of this is that the palette and data loading is now
> done in different phases. And that the LCD must be disabled
> temporarily after the palette is loaded but this will only happen
> once after init and each time the palette is changed. I think this
> is OK.
>
> . Allocate two (ping and pong) framebuffers from memory.
>
> . Add pan_display handler which toggles the LCDC DMA registers between
> the ping and pong buffers.
>
> Signed-off-by: Martin Ambrose <martin@ti.com>
>
Just a quick comment on code formatting...
> diff --git a/drivers/video/da8xx-fb.c b/drivers/video/da8xx-fb.c
> index 369a5b3..7e192e2 100644
> --- a/drivers/video/da8xx-fb.c
> +++ b/drivers/video/da8xx-fb.c
> @@ -35,7 +35,9 @@
> #define DRIVER_NAME "da8xx_lcdc"
>
> /* LCD Status Register */
> +#define LCD_END_OF_FRAME1 BIT(9)
> #define LCD_END_OF_FRAME0 BIT(8)
> +#define LCD_PL_LOAD_DONE BIT(6)
>
Could you use tabs consistently?
> #define LCD_FIFO_UNDERFLOW BIT(5)
> #define LCD_SYNC_LOST BIT(2)
>
> @@ -57,11 +59,13 @@
> #define LCD_PALETTE_LOAD_MODE(x) ((x) << 20)
> #define PALETTE_AND_DATA 0x00
> #define PALETTE_ONLY 0x01
> +#define DATA_ONLY 0x02
>
> #define LCD_MONO_8BIT_MODE BIT(9)
> #define LCD_RASTER_ORDER BIT(8)
> #define LCD_TFT_MODE BIT(7)
> #define LCD_UNDERFLOW_INT_ENA BIT(6)
> +#define LCD_PL_ENABLE BIT(4)
>
Same here...
WBR, Sergei
next reply other threads:[~2010-03-24 14:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-24 14:53 Sergei Shtylyov [this message]
2010-03-29 12:48 ` [PATCH] DA8XX/OMAP-L1XX: FB: Implement double buffering Ambrose, Martin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4BAA2758.8060105@mvista.com \
--to=sshtylyov@mvista.com \
--cc=linux-fbdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.