From: Mark Brown <broonie@kernel.org>
To: Takashi Iwai <tiwai@suse.de>
Cc: Liam Girdwood <liam.r.girdwood@linux.intel.com>,
"alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Nenghua Cao <nhcao@marvell.com>
Subject: Re: [alsa-devel] [PATCH] ASoC: dpcm: don't do hw_param when BE has done hw_param
Date: Sat, 11 Jan 2014 12:08:26 +0000 [thread overview]
Message-ID: <20140111120826.GS29039@sirena.org.uk> (raw)
In-Reply-To: <s5hzjn2n9ne.wl%tiwai@suse.de>
[-- Attachment #1: Type: text/plain, Size: 706 bytes --]
On Sat, Jan 11, 2014 at 10:35:33AM +0100, Takashi Iwai wrote:
> But, the point is that basically we already know that something is
> wrong at the point BE2 setting up an incompatible hw_params; then it
> should be notified properly to FE1, or the incompatible change must be
> handled as an error. This is the missing piece in the current
> implementation. The skip of redundant BE hw_params call can be
> implemented as an optimization in this compatibility check, too.
Only in the case where they actually are incompatible though - if
there's DSP in place which can do suitable mixing it's not an issue.
At the minute the core is relying on the drivers handling any limits
just like with the CODECs.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2014-01-11 12:08 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-10 5:36 [PATCH] ASoC: dpcm: don't do hw_param when BE has done hw_param Nenghua Cao
2014-01-10 10:55 ` [alsa-devel] " Takashi Iwai
2014-01-10 11:21 ` Nenghua Cao
2014-01-10 11:47 ` [alsa-devel] " Liam Girdwood
2014-01-10 11:59 ` Nenghua Cao
2014-01-10 12:01 ` Takashi Iwai
2014-01-10 12:22 ` Nenghua Cao
2014-01-10 13:34 ` [alsa-devel] " Takashi Iwai
2014-01-10 12:29 ` Liam Girdwood
2014-01-10 12:51 ` Nenghua Cao
2014-01-10 13:46 ` [alsa-devel] " Takashi Iwai
2014-01-10 18:43 ` Liam Girdwood
2014-01-11 9:35 ` Takashi Iwai
2014-01-11 12:08 ` Mark Brown [this message]
2014-01-13 10:48 ` [alsa-devel] " Liam Girdwood
2014-01-13 10:57 ` Takashi Iwai
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=20140111120826.GS29039@sirena.org.uk \
--to=broonie@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=liam.r.girdwood@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nhcao@marvell.com \
--cc=tiwai@suse.de \
/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