From: u.kleine-koenig@pengutronix.de (Uwe Kleine-König)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 3/3] video: mxsfb: add DOTCLK polarity configuration support
Date: Mon, 4 Apr 2011 17:04:30 +0200 [thread overview]
Message-ID: <20110404150430.GB13963@pengutronix.de> (raw)
In-Reply-To: <1299341931-30241-4-git-send-email-shawn.guo@freescale.com>
Hello,
On Sun, Mar 06, 2011 at 12:18:51AM +0800, Shawn Guo wrote:
> The current implementation provides configuration for HSYNC_POL,
> VSYNC_POL and ENABLE_POL via 'sync' of fb_videomode, but DOTCLK_POL
> is missing there. It's assuming that data sampling at rising/positive
> edge is always the case. However, it's not true. For example, the
> panel on mx28evk board (Seiko 43WVF1G) samples data at
> failing/negative edge. The patch is to add this configuration.
s/failing/falling?
>
> Also, to unify the naming schema of all these polarity configurations
> and match them with the bits name in Reference Manual, a couple of
> definitions are renamed.
>
> Lastly, to reduce the chance of defining customized 'FB_SYNC_' flag
> by incrementing the preceeding value, the definitions are changed to
> bit shifting way.
>
> Signed-off-by: Shawn Guo <shawn.guo@freescale.com>
> ---
> arch/arm/mach-mxs/include/mach/mxsfb.h | 3 ++-
> drivers/video/mxsfb.c | 8 +++++---
> 2 files changed, 7 insertions(+), 4 deletions(-)
>
> diff --git a/arch/arm/mach-mxs/include/mach/mxsfb.h b/arch/arm/mach-mxs/include/mach/mxsfb.h
> index 923f397..e4d7979 100644
> --- a/arch/arm/mach-mxs/include/mach/mxsfb.h
> +++ b/arch/arm/mach-mxs/include/mach/mxsfb.h
> @@ -24,7 +24,8 @@
> #define STMLCDIF_18BIT 2 /** pixel data bus to the display is of 18 bit width */
> #define STMLCDIF_24BIT 3 /** pixel data bus to the display is of 24 bit width */
>
> -#define FB_SYNC_DATA_ENABLE_HIGH_ACT 64
> +#define FB_SYNC_DATA_ENABLE_HIGH_ACT (1 << 6)
> +#define FB_SYNC_DOTCLK_FAILING_ACT (1 << 7) /* failing/negtive edge sampling */
ditto + s/negtive/negative/
As your patch is already in mainline, do you care to send a followup?
Best regards
Uwe
--
Pengutronix e.K. | Uwe Kleine-K?nig |
Industrial Linux Solutions | http://www.pengutronix.de/ |
next prev parent reply other threads:[~2011-04-04 15:04 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-05 16:18 A few mxsfb patches Shawn Guo
2011-03-05 16:18 ` [PATCH 1/3] video: mxsfb: smarten the code a little bit Shawn Guo
2011-03-05 16:41 ` Arnd Bergmann
2011-03-06 4:09 ` Shawn Guo
2011-03-06 6:30 ` Shawn Guo
2011-03-06 6:18 ` [PATCH 1/3 RESEND] " Shawn Guo
2011-03-05 16:18 ` [PATCH 2/3] video: mxsfb: fix the incorrect error checking for alloc_pages_exact Shawn Guo
2011-03-05 16:18 ` [PATCH 3/3] video: mxsfb: add DOTCLK polarity configuration support Shawn Guo
2011-04-04 15:04 ` Uwe Kleine-König [this message]
2011-04-04 15:42 ` Shawn Guo
2011-04-05 5:53 ` Lothar Waßmann
2011-04-05 6:24 ` Shawn Guo
2011-04-05 7:32 ` Uwe Kleine-König
2011-04-05 6:47 ` [PATCH] video: mxsfb: correct typo 'FAILING' to 'FALLING' Shawn Guo
2011-04-05 7:36 ` Uwe Kleine-König
2011-03-07 7:26 ` A few mxsfb patches Sascha Hauer
2011-03-07 7:45 ` Shawn Guo
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=20110404150430.GB13963@pengutronix.de \
--to=u.kleine-koenig@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).