[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20201014082752.GA31728@amd>
Date: Wed, 14 Oct 2020 10:27:52 +0200
From: Pavel Machek <pavel@....cz>
To: Udo van den Heuvel <udovdh@...all.nl>
Cc: Takashi Iwai <tiwai@...e.de>, Randy Dunlap <rdunlap@...radead.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
linux-leds@...r.kernel.org, Dan Murphy <dmurphy@...com>,
moderated for non-subscribers <alsa-devel@...a-project.org>
Subject: Re: disabling CONFIG_LED_CLASS (SND_HDA_CODEC_REALTEK)
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
Download attachment "signature.asc" of type "application/pgp-signature" (182 bytes)
Powered by blists - more mailing lists