All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Henningsson <david.henningsson@canonical.com>
To: Arnout Engelen <alsalist@bzzt.net>
Cc: alsa-devel@alsa-project.org
Subject: Re: HD Audio with 'mute light'
Date: Mon, 24 Sep 2012 10:12:19 +0200	[thread overview]
Message-ID: <506015E3.1080605@canonical.com> (raw)
In-Reply-To: <20120922185411.GE2822@bzzt.net>

On 09/22/2012 08:54 PM, Arnout Engelen wrote:
> Hi,
>
> I've got a laptop with a HD Audio onboard sound card: the CX20590.
>
> It seems like this card has a sort of 'hardware mute state': the 'mute button'
> has a light, and when this light is on, no sound is heard, regardless of
> whether or not the channel is muted in the ALSA mixer.
>
> The hardware mute button switches the 'hardware mute state', and also sends a
> keyboard event which I can use to also update the ALSA mixer mute.
>
> This doesn't, however, work the other way around: I haven't found any way yet
> to manipulate the 'hardware mute state' from software.
>
> Looking with hda_analyzer, I notice this card has a 'Vendor Defined Widget'.
> Might this be something that could be used to manipulate the hardware mute
> state? I can use hda-verb but I wouldn't know how to discover which verb to
> use. Anything else to try?
>
> Attached is the codec info.

We generally recommend people to submit the entire alsa-info, rather 
than just the codec info (which, btw, was an empty attachment). In 
particular; if you're having a thinkpad, the mute LED is controlled 
through thinkpad-acpi, and if you're having an HP, it's usually 
connected to the codec in a way hinted by BIOS. Given that you have a 
conexant codec, I'm guessing it's a thinkpad.


-- 
David Henningsson, Canonical Ltd.
https://launchpad.net/~diwic

  parent reply	other threads:[~2012-09-24  8:12 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-22 18:54 HD Audio with 'mute light' Arnout Engelen
2012-09-24  8:09 ` Takashi Iwai
2012-09-24  8:12 ` David Henningsson [this message]
2012-09-24 10:06   ` Arnout Engelen

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=506015E3.1080605@canonical.com \
    --to=david.henningsson@canonical.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=alsalist@bzzt.net \
    /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.