From: Patrick Lai <plai@codeaurora.org>
To: Liam Girdwood <lrg@ti.com>
Cc: alsa-devel@alsa-project.org,
Mark Brown <broonie@opensource.wolfsonmicro.com>
Subject: Re: Store codec capabilites in alsa
Date: Sun, 28 Oct 2012 18:13:08 -0700 [thread overview]
Message-ID: <508DD824.3040600@codeaurora.org> (raw)
In-Reply-To: <508A69DB.7030009@ti.com>
On 10/26/2012 3:45 AM, Liam Girdwood wrote:
Hi Liam,
> The codec DAI driver does register some of it's capabilities with the core.
The CODEC Bharath and I are working with has hardware providing
information back to CPU so post processing modules running on CPU can
fine tune things on the CODEC continuously.
So, the information need to exposed to CPU is more than supported rates,
format, and channels but very CODEC specific.
I doubt that ASoC has mechanism for vendor's own CODEC driver to
advertise CODEC specific information. However, we would like to check
ahead of time before coming up with something on our own.
Thanks
Patrick
>
>
>>
>> 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
>
> _______________________________________________
> Alsa-devel mailing list
> Alsa-devel@alsa-project.org
> http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
>
--
Sent by an employee of the Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum.
next prev parent reply other threads:[~2012-10-29 1:13 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
2012-10-29 1:13 ` Patrick Lai [this message]
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=508DD824.3040600@codeaurora.org \
--to=plai@codeaurora.org \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=lrg@ti.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).