From: Miguel Aguilar <miguel.aguilar@ridgerun.com>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: davinci-linux-open-source@linux.davincidsp.com,
clark.becker@ridgerun.com, santiago.nunez@ridgerun.com, "Nori,
Sekhar" <nsekhar@ti.com>,
diego.dompe@ridgerun.com, alsa-devel@alsa-project.org,
"Narnakaje, Snehaprabha" <nsnehaprabha@ti.com>,
todd.fischer@ridgerun.com
Subject: Re: [PATCH 2/2] Davinci: DM365: Enable DaVinci Voice Codec support for DM365 EVM
Date: Tue, 19 Jan 2010 14:47:16 -0600 [thread overview]
Message-ID: <4B561A54.6070201@ridgerun.com> (raw)
In-Reply-To: <20100111162101.GA26771@rakim.wolfsonmicro.main>
Hi Mark,
I have a specific doubt about the codec_dev element snd_soc_device struct of the
DM365 EVM.
Since I have two codecs on the EVM, I have two snd_soc_codec_device structures:
* AIC3x
struct snd_soc_codec_device soc_codec_dev_aic3x = {
.probe = aic3x_probe,
.remove = aic3x_remove,
.suspend = aic3x_suspend,
.resume = aic3x_resume,
};
* Voice Codec
struct snd_soc_codec_device soc_codec_dev_cq93vc = {
.probe = cq93vc_probe,
.remove = cq93vc_remove,
.suspend = cq93vc_suspend,
.resume = cq93vc_resume,
};
But I can set only one at a time in the dm365_evm_snd_devdata:
/* evm audio subsystem */
static struct snd_soc_device dm365_evm_snd_devdata = {
.card = &dm365_snd_soc_card_evm,
***
.codec_dev = &soc_codec_dev_aic3x,
or
.codec_dev = &soc_codec_dev_cq93vc,
***
.codec_data = &aic3x_setup,
};
So in case what is the proper way to do this?
Thanks,
Miguel Aguilar
next prev parent reply other threads:[~2010-01-19 20:50 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-07 22:17 [PATCH 2/2] Davinci: DM365: Enable DaVinci Voice Codec support for DM365 EVM miguel.aguilar
2010-01-08 11:31 ` Mark Brown
2010-01-08 17:36 ` Miguel Aguilar
2010-01-08 19:37 ` Mark Brown
2010-01-11 15:11 ` Miguel Aguilar
2010-01-11 15:34 ` Mark Brown
2010-01-11 15:53 ` Miguel Aguilar
2010-01-11 16:21 ` Mark Brown
2010-01-19 20:47 ` Miguel Aguilar [this message]
2010-01-19 22:10 ` Mark Brown
2010-01-20 14:32 ` Miguel Aguilar
2010-01-20 15:01 ` Mark Brown
2010-01-11 16:04 ` Kevin Hilman
2010-01-11 16:08 ` Miguel Aguilar
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=4B561A54.6070201@ridgerun.com \
--to=miguel.aguilar@ridgerun.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=clark.becker@ridgerun.com \
--cc=davinci-linux-open-source@linux.davincidsp.com \
--cc=diego.dompe@ridgerun.com \
--cc=nsekhar@ti.com \
--cc=nsnehaprabha@ti.com \
--cc=santiago.nunez@ridgerun.com \
--cc=todd.fischer@ridgerun.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