From: Jarkko Nikula <jhnikula@gmail.com>
To: Bob Liu <lliubbo@gmail.com>
Cc: linux-omap@vger.kernel.org, broonie@opensource.wolfsonmicro.com,
lrg@slimlogic.co.uk, lars@metafoo.de, paul@pwsan.com,
peter.ujfalusi@nokia.com
Subject: Re: [HELP] Audio on BeagleBoard xM can't work
Date: Tue, 15 Mar 2011 11:53:15 +0200 [thread overview]
Message-ID: <20110315115315.bcd2451b.jhnikula@gmail.com> (raw)
In-Reply-To: <AANLkTikMCttrVTS==b2j9VyvSSz+WzoBg8dZ-nb4QUaN@mail.gmail.com>
On Tue, 15 Mar 2011 11:12:17 +0800
Bob Liu <lliubbo@gmail.com> 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".
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.
--
Jarkko
next prev parent reply other threads:[~2011-03-15 9:51 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-15 3:12 [HELP] Audio on BeagleBoard xM can't work Bob Liu
2011-03-15 9:53 ` Jarkko Nikula [this message]
2011-03-15 9:57 ` Bob Liu
2011-03-15 16:21 ` Premi, Sanjeev
2011-03-16 3:39 ` Bob Liu
2011-03-16 5:31 ` ABRAHAM, KISHON VIJAY
2011-03-16 5:45 ` Bob Liu
2011-03-16 7:40 ` Peter Ujfalusi
2011-03-16 9:27 ` Bob Liu
2011-03-16 10:42 ` Peter Ujfalusi
2011-03-16 10:52 ` Bob Liu
2011-03-16 11:29 ` Peter Ujfalusi
2011-03-16 6:59 ` Premi, Sanjeev
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20110315115315.bcd2451b.jhnikula@gmail.com \
--to=jhnikula@gmail.com \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=lars@metafoo.de \
--cc=linux-omap@vger.kernel.org \
--cc=lliubbo@gmail.com \
--cc=lrg@slimlogic.co.uk \
--cc=paul@pwsan.com \
--cc=peter.ujfalusi@nokia.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox