[PATCH v4] da8xx-fb: allow frame to complete after disabling LCDC

2012-08-22 Thread Manjunathappa, Prakash
Wait for active frame transfer to complete after disabling LCDC. At the same this wait is not be required when there are sync and underflow errors. Patch applies for revision 2 of LCDC present am335x. More information on disable and reset sequence can be found in section 13.4.6 of AM335x TRM

RE: [PATCH 1/5] ASoC/ARM: Davinci: McASP: split asp header into platform and audio specific

2012-08-22 Thread Hebbar, Gururaja
On Fri, Aug 17, 2012 at 23:43:44, Nori, Sekhar wrote: Hi Gururaja, On 8/14/2012 6:12 PM, Hebbar, Gururaja wrote: Davinci McASP header driver are shared by few OMAP platforms (like TI81xx, AM335x). Splitting asp header into Davinci platform specific header and Audio specific header helps

RE: [PATCH v4] da8xx-fb: allow frame to complete after disabling LCDC

2012-08-22 Thread Manjunathappa, Prakash
Hi, On Wed, Aug 22, 2012 at 11:28:23, Manjunathappa, Prakash wrote: Wait for active frame transfer to complete after disabling LCDC. At the same this wait is not be required when there are sync and underflow errors. Patch applies for revision 2 of LCDC present am335x. More information on

Re: [PATCH] [media] davinci: vpfe: Add documentation

2012-08-22 Thread Manjunath Hadli
Hi Sakari, On Thursday 16 August 2012 09:53 PM, Sakari Ailus wrote: Hi Manju, On Thu, Aug 09, 2012 at 09:13:52AM +0530, Manjunath Hadli wrote: Hi Sakari, Thank you for the comments. Thanks for the graphs! On Thursday 02 August 2012 05:37 AM, Sakari Ailus wrote: Hi Manju, Thanks

RE: [PATCH 5/5] ASoC: tlv320aic3x: Add device tree bindings

2012-08-22 Thread Hebbar, Gururaja
On Sat, Aug 18, 2012 at 04:15:13, Mark Brown wrote: On Tue, Aug 14, 2012 at 06:12:05PM +0530, Hebbar, Gururaja wrote: +- gpio-reset - int - gpio pin number used for codec reset This should be a standard DT GPIO reference by phandle like: gpio = gpio1 16 0; I will correct in V2

RE: [PATCH 4/5] ASoC: Davinci: machine: Add device tree binding

2012-08-22 Thread Hebbar, Gururaja
On Sat, Aug 18, 2012 at 04:13:28, Mark Brown wrote: On Tue, Aug 14, 2012 at 06:12:04PM +0530, Hebbar, Gururaja wrote: +- ti,codec-clock : The Codec Clock from the board I think this is the clock rate? Please specify it more specifically. I will correct it in v2. +CODEC DAI Name,

Re: Power management is possible in dm355

2012-08-22 Thread venkatasubramanian P
Dear sir, Dm 355 is only for indoor application ?.The device capturing picture in indoor correctly.If i put it in the sun the image is completely washed out?. On 18 August 2012 12:06, venkatasubramanian P venkates...@avench.comwrote: Dear sir, Thank for your help

RE: [PATCH 1/5] ASoC/ARM: Davinci: McASP: split asp header into platform and audio specific

2012-08-22 Thread Hebbar, Gururaja
On Sat, Aug 18, 2012 at 04:03:58, Mark Brown wrote: On Tue, Aug 14, 2012 at 06:12:01PM +0530, Hebbar, Gururaja wrote: Davinci McASP header driver are shared by few OMAP platforms (like TI81xx, AM335x). Splitting asp header into Davinci platform specific header and Audio specific header

RE: [PATCH 3/5] ASoC: Davinci: pcm: Add device tree bindings

2012-08-22 Thread Hebbar, Gururaja
On Sat, Aug 18, 2012 at 04:01:24, Mark Brown wrote: On Tue, Aug 14, 2012 at 06:12:03PM +0530, Hebbar, Gururaja wrote: Device tree support for Davinci/OMAP2+ pcm driver. This looks like it's a device which maps a shared DMA controller in the SoC core into ASoC rather than actual hardware.

Re: [PATCH 3/5] ASoC: Davinci: pcm: Add device tree bindings

2012-08-22 Thread Mark Brown
On Wed, Aug 22, 2012 at 01:50:09PM +, Hebbar, Gururaja wrote: From your for-3.7 branch, I could only find such implementation in Tegra Platform. Most Freescale platforms implements this through a device/driver method. Exception being sound/soc/mxs/mxs-pcm.c So should I follow tegra

Re: [PATCH v2 3/3] spi: spi-davinci: convert to DMA engine API

2012-08-22 Thread Matt Porter
On Wed, Aug 22, 2012 at 09:15:22AM +0530, Vinod Koul wrote: On Tue, 2012-08-21 at 14:43 -0400, Matt Porter wrote: Removes use of the DaVinci EDMA private DMA API and replaces it with use of the DMA engine API. Signed-off-by: Matt Porter mpor...@ti.com --- + struct

Re: [PATCH v2 1/3] dmaengine: add TI EDMA DMA engine driver

2012-08-22 Thread Matt Porter
On Wed, Aug 22, 2012 at 12:37:18PM +, Hebbar, Gururaja wrote: On Wed, Aug 22, 2012 at 00:13:07, Porter, Matt wrote: Add a DMA engine driver for the TI EDMA controller. This driver is implemented as a wrapper around the existing DaVinci private DMA implementation. This approach allows

[PATCH v3 0/3] DaVinci DMA engine conversion

2012-08-22 Thread Matt Porter
Changes since v1: - Add virt-dma support. Better error checks and simplified descriptor handling. - Fix support for multiple EDMA controllers Tested on AM18x EVM with WL12xx on MMC1 Changes since v2: - Set default Kconfig state to off - Fix

[PATCH v3 1/3] dmaengine: add TI EDMA DMA engine driver

2012-08-22 Thread Matt Porter
Add a DMA engine driver for the TI EDMA controller. This driver is implemented as a wrapper around the existing DaVinci private DMA implementation. This approach allows for incremental conversion of each peripheral driver to the DMA engine API. The EDMA driver supports slave transfers but does not

[PATCH v3 2/3] mmc: davinci_mmc: convert to DMA engine API

2012-08-22 Thread Matt Porter
Removes use of the DaVinci EDMA private DMA API and replaces it with use of the DMA engine API. Signed-off-by: Matt Porter mpor...@ti.com --- drivers/mmc/host/davinci_mmc.c | 271 1 file changed, 82 insertions(+), 189 deletions(-) diff --git

[PATCH v3 3/3] spi: spi-davinci: convert to DMA engine API

2012-08-22 Thread Matt Porter
Removes use of the DaVinci EDMA private DMA API and replaces it with use of the DMA engine API. Signed-off-by: Matt Porter mpor...@ti.com --- drivers/spi/spi-davinci.c | 292 - 1 file changed, 130 insertions(+), 162 deletions(-) diff --git

RE: [PATCH 3/5] ASoC: Davinci: pcm: Add device tree bindings

2012-08-22 Thread Hebbar, Gururaja
On Wed, Aug 22, 2012 at 21:28:08, Mark Brown wrote: On Wed, Aug 22, 2012 at 01:50:09PM +, Hebbar, Gururaja wrote: From your for-3.7 branch, I could only find such implementation in Tegra Platform. Most Freescale platforms implements this through a device/driver method. Exception