From: nsekhar@ti.com (Sekhar Nori)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 0/2] ARM: davinci: da850/omap-l138: add support for VPIF driver
Date: Wed, 3 Oct 2012 13:47:58 +0530 [thread overview]
Message-ID: <506BF4B6.8090701@ti.com> (raw)
In-Reply-To: <1347344709-6180-1-git-send-email-prabhakar.lad@ti.com>
Hi Prabhakar,
On 9/11/2012 11:55 AM, Prabhakar Lad wrote:
> 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 v3:
> 1: Clubbed the code for DA850_UI_SD_VIDEO_PORT config
> as pointed by Sekhar.
> 2: Define the resource structure outside the function as pointed
> by Sekhar.
>
> 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
>
> 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 | 7 ++
> arch/arm/mach-davinci/board-da850-evm.c | 156 ++++++++++++++++++++++++++++
> arch/arm/mach-davinci/da850.c | 152 +++++++++++++++++++++++++++
> 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, 369 insertions(+), 0 deletions(-)
The patches look good to me. In case you want to queue them through the
media tree to manage the dependencies, feel free to add my:
Acked-by: Sekhar Nori <nsekhar@ti.com>
Note that the subject like prefix for DA850 soc patches should be
"ARM: davinci: da850: .."
and that for DA850 EVM patches should be:
"ARM: davinci: da850 evm: .."
instead of what you have used here. Please fix these if you are queuing
them and take care of this in future.
Thanks,
Sekhar
WARNING: multiple messages have this Message-ID (diff)
From: Sekhar Nori <nsekhar@ti.com>
To: Prabhakar Lad <prabhakar.lad@ti.com>
Cc: LAK <linux-arm-kernel@lists.infradead.org>,
dlos <davinci-linux-open-source@linux.davincidsp.com>,
<linux-kernel@vger.kernel.org>,
Manjunath Hadli <manjunath.hadli@ti.com>
Subject: Re: [PATCH v3 0/2] ARM: davinci: da850/omap-l138: add support for VPIF driver
Date: Wed, 3 Oct 2012 13:47:58 +0530 [thread overview]
Message-ID: <506BF4B6.8090701@ti.com> (raw)
In-Reply-To: <1347344709-6180-1-git-send-email-prabhakar.lad@ti.com>
Hi Prabhakar,
On 9/11/2012 11:55 AM, Prabhakar Lad wrote:
> 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 v3:
> 1: Clubbed the code for DA850_UI_SD_VIDEO_PORT config
> as pointed by Sekhar.
> 2: Define the resource structure outside the function as pointed
> by Sekhar.
>
> 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
>
> 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 | 7 ++
> arch/arm/mach-davinci/board-da850-evm.c | 156 ++++++++++++++++++++++++++++
> arch/arm/mach-davinci/da850.c | 152 +++++++++++++++++++++++++++
> 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, 369 insertions(+), 0 deletions(-)
The patches look good to me. In case you want to queue them through the
media tree to manage the dependencies, feel free to add my:
Acked-by: Sekhar Nori <nsekhar@ti.com>
Note that the subject like prefix for DA850 soc patches should be
"ARM: davinci: da850: .."
and that for DA850 EVM patches should be:
"ARM: davinci: da850 evm: .."
instead of what you have used here. Please fix these if you are queuing
them and take care of this in future.
Thanks,
Sekhar
next prev parent reply other threads:[~2012-10-03 8:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-11 6:25 [PATCH v3 0/2] ARM: davinci: da850/omap-l138: add support for VPIF driver Prabhakar Lad
2012-09-11 6:25 ` Prabhakar Lad
2012-09-11 6:25 ` [PATCH v3 1/2] ARM: da850/omap-l138: Add SoC related definitions for VPIF Prabhakar Lad
2012-09-11 6:25 ` Prabhakar Lad
2012-09-11 6:25 ` [PATCH v3 2/2] ARM: da850/omap-l138: Add EVM specific code for VPIF to work Prabhakar Lad
2012-09-11 6:25 ` Prabhakar Lad
2012-10-03 8:17 ` Sekhar Nori [this message]
2012-10-03 8:17 ` [PATCH v3 0/2] ARM: davinci: da850/omap-l138: add support for VPIF driver Sekhar Nori
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=506BF4B6.8090701@ti.com \
--to=nsekhar@ti.com \
--cc=linux-arm-kernel@lists.infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.