From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: "Koul, Vinod" <vinod.koul@intel.com>
Cc: "tiwai@suse.de" <tiwai@suse.de>,
"alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
"alan@linux.intel.com" <alan@linux.intel.com>,
"Harsha, Priya" <priya.harsha@intel.com>,
"lrg@slimlogic.co.uk" <lrg@slimlogic.co.uk>
Subject: Re: [PATCH 1/4] ASoC sst v2: Add sn95031 codec driver
Date: Thu, 6 Jan 2011 13:45:41 +0000 [thread overview]
Message-ID: <20110106134540.GA6328@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <438BB0150E931F4B9CE701519A44630104C119C32E@bgsmsx502.gar.corp.intel.com>
On Thu, Jan 06, 2011 at 12:17:04PM +0530, Koul, Vinod wrote:
> > > + /* PCM interface config
> > > + * This sets the pcm rx slot conguration to max 6 slots
> > > + * for max 4 dais (2 stereo and 2 mono)
> > > + */
> > This stuff should all be dynamically configured at runtime - the clocks
> > should be being managed with set_sysclk() and the slot configuration
> > with the TDM API or dynamic routing depending on what the actual control
> > is.
> Since we have single PCM port and TDM slots. For all DAIs it needs to be single
> configuration and not changed while one is running.
It's a big jump to go from not being able to configure while active to
hard coding within the CODEC driver - machine drivers should be able to
change this sort of thing during initialisation, and ideally also
dynamically where possible (for example, only while there are no active
audio streams).
next prev parent reply other threads:[~2011-01-06 13:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-04 14:46 [PATCH 1/4] ASoC sst v2: Add sn95031 codec driver Koul, Vinod
2011-01-05 23:56 ` Mark Brown
2011-01-06 6:47 ` Koul, Vinod
2011-01-06 13:45 ` Mark Brown [this message]
2011-01-09 11:30 ` Liam Girdwood
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=20110106134540.GA6328@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alan@linux.intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=lrg@slimlogic.co.uk \
--cc=priya.harsha@intel.com \
--cc=tiwai@suse.de \
--cc=vinod.koul@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.