RE: [alsa-devel] [PATCH v3 5/6] ARM: DaVinci: ASoC: Add mcasp support for DM646x

2009-06-04 Thread chaithrika
On Wed, Jun 03, 2009 at 17:42:37, Mark Brown wrote: On Wed, Jun 03, 2009 at 04:33:51PM +0530, chaithrika wrote: Why is the McASP driver using platform data called 'evm_snd_patform_data'? This suggests that there's some abstraction problem with the separation between the machine and

RE: [alsa-devel] [PATCH v3 5/6] ARM: DaVinci: ASoC: Add mcasp support for DM646x

2009-06-03 Thread chaithrika
Mark, +static int davinci_i2s_mcasp_probe(struct platform_device *pdev) +{ + struct evm_snd_platform_data *parray = pdev-dev.platform_data; + struct davinci_pcm_dma_params *dma_data; + struct resource *mem, *ioarea, *res; + struct evm_snd_platform_data *pdata; Why is the

RE: [alsa-devel] [PATCH v3 5/6] ARM: DaVinci: ASoC: Add mcasp support for DM646x

2009-06-01 Thread chaithrika
: [alsa-devel] [PATCH v3 5/6] ARM: DaVinci: ASoC: Add mcasp support for DM646x On Thu, May 28, 2009 at 05:11:08AM -0400, Chaithrika U S wrote: The codec on the DM646x EVM is AIC32 which is connected to Serializer0 and Serializer1 of McASP0. The McASP0 consists of transmit and receive sections