From: Takashi Iwai <tiwai@suse.de>
To: Pavel Machek <pavel@ucw.cz>
Cc: moderated for non-subscribers <alsa-devel@alsa-project.org>,
Randy Dunlap <rdunlap@infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Udo van den Heuvel <udovdh@xs4all.nl>,
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:08:27 +0200 [thread overview]
Message-ID: <s5h4kmxmdqc.wl-tiwai@suse.de> (raw)
In-Reply-To: <20201014075458.GA29881@amd>
On Wed, 14 Oct 2020 09:54:59 +0200,
Pavel Machek wrote:
>
> Hi!
>
> > >>> I.e.: it looks like I will lose some funcionality when I disable
> > >>> SND_HDA_CODEC_REALTEK.
> > >>
> > >> OK. At present you can't have it both ways, i.e., SND_HDA_CODEC_REALTEK
> > >> with no LEDS. That driver apparently wants LEDS.
> > >
> > > Thanks but why have I gone for years without LEDS?
> > > I do not need LEDS, I do not want LEDS, I do not have LEDS (that are
> > > visible, usable, etc).
> > >
> > > Please make this selectable instead of forcing more bulk into my
> >> kernel.
>
> LED core is not that big, and this avoided some rather "interesting"
> hacks IIRC. If Udo wants more config complexity, lets first make him
> measure the benefits, second submit a patch.
>
> But I'd suggest to just live with it.
>
> And yes, we should probably get rid of "CONFIG_NEW_LEDS" symbol. That
> one is actually useless.
IIRC, this was needed for the reverse selection of CONFIG_LEDS_CLASS
and co. But if it's really useless, I'll happily delete it.
thanks,
Takashi
next prev parent reply other threads:[~2020-10-14 8:09 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <2835d02a-380b-6a3a-0e4d-abf07aee18bc@xs4all.nl>
[not found] ` <53e698c1-86e4-8b1f-afb0-b8471349e701@xs4all.nl>
[not found] ` <43b79598-1592-683f-46df-9e5489110780@infradead.org>
[not found] ` <6fd1e91e-19d0-6682-dfc6-49f1cd60408b@infradead.org>
[not found] ` <3c6d174c-30db-3d03-3d16-42df405f38d9@xs4all.nl>
[not found] ` <58e774c5-fc80-2060-2091-9a6398582cc5@infradead.org>
[not found] ` <9fc679e9-e9a9-ad80-b24c-f04489b98aa7@xs4all.nl>
[not found] ` <27e159be-4376-e87b-5e60-803bc3749ec2@infradead.org>
[not found] ` <eadc23e7-b383-e2fc-6e20-ed22745d0bfc@xs4all.nl>
[not found] ` <2739e1fd-75c6-4e43-cd79-9028479f91bf@infradead.org>
[not found] ` <1e6b1961-9e9b-5f82-86a1-bf838cb68f55@xs4all.nl>
2020-10-14 5:54 ` disabling CONFIG_LED_CLASS (SND_HDA_CODEC_REALTEK) Randy Dunlap
2020-10-14 7:49 ` Takashi Iwai
2020-10-14 7:51 ` Takashi Iwai
2020-10-14 7:58 ` Pavel Machek
2020-10-14 8:06 ` Takashi Iwai
[not found] ` <056a8933-378f-30f2-c7af-5514d93d3c36@xs4all.nl>
2020-10-14 8:11 ` Pavel Machek
[not found] ` <2be6e184-97d4-a2b1-a500-6ea3528cff37@xs4all.nl>
2020-10-14 8:27 ` Pavel Machek
[not found] ` <9cf705b9-1fca-2445-43de-916b13b9103f@xs4all.nl>
2020-10-14 8:37 ` Pavel Machek
2020-10-19 8:35 ` Udo van den Heuvel
2020-10-19 10:58 ` Marek Behún
2020-10-14 7:54 ` Pavel Machek
2020-10-14 8:08 ` Takashi Iwai [this message]
2020-10-14 8:13 ` Pavel Machek
2020-10-14 8:17 ` 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=s5h4kmxmdqc.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@alsa-project.org \
--cc=dmurphy@ti.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=rdunlap@infradead.org \
--cc=udovdh@xs4all.nl \
/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).