From: James Simmons <jsimmons@infradead.org>
To: linux-fbdev@vger.kernel.org
Subject: fw: [PATCH v1 0/2] ARM: S5PV210: Add MIPI-DSI support.
Date: Tue, 06 Jul 2010 15:26:26 +0000 [thread overview]
Message-ID: <alpine.LFD.2.00.1007061612280.3285@casper.infradead.org> (raw)
Hello all,
This patch is for MIPI-DSI controller based on S5PV210 (or S5PC110).
this version corrects some problems Ben pointed out.
v1 patch includes below contents.
- set callbacks to MIPI Client driver at mipi_ddi_platform_data declaration.
- use MIPI regulator names set at s5p_platform_dsim declaration to get regulators for them.
- use a table to get freq_band value.
- code clean and fix minor bugs.
LCD Panel can use following interfaces,
- RGB or CPU Interface.
- RGB or CPU Interface based on MIPI-DSI.
in case of cell phone device, small size lcd panel(less then 480x800) was ok only rgb or cpu interface not using mipi controller.
but big size panel(bigger then 480x800) needs MIPI-DSI Interface or other hardwares like LVDS to transfer image data to lcd panel fine.
I tested this patch on cpu interface based on MIPI-DSI and also considered RGB interface.
This patch set consists of the following patches,
[PATCH v1 1/2] S5PV210: FB: Add MIPI-DSI and CPU Interface features.
[PATCH v1 2/2] S5PV210: Add MIPI-DSI Driver.
Best regards,
InKi Dae
[ Part 3: "Included Message" ]
From: linux-fbdev-devel-request@lists.sourceforge.net
Subject: confirm a131e69dac1c92ff53f639daca88d07fe442c6a9
If you reply to this message, keeping the Subject: header intact,
Mailman will discard the held message. Do this if the message is
spam. If you reply to this message and include an Approved: header
with the list password in it, the message will be approved for posting
to the list. The Approved: header can also appear in the first line
of the body of the reply.
reply other threads:[~2010-07-06 15:26 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=alpine.LFD.2.00.1007061612280.3285@casper.infradead.org \
--to=jsimmons@infradead.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).