From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Rajeev kumar <rajeev-dlh.kumar@st.com>
Cc: Vinod Koul <vinod.koul@linux.intel.com>,
"alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
"lrg@slimlogic.co.uk" <lrg@slimlogic.co.uk>
Subject: Re: Exporting playback and capture capability to user space
Date: Tue, 22 Nov 2011 13:08:23 +0000 [thread overview]
Message-ID: <20111122130822.GE21029@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <4ECB24C7.4080908@st.com>
On Tue, Nov 22, 2011 at 09:57:51AM +0530, Rajeev kumar wrote:
>
> static struct snd_soc_dai_driver sta529_dai = {
> .rates = SPEAR_PCM_RATES,
> .formats = SPEAR_PCM_FORMAT,
This looks wrong...
> cpu dai: In case of cpu dai, we are passing the playback and capture
> capability from the platform code and depending on the capability we
> are filling the cpu dai structure in probe function, like
Why are you doing this? Your driver should export the capabilities of
the hardware and let the machine driver pick any specific configuration
that's needed.
next prev parent reply other threads:[~2011-11-22 13:08 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-06 9:34 overrun in case of record Rajeev kumar
2011-09-06 18:01 ` Mark Brown
2011-09-07 4:14 ` Rajeev kumar
2011-09-07 8:35 ` Clemens Ladisch
2011-11-17 13:35 ` Exporting playback and capture capability to user space Rajeev kumar
2011-11-17 15:19 ` Mark Brown
2011-11-21 5:49 ` Rajeev kumar
2011-11-21 6:23 ` Vinod Koul
2011-11-22 4:27 ` Rajeev kumar
2011-11-22 13:08 ` Mark Brown [this message]
2011-11-23 4:36 ` Rajeev kumar
2011-12-02 10:50 ` Rajeev kumar
2011-12-02 11:50 ` Vinod Koul
2012-01-09 6:31 ` Rajeev kumar
2012-01-12 8:45 ` Rajeev kumar
2011-11-21 10:55 ` 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=20111122130822.GE21029@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=lrg@slimlogic.co.uk \
--cc=rajeev-dlh.kumar@st.com \
--cc=vinod.koul@linux.intel.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).