Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Lars-Peter Clausen <lars@metafoo.de>
Cc: Liam Girdwood <liam.r.girdwood@linux.intel.com>,
	Charles Keepax <ckeepax@opensource.wolfsonmicro.com>,
	Richard Fitzgerald <rf@opensource.wolfsonmicro.com>,
	Sergey Kiselev <sergey.kiselev@intel.com>,
	alsa-devel@alsa-project.org
Subject: Re: wm8731 - redundant register initialization, stream name vs DAPM widgets, snd_soc_io to regmap_io conversion
Date: Tue, 9 Jun 2015 19:31:28 +0100	[thread overview]
Message-ID: <20150609183128.GX14071@sirena.org.uk> (raw)
In-Reply-To: <55772F7B.8020709@metafoo.de>


[-- Attachment #1.1: Type: text/plain, Size: 797 bytes --]

On Tue, Jun 09, 2015 at 08:24:59PM +0200, Lars-Peter Clausen wrote:
> On 06/08/2015 11:51 AM, Charles Keepax wrote:

> >The documentation is fairly out of date here I think and even so
> >it decidely implies a substring match looking at the examples it
> >gives. I might defer to Mark or Lars for the definitive answer on
> >this one.

> It looks as if the code itself always used substring matching.

Yes, that's the case - we've always relied on that.

> These days the preferred method for connecting the stream is to directly
> connect the widget that is created for the stream by the core directly in
> the DAPM route table to the DAC/ADC widget rather than setting the stream
> name.

Indeed, that's the appropriate fix if there are any problems (and a
useful cleanup even if there aren't).

[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 473 bytes --]

[-- Attachment #2: Type: text/plain, Size: 0 bytes --]



      reply	other threads:[~2015-06-09 18:31 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-05 19:27 wm8731 - redundant register initialization, stream name vs DAPM widgets, snd_soc_io to regmap_io conversion Sergey Kiselev
2015-06-08  9:51 ` Charles Keepax
2015-06-09 18:24   ` Lars-Peter Clausen
2015-06-09 18:31     ` 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=20150609183128.GX14071@sirena.org.uk \
    --to=broonie@kernel.org \
    --cc=alsa-devel@alsa-project.org \
    --cc=ckeepax@opensource.wolfsonmicro.com \
    --cc=lars@metafoo.de \
    --cc=liam.r.girdwood@linux.intel.com \
    --cc=rf@opensource.wolfsonmicro.com \
    --cc=sergey.kiselev@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