From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Jarkko Nikula <jhnikula@gmail.com>
Cc: alsa-devel@alsa-project.org, patches@opensource.wolfsonmicro.com,
Liam Girdwood <lrg@slimlogic.co.uk>
Subject: Re: [PATCH 2.6.37 1/2] ASoC: Fix dapm_seq_compare() for multi-component
Date: Fri, 12 Nov 2010 19:10:45 +0000 [thread overview]
Message-ID: <20101112191045.GH17283@rakim.wolfsonmicro.main> (raw)
In-Reply-To: <20101112210637.0ec2d25c.jhnikula@gmail.com>
On Fri, Nov 12, 2010 at 09:06:37PM +0200, Jarkko Nikula wrote:
> This sounds feasible change. What I was thinking are there any
> benefit which one, the register or codec is compared first but I don't
> think there's any practical difference.
> A1, B1, A2, B2 (now)
> or
> A1, A2, B1, B2 (codec comparison before register)
If you've got two identical CODECs it will *probably* sound smoother to
alternate between the two rather than enabling one then the other -
there will be less time difference between any audible issues in each
path. Probably a very small chance of that having an effect but it
seemed more likely to do something useful than any other scenario.
prev parent reply other threads:[~2010-11-12 19:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-12 16:01 [PATCH 2.6.37 1/2] ASoC: Fix dapm_seq_compare() for multi-component Mark Brown
2010-11-12 16:01 ` [PATCH 2/2] ASoC: Use DAPM context rather than CODEC when constructing sequences Mark Brown
2010-11-12 19:06 ` Jarkko Nikula
2010-11-15 13:10 ` Liam Girdwood
2010-11-12 19:06 ` [PATCH 2.6.37 1/2] ASoC: Fix dapm_seq_compare() for multi-component Jarkko Nikula
2010-11-12 19:10 ` 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=20101112191045.GH17283@rakim.wolfsonmicro.main \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=jhnikula@gmail.com \
--cc=lrg@slimlogic.co.uk \
--cc=patches@opensource.wolfsonmicro.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.