linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Damian Hobson-Garcia <dhobsong@igel.co.jp>
To: linux-fbdev@vger.kernel.org
Subject: [PATCH 2/2] fbdev: sh_mobile_lcdc: Define additional .nonstd flags for sh7372
Date: Wed, 23 Feb 2011 10:16:50 +0000	[thread overview]
Message-ID: <1298456210-26519-3-git-send-email-dhobsong@igel.co.jp> (raw)

The value of the .nonstd member of struct sh_mobile_lcdc_info is written
directly into bits 16 and up of LDDFR in the LCDC. This patch defines
additional flags that can be "or'ed" with the .nonstd value to control
the LCDC behaviour when operating the the YUV display mode.

Signed-off-by: Damian Hobson-Garcia <dhobsong@igel.co.jp>
---
 arch/arm/mach-shmobile/include/mach/sh7372.h |   11 +++++++++++
 1 files changed, 11 insertions(+), 0 deletions(-)

diff --git a/arch/arm/mach-shmobile/include/mach/sh7372.h b/arch/arm/mach-shmobile/include/mach/sh7372.h
index 5736efc..cdbc2cf 100644
--- a/arch/arm/mach-shmobile/include/mach/sh7372.h
+++ b/arch/arm/mach-shmobile/include/mach/sh7372.h
@@ -13,6 +13,17 @@
 
 #include <linux/sh_clk.h>
 
+/* LCDC YUV support:
+ * The following bit flags are used to set the bits 17 and up
+ * in the MLDDFR. These flags should be used to set the
+ * .nonstd field in the struct sh_mobile_lcdc_info.
+ * Bit 16, which is accessible from user space is defined in
+ * <linux/sh_mobile_fb.h>
+ * The flags have different values for different chips
+ */
+#define LCDC_YUV_FULL_RANGE ((0x1 << 17) >> 16)
+#define LCDC_YUV_BT_709 ((0x1 << 18) >> 16)
+
 /*
  * Pin Function Controller:
  *	GPIO_FN_xx - GPIO used to select pin function
-- 
1.7.1


                 reply	other threads:[~2011-02-23 10:16 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=1298456210-26519-3-git-send-email-dhobsong@igel.co.jp \
    --to=dhobsong@igel.co.jp \
    --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 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).