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: Charles Keepax <ckeepax@opensource.wolfsonmicro.com>,
	patches@opensource.wolfsonmicro.com, alsa-devel@alsa-project.org,
	lgirdwood@gmail.com
Subject: Re: [PATCH] ASoC: dapm: Replace siggen widget type with mic widgets
Date: Tue, 1 Dec 2015 19:36:13 +0000	[thread overview]
Message-ID: <20151201193613.GP1929@sirena.org.uk> (raw)
In-Reply-To: <565DED87.1030600@metafoo.de>


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

On Tue, Dec 01, 2015 at 07:57:11PM +0100, Lars-Peter Clausen wrote:
> On 12/01/2015 06:32 PM, Charles Keepax wrote:

> > The siggen widget type doesn't really require its own special handling.
> > It can be handled identically to a mic widget, ie. it is a source of a
> > signal and causes things to power up when an output is connected.

> > However, as siggen widgets present as always on (the power check always
> > returns 1), this leads to some odd interactions with DAPM.

> Sounds sensible, but I'd keep the siggen type and just change the
> power_check callback. snd_soc_dapm_mic widgets are a bit special in that
> they also influence how input and output widgets behave, we don't want the
> same behavior for siggen widgets, since siggen widgets are internal to CODEC
> while mic widgets are usually external.

Yeah, the siggen widgets were created because mics are funky - best to
just fix the bug.

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

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



  reply	other threads:[~2015-12-01 19:36 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-01 17:32 [PATCH] ASoC: dapm: Replace siggen widget type with mic widgets Charles Keepax
2015-12-01 18:57 ` Lars-Peter Clausen
2015-12-01 19:36   ` Mark Brown [this message]
2015-12-02  9:15     ` Charles Keepax

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=20151201193613.GP1929@sirena.org.uk \
    --to=broonie@kernel.org \
    --cc=alsa-devel@alsa-project.org \
    --cc=ckeepax@opensource.wolfsonmicro.com \
    --cc=lars@metafoo.de \
    --cc=lgirdwood@gmail.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox