Actions
Forum Thread Details
  • State Not Answered
  • Replies 17 replies
  • Subscribers 355 subscribers
  • Views 2189 views
  • Users 0 members are here
Related

I2S Audio linux reference design

metinburak_

Hi,

Could somebody found an I2S (not HDMI) reference design and kernel w driver for the onboard audio codec adau1761 for linux?
The analog devices reference design's design tree source comments out the I2S device. Digilent reference design uses the HDMI device and the xillybus reference design is buggy that, rebooting make the onboard sound codec randomly out of order.

Is there someone using the I2S audio codec with Linux without problem?

Thanks in advance.

Parents
  • 0

    Hi,

    I can't see any reason why zedboard_sound_setup.pl would fail. If this repeats itself, please detail exactly what you did.

    I would suggest removing all pulseaudio related files in the rc.d subdirectories (i.e. S50pulseaudio and such). I'm under the impression that they aren't executed anyhow, and if they are, it's not helpful. It's the upstart script that should bring up the sound interface.

    Also, if you choose to manually start pulseaudio, I'd suggest removing the upstart file as well, rather than killing pulseaudio. Even though I have quite some experience with killing that process (on my desktop in particular) I'm not sure it's good practice for a production system.

    As a side note, I'd point out that you can use

    pacmd list-sinks

    to tell if Pulseaudio detected Xillybus audio. So it's possible to write a little shell script that checks if everything is fine, and if not, restart pulseaudio and try again (hopefully with a short sleep and maybe a count limit to prevent this from going crazy). Not the most elegant solution, but if everything else fails...

Reply
  • 0

    Hi,

    I can't see any reason why zedboard_sound_setup.pl would fail. If this repeats itself, please detail exactly what you did.

    I would suggest removing all pulseaudio related files in the rc.d subdirectories (i.e. S50pulseaudio and such). I'm under the impression that they aren't executed anyhow, and if they are, it's not helpful. It's the upstart script that should bring up the sound interface.

    Also, if you choose to manually start pulseaudio, I'd suggest removing the upstart file as well, rather than killing pulseaudio. Even though I have quite some experience with killing that process (on my desktop in particular) I'm not sure it's good practice for a production system.

    As a side note, I'd point out that you can use

    pacmd list-sinks

    to tell if Pulseaudio detected Xillybus audio. So it's possible to write a little shell script that checks if everything is fine, and if not, restart pulseaudio and try again (hopefully with a short sleep and maybe a count limit to prevent this from going crazy). Not the most elegant solution, but if everything else fails...

Children
No Data