[alsa-devel] Configure a CODEC which has I2C connected to CPU, but no PCM bus connection
I have an embedded device with somewhat unusual configuration: there is a second audio CODEC (Wolfson WM8940) which is connected to the PCM interface of another device (a radio module, which is acting as PCM bus master), so that radio device can do analog audio I/O. So there is no CPU<-->CODEC PCM link, but the CODEC _is_ connected to the CPU's I2C, and the CPU needs to configure the CODEC registers to interface to the radio module.
See the attached diagram which shows a simplified view of the configuration. This configuration came about because both the CPU and the radio module can _only_ operate as PCM bus masters.
I am not sure how I could fit this into the ALSA ASoC architecture. Is the ALSA ASoC driver architecture able to accommodate this scenario? Can I use the WM8940 driver to configure the second CODEC through I2C? Could I simply set up a machine driver that defines a DAI including a pointer to the WM8940 CODEC DAI, but NULL pointer for CPU DAI? Can I set it up so the Wolfson CODEC gains could appear as ALSA mixer widgets?
Regards, Craig McQueen
On Tue, Feb 26, 2013 at 12:01:02AM +0000, Craig McQueen wrote:
Always CC maintainers on posts, if you just mail the list your message is likely to be lost in the noise. Also please fix your MUA to word wrap within paragraphs for legibility.
That's fairly normal - most mobile phones do this. Take a look at the neo1973, speyside or bells drivers for example of such a configuration. You can just connect two CODEC DAIs directly together and either start the audio from the application layer by running through all the steps for streaming except for actually starting DMA like:
http://opensource.wolfsonmicro.com/~gg/bluetooth_pcm.c
does or supply a configuration in the machine driver (if the format is fixed) like speyside and bells do.
participants (2)
-
Craig McQueen -
Mark Brown