From: Takashi Iwai <tiwai@suse.de>
To: Kailang <kailang@realtek.com>
Cc: alsa-devel@alsa-project.org
Subject: Re: Enable more HP machine to enable mute led
Date: Wed, 18 Jun 2014 12:14:21 +0200 [thread overview]
Message-ID: <s5hppi6bk3m.wl%tiwai@suse.de> (raw)
In-Reply-To: <4E5CB94F927642A1ACA12B1DBC30E7C7@realtek.com.tw>
At Wed, 18 Jun 2014 11:49:40 +0800,
Kailang wrote:
>
> > At Fri, 13 Jun 2014 17:27:31 +0800,
> > Kailang wrote:
> >>
> >> Hi Takashi,
> >>
> >> Add more HP machine to support mute led functions.
> >
> > Applied this now as is. But, the table looks bigger and bigger, which
> > I don't like any more.
> >
> > So, all these devices have no indication of mute LED in any DMI or
> > whatever entries? In the past, most of HP machines had a DMI string
> > showing the mute LED capability.
> >
>
> HP says that was support for IDT only.
> If we want to use this string, we need to discuss with their BIOS manager.
> We will try to go this feature.
>
> HP has new platform that had speaker mute led and capture mute led.
> HP_MUTE_LED_P_G => DMI string was not enough field for two leds.
> Do you have any idea for dmi string?
>
> HP_MUTE_LED_P_G_G => last G for second led for capture mute led
This would work. If the mic LED might have a different polarity, it
can be P_G_P_G, too.
thanks,
Takashi
>
> >
> > thanks,
> >
> > Takashi
> >
> > ------Please consider the environment before printing this e-mail.
>
next prev parent reply other threads:[~2014-06-18 10:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-13 9:27 Enable more HP machine to enable mute led Kailang
2014-06-13 9:41 ` Takashi Iwai
2014-06-13 9:56 ` Kailang
2014-06-18 3:49 ` Kailang
2014-06-18 10:14 ` Takashi Iwai [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-02-21 8:38 Kailang
2014-02-21 11:05 ` 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=s5hppi6bk3m.wl%tiwai@suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@alsa-project.org \
--cc=kailang@realtek.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