From: Vikas C Sajjan <vikas.sajjan@linaro.org>
To: linux-media@vger.kernel.org, dri-devel@lists.freedesktop.org
Cc: inki.dae@samsung.com, laurent.pinchart@ideasonboard.com,
tomi.valkeinen@ti.com, jesse.barker@linaro.org,
aditya.ps@samsung.com
Subject: [PATCH 0/2] Making Exynos MIPI Complaint with Common Display Framework
Date: Wed, 2 Jan 2013 18:47:20 +0530 [thread overview]
Message-ID: <1357132642-24588-1-git-send-email-vikas.sajjan@linaro.org> (raw)
From: Vikas Sajjan <vikas.sajjan@linaro.org>
This patchset contains 2 RFCs, 1st RFC has modiifications in exynos MIPI DSI
driver.
2nd RFC has additions done to video source struct as per exynos requirements.
I have NOT tested the patch yet, as i am yet recieve the MIPI DSI panel.
This based on Tomi's CDF RFC.
I am yet to modify s6e8ax0.c as per CDF and I have NOT tested these patches yet,
as i am yet recieve the MIPI DSI panel.
Vikas Sajjan (2):
[RFC] video: exynos mipi dsi: Making Exynos MIPI Complaint with CDF
[RFC] video: display: Adding frame related ops to MIPI DSI video
source struct
drivers/video/exynos/exynos_mipi_dsi.c | 46 ++++++++++++++++++-------
drivers/video/exynos/exynos_mipi_dsi_common.c | 22 ++++++++----
drivers/video/exynos/exynos_mipi_dsi_common.h | 12 +++----
include/video/display.h | 6 ++++
include/video/exynos_mipi_dsim.h | 5 ++-
5 files changed, 62 insertions(+), 29 deletions(-)
--
1.7.9.5
next reply other threads:[~2013-01-02 13:17 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-02 13:17 Vikas C Sajjan [this message]
2013-01-02 13:17 ` [PATCH 1/2] [RFC] video: exynos mipi dsi: Making Exynos MIPI Complaint with CDF Vikas C Sajjan
2013-01-03 5:44 ` Sachin Kamat
2013-01-03 8:30 ` Vikas Sajjan
2013-01-02 13:17 ` [PATCH 2/2] [RFC] video: display: Adding frame related ops to MIPI DSI video source struct Vikas C Sajjan
2013-01-03 10:59 ` Tomasz Figa
2013-01-04 4:54 ` Vikas Sajjan
2013-01-09 23:35 ` Laurent Pinchart
2013-01-10 5:37 ` Vikas Sajjan
2013-01-10 7:43 ` Inki Dae
2013-01-10 11:33 ` Jani Nikula
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=1357132642-24588-1-git-send-email-vikas.sajjan@linaro.org \
--to=vikas.sajjan@linaro.org \
--cc=aditya.ps@samsung.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=inki.dae@samsung.com \
--cc=jesse.barker@linaro.org \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-media@vger.kernel.org \
--cc=tomi.valkeinen@ti.com \
/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).