From: Prabhakar lad <prabhakar.csengg@gmail.com>
To: DLOS <davinci-linux-open-source@linux.davincidsp.com>,
LAK <linux-arm-kernel@lists.infradead.org>,
Sekhar Nori <nsekhar@ti.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
"Lad, Prabhakar" <prabhakar.csengg@gmail.com>
Subject: [PATCH v6 0/2] ARM: davinci: dm355: add support for vpbe display
Date: Fri, 22 Mar 2013 13:39:27 +0530 [thread overview]
Message-ID: <1363939769-22506-1-git-send-email-prabhakar.csengg@gmail.com> (raw)
From: Lad, Prabhakar <prabhakar.csengg@gmail.com>
This patch series enables VPBE display driver on DM355.
This patch series is dependent on VPSS clock cleanup patches
(http://www.mail-archive.com/davinci-linux-open-source@linux.davincidsp.com/msg25499.html)
posted.
Chnages for v6:
1: Fixed nits pointed by Sekhar.
Changes for v5:
1: Rebased on 3.9, fix review comments pointed by Sekhar for DM365 series.
Changes for v4:
1: pass different platform names to handle different ip's.
Changes for v3:
1: Replaced obsolete preset API by timings API.
Changes for v2:
1: Removed VPSS clock alias for master and slave which was
sent for VPSS driver. since this patch was dependent on
patch[1]. I will revist this patch once MC(captrure driver)
goes into mainline.
[1] http://www.spinics.net/lists/linux-media/msg50562.html
Lad, Prabhakar (2):
ARM: davinci: dm355: add support for v4l2 video display
ARM: davinci: dm355 EVM: add support for VPBE display
arch/arm/mach-davinci/board-dm355-evm.c | 71 ++++++++++++-
arch/arm/mach-davinci/davinci.h | 2 +-
arch/arm/mach-davinci/dm355.c | 181 ++++++++++++++++++++++++++++++-
3 files changed, 246 insertions(+), 8 deletions(-)
--
1.7.4.1
next reply other threads:[~2013-03-22 8:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-22 8:09 Prabhakar lad [this message]
2013-03-22 8:09 ` [PATCH v6 1/2] ARM: davinci: dm355: add support for v4l2 video display Prabhakar lad
2013-03-22 8:09 ` [PATCH v6 2/2] ARM: davinci: dm355 EVM: add support for VPBE display Prabhakar lad
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=1363939769-22506-1-git-send-email-prabhakar.csengg@gmail.com \
--to=prabhakar.csengg@gmail.com \
--cc=davinci-linux-open-source@linux.davincidsp.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nsekhar@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
all inboxes | Powered by JetHome®