<?xml version="1.0"?>
<?xml-stylesheet type="text/xsl" href="/rss.xsl.xml"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/">
<channel>
    <title>Changes in Kconfig</title>
    <description></description>
    <language>en</language>
    <copyright>Copyright 2015</copyright>
    <generator>Java</generator><item>
        <title>6f963a20 - leds: trigger: Add new LED Input events trigger</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/leds/trigger/Kconfig#6f963a20</link>
        <description>leds: trigger: Add new LED Input events triggerAdd a new trigger which turns LEDs on when there is input(/dev/input/event*) activity and turns them back off again after there hasbeen no activity for 5 seconds.This is primarily intended to control LED devices which are a backlight forcapacitive touch-buttons, such as e.g. the menu / home / back buttons foundon the bottom bezel of many somewhat older smartphones and tablets.This can also be used to turn on the keyboard backlight LED on inputevents and turn the keyboard backlight off again when idle.Signed-off-by: Hans de Goede &lt;hdegoede@redhat.com&gt;Link: https://lore.kernel.org/r/20240531135910.168965-2-hdegoede@redhat.comSigned-off-by: Lee Jones &lt;lee@kernel.org&gt;

            List of files:
            /linux-6.15/drivers/leds/trigger/Kconfig</description>
        <pubDate>Fri, 31 May 2024 13:59:10 +0000</pubDate>
        <dc:creator>Hans de Goede &lt;hdegoede@redhat.com&gt;</dc:creator>
    </item>
<item>
        <title>a24de38d - ALSA: control-led: Integrate mute led trigger</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/leds/trigger/Kconfig#a24de38d</link>
        <description>ALSA: control-led: Integrate mute led triggerThis driver is the only one calling ledtrig_audio_set(), thereforethe LED audio trigger isn&apos;t usable standalone. So it makes senseto fully integrate LED audio triger handling here.The module aliases ensure that the driver is auto-loaded (if builtas module) if a LED device has one of the two audio triggers asdefault trigger.In addition disable building the old audio mute LED trigger.Signed-off-by: Heiner Kallweit &lt;hkallweit1@gmail.com&gt;Reviewed-by: Takashi Iwai &lt;tiwai@suse.de&gt;Link: https://lore.kernel.org/r/107634e6-d9ad-4a9f-881d-1eb72ea1a5a7@gmail.comSigned-off-by: Lee Jones &lt;lee@kernel.org&gt;

            List of files:
            /linux-6.15/drivers/leds/trigger/Kconfig</description>
        <pubDate>Mon, 04 Mar 2024 20:58:46 +0000</pubDate>
        <dc:creator>Heiner Kallweit &lt;hkallweit1@gmail.com&gt;</dc:creator>
    </item>
<item>
        <title>4a11dbf0 - leds: triggers: gpio: Rewrite to use trigger-sources</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/leds/trigger/Kconfig#4a11dbf0</link>
        <description>leds: triggers: gpio: Rewrite to use trigger-sourcesBy providing a GPIO line as &quot;trigger-sources&quot; in the FWNODE(such as from the device tree) and combining with theGPIO trigger, we can support a GPIO LED trigger in a naturalway from the hardware description instead of using thecustom sysfs and deprecated global GPIO numberspace.Example:gpio: gpio@0 {    compatible &quot;my-gpio&quot;;    gpio-controller;    #gpio-cells = &lt;2&gt;;    interrupt-controller;    #interrupt-cells = &lt;2&gt;;    #trigger-source-cells = &lt;2&gt;;};leds {    compatible = &quot;gpio-leds&quot;;    led-my-gpio {        label = &quot;device:blue:myled&quot;;        gpios = &lt;&amp;gpio 0 GPIO_ACTIVE_HIGH&gt;;        default-state = &quot;off&quot;;        linux,default-trigger = &quot;gpio&quot;;        trigger-sources = &lt;&amp;gpio 1 GPIO_ACTIVE_HIGH&gt;;    };};Make this the norm, unmark the driver as broken.Delete the sysfs handling of GPIOs.Since GPIO descriptors inherently can describe inversion,the inversion handling can just be deleted.Signed-off-by: Linus Walleij &lt;linus.walleij@linaro.org&gt;Link: https://lore.kernel.org/r/20230926-gpio-led-trigger-dt-v2-3-e06e458b788e@linaro.orgSigned-off-by: Lee Jones &lt;lee@kernel.org&gt;

            List of files:
            /linux-6.15/drivers/leds/trigger/Kconfig</description>
        <pubDate>Tue, 26 Sep 2023 21:48:13 +0000</pubDate>
        <dc:creator>Linus Walleij &lt;linus.walleij@linaro.org&gt;</dc:creator>
    </item>
<item>
        <title>8f0adae1 - leds: Mark GPIO LED trigger broken</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/leds/trigger/Kconfig#8f0adae1</link>
        <description>leds: Mark GPIO LED trigger brokenThe GPIO LED trigger exposes a userspace ABI where a usercan echo a GPIO number from the global GPIO numberspace intoa file that will trigger a certain LED when active.This is problematic because the global GPIO numberspace isinherently instable. The trigger came about at a time whensystems had one GPIO controller that defined hard-wiredGPIOs numbered 0..N and this number space was stable.We have since moved to dynamic allocation of GPIO numbersand there is no real guarantee that a GPIO number will stayconsistent even across a reboot: consider a USB attachedGPIO controller for example. Or two. Or the effect ofprobe order after adding -EPROBE_DEFER to the kernel.The trigger was added to support keypad LEDs on the Nokian810 from the GPIO event when a user slides up/down thekeypad. This is arch/arm/boot/dts/omap2420-n810.dts.A userspace script is needed to activate the trigger.This will be broken unless the script was updated recentlysince the OMAP GPIO controller now uses dynamic GPIOnumber allocations.I want to know that this trigger has active users thatcannot live without it if we are to continue to support it.Option if this is really needed: I can develop a new triggerthat can associate GPIOs with LEDs as triggers using devicetree, which should also remove the use of userspace customscripts to achieve this and be much more trustworthy, ifsomeone with the Nokia n810 or a device with a similar needis willing to test it.Suggested-by Pavel Machek &lt;pavel@ucw.cz&gt;Signed-off-by: Linus Walleij &lt;linus.walleij@linaro.org&gt;Signed-off-by: Lee Jones &lt;lee@kernel.org&gt;Link: https://lore.kernel.org/r/20230314210059.419159-1-linus.walleij@linaro.org

            List of files:
            /linux-6.15/drivers/leds/trigger/Kconfig</description>
        <pubDate>Tue, 14 Mar 2023 21:00:59 +0000</pubDate>
        <dc:creator>Linus Walleij &lt;linus.walleij@linaro.org&gt;</dc:creator>
    </item>
<item>
        <title>97b31c1f - leds: trigger: Disable CPU trigger on PREEMPT_RT</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/leds/trigger/Kconfig#97b31c1f</link>
        <description>leds: trigger: Disable CPU trigger on PREEMPT_RTThe CPU trigger is invoked on ARM from CPU-idle. That trigger laterinvokes led_trigger_event() which may invoke the callback of the actual driver.That driver can acquire a spinlock_t which is okay on kernel withoutPREEMPT_RT. On a PREEMPT_RT enabled kernel this lock is turned into asleeping lock and must not be acquired with disabled interrupts.Disable the CPU trigger on PREEMPT_RT.Signed-off-by: Sebastian Andrzej Siewior &lt;bigeasy@linutronix.de&gt;Link: https://lkml.kernel.org/r/20210924111501.m57cwwn7ahiyxxdd@linutronix.deSigned-off-by: Pavel Machek &lt;pavel@ucw.cz&gt;

            List of files:
            /linux-6.15/drivers/leds/trigger/Kconfig</description>
        <pubDate>Wed, 13 Oct 2021 09:37:19 +0000</pubDate>
        <dc:creator>Sebastian Andrzej Siewior &lt;bigeasy@linutronix.de&gt;</dc:creator>
    </item>
<item>
        <title>5358680e - leds: trigger: remove reference to obsolete CONFIG_IDE_GD_ATA</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/leds/trigger/Kconfig#5358680e</link>
        <description>leds: trigger: remove reference to obsolete CONFIG_IDE_GD_ATACommit b7fb14d3ac63 (&quot;ide: remove the legacy ide driver&quot;) removes thedefinition of the config IDE_GD_ATA.So, remove the obsolete reference in ./drivers/leds/trigger/Kconfig.Signed-off-by: Lukas Bulwahn &lt;lukas.bulwahn@gmail.com&gt;Signed-off-by: Pavel Machek &lt;pavel@ucw.cz&gt;

            List of files:
            /linux-6.15/drivers/leds/trigger/Kconfig</description>
        <pubDate>Wed, 04 Aug 2021 12:34:25 +0000</pubDate>
        <dc:creator>Lukas Bulwahn &lt;lukas.bulwahn@gmail.com&gt;</dc:creator>
    </item>
<item>
        <title>fd4a641a - leds: trigger: implement a tty trigger</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/leds/trigger/Kconfig#fd4a641a</link>
        <description>leds: trigger: implement a tty triggerUsage is as follows:	myled=ledname	tty=ttyS0	echo tty &gt; /sys/class/leds/$myled/trigger	echo $tty &gt; /sys/class/leds/$myled/ttyname. When this new trigger is active it periodically checks the tty&apos;sstatistics and when it changed since the last check the led is flashedonce.Signed-off-by: Uwe Kleine-K&#246;nig &lt;u.kleine-koenig@pengutronix.de&gt;Link: https://lore.kernel.org/r/20210113173018.bq2fkea2o3yp6rf6@pengutronix.deSigned-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

            List of files:
            /linux-6.15/drivers/leds/trigger/Kconfig</description>
        <pubDate>Wed, 13 Jan 2021 17:30:18 +0000</pubDate>
        <dc:creator>Uwe Kleine-K&#246;nig &lt;u.kleine-koenig@pengutronix.de&gt;</dc:creator>
    </item>
<item>
        <title>8dab9197 - docs: leds: convert to ReST</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/leds/trigger/Kconfig#8dab9197</link>
        <description>docs: leds: convert to ReSTRename the leds documentation files to ReST, add anindex for them and adjust in order to produce a nice htmloutput via the Sphinx build system.At its new index.rst, let&apos;s add a :orphan: while this is not linked tothe main index.rst file, in order to avoid build warnings.Signed-off-by: Mauro Carvalho Chehab &lt;mchehab+samsung@kernel.org&gt;Acked-by: Pavel Machek &lt;pavel@ucw.cz&gt;Signed-off-by: Jacek Anaszewski &lt;jacek.anaszewski@gmail.com&gt;

            List of files:
            /linux-6.15/drivers/leds/trigger/Kconfig</description>
        <pubDate>Fri, 28 Jun 2019 12:20:20 +0000</pubDate>
        <dc:creator>Mauro Carvalho Chehab &lt;mchehab+samsung@kernel.org&gt;</dc:creator>
    </item>
<item>
        <title>ec8f24b7 - treewide: Add SPDX license identifier - Makefile/Kconfig</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/leds/trigger/Kconfig#ec8f24b7</link>
        <description>treewide: Add SPDX license identifier - Makefile/KconfigAdd SPDX license identifiers to all Make/Kconfig files which: - Have no license information of any formThese files fall under the project license, GPL v2 only. The resulting SPDXlicense identifier is:  GPL-2.0-onlySigned-off-by: Thomas Gleixner &lt;tglx@linutronix.de&gt;Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

            List of files:
            /linux-6.15/drivers/leds/trigger/Kconfig</description>
        <pubDate>Sun, 19 May 2019 12:07:45 +0000</pubDate>
        <dc:creator>Thomas Gleixner &lt;tglx@linutronix.de&gt;</dc:creator>
    </item>
<item>
        <title>faa2541f - leds: trigger: Introduce audio mute LED trigger</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/leds/trigger/Kconfig#faa2541f</link>
        <description>leds: trigger: Introduce audio mute LED triggerThis patch adds a new LED trigger for coupling the audio mixer changewith the LED on laptops or other devices.  Currently there are twotrigger types, &quot;audio-mute&quot; and &quot;audio-micmute&quot;.The audio driver triggers the LED brightness change vialedtrig_audio_set() call with the proper type (either mute ormic-mute).  OTOH, the consumers may call ledtrig_audio_get() for theinitial brightness value that may have been set by the audio driverbeforehand.This new stuff will be used by HD-audio codec driver and some platformdrivers (thinkpad_acpi and dell-laptop, also upcoming huawei-wmi).Acked-by: Jacek Anaszewski &lt;jacek.anaszewski@gmail.com&gt;Acked-by: Pavel Machek &lt;pavel@ucw.cz&gt;Acked-by: Pali Roh&#225;r &lt;pali.rohar@gmail.com&gt;Signed-off-by: Takashi Iwai &lt;tiwai@suse.de&gt;

            List of files:
            /linux-6.15/drivers/leds/trigger/Kconfig</description>
        <pubDate>Mon, 26 Nov 2018 16:47:44 +0000</pubDate>
        <dc:creator>Takashi Iwai &lt;tiwai@suse.de&gt;</dc:creator>
    </item>
<item>
        <title>5fd752b6 - leds: core: Introduce LED pattern trigger</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/leds/trigger/Kconfig#5fd752b6</link>
        <description>leds: core: Introduce LED pattern triggerThis patch adds a new LED trigger that LED device can configureto employ software or hardware pattern engine.Consumers can write &apos;pattern&apos; file to enable the software patternwhich alters the brightness for the specified duration with onesoftware timer.Moreover consumers can write &apos;hw_pattern&apos; file to enable the hardwarepattern for some LED controllers which can autonomously controlbrightness over time, according to some preprogrammed hardwarepatterns.Signed-off-by: Raphael Teysseyre &lt;rteysseyre@gmail.com&gt;Signed-off-by: Baolin Wang &lt;baolin.wang@linaro.org&gt;Signed-off-by: Jacek Anaszewski &lt;jacek.anaszewski@gmail.com&gt;

            List of files:
            /linux-6.15/drivers/leds/trigger/Kconfig</description>
        <pubDate>Thu, 11 Oct 2018 04:07:14 +0000</pubDate>
        <dc:creator>Baolin Wang &lt;baolin.wang@linaro.org&gt;</dc:creator>
    </item>
<item>
        <title>3d74243d - leds: triggers: don&apos;t depend on LEDS_TRIGGERS twice</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/leds/trigger/Kconfig#3d74243d</link>
        <description>leds: triggers: don&apos;t depend on LEDS_TRIGGERS twiceAll the triggers are defined in a big if LEDS_TRIGGERS...endif block.So there is no need to let each driver depend on LEDS_TRIGGERS explicitlyonce more.Signed-off-by: Uwe Kleine-K&#246;nig &lt;u.kleine-koenig@pengutronix.de&gt;Acked-by: Pavel Machek &lt;pavel@ucw.cz&gt;Signed-off-by: Jacek Anaszewski &lt;jacek.anaszewski@gmail.com&gt;

            List of files:
            /linux-6.15/drivers/leds/trigger/Kconfig</description>
        <pubDate>Tue, 26 Jun 2018 09:37:58 +0000</pubDate>
        <dc:creator>Uwe Kleine-K&#246;nig &lt;u.kleine-koenig@pengutronix.de&gt;</dc:creator>
    </item>
<item>
        <title>06f502f5 - leds: trigger: Introduce a NETDEV trigger</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/leds/trigger/Kconfig#06f502f5</link>
        <description>leds: trigger: Introduce a NETDEV triggerThis commit introduces a NETDEV trigger for named deviceactivity. Available triggers are link, rx, and tx.Signed-off-by: Ben Whitten &lt;ben.whitten@gmail.com&gt;Acked-by: Pavel Machek &lt;pavel@ucw.cz&gt;Signed-off-by: Jacek Anaszewski &lt;jacek.anaszewski@gmail.com&gt;

            List of files:
            /linux-6.15/drivers/leds/trigger/Kconfig</description>
        <pubDate>Sun, 10 Dec 2017 21:17:55 +0000</pubDate>
        <dc:creator>Ben Whitten &lt;ben.whitten@gmail.com&gt;</dc:creator>
    </item>
<item>
        <title>a72d3b5d - ledtrig-activity: Grammar s/a immediate/an immediate/</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/leds/trigger/Kconfig#a72d3b5d</link>
        <description>ledtrig-activity: Grammar s/a immediate/an immediate/Fixes: 7df4f9a9f0667ee6 (&quot;leds: ledtrig-activity: Add a system activity LED trigger&quot;)Signed-off-by: Geert Uytterhoeven &lt;geert+renesas@glider.be&gt;Signed-off-by: Jacek Anaszewski &lt;jacek.anaszewski@gmail.com&gt;

            List of files:
            /linux-6.15/drivers/leds/trigger/Kconfig</description>
        <pubDate>Thu, 30 Nov 2017 13:36:41 +0000</pubDate>
        <dc:creator>Geert Uytterhoeven &lt;geert+renesas@glider.be&gt;</dc:creator>
    </item>
<item>
        <title>7df4f9a9 - leds: ledtrig-activity: Add a system activity LED trigger</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/leds/trigger/Kconfig#7df4f9a9</link>
        <description>leds: ledtrig-activity: Add a system activity LED triggerThe &quot;activity&quot; trigger was inspired by the heartbeat one, but aims atproviding instant indication of the immediate CPU usage. Under idlecondition, it flashes 10ms every second. At 100% usage, it flashes90ms every 100ms. The blinking frequency increases from 1 to 10 Hzuntil either the load is high enough to saturate one CPU core or 50%load is reached on a single-core system. Then past this point only theduty cycle increases from 10 to 90%.This results in a very visible activity reporting allowing one toimmediately tell whether a machine is under load or not, making itquite suitable to be used in clusters.Signed-off-by: Willy Tarreau &lt;w@1wt.eu&gt;Signed-off-by: Jacek Anaszewski &lt;jacek.anaszewski@gmail.com&gt;

            List of files:
            /linux-6.15/drivers/leds/trigger/Kconfig</description>
        <pubDate>Mon, 28 Aug 2017 18:44:51 +0000</pubDate>
        <dc:creator>Willy Tarreau &lt;w@1wt.eu&gt;</dc:creator>
    </item>
<item>
        <title>eb25cb99 - leds: convert IDE trigger to common disk trigger</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/leds/trigger/Kconfig#eb25cb99</link>
        <description>leds: convert IDE trigger to common disk triggerThis patch converts the IDE specific LED trigger to a generic diskactivity LED trigger. The libata core is now a trigger source justlike before the IDE disk driver. It&apos;s merely a replacement of thestring ide by disk.The patch is taken from http://dev.gentoo.org/~josejx/ata.patch and iswidely used by any ibook/powerbook owners with great satisfaction.Likewise, it is very often used successfully on different ARM platforms.Unlike the original patch, the existing &apos;ide-disk&apos; trigger is stillavailable for backward compatibility. That reduce the amount of patchesin affected device trees out of the mainline kernel. For furtherdevelopment, the new name &apos;disk-activity&apos; should be used.Cc: Joseph Jezak &lt;josejx@gentoo.org&gt;Cc: J&#246;rg Sommer &lt;joerg@alea.gnuu.de&gt;Cc: Richard Purdie &lt;rpurdie@rpsys.net&gt;Signed-off-by: Stephan Linz &lt;linz@li-pro.net&gt;Signed-off-by: Jacek Anaszewski &lt;j.anaszewski@samsung.com&gt;

            List of files:
            /linux-6.15/drivers/leds/trigger/Kconfig</description>
        <pubDate>Fri, 10 Jun 2016 05:59:56 +0000</pubDate>
        <dc:creator>Stephan Linz &lt;linz@li-pro.net&gt;</dc:creator>
    </item>
<item>
        <title>ba93cdce - leds: triggers: Allow to switch the trigger to &quot;panic&quot; on a kernel panic</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/leds/trigger/Kconfig#ba93cdce</link>
        <description>leds: triggers: Allow to switch the trigger to &quot;panic&quot; on a kernel panicThis commit adds a new led_cdev flag LED_PANIC_INDICATOR, whichallows to mark a specific LED to be switched to the &quot;panic&quot;trigger, on a kernel panic.This is useful to allow the user to assign a regular triggerto a given LED, and still blink that LED on a kernel panic.Signed-off-by: Ezequiel Garcia &lt;ezequiel@vanguardiasur.com.ar&gt;Reviewed-by: Matthias Brugger &lt;mbrugger@suse.com&gt;Acked-by: Pavel Machek &lt;pavel@ucw.cz&gt;Signed-off-by: Jacek Anaszewski &lt;j.anaszewski@samsung.com&gt;

            List of files:
            /linux-6.15/drivers/leds/trigger/Kconfig</description>
        <pubDate>Thu, 28 Apr 2016 22:03:38 +0000</pubDate>
        <dc:creator>Ezequiel Garcia &lt;ezequiel@vanguardiasur.com.ar&gt;</dc:creator>
    </item>
<item>
        <title>4b721174 - leds: trigger: Introduce a MTD (NAND/NOR) trigger</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/leds/trigger/Kconfig#4b721174</link>
        <description>leds: trigger: Introduce a MTD (NAND/NOR) triggerThis commit introduces a MTD trigger for flash (NAND/NOR) deviceactivity. The implementation is copied from IDE disk.This trigger deprecates the &quot;nand-disk&quot; LED trigger, but for backwardscompatibility, we still keep the &quot;nand-disk&quot; trigger around.The motivation for deprecating the &quot;nand-disk&quot; LED trigger is thatit only works for NAND drivers, whereas the &quot;mtd&quot; LED triggeris more generic (in fact, &quot;nand-disk&quot; currently only works forcertain NAND drivers).Signed-off-by: Ezequiel Garcia &lt;ezequiel@vanguardiasur.com.ar&gt;Acked-by: Boris Brezillon &lt;boris.brezillon@free-electrons.com&gt;Signed-off-by: Jacek Anaszewski &lt;j.anaszewski@samsung.com&gt;

            List of files:
            /linux-6.15/drivers/leds/trigger/Kconfig</description>
        <pubDate>Tue, 12 Apr 2016 20:46:40 +0000</pubDate>
        <dc:creator>Ezequiel Garcia &lt;ezequiel@vanguardiasur.com.ar&gt;</dc:creator>
    </item>
<item>
        <title>916fe619 - leds: trigger: Introduce a kernel panic LED trigger</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/leds/trigger/Kconfig#916fe619</link>
        <description>leds: trigger: Introduce a kernel panic LED triggerThis commit introduces a new LED trigger which allows to configurea LED to blink on a kernel panic (through panic_blink).Notice that currently the Openmoko FreeRunner (GTA02) mach codesets panic_blink to blink a hard-coded LED. The new trigger ismeant to introduce a generic mechanism to achieve this.Signed-off-by: Ezequiel Garcia &lt;ezequiel@vanguardiasur.com.ar&gt;Signed-off-by: Jacek Anaszewski &lt;j.anaszewski@samsung.com&gt;

            List of files:
            /linux-6.15/drivers/leds/trigger/Kconfig</description>
        <pubDate>Tue, 29 Mar 2016 20:35:47 +0000</pubDate>
        <dc:creator>Ezequiel Garcia &lt;ezequiel@vanguardiasur.com.ar&gt;</dc:creator>
    </item>
<item>
        <title>82322741 - leds: Allow compile test of GPIO consumers if !GPIOLIB</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/leds/trigger/Kconfig#82322741</link>
        <description>leds: Allow compile test of GPIO consumers if !GPIOLIBThe GPIO subsystem provides dummy GPIO consumer functions if GPIOLIB isnot enabled. Hence drivers that depend on GPIOLIB, but use GPIO consumerfunctionality only, can still be compiled if GPIOLIB is not enabled.Relax the dependency on GPIOLIB if COMPILE_TEST is enabled, whereappropriate.Signed-off-by: Geert Uytterhoeven &lt;geert@linux-m68k.org&gt;Cc: Richard Purdie &lt;rpurdie@rpsys.net&gt;Cc: linux-leds@vger.kernel.orgSigned-off-by: Jacek Anaszewski &lt;j.anaszewski@samsung.com&gt;

            List of files:
            /linux-6.15/drivers/leds/trigger/Kconfig</description>
        <pubDate>Tue, 05 May 2015 16:32:25 +0000</pubDate>
        <dc:creator>Geert Uytterhoeven &lt;geert@linux-m68k.org&gt;</dc:creator>
    </item>
</channel>
</rss>
