mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
Cc: Perry Yuan <Perry.Yuan@dell.com>,
	oder_chiou@realtek.com, alsa-devel@alsa-project.org,
	lgirdwood@gmail.com,
	Limonciello Mario <Mario.Limonciello@dell.com>,
	linux-kernel@vger.kernel.org, tiwai@suse.com
Subject: Re: [PATCH] ASoC: rt715:add Mic Mute LED control support
Date: Tue, 3 Nov 2020 17:59:48 +0000	[thread overview]
Message-ID: <20201103175948.GF5545@sirena.org.uk> (raw)
In-Reply-To: <5f2c1282-4401-276a-8dad-127fa1f449fd@linux.intel.com>

[-- Attachment #1: Type: text/plain, Size: 935 bytes --]

On Tue, Nov 03, 2020 at 10:13:03AM -0600, Pierre-Louis Bossart wrote:
> Somehow this patch was filtered by alsa-devel servers?

It'll be a post by a non-subscriber I guess, in which case it will
appear later.

> Actually thinking more about it, having two controls for 'mute LED' and
> 'capture switch' could lead to inconsistent states where the LED is on
> without mute being activated.  we should really bolt the LED activation to
> the capture switch, that way the mute and LED states are aligned.

Yeah, it's just asking for trouble and seems to defeat the point of
having the LED in the first place - aside from the general issues with
it being software controlled it'll require specific userspace support to
set it.  Users won't be able to trust that the LED state accurately
reflects if they're muted or not.  Your proposal is more what I'd expect
here, I'm not sure we can do much better with something software
controllable.

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

  parent reply	other threads:[~2020-11-03 18:00 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-03 12:58 Perry Yuan
2020-11-03 13:12 ` Mark Brown
2020-11-03 16:13   ` Pierre-Louis Bossart
2020-11-03 17:51     ` Limonciello, Mario
2020-11-03 17:59     ` Mark Brown [this message]
2020-11-03 18:04       ` Limonciello, Mario
2020-11-03 18:31         ` Mark Brown
2020-11-03 19:01           ` Limonciello, Mario
2020-11-03 18:35         ` Pierre-Louis Bossart
2020-11-03 19:03 ` kernel test robot

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=20201103175948.GF5545@sirena.org.uk \
    --to=broonie@kernel.org \
    --cc=Mario.Limonciello@dell.com \
    --cc=Perry.Yuan@dell.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=lgirdwood@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=oder_chiou@realtek.com \
    --cc=pierre-louis.bossart@linux.intel.com \
    --cc=tiwai@suse.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

all inboxes | Powered by JetHome®