From: Mark Brown <broonie@kernel.org>
To: Benoit Cousson <bcousson@baylibre.com>
Cc: alsa-devel@alsa-project.org, lars@metafoo.de,
lgirdwood@gmail.com, Misael Lopez Cruz <misael.lopez@ti.com>
Subject: Re: [RFC] ASoC: core: Add support for DAI multicodec
Date: Thu, 13 Mar 2014 19:22:30 +0000 [thread overview]
Message-ID: <20140313192230.GJ366@sirena.org.uk> (raw)
In-Reply-To: <53219AA3.2060305@baylibre.com>
[-- Attachment #1.1: Type: text/plain, Size: 1103 bytes --]
On Thu, Mar 13, 2014 at 12:46:43PM +0100, Benoit Cousson wrote:
> On 12/03/2014 23:51, Mark Brown wrote:
> >On Tue, Mar 11, 2014 at 12:17:24PM +0100, Benoit Cousson wrote:
> >is handy. Instead of having a fixup function if we specified a TDM
> >and channel map configuration then the core core could override the
> >params so that the channel count was clamped by how many channels are
> >actually being sent to the device - so if there's two TDM slots active
> >the device would be told to play stereo. Would that work for your use
> >cases?
> Yes, I think so. My current setup is pretty basic: 2 mono Class D amplifiers
> connected to the same I2S link to build a stereo card.
> OK, so I'll rebase the patch to asoc/next. I'll try to split the huge patch
> at least into a series of 2 or 3 patches, and I'll remove the fixup part.
Sounds good. We will need some configuration here so I think adding TDM
parameters to the various structs (I guess slot size and overall counts
should go in the link rather than per CODEC) but we could probably even
get away with doing this after the core patch.
[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
prev parent reply other threads:[~2014-03-13 19:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-11 11:17 [RFC] ASoC: core: Add support for DAI multicodec Benoit Cousson
2014-03-12 0:28 ` Mark Brown
2014-03-13 10:42 ` Benoit Cousson
2014-03-12 22:51 ` Mark Brown
2014-03-13 11:46 ` Benoit Cousson
2014-03-13 19:22 ` Mark Brown [this message]
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=20140313192230.GJ366@sirena.org.uk \
--to=broonie@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=bcousson@baylibre.com \
--cc=lars@metafoo.de \
--cc=lgirdwood@gmail.com \
--cc=misael.lopez@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