From: Paul Mundt <lethal@linux-sh.org>
To: linux-fbdev@vger.kernel.org
Subject: Re: [PATCH] fbdev: sh_mobile_lcdcfb: Enable 32 bpp and 24 bpp support
Date: Thu, 06 Jan 2011 08:07:45 +0000 [thread overview]
Message-ID: <20110106080745.GD15914@linux-sh.org> (raw)
In-Reply-To: <20110105102100.13620.6354.sendpatchset@t400s>
On Wed, Jan 05, 2011 at 07:21:00PM +0900, Magnus Damm wrote:
> From: Magnus Damm <damm@opensource.se>
>
> This patch extends the LCDC driver with 24 bpp
> and 32 bpp support.
>
> These modes have been kept disabled earlier due
> to dependencies between the potential two LCDC
> channels that are exported as two separate
> framebuffer devices. The dependency boils down
> to a byte swap register that is shared between
> multiple channels.
>
> With this patch applied all single channel LCDC
> hardware can chose freely from 16, 24 and 32 bpp.
> Dual channel LCDC must stick to the same setup
> for both channels.
>
> Without this patch only 16 bpp is fully supported.
>
> Signed-off-by: Magnus Damm <damm@opensource.se>
Applied, thanks.
prev parent reply other threads:[~2011-01-06 8:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-05 10:21 [PATCH] fbdev: sh_mobile_lcdcfb: Enable 32 bpp and 24 bpp support Magnus Damm
2011-01-06 8:07 ` Paul Mundt [this message]
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=20110106080745.GD15914@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).