From: Takashi Iwai <tiwai@suse.de>
To: "Jerónimo Borque" <jeronimo@borque.com.ar>
Cc: alsa-devel@alsa-project.org
Subject: Re: [PATCH] ALSA: hda - Fixes inverted Conexant GPIO mic mute led
Date: Thu, 15 Aug 2019 19:06:06 +0200 [thread overview]
Message-ID: <s5ha7ca9x4x.wl-tiwai@suse.de> (raw)
In-Reply-To: <CAHNnQd+B5UGKJBq+ikDBYa20vzL=Fj9tDGNeRZGp5qxcSiEDhQ@mail.gmail.com>
On Thu, 15 Aug 2019 18:33:50 +0200,
Jerónimo Borque wrote:
>
> Hi Takashi,
> Modifying Mic Mute-LED Mode does indeed alter the behavior. The thing is that
> this ends being confusing as in all machines I've been testing this setting
> Mic Mute-LED Mode to "Follow Capture" actually makes it follow mute, as
> setting it to "On" turns the LED off.
> There is other setting called "mute_led_polarity" but this does not work, as
> currently mic mute LED and mute LED do not follow the same logic.
> What I think may be causing confusion is "cxt_update_gpio_led" "enabled"
> parameter. Setting "enabled" to "true" sets the GPIO pin to 0 causing the led
> to be turned off. I think "enabled" used to refer to the input capture or
> output status and not to the LED being lit or not. Output or input not enabled
> (enabled==false) caused the LED to be turned on.
> This logic in the function negates it on the GPIO output.
>
> if (enabled)
> spec->gpio_led &= ~mask;
> else
> spec->gpio_led |= mask;
>
> May be I can do a more comprehensive fix, reversing the behavior of
> "cxt_update_gpio_led" "enabled" parameter to refer the GPIO output value (
> enabled==true => GPIO pin output high )
> Then also modify the call to "cxt_update_gpio_led" in
> "cxt_fixup_gpio_mute_hook" to make it work consistently.
OK, if the "On" turns the LED off, it's indeed inverted.
Then we'd need to consider both fixing the inverted behavior and the
default mic-mute mode.
Could you confirm the following?
- Which models and codecs are checked?
- GPIO pin high = mic LED on or off?
- How is the expected behavior on Windows?
Mute is on when mic is muted, or mute-on when mic is ready?
thanks,
Takashi
>
> Thanks,
> Jerónimo
>
> El jue., 15 de ago. de 2019 a la(s) 02:58, Takashi Iwai (tiwai@suse.de)
> escribió:
>
> On Thu, 15 Aug 2019 03:38:24 +0200,
> <jeronimo@borque.com.ar> wrote:
> >
> > From: Jeronimo Borque <jeronimo@borque.com.ar>
> >
> > "enabled" parameter historically referred to the device input or
> > output, not to the led indicator. After the changes added with the
> > led helper functions the mic mute led logic refers to the led and not
> > to the mic input which caused led indicator to be negated (Mic mute
> > led was on when the input enabled) Fixing it in the call to
> > cxt_update_gpio_led at the cxt_gpio_micmute_update hook.
> > Maybe more changes are required to be consistent everywhere.
> >
> > Signed-off-by: Jeronimo Borque <jeronimo@borque.com.ar>
>
> Could you check which value you have in "Mic Mute-LED Mode" mixer
> element? I guess it's "Follow Mute". If so, change it to "Follow
> Capture".
>
> If this works, it means that the driver works as expected but the
> problem is only about the default value. The default value set in the
> generic parser is based on other machine's standard (LED on at mic
> off), while some machines might expect differently. On such machines,
> we need to set the different value initially in the quirk fixup.
>
> thanks,
>
> Takashi
>
>
_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
https://mailman.alsa-project.org/mailman/listinfo/alsa-devel
next prev parent reply other threads:[~2019-08-15 17:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-15 1:38 [PATCH] ALSA: hda - Fixes inverted Conexant GPIO mic mute led jeronimo
2019-08-15 5:58 ` Takashi Iwai
2019-08-15 16:33 ` Jerónimo Borque
2019-08-15 17:06 ` Takashi Iwai [this message]
2019-08-15 23:08 ` Jerónimo Borque
2019-08-16 7:11 ` Takashi Iwai
2019-08-18 21:23 ` [PATCH v2] " jeronimo
2019-08-19 0:01 ` Jerónimo Borque
2019-08-19 1:35 ` [PATCH v3] " jeronimo
2019-08-19 17:42 ` 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=s5ha7ca9x4x.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@alsa-project.org \
--cc=jeronimo@borque.com.ar \
/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.