> -----Original Message----- > From: linux-omap-owner@xxxxxxxxxxxxxxx > [mailto:linux-omap-owner@xxxxxxxxxxxxxxx] On Behalf Of Bob Liu > Sent: Tuesday, March 15, 2011 3:27 PM > To: Jarkko Nikula > Cc: linux-omap@xxxxxxxxxxxxxxx; > broonie@xxxxxxxxxxxxxxxxxxxxxxxxxxx; lrg@xxxxxxxxxxxxxxx; > lars@xxxxxxxxxx; paul@xxxxxxxxx; peter.ujfalusi@xxxxxxxxx > Subject: Re: [HELP] Audio on BeagleBoard xM can't work > > On Tue, Mar 15, 2011 at 5:53 PM, Jarkko Nikula > <jhnikula@xxxxxxxxx> wrote: > > On Tue, 15 Mar 2011 11:12:17 +0800 > > Bob Liu <lliubbo@xxxxxxxxx> wrote: > > > >> It seems that the code in sound/soc/omap/omap-mcbsp.c uses > the function > >> "cpu-is-omap343x()" which fails and returns ENODEV. > >> > >> But I have enabled "OMAP3430 support" in "System Type" / > "TI OMAP2/3/4 > >> Specific Features", > >> why it still return ENODEV? (Attached my kernel config). > >> > >> And after I changed that check to "cpu-is-omap34xx()", there was no > >> error message but neither any audio output, > >> I can't hear any sound. > >> ---------------------------- > > > > Is the DMA running after you change the cpu_is_omap34xx and > try to play > > e.g. "aplay /dev/urandom"? If audio is running you should see DMA > > interrupt count increasing with "grep DMA /proc/interrupts". > > > > Yes, DMA interrupt count increased after aplay /dev/urandom or some > other audio file. > Thanks > > > If that is working then issue could be in codec side. I don't have a > > beagle at the moment to verify but IRCC something like ~10 > TWL4030 ALSA > > controls must be adjusted in order to route audio from DAC > to outputs > > at proper volume. I don't have HW with me right now, can you try the following? (Got the steps over phone from Abhilash) 1) run command "alsamixer" 2) Un-mute by pressing the key "m" 3) Play the audio using aplay If it doesn't work, you may want to check the options used by alsamixer. I will be able to try it myself tomorrow morning. ~sanjeev > > > > -- > Regards, > --Bob > -- > To unsubscribe from this list: send the line "unsubscribe > linux-omap" in > the body of a message to majordomo@xxxxxxxxxxxxxxx > More majordomo info at http://vger.kernel.org/majordomo-info.html > -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
