The documentation is spilt into the following sections: ALSA SoC Layer Overview · ASoC Design · ASoC Codec Class Driver · ASoC Codec driver breakdown. ASoC. ASoC, ALSA System on Chip: is a Linux kernel subsystem created to provide better. ALSA support for system-on-chip and portable audio codecs. Need to edit the board’s file that defines platform devices. I needed to modify arch /arm/mach-lpc32xx/eac: Add this: /* * Platform Data for UDA
|Published (Last):||4 June 2017|
|PDF File Size:||15.93 Mb|
|ePub File Size:||4.31 Mb|
|Price:||Free* [*Free Regsitration Required]|
The board I am testing with is the Embedded Artists V2 development board. There is also a different development board, called Phytecwhich contains the same UDA codec chip.
I have verified the chip is powered up, and I can communicate to it by using the I2C-tools package.
Advanced Linux Sound Architecture (ALSA)
It responds to i2cdetect and I can read registers from the xlsa correctly using i2cget. I needed to edit the Phytec driver files to change the address of the codec chip.
I edited this section of lpc3xxx-uda After I made this change, I went ahead and built the system again and everything compiled OK. I am unable to detect the soundcard.
linux kernel – Configuring I2C and I2S in ALSA ASoC – Stack Overflow
Does this mean I must now make a new device called udacodec assoc address 0x1a and bind it to a driver? I have tried doing the following: Instantiated device udacodec at 0x1a Then I try to bind a driver to the device: No such device I get this error for everything I try!
I have a feeling I am not creating the device correctly, and then I’m not sure how to bind it to the correct driver. I was playing with this last night and was somehow able to get ASoC to wake up and at least probe for the card. I was playing with different bindings, I guess. It was late and hard to remember my steps, but I was able to at least get the following error somehow:.
I’ve confirmed my modified code is being compiled, so the driver should be talking to the correct address now.
It was late and hard to remember my steps, but I was able to at least get the following error somehow: After manually loading the modules, the output of lsmod is: And my device table: You should read the ASoC documentation, and then ask on the alsa-devel list where you will be told that 2. Dec 26 ’12 at I posted to alsa-devel and nobody responded. That I can tell – I hate mail-lists, they are the worst to read through.
Here I go again, on my own Sign up or log in Sign up using Google. Sign up using Facebook. Sign up using Email and Password. Post as a guest Name.