From: Paul Mundt <lethal@linux-sh.org>
To: linux-fbdev@vger.kernel.org
Subject: Re: [PATCH v2] fbdev: sh_mobile_lcdc: Add YUV input support
Date: Fri, 11 Mar 2011 04:54:20 +0000 [thread overview]
Message-ID: <20110311045420.GB19466@linux-sh.org> (raw)
In-Reply-To: <1298526433-6621-1-git-send-email-dhobsong@igel.co.jp>
On Wed, Mar 02, 2011 at 03:42:13PM +0900, Damian wrote:
> Supports YCbCr420sp, YCbCr422sp, and YCbCr44sp, formats
> (bpp = 12, 16, and 24) respectively.
>
> When double-buffering both Y planes appear before the C planes (Y-Y-C-C),
> as opposed to Y-C-Y-C.
> Set .nonstd in struct sh_mobile_lcdc_chan_cfg to enable YUV mode, and use
> .bpp to distiguish between the 3 modes.
> The value of .nonstd is copied to bits 16-31 of LDDFR in the LCDC and
> should be set accordingly.
> .nonstd must be set to 0 for RGB mode.
>
> Due to the encoding of YUV data, the framebuffer will clear to green
> instead of black.
>
> In YUV 420 mode, panning is only possible in 2 line increments.
> Additionally in YUV 420 mode the vertical resolution of the framebuffer
> must be an even number.
>
> Signed-off-by: Damian Hobson-Garcia <dhobsong@igel.co.jp>
This version of the patch was horribly line-wrapped, but the previous one
'fbdev: sh_mobile_lcdc: Add YUV framebuffer support' which seemed to have
an identical description and versioning looked fine, so I've taken that
one in to the fbdev tree.
You may wish to double check to make sure that what has been merged is in
sync with your latest changes.
next prev parent reply other threads:[~2011-03-11 4:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-24 5:47 [PATCH v2] fbdev: sh_mobile_lcdc: Add YUV framebuffer support Damian Hobson-Garcia
2011-03-02 6:42 ` [PATCH v2] fbdev: sh_mobile_lcdc: Add YUV input support Damian
2011-03-11 4:54 ` Paul Mundt [this message]
2011-03-15 1:23 ` Damian
2011-03-16 8:28 ` Paul Mundt
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=20110311045420.GB19466@linux-sh.org \
--to=lethal@linux-sh.org \
--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).