Re: disabling CONFIG_LED_CLASS (SND_HDA_CODEC_REALTEK)

From: Pavel Machek <pavel@ucw.cz>
To: Udo van den Heuvel <udovdh@xs4all.nl>
Cc: moderated for non-subscribers <alsa-devel@alsa-project.org>,
	Takashi Iwai <tiwai@suse.de>,
	Randy Dunlap <rdunlap@infradead.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Dan Murphy <dmurphy@ti.com>,
	linux-leds@vger.kernel.org
Subject: Re: disabling CONFIG_LED_CLASS (SND_HDA_CODEC_REALTEK)
Date: Wed, 14 Oct 2020 10:27:52 +0200	[thread overview]
Message-ID: <20201014082752.GA31728@amd> (raw)
In-Reply-To: <2be6e184-97d4-a2b1-a500-6ea3528cff37@xs4all.nl>

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

On Wed 2020-10-14 10:22:01, Udo van den Heuvel wrote:
> On 14-10-2020 10:11, Pavel Machek wrote:
> >> It's a computer, not a disco-light or anything like that.
> > 
> > And you probably have numlock LED.
> 
> On the case? no way.
> It is on the keyboard, a separate device, and already has a function.
> We also have a caps lock LED and scroll lock LED there, with separate
> functions.
> I do not need 'extra' functionality for those.
> 
> > Additional config options have costs, too, and we don't want to
> > support gazillion config options. 
> 
> That is not the issue.
> One should have thought about stuff beforehand.

We did. And decided this is best solution.

> The non-selectability is not my fault.

It also does not affect you in any way.

Feel free to go to the mic LED discussion to see why we did it like
this. Then you can come up with better solution for problem at hand.

									Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]