All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lars-Peter Clausen <lars@metafoo.de>
To: Jarkko Nikula <jarkko.nikula@bitmer.com>,
	Peter Ujfalusi <peter.ujfalusi@ti.com>,
	Mark Brown <broonie@kernel.org>
Cc: alsa-devel@alsa-project.org, Liam Girdwood <lgirdwood@gmail.com>,
	pavel@ucw.cz
Subject: Re: [PATCH] ASoC: rx51: Correct DAPM route for capture
Date: Mon, 02 Feb 2015 18:13:01 +0100	[thread overview]
Message-ID: <54CFB01D.7080908@metafoo.de> (raw)
In-Reply-To: <54CBCE44.6040907@bitmer.com>

On 01/30/2015 07:32 PM, Jarkko Nikula wrote:
[...]
> Here's additional data. Without this patch there are these errors below
> when registering the card:
>
> [    8.804626] rx51-audio n900-audio: Connecting non-supply widget to
> supply widget is not supported (DMic -> Mic Bias)
> [    8.815795] rx51-audio n900-audio: ASoC: no dapm match for DMic -->
> (null) --> Mic Bias
> [    8.824249] rx51-audio n900-audio: ASoC: Failed to add route DMic ->
> direct -> Mic Bias
> [    8.832763] rx51-audio n900-audio: Connecting non-supply widget to
> supply widget is not supported (HS Mic -> b Mic Bias)
> [    8.844238] rx51-audio n900-audio: ASoC: no dapm match for HS Mic -->
> (null) --> b Mic Bias
> [    8.853057] rx51-audio n900-audio: ASoC: Failed to add route HS Mic
> -> direct -> b Mic Bias
>
> This don't happen on v3.18 so in that sense Peter's patch is kind of
> half-regression fix for v3.19.

What's new in v3.19 is that the kernel will shout if it encounters such a 
invalid route, previously it was just silently ignored. But either way it 
never actually worked, so it's not really a v3.19 regression.

- Lars

  reply	other threads:[~2015-02-02 17:13 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-30  7:32 [PATCH] ASoC: rx51: Correct DAPM route for capture Peter Ujfalusi
2015-01-30 18:32 ` Jarkko Nikula
2015-02-02 17:13   ` Lars-Peter Clausen [this message]
2015-02-02 19:29     ` Jarkko Nikula

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=54CFB01D.7080908@metafoo.de \
    --to=lars@metafoo.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@kernel.org \
    --cc=jarkko.nikula@bitmer.com \
    --cc=lgirdwood@gmail.com \
    --cc=pavel@ucw.cz \
    --cc=peter.ujfalusi@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 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.