Changes in Makefile

6f963a20 - leds: trigger: Add new LED Input events trigger

Fri, 31 May 2024 13:59:10 +0000

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 Link: https://lore.kernel.org/r/20240531135910.168965-2-hdegoede@redhat.comSigned-off-by: Lee Jones List of files: /linux-6.15/drivers/leds/trigger/Makefile

a24de38d - ALSA: control-led: Integrate mute led trigger

Mon, 04 Mar 2024 20:58:46 +0000

ALSA: control-led: Integrate mute led triggerThis driver is the only one calling ledtrig_audio_set(), thereforethe LED audio trigger isn'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 Reviewed-by: Takashi Iwai Link: https://lore.kernel.org/r/107634e6-d9ad-4a9f-881d-1eb72ea1a5a7@gmail.comSigned-off-by: Lee Jones List of files: /linux-6.15/drivers/leds/trigger/Makefile

fd4a641a - leds: trigger: implement a tty trigger

Wed, 13 Jan 2021 17:30:18 +0000

leds: trigger: implement a tty triggerUsage is as follows: myled=ledname tty=ttyS0 echo tty > /sys/class/leds/$myled/trigger echo $tty > /sys/class/leds/$myled/ttyname. When this new trigger is active it periodically checks the tty'sstatistics and when it changed since the last check the led is flashedonce.Signed-off-by: Uwe Kleine-König Link: https://lore.kernel.org/r/20210113173018.bq2fkea2o3yp6rf6@pengutronix.deSigned-off-by: Greg Kroah-Hartman List of files: /linux-6.15/drivers/leds/trigger/Makefile

faa2541f - leds: trigger: Introduce audio mute LED trigger

Mon, 26 Nov 2018 16:47:44 +0000

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, "audio-mute" and "audio-micmute".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 Acked-by: Pavel Machek Acked-by: Pali Rohár Signed-off-by: Takashi Iwai List of files: /linux-6.15/drivers/leds/trigger/Makefile

5fd752b6 - leds: core: Introduce LED pattern trigger

Thu, 11 Oct 2018 04:07:14 +0000

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 'pattern' file to enable the software patternwhich alters the brightness for the specified duration with onesoftware timer.Moreover consumers can write 'hw_pattern' 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 Signed-off-by: Baolin Wang Signed-off-by: Jacek Anaszewski List of files: /linux-6.15/drivers/leds/trigger/Makefile

06f502f5 - leds: trigger: Introduce a NETDEV trigger

Sun, 10 Dec 2017 21:17:55 +0000

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 Acked-by: Pavel Machek Signed-off-by: Jacek Anaszewski List of files: /linux-6.15/drivers/leds/trigger/Makefile

b2441318 - License cleanup: add SPDX GPL-2.0 license identifier to files with no license

Wed, 01 Nov 2017 14:07:57 +0000

License cleanup: add SPDX GPL-2.0 license identifier to files with no licenseMany source files in the tree are missing licensing information, whichmakes it harder for compliance tools to determine the correct license.By default all files without license information are under the defaultlicense of the kernel, which is GPL version 2.Update the files which contain no license information with the 'GPL-2.0'SPDX license identifier. The SPDX identifier is a legally bindingshorthand, which can be used instead of the full boiler plate text.This patch is based on work done by Thomas Gleixner and Kate Stewart andPhilippe Ombredanne.How this work was done:Patches were generated and checked against linux-4.14-rc6 for a subset ofthe use cases: - file had no licensing information it it. - file was a */uapi/* one with no licensing information in it, - file was a */uapi/* one with existing licensing information,Further patches will be generated in subsequent months to fix up caseswhere non-standard license headers were used, and references to licensehad to be inferred by heuristics based on keywords.The analysis to determine which SPDX License Identifier to be applied toa file was done in a spreadsheet of side by side results from of theoutput of two independent scanners (ScanCode & Windriver) producing SPDXtag:value files created by Philippe Ombredanne. Philippe prepared thebase worksheet, and did an initial spot review of a few 1000 files.The 4.13 kernel was the starting point of the analysis with 60,537 filesassessed. Kate Stewart did a file by file comparison of the scannerresults in the spreadsheet to determine which SPDX license identifier(s)to be applied to the file. She confirmed any determination that was notimmediately clear with lawyers working with the Linux Foundation.Criteria used to select files for SPDX license identifier tagging was: - Files considered eligible had to be source code files. - Make and config files were included as candidates if they contained >5 lines of source - File already had some variant of a license header in it (even if <5 lines).All documentation files were explicitly excluded.The following heuristics were used to determine which SPDX licenseidentifiers to apply. - when both scanners couldn't find any license traces, file was considered to have no license information in it, and the top level COPYING file license applied. For non */uapi/* files that summary was: SPDX license identifier # files ---------------------------------------------------|------- GPL-2.0 11139 and resulted in the first patch in this series. If that file was a */uapi/* path one, it was "GPL-2.0 WITH Linux-syscall-note" otherwise it was "GPL-2.0". Results of that was: SPDX license identifier # files ---------------------------------------------------|------- GPL-2.0 WITH Linux-syscall-note 930 and resulted in the second patch in this series. - if a file had some form of licensing information in it, and was one of the */uapi/* ones, it was denoted with the Linux-syscall-note if any GPL family license was found in the file or had no licensing in it (per prior point). Results summary: SPDX license identifier # files ---------------------------------------------------|------ GPL-2.0 WITH Linux-syscall-note 270 GPL-2.0+ WITH Linux-syscall-note 169 ((GPL-2.0 WITH Linux-syscall-note) OR BSD-2-Clause) 21 ((GPL-2.0 WITH Linux-syscall-note) OR BSD-3-Clause) 17 LGPL-2.1+ WITH Linux-syscall-note 15 GPL-1.0+ WITH Linux-syscall-note 14 ((GPL-2.0+ WITH Linux-syscall-note) OR BSD-3-Clause) 5 LGPL-2.0+ WITH Linux-syscall-note 4 LGPL-2.1 WITH Linux-syscall-note 3 ((GPL-2.0 WITH Linux-syscall-note) OR MIT) 3 ((GPL-2.0 WITH Linux-syscall-note) AND MIT) 1 and that resulted in the third patch in this series. - when the two scanners agreed on the detected license(s), that became the concluded license(s). - when there was disagreement between the two scanners (one detected a license but the other didn't, or they both detected different licenses) a manual inspection of the file occurred. - In most cases a manual inspection of the information in the file resulted in a clear resolution of the license that should apply (and which scanner probably needed to revisit its heuristics). - When it was not immediately clear, the license identifier was confirmed with lawyers working with the Linux Foundation. - If there was any question as to the appropriate license identifier, the file was flagged for further research and to be revisited later in time.In total, over 70 hours of logged manual review was done on thespreadsheet to determine the SPDX license identifiers to apply to thesource files by Kate, Philippe, Thomas and, in some cases, confirmationby lawyers working with the Linux Foundation.Kate also obtained a third independent scan of the 4.13 code base fromFOSSology, and compared selected files where the other two scannersdisagreed against that SPDX file, to see if there was new insights. TheWindriver scanner is based on an older version of FOSSology in part, sothey are related.Thomas did random spot checks in about 500 files from the spreadsheetsfor the uapi headers and agreed with SPDX license identifier in thefiles he inspected. For the non-uapi files Thomas did random spot checksin about 15000 files.In initial set of patches against 4.14-rc6, 3 files were found to havecopy/paste license identifier errors, and have been fixed to reflect thecorrect identifier.Additionally Philippe spent 10 hours this week doing a detailed manualinspection and review of the 12,461 patched files from the initial patchversion early this week with: - a full scancode scan run, collecting the matched texts, detected license ids and scores - reviewing anything where there was a license detected (about 500+ files) to ensure that the applied SPDX license was correct - reviewing anything where there was no detection but the patch license was not GPL-2.0 WITH Linux-syscall-note to ensure that the applied SPDX license was correctThis produced a worksheet with 20 files needing minor correction. Thisworksheet was then exported into 3 different .csv files for thedifferent types of files to be modified.These .csv files were then reviewed by Greg. Thomas wrote a script toparse the csv files and add the proper SPDX tag to the file, in theformat that the file expected. This script was further refined by Gregbased on the output to detect more types of files automatically and todistinguish between header and source .c files (which need differentcomment types.) Finally Greg ran the script using the .csv files togenerate the patches.Reviewed-by: Kate Stewart Reviewed-by: Philippe Ombredanne Reviewed-by: Thomas Gleixner Signed-off-by: Greg Kroah-Hartman List of files: /linux-6.15/drivers/leds/trigger/Makefile

7df4f9a9 - leds: ledtrig-activity: Add a system activity LED trigger

Mon, 28 Aug 2017 18:44:51 +0000

leds: ledtrig-activity: Add a system activity LED triggerThe "activity" 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 Signed-off-by: Jacek Anaszewski List of files: /linux-6.15/drivers/leds/trigger/Makefile

eb25cb99 - leds: convert IDE trigger to common disk trigger

Fri, 10 Jun 2016 05:59:56 +0000

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'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 'ide-disk' 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 'disk-activity' should be used.Cc: Joseph Jezak Cc: Jörg Sommer Cc: Richard Purdie Signed-off-by: Stephan Linz Signed-off-by: Jacek Anaszewski List of files: /linux-6.15/drivers/leds/trigger/Makefile

4b721174 - leds: trigger: Introduce a MTD (NAND/NOR) trigger

Tue, 12 Apr 2016 20:46:40 +0000

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 "nand-disk" LED trigger, but for backwardscompatibility, we still keep the "nand-disk" trigger around.The motivation for deprecating the "nand-disk" LED trigger is thatit only works for NAND drivers, whereas the "mtd" LED triggeris more generic (in fact, "nand-disk" currently only works forcertain NAND drivers).Signed-off-by: Ezequiel Garcia Acked-by: Boris Brezillon Signed-off-by: Jacek Anaszewski List of files: /linux-6.15/drivers/leds/trigger/Makefile

916fe619 - leds: trigger: Introduce a kernel panic LED trigger

Tue, 29 Mar 2016 20:35:47 +0000

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 Signed-off-by: Jacek Anaszewski List of files: /linux-6.15/drivers/leds/trigger/Makefile

48a1d032 - leds: add camera LED triggers

Thu, 14 Mar 2013 11:29:24 +0000

leds: add camera LED triggersSome LED devices support flash/torch functionality through the LED subsystem.This patch enables direct LED trigger controls by the driver.Flash on/off and torch on/off can be done simply by other driver space.Two trigger APIs are added, ledtrig_flash_ctrl() and ledtrig_torch_ctrl().Signed-off-by: Milo(Woogyom) Kim Signed-off-by: Bryan Wu List of files: /linux-6.15/drivers/leds/trigger/Makefile

f07fb521 - leds: move LED trigger drivers into new subdirectory

Wed, 20 Feb 2013 08:36:01 +0000

leds: move LED trigger drivers into new subdirectoryFor better driver management, new subdirectory, 'trigger' is created.All LED trigger drivers are moved into this directory.Internal header, 'leds.h' is included in each LED trigger drivers.Fix the location of header file, "leds.h" -> "../leds.h" in driver files.One exception is here, 'ledtrig-timer.c'.There is no need to include 'leds.h'. so '#include "leds.h"' line was removed.Signed-off-by: Milo(Woogyom) Kim Signed-off-by: Bryan Wu List of files: /linux-6.15/drivers/leds/trigger/Makefile