From: David Henningsson <david.henningsson@canonical.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: alsa-devel@alsa-project.org, platform-driver-x86@vger.kernel.org,
ibm-acpi@hmh.eng.br, alex.hung@canonical.com,
hui.wang@canonical.com
Subject: Re: [RFC PATCH 2/2] ALSA: hda - add connection to thinkpad_acpi to control mute/micmute LEDs
Date: Wed, 16 Oct 2013 23:08:44 +0200 [thread overview]
Message-ID: <525F005C.3060806@canonical.com> (raw)
In-Reply-To: <s5hob6puuyg.wl%tiwai@suse.de>
On 10/16/2013 04:55 PM, Takashi Iwai wrote:
> At Wed, 16 Oct 2013 14:15:36 +0200,
> David Henningsson wrote:
>>
>> Notes/questions:
>>
>> For mute LEDs we can follow master like we already do on HP machines, but for
>> mic mutes, we might have several capture switches. Honestly, on these laptops
>> which almost always have autoswitched mics, there is only one recording source
>> anyway. Can't we simply remove the extra capture PCMs, that seems easiest?
>
> The fixup would be applied only to specific machines, so they are
> without extra capture PCMs, no?
Actually, what I was thinking of is already implemented: when auto_mic
is turned on, num_adc_nids is set to one, so there are no extra ADCs. I
think we can get away (at least for now) with just an extra check that
there are no extra ADCs (added in v2 of the patch).
>> For some reason CONFIG_THINKPAD_ACPI did not work here (it was not defined),
>> but maybe it's due to the way I'm testing, or I'm missing something obvious.
>> Not sure.
>
> It can be a module. Use IS_ENABLED() macro.
>
> #if IS_ENABLED(CONFIG_THINKPAD_ACPI)
Thanks!
>> There are Thinkpad's with Realtek codecs as well which have mute/micmute.
>> Maybe we should consider a more generic solution instead of copy-pasting
>> between differen patch_* files?
>
> Maybe. But it's not that wide spread.
Perhaps other people on this list have a better overview than I, but I
get the feeling that at least the mute LED is quite common on Thinkpads.
The micmute LED perhaps not so much.
> Let's make this one working at
> first. The further code sharing (involving module split eventually)
> can be discussed later.
Ok.
>> And also, we're missing a symbol_put in this version. Should we add a new
>> "free" fixup action where we can add a call to symbol_put, or do you have a
>> better suggestion?
>
> Hm, yes, a new free fixup action is a feasible option.
Ok, added in v2.
--
David Henningsson, Canonical Ltd.
https://launchpad.net/~diwic
prev parent reply other threads:[~2013-10-16 21:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-16 12:15 [RFC PATCH 0/2] Enable mute LEDs and mic mute LEDs on Thinkpad David Henningsson
2013-10-16 12:15 ` [RFC PATCH 1/2] thinkpad-acpi: Add mute and mic-mute LED functionality David Henningsson
2013-10-16 12:35 ` Henrique de Moraes Holschuh
2013-10-16 13:09 ` Takashi Iwai
2013-10-16 14:34 ` David Henningsson
2013-10-16 12:15 ` [RFC PATCH 2/2] ALSA: hda - add connection to thinkpad_acpi to control mute/micmute LEDs David Henningsson
2013-10-16 14:55 ` Takashi Iwai
2013-10-16 21:08 ` David Henningsson [this message]
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=525F005C.3060806@canonical.com \
--to=david.henningsson@canonical.com \
--cc=alex.hung@canonical.com \
--cc=alsa-devel@alsa-project.org \
--cc=hui.wang@canonical.com \
--cc=ibm-acpi@hmh.eng.br \
--cc=platform-driver-x86@vger.kernel.org \
--cc=tiwai@suse.de \
/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;
as well as URLs for NNTP newsgroup(s).