From: Prabhakar Lad <prabhakar.lad@ti.com>
To: <linux-arm-kernel@lists.infradead.org>
Cc: dlos <davinci-linux-open-source@linux.davincidsp.com>,
<linux-kernel@vger.kernel.org>,
Prabhakar Lad <prabhakar.lad@ti.com>
Subject: [PATCH v2 0/2] ARM: davinci: da850/omap-l138: add support for VPIF driver
Date: Mon, 20 Aug 2012 19:38:49 +0530 [thread overview]
Message-ID: <1345471731-31678-1-git-send-email-prabhakar.lad@ti.com> (raw)
This patch series adds support for VPIF
capture and display driver on da850/omap-l138.
Enables SD capture and display.
This patch series is dependent on the following patch:
https://patchwork.kernel.org/patch/1332311/
Changes for v2:
1: Avoid breaking of print messages.
2: Removed the handlers which just returned zero (which did nothing).
3: Clubbed the code where ever possible for DA850_UI_SD_VIDEO_PORT
config option.
4: Removed the dma_declare_coherent_memory() calls and used
global CMA.
5: Added the base address in increasing order.
Manjunath Hadli (2):
ARM: da850/omap-l138: Add SoC related definitions for VPIF
ARM: da850/omap-l138: Add EVM specific code for VPIF to work
arch/arm/mach-davinci/Kconfig | 9 ++
arch/arm/mach-davinci/board-da850-evm.c | 178 ++++++++++++++++++++++++++++
arch/arm/mach-davinci/da850.c | 162 +++++++++++++++++++++++++
arch/arm/mach-davinci/include/mach/da8xx.h | 11 ++
arch/arm/mach-davinci/include/mach/mux.h | 42 +++++++
arch/arm/mach-davinci/include/mach/psc.h | 1 +
6 files changed, 403 insertions(+), 0 deletions(-)
next reply other threads:[~2012-08-20 14:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-20 14:08 Prabhakar Lad [this message]
2012-08-20 14:08 ` [PATCH v2 1/2] ARM: da850/omap-l138: Add SoC related definitions for VPIF Prabhakar Lad
2012-09-07 17:01 ` Sekhar Nori
2012-08-20 14:08 ` [PATCH v2 2/2] ARM: da850/omap-l138: Add EVM specific code for VPIF to work Prabhakar Lad
2012-09-07 17:18 ` Sekhar Nori
2012-09-07 17:34 ` Prabhakar Lad
2012-09-10 9:27 ` Sekhar Nori
2012-09-10 12:06 ` 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=1345471731-31678-1-git-send-email-prabhakar.lad@ti.com \
--to=prabhakar.lad@ti.com \
--cc=davinci-linux-open-source@linux.davincidsp.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@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).