Thanks I will check out what I did on the A10 board. I did notice some differences in sunxi-i2sdma.c There are some if CONFIG_ARCH_SUN4I || CONFIG_ARCH_SUN5I that don't include the CONFIG_ARCH_SUN7I. And if I include CONFIG_ARCH_SUN7I I get errors So I will follow that back.
I am trying to play to an external I2S DAC, but that should not matter, because there is no feedback from the DAC. I will probably just disconnect it and hook up my scope, Dennis On Wednesday, April 9, 2014 12:51:56 PM UTC-6, CodeKipper wrote: > > > > > On 9 April 2014 20:28, Dennis Kerrisk <denni...@gmail.com <javascript:>>wrote: > >> I am also getting dma trigger messages in the log: >> [15379.941504] [IIS] dma trigger start >> [15379.948491] [IIS] 0x01c22400+0x24 = 0x0, line= 235 >> [15389.952592] [IIS] dma trigger stop >> >> >> >> On Wednesday, April 9, 2014 12:05:39 PM UTC-6, Dennis Kerrisk wrote: >>> >>> I now have the I2S showing up in ALSA, but when I try to play to it I >>> get: >>> oot@OlimexWork:~# aplay -D hw:1,0 /usr/src/y.wav >>> Playing WAVE '/usr/src/y.wav' : Signed 16 bit Little Endian, Rate 44100 >>> Hz, Stereo >>> aplay: pcm_write:1710: write error: Input/output error >>> >>> >>> Here are the outputs from aplay -l and -L >>> root@OlimexWork:~# aplay -L >>> null >>> Discard all samples (playback) or generate zero samples (capture) >>> sysdefault:CARD=sunxicodec >>> sunxi-CODEC, sunxi PCM >>> Default Audio Device >>> sysdefault:CARD=sunxisndi2s >>> sunxi-sndi2s, >>> Default Audio Device >>> >> > Hi Dennis, > It is probably worth retracing your steps on the A10 board. What are you > connecting to? > and how are you configuring it? I think you're entering uncharted > territory so it would be > nice to get the overall picture. You will need to add some debugging to > the triggering functions > to ensure they are being called and would also be wise to get a snap shot > of the register > values before playback/capture occurs. > I've no linux experience with i2s but I would be under the impression that > you would be > interfacing to a codec driver (loads of which live under sound/soc/codecs) > and that will > have to be a glue layer between that and the i2s driver. > If anybody else has soon i2s experience of the A10 or linux then please > share, > CK > >> >>> >>> root@OlimexWork:~# aplay -l >>> **** List of PLAYBACK Hardware Devices **** >>> card 0: sunxicodec [sunxi-CODEC], device 0: M1 PCM [sunxi PCM] >>> Subdevices: 1/1 >>> Subdevice #0: subdevice #0 >>> card 1: sunxisndi2s [sunxi-sndi2s], device 0: SUNXI-I2S sndi2s-0 [] >>> Subdevices: 1/1 >>> Subdevice #0: subdevice #0 >>> >>> >>> What could I be missing or not have set up correctly? >>> >>> Dennis >>> >> -- >> You received this message because you are subscribed to the Google Groups >> "linux-sunxi" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to linux-sunxi...@googlegroups.com <javascript:>. >> For more options, visit https://groups.google.com/d/optout. >> > > -- You received this message because you are subscribed to the Google Groups "linux-sunxi" group. To unsubscribe from this group and stop receiving emails from it, send an email to linux-sunxi+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
