From: Liam Girdwood <lrg@ti.com>
To: alsa-devel@alsa-project.org
Cc: Mark Brown <broonie@opensource.wolfsonmicro.com>
Subject: Re: Store codec capabilites in alsa
Date: Fri, 26 Oct 2012 11:45:47 +0100 [thread overview]
Message-ID: <508A69DB.7030009@ti.com> (raw)
In-Reply-To: <000001cdb31e$9a76a530$cf63ef90$@codeaurora.org>
On 26/10/12 03:07, Bharath Ramachandramurthy wrote:
> Hello
>
>
>
> Is there a mechanism for the codec driver to register the codec
> capabilities to the ALSA framework ?
>
>
The codec DAI driver does register some of it's capabilities with the core.
>
> The BE CPU dai driver can then read the capabilities of the codec and talk
> to the DSP.
>
>
You should be able to do this by looking at the RTD codec->driver pointer to get supported rates, formats and channels.
Regards
Liam
next prev parent reply other threads:[~2012-10-26 10:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-26 2:07 Store codec capabilites in alsa Bharath Ramachandramurthy
2012-10-26 10:45 ` Liam Girdwood [this message]
2012-10-29 1:13 ` Patrick Lai
2012-10-29 17:07 ` Mark Brown
2012-10-30 3:23 ` Patrick Lai
2012-10-30 15:13 ` Mark Brown
2012-10-30 18:18 ` Patrick Lai
2012-10-30 18:42 ` Mark Brown
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=508A69DB.7030009@ti.com \
--to=lrg@ti.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@opensource.wolfsonmicro.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;
as well as URLs for NNTP newsgroup(s).