From: Prabhakar Lad <prabhakar.lad@ti.com>
To: Mauro Carvalho Chehab <mchehab@infradead.org>
Cc: LMML <linux-media@vger.kernel.org>,
"davinci-linux-open-source@linux.davincidsp.com"
<davinci-linux-open-source@linux.davincidsp.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
LAK <linux-arm-kernel@lists.infradead.org>,
Manjunath Hadli <manjunath.hadli@ti.com>,
Hans Verkuil <hans.verkuil@cisco.com>,
Mauro Carvalho Chehab <mchehab@redhat.com>,
Sekhar Nori <nsekhar@ti.com>
Subject: [GIT PULL FOR v3.7] Davinci VPBE feature enhancement and fixes
Date: Wed, 3 Oct 2012 15:33:27 +0530 [thread overview]
Message-ID: <506C0D6F.1070700@ti.com> (raw)
Hi Mauro,
Can you please pull the following patches for davinci VPBE driver.
Some of the patches include platform changes for which Sekhar has Acked it.
Thanks and Regards,
--Prabhakar Lad
The following changes since commit 2425bb3d4016ed95ce83a90b53bd92c7f31091e4:
em28xx: regression fix: use DRX-K sync firmware requests on em28xx
(2012-10-02 17:15:22 -0300)
are available in the git repository at:
git://linuxtv.org/mhadli/v4l-dvb-davinci_devices.git vpbe_3.7_pull
Hans Verkuil (1):
dm644x: replace the obsolete preset API by the timings API.
Lad, Prabhakar (2):
media: davinci: vpbe: fix build warning
davinci: vpbe: replace V4L2_OUT_CAP_CUSTOM_TIMINGS with
V4L2_OUT_CAP_DV_TIMINGS
Manjunath Hadli (1):
ths7303: enable THS7303 for HD modes
arch/arm/mach-davinci/board-dm644x-evm.c | 15 ++--
arch/arm/mach-davinci/dm644x.c | 17 +---
drivers/media/i2c/ths7303.c | 106
++++++++++++++++++++----
drivers/media/platform/davinci/vpbe.c | 110
+++++++++++--------------
drivers/media/platform/davinci/vpbe_display.c | 80 +++++++++---------
drivers/media/platform/davinci/vpbe_venc.c | 25 +++---
include/media/davinci/vpbe.h | 14 ++--
include/media/davinci/vpbe_types.h | 8 +--
include/media/davinci/vpbe_venc.h | 2 +-
9 files changed, 211 insertions(+), 166 deletions(-)
reply other threads:[~2012-10-03 10:03 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=506C0D6F.1070700@ti.com \
--to=prabhakar.lad@ti.com \
--cc=davinci-linux-open-source@linux.davincidsp.com \
--cc=hans.verkuil@cisco.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=manjunath.hadli@ti.com \
--cc=mchehab@infradead.org \
--cc=mchehab@redhat.com \
--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