Home
last modified time | relevance | path

Searched refs:LED (Results 1 – 166 of 166) sorted by relevance

/linux-4.1.27/Documentation/devicetree/bindings/leds/
Dcommon.txt3 LED and flash LED devices provide the same basic functionality as current
4 regulators, but extended with LED and flash LED specific features like
7 Many LED devices expose more than one current output that can be connected
8 to one or more discrete LED component. Since the arrangement of connections
9 can influence the way of the LED device initialization, the LED components
10 have to be tightly coupled with the LED device binding. They are represented
11 by child nodes of the parent LED device binding.
14 - led-sources : List of device current outputs the LED is connected to. The
16 in the LED device binding documentation.
17 - label : The label for this LED. If omitted, the label is taken from the node
[all …]
Dleds-ns2.txt1 Binding for dual-GPIO LED found on Network Space v2 (and parents).
6 Each LED is represented as a sub-node of the ns2-leds device.
9 - cmd-gpio: Command LED GPIO. See OF device-tree GPIO specification.
10 - slow-gpio: Slow LED GPIO. See OF device-tree GPIO specification.
13 - label: Name for this LED. If omitted, the label is taken from the node name.
14 - linux,default-trigger: Trigger assigned to the LED.
Dleds-gpio.txt6 Each LED is represented as a sub-node of the gpio-leds device. Each
7 node's name represents the name of the corresponding LED.
9 LED sub-node properties:
10 - gpios : Should specify the LED's GPIO, see "gpios property" in
17 - default-state: (optional) The initial state of the LED. Valid
18 values are "on", "off", and "keep". If the LED is already on or off
20 glitch should be produced where the LED momentarily turns off (or
21 on). The "keep" setting will keep the LED at whatever its current
41 /* Keep LED on if BIOS detected hardware fault */
Dregister-bit-led.txt5 single LED. The register bit LEDs appear as children to the
10 Each LED is represented as a sub-node of the syscon device. Each
11 node's name represents the name of the corresponding LED.
13 LED sub-node properties:
17 - offset : register offset to the register controlling this LED
18 - mask : bit mask for the bit controlling this LED in the register
26 - default-state: (optional) The initial state of the LED. Valid
27 values are "on", "off", and "keep". If the LED is already on or off
29 glitch should be produced where the LED momentarily turns off (or
30 on). The "keep" setting will keep the LED at whatever its current
Dleds-pwm.txt1 LED connected to PWM
6 Each LED is represented as a sub-node of the pwm-leds device. Each
7 node's name represents the name of the corresponding LED.
9 LED sub-node properties:
15 - max-brightness : Maximum brightness possible for the LED
16 - active-low : (optional) For PWMs where the LED is wired to supply
32 /* provides one PWM (id 0 for Charing indicator LED) */
Dleds-lp8860.txt1 * Texas Instruments - lp8860 4-Channel LED Driver
3 The LP8860-Q1 is an high-efficiency LED
16 - supply - "vled" - LED supply
Dtca6507.txt15 LED sub-node properties:
17 - reg : number of LED line (could be from 0 to 6)
Dpca963x.txt13 LED sub-node properties:
15 - reg : number of LED line (could be from 0 to 3 in pca9632 or pca9633,
Dleds-pm8941-wled.txt10 - linux,default-trigger: Default trigger assigned to the LED
Dleds-lp55xx.txt33 3 LED channels, external clock used. Channel names are 'lp5521_pri:channel0',
61 9 LED channels with specific name. Internal clock used.
/linux-4.1.27/drivers/leds/
DKconfig9 bool "LED Support"
11 Say Y to enable Linux LED support. This allows control of supported
20 tristate "LED Class Support"
26 tristate "LED Flash Class Support"
30 It wrapps LED Class and adds flash LEDs specific sysfs attributes
32 for the flash related features of a LED device. It can be built
35 comment "LED drivers"
38 tristate "LED Support for Marvell 88PM860x PMIC"
42 This option enables support for on-chip LED drivers found on Marvell
56 tristate "LED support for LM3533"
[all …]
/linux-4.1.27/arch/cris/arch-v32/
DKconfig14 prompt "Nbr of Ethernet LED groups"
18 Select how many Ethernet LED groups that can be used. Usually one per Ethernet
22 bool "Use zero LED groups"
27 bool "Use one LED group"
29 Select this if you want one Ethernet LED group. This LED group
31 recommended that each Ethernet interface use a dedicated LED group.
34 bool "Use two LED groups"
36 Select this if you want two Ethernet LED groups. This is the
43 string "Ethernet LED group 0 green LED bit"
47 Bit to use for the green LED in Ethernet LED group 0.
[all …]
/linux-4.1.27/arch/cris/arch-v10/
DKconfig18 prompt "Product LED port"
25 The ETRAX network driver is responsible for flashing LED's when
35 The ETRAX network driver is responsible for flashing LED's when
45 The ETRAX network driver is responsible for flashing LED's when
56 Select this option if you don't have any LED at all.
61 int "First green LED bit"
65 Bit to use for the first green LED.
69 int "First red LED bit"
73 Bit to use for the first red LED.
75 For products with only one controllable LED,
[all …]
/linux-4.1.27/Documentation/leds/
Dleds-class-flash.txt2 Flash LED handling under Linux
5 Some LED devices provide two modes - torch and flash. In the LED subsystem
6 those modes are supported by LED class (see Documentation/leds/leds-class.txt)
7 and LED Flash class respectively. The torch mode related features are enabled
12 must be defined in the kernel config. A LED Flash class driver must be
13 registered in the LED subsystem with led_classdev_flash_register function.
15 Following sysfs attributes are exposed for controlling flash LED devices:
Dleds-class.txt2 LED handling under Linux
8 In its simplest form, the LED class just allows control of LEDs from
10 LED is defined in max_brightness file. The brightness file will set the brightness
11 of the LED (taking a value 0-max_brightness). Most LEDs don't have hardware
14 The class also introduces the optional concept of an LED trigger. A trigger
21 Complex triggers whilst available to all LEDs have LED specific
22 parameters and work on a per LED basis. The timer trigger is an example.
23 The timer trigger will periodically change the LED brightness between
26 You can change the brightness value of a LED independently of the timer
44 LED Device Naming
[all …]
Dledtrig-oneshot.txt1 One-shot LED Trigger
4 This is a LED trigger useful for signaling the user of an event where there are
7 happened, than the trigger turns the LED on and than keeps it off for a
15 A one-shot LED only stays in a constant state when there are no events. An
16 additional "invert" property specifies if the LED has to stay off (normal) or
24 This adds the following sysfs attributes to the LED:
26 delay_on - specifies for how many milliseconds the LED has to stay at
30 delay_off - specifies for how many milliseconds the LED has to stay at
35 ms, then blink off for delay_off ms, leaving the LED normally off. If
37 leaving the LED normally on.
[all …]
Dledtrig-transient.txt1 LED Transient Trigger
7 to be off. The delay_on value specifies the time period an LED should stay
8 in on state, followed by a delay_off value that specifies how long the LED
32 class device, the LED state does not change.
35 trigger will be called, and LED state is changed to LED_OFF.
37 Driver suspend changes the LED state to LED_OFF and resume doesn't change
39 suspend and resume actions and the currently enabled trigger. LED state
42 being able to actually change the LED state. Once driver is resumed, triggers
45 LED state changes are controlled using brightness which is a common led
52 registration, the LED state does not change, unless there is another trigger
[all …]
D00-INDEX4 - Driver for BlinkM LED-devices.
6 - documents LED handling under Linux.
20 - One-shot LED trigger for both sporadic and dense events.
22 - LED Transient Trigger, one shot timer activation.
Dleds-lp55xx.txt12 Create LED class devices for multiple output channels
14 Program memory for running LED patterns
26 control multi output LED channels such as led current, channel index.
30 For example, LP5521 has maximum 3 LED channels.
52 Setting LED output current
59 various LED patterns.
77 It is used for selecting LED output(s) at each engine number.
108 Full LED strings are selected by 'engine2_leds'.
155 loading a LED pattern. That is 'predefined' pattern.
190 echo 1 > /sys/bus/i2c/devices/xxxx/led_pattern # red blinking LED pattern
[all …]
Dleds-lp5562.txt4 * TI LP5562 LED Driver
14 LP5562 has the internal program memory for running various LED patterns.
23 This attribute is used for programming LED data with the firmware interface.
27 LED Map
62 Like LP5521 and LP5523/55231, LP5562 provides LED current settings.
Dleds-lm3556.txt5 1.5 A Synchronous Boost LED Flash Driver w/ High-Side Current Source
17 In Flash Mode, the LED current source(LED) provides 16 target current levels
32 In Torch Mode, the current source(LED) is programmed via the CURRENT CONTROL
Dleds-blinkm.txt3 They are RGB-LED modules driven by a (AT)tiny microcontroller and
14 a) LED class interface for use with triggers
Dleds-lp5523.txt30 LP5523 has the internal program memory for running various LED patterns.
31 There are two ways to run LED patterns.
Dleds-lp5521.txt20 LP5521 has the internal program memory for running various LED patterns.
21 There are two ways to run LED patterns.
/linux-4.1.27/drivers/leds/trigger/
DKconfig2 bool "LED Trigger support"
12 tristate "LED Timer Trigger"
16 via sysfs. Some LED hardware can be programmed to start
17 blinking the LED without any further software interaction.
23 tristate "LED One-shot Trigger"
29 or on dense events, where this blinks the LED at constant rate if
37 bool "LED IDE Disk Trigger"
45 tristate "LED Heartbeat Trigger"
54 tristate "LED backlight Trigger"
63 bool "LED CPU Trigger"
[all …]
/linux-4.1.27/Documentation/ABI/testing/
Dsysfs-class-led-flash6 Set the brightness of this LED in the flash strobe mode, in
7 microamperes. The file is created only for the flash LED devices
18 Maximum brightness level for this LED in the flash strobe mode,
28 of the strobe. The file is created only for the flash LED
36 Maximum flash timeout for this LED, in microseconds.
58 * led-over-voltage - flash controller voltage to the flash LED
67 * led-power-supply-over-current - current in the LED power
71 a short or open circuit condition on the indicator LED
73 LED has been below the minimum limit specific to
79 * led-over-temperature - the temperature of the LED has exceeded
Dsysfs-class-led6 Set the brightness of the LED. Most LEDs don't
23 Set the trigger for this LED. A trigger is a kernel based source
34 Invert the LED on/off state. This parameter is specific to
36 it is useful when driving a LED which is intended to indicate
Dsysfs-platform-asus-laptop29 Some models like the W1N have a LED display that can be
31 To control the LED display, use the following :
Dsysfs-class-leds-gt683r7 of one LED will update the mode of its two sibling devices as
Dsysfs-platform-msi-laptop47 on. In turbo mode power LED is orange and processor is
60 In ECO mode power LED is green and userspace should do some
Dsysfs-driver-wacom27 Writing to this file sets the status LED luminance (1..127)
36 Writing to this file sets the status LED luminance (1..127)
/linux-4.1.27/drivers/mfd/
Ddm355evm_msp.c102 MSP_GPIO(0, LED), MSP_GPIO(1, LED),
103 MSP_GPIO(2, LED), MSP_GPIO(3, LED),
104 MSP_GPIO(4, LED), MSP_GPIO(5, LED),
105 MSP_GPIO(6, LED), MSP_GPIO(7, LED),
DKconfig269 tristate "HTC PASIC3 LED/DS1WM chip support"
272 This core driver provides register access for the LED/DS1WM
549 The device supports multiple sub-devices like LED, HWMON and WDT.
700 sub-devices like charger, fuel gauge, flash LED, current source,
985 With these functionalities, it can be used for LED string control or
1025 high-power "white LED driver". This boost converter is
1071 tristate "TI TPS65217 Power Management / White LED chips"
1077 Power Management / White LED chips.
1246 additional drivers must be enabled in order to use the LED,
/linux-4.1.27/Documentation/devicetree/bindings/pwm/
Dti,twl-pwmled.txt1 Texas Instruments TWL series PWM drivers connected to LED terminals
5 On TWL6030 series: LED PWM (mainly used as charging indicator LED)
Dnxp,pca9685-pwm.txt1 NXP PCA9685 16-channel 12-bit PWM LED controller
Dpwm-lp3943.txt17 PWM 0 is for RGB LED brightness control
/linux-4.1.27/Documentation/networking/
Dskfp.txt125 The functionality of the LED's on the FDDI network adapters was
127 LED works as a ring operational indicator. An active yellow LED
128 indicates that the ring is down. The green LED on the adapter now
129 works as a link indicator where an active GREEN LED indicates that
133 yellow LED was off while the green LED(s) showed the connection
134 status of the adapter. During a ring down the green LED was off and
135 the yellow LED was on.
184 - New SMT module included, changing LED functionality
D6pack.txt74 and the status LED are lit for about a second if the firmware initialises
131 FlexNet, the connect LED is on if there is a connection; the status LED is
136 as they are in KISS mode: The connect LED is turned on if data is transferred
137 from the PC to the TNC over the serial line, the status LED if data is
DREADME.ipw2200173 Can be used to turn on experimental LED code.
309 0 = LED code disabled
310 1 = LED code enabled
312 0 = Disable LED code
313 1 = Enable LED code
315 NOTE: The LED code has been reported to hang some systems when
Dcs89x0.txt433 adapter's cable is connected to the network (check for LED activity for
492 Link Integrity LED: A "steady" ON of the green LED indicates a valid 10Base-T
493 connection. (Only applies to 10Base-T. The green LED has no significance for
496 TX/RX LED: The yellow LED lights briefly each time the adapter transmits or
497 receives data. (The yellow LED will appear to "flicker" on a typical network.)
Diphase.txt44 LED on the front panel of the adapter will be on if the adapter is
61 The yellow 'status' LED on the front panel of the adapter will blink
Darcnet-hardware.txt349 Also, on many cards (not mine, though) there are red and green LED's.
716 The green LED monitors the network activity: the red one shows the
943 The green LED monitors the network activity: the red one shows the
1195 the red transmit LED to blink, is the one that I thought works.
1198 ARCETHER packet driver loaded fine, but without the red LED
1291 | LED |___|
1506 > |oo| JP2 | | LED |___|
1507 < |oo| JP1 | 9026 | LED |___|
1539 LED
1667 | | SW1 | LED |__|
[all …]
Ds2io.txt37 The corresponding adapter's LED will blink multiple times.
/linux-4.1.27/arch/cris/arch-v32/mach-a3/
DKconfig54 There are some guidelines though - if you know that only LED's are
57 LED's at the general ports, these bits are used for all kinds of
74 There are some guidelines though - if you know that only LED's are
77 LED's at the general ports, these bits are used for all kinds of
94 There are some guidelines though - if you know that only LED's are
97 LED's at the general ports, these bits are used for all kinds of
/linux-4.1.27/arch/cris/arch-v32/mach-fs/
DKconfig92 There are some guidelines though - if you know that only LED's are
95 LED's at the general ports, these bits are used for all kinds of
114 There are some guidelines though - if you know that only LED's are
117 LED's at the general ports, these bits are used for all kinds of
136 There are some guidelines though - if you know that only LED's are
139 LED's at the general ports, these bits are used for all kinds of
158 There are some guidelines though - if you know that only LED's are
161 LED's at the general ports, these bits are used for all kinds of
180 There are some guidelines though - if you know that only LED's are
183 LED's at the general ports, these bits are used for all kinds of
/linux-4.1.27/arch/arm/boot/dts/
Domap3-ha-common.dtsi31 OMAP3_CORE1_IOPAD(0x2110, PIN_OUTPUT | MUX_MODE4) /* cam_xclka gpio_96, LED blue */
37 OMAP3_CORE1_IOPAD(0x2126, PIN_OUTPUT | MUX_MODE4) /* cam_d8 gpio_107, LED green */
43 OMAP3_CORE1_IOPAD(0x212e, PIN_OUTPUT_PULLUP | MUX_MODE4) /* cam_xclkb gpio_111, LED red */
Dorion5x-maxtor-shared-storage-2.dts125 * MPP0: Power LED
126 * MPP1: Error LED
163 * GPIO 23: Blue front LED off
Dorion5x-lacie-d2-network.dts190 * MPP6: Red front LED
191 * MPP16: Blue front LED blink control
221 * GPIO 23: Blue front LED off
Dstih416-b2020e.dts21 label = "Front Panel LED";
Dstihxxx-b2120.dtsi19 label = "Front Panel LED";
Dstih418-b2199.dts38 label = "Front Panel LED";
Dstih41x-b2020.dtsi34 label = "Front Panel LED";
Dintegrator.dtsi12 /* Use core module LED to indicate CPU load */
Dtwl6030.dtsi98 /* provides one PWM (id 0 for Charging indicator LED) */
Dstih41x-b2000.dtsi37 label = "Front Panel LED";
Dimx6qdl-phytec-pfla02.dtsi217 MX6QDL_PAD_ENET_TXD0__GPIO1_IO30 0x80000000 /* Green LED */
218 MX6QDL_PAD_EIM_EB3__GPIO2_IO31 0x80000000 /* Red LED */
Dat91-foxg20.dts147 /* red LED marked "PC7" near mini USB (device) receptacle */
Domap3-beagle-xm.dts37 gpios = <&gpio5 22 GPIO_ACTIVE_HIGH>; /* 150 -> D6 LED */
43 gpios = <&gpio5 21 GPIO_ACTIVE_HIGH>; /* 149 -> D7 LED */
Dste-nomadik-s8815.dts116 /* The user LED on the board is set up to be used for heartbeat */
Dat91-ariag25.dts172 /* little green LED in middle of Aria G25 module */
Domap3-beagle.dts41 gpios = <&gpio5 22 GPIO_ACTIVE_HIGH>; /* 150 -> D6 LED */
47 gpios = <&gpio5 21 GPIO_ACTIVE_HIGH>; /* 149 -> D7 LED */
Dkirkwood-topkick.dts112 * GPIO LED layout
Dkirkwood-b3.dts127 * There is one LED "port" on the front and the colours
Dste-hrefv60plus.dtsi62 * LED on IP GPIO 4 (XENON_EN2) on altfunction C, that need bias
Dsun9i-a80-optimus.dts75 /* The LED names match those found on the board */
Dimx6dl-riotboard.dts202 reg_vgen5_2v5_sgtl: vgen5 { /* Pwr LED & 5V0_delayed enable */
Dimx53-tx53.dtsi260 /* MX53_PAD_EIM_A18__GPIO2_20 0x1f4 used by LED */
Dimx6qdl-tx6.dtsi301 MX6QDL_PAD_EIM_A18__GPIO2_IO20 0x1b0b1 /* LED */
Domap5-uevm.dts71 gpios = <&gpio5 25 GPIO_ACTIVE_HIGH>; /* gpio5_153 D1 LED */
Dimx28-tx28.dts507 MX28_PAD_ENET0_RXD3__GPIO_4_10 /* module LED */
/linux-4.1.27/arch/sh/drivers/
DKconfig7 bool "Heartbeat LED"
9 Use the power-on LED on your machine as a load meter. The exact
/linux-4.1.27/Documentation/laptops/
Dasus-laptop.txt37 - LED control
38 - LED Display control
73 will switch the mail LED on.
87 (only on models with Bluetooth). This usually controls the associated LED.
176 LED display
179 Some models like the W1N have a LED display that can be used to display
182 LED display works for the following models:
186 To control the LED display, use the following :
Dthinkpad-acpi.txt40 - LED control
664 sysfs attributes: as per LED class, for the "tpacpi::thinklight" LED
677 The ThinkLight sysfs interface is documented by the LED class
678 documentation, in Documentation/leds/leds-class.txt. The ThinkLight LED name
681 Due to limitations in the sysfs LED class, if the status of the ThinkLight
722 LED control
726 sysfs attributes: as per LED class, see below for names
728 Some of the LED indicators can be controlled through this feature. On
730 LED indicators as well. Newer ThinkPads cannot query the real status
731 of the LED indicators.
[all …]
/linux-4.1.27/Documentation/zh_CN/
Dgpio.txt71 插入/移除、检测卡的写保护状态、驱动 LED、配置收发器、模拟串行总线、
340 { 32, GPIOF_OUT_INIT_HIGH, "Power LED" }, /* 默认开启 */
341 { 33, GPIOF_OUT_INIT_LOW, "Green LED" }, /* 默认关闭 */
342 { 34, GPIOF_OUT_INIT_LOW, "Red LED" }, /* 默认关闭 */
343 { 35, GPIOF_OUT_INIT_LOW, "Blue LED" }, /* 默认关闭 */
544 注意：标准内核驱动中已经存在通用的“LED 和按键”GPIO 任务，分别是:
/linux-4.1.27/firmware/
Dwhiteheat_loader.HEX303 * Port 1 LED flashes when the vend_ax program is running
304 * Port 2 LED flashes when any SETUP command arrives
305 * Port 3 LED flashes when any valid VENDOR request occurs
306 * Port 4 LED flashes when the EXTERNAL RAM DOWNLOAD request occurs
Dwhiteheat_loader_debug.HEX392 * Port 1 LED flashes when the vend_ax program is running
393 * Port 2 LED flashes when any SETUP command arrives
394 * Port 3 LED flashes when any valid VENDOR request occurs
395 * Port 4 LED flashes when the EXTERNAL RAM DOWNLOAD request occurs
Dwhiteheat.HEX1086 * Port 1 LED flashes when the vend_ax program is running
1087 * Port 2 LED flashes when any SETUP command arrives
1088 * Port 3 LED flashes when any valid VENDOR request occurs
1089 * Port 4 LED flashes when the EXTERNAL RAM DOWNLOAD request occurs
DWHENCE267 Port 1 LED flashes when the vend_ax program is running
268 Port 2 LED flashes when any SETUP command arrives
269 Port 3 LED flashes when any valid VENDOR request occurs
270 Port 4 LED flashes when the EXTERNAL RAM DOWNLOAD request occurs
/linux-4.1.27/drivers/pinctrl/
Dpinctrl-falcon.c123 MFP_FALCON(GPIO9, LED, GPIO, NONE, NONE),
124 MFP_FALCON(GPIO10, LED, GPIO, NONE, NONE),
125 MFP_FALCON(GPIO11, LED, GPIO, NONE, NONE),
126 MFP_FALCON(GPIO12, LED, GPIO, NONE, NONE),
127 MFP_FALCON(GPIO13, LED, GPIO, NONE, NONE),
128 MFP_FALCON(GPIO14, LED, GPIO, NONE, NONE),
195 GRP_MUX("bootled", LED, pins_bled),
Dpinctrl-palmas.c312 FUNCTION_GROUP(led, LED), \
471 PIN_INFO(led1, LED, NULL, NULL);
472 PIN_INFO(led2, LED, NULL, NULL);
/linux-4.1.27/Documentation/devicetree/bindings/net/
Dmicrel.txt7 - micrel,led-mode : LED mode value to set for PHYs with configurable LEDs.
9 Configure the LED mode with single value. The list of PHYs and the
/linux-4.1.27/Documentation/devicetree/bindings/mfd/
Dmc13xxx.txt22 Each led node should contain "reg", which used as LED ID (described below).
28 MC13783 LED IDs:
42 MC13892 LED IDs:
50 MC34708 LED IDs:
Dmfd.txt10 silicon) that handles analog drivers for things like audio amplifiers, LED
Dmax77693.txt6 - LED,
/linux-4.1.27/arch/frv/kernel/
Dhead-mmu-fr451.S50 # GR30 LED address [saved]
76 # GR30 LED address revised LED address
159 # adjust LED bank address
173 # GR30 LED address [saved]
227 # GR30 LED address [saved]
Dhead-uc-fr401.S49 # GR30 LED address [saved]
83 # GR30 LED address revised LED address
166 # adjust LED bank address
178 # GR30 LED address [saved]
238 # GR30 LED address [saved]
Dhead-uc-fr555.S48 # GR30 LED address [saved]
74 # GR30 LED address revised LED address
152 # adjust LED bank address
166 # GR30 LED address [saved]
221 # GR30 LED address saved
Dhead-uc-fr451.S44 # GR30 LED address [saved]
Dhead.S560 # GR30 LED address [saved]
/linux-4.1.27/drivers/parisc/
DKconfig129 bool "Chassis LCD and LED support"
137 This has nothing to do with LED State support for A and E class.
146 That includes support for LED State front panel as found on E
147 class, and support for the GSP Virtual Front Panel (LED State and
152 shown by the LED/LCD driver.
153 This driver updates the state panel (LED and/or LCD) upon system
/linux-4.1.27/drivers/media/usb/pwc/
Dphilips.txt84 turn off the LED. Not all cameras support this though (the 645 and 646
110 This settings takes 2 integers, that define the on/off time for the LED
112 this is let the LED blink while the camera is in use. This:
116 will blink the LED once every second. But with:
120 the LED never goes on, making it suitable for silent surveillance.
122 By default the camera's LED is on solid while in use, and turned off
127 the LED cannot be controlled.
130 open the camera device. Until then, the LED remains on.
/linux-4.1.27/arch/powerpc/boot/dts/
Dmotionpro.dts16 &gpt6 { // Motion-PRO status LED
21 &gpt7 { // Motion-PRO ready LED
Dsbc8548.dts60 0x0 0x0 0x5 0x000000 0x1fff /* LED */
Dsbc8548-altflash.dts63 0x0 0x0 0x5 0x000000 0x1fff /* LED */
/linux-4.1.27/arch/m32r/platforms/mappi/
Ddot.gdbinit37 # LED ON
41 # LED OFF
45 P5=LED(output), P6.b4=LAN_RESET(output)
79 # Reset (P5=LED,P6.b4=LAN_RESET)
Ddot.gdbinit.nommu37 # LED ON
41 # LED OFF
45 P5=LED(output), P6.b4=LAN_RESET(output)
79 # Reset (P5=LED,P6.b4=LAN_RESET)
Ddot.gdbinit.smp100 # LED ON
104 # LED OFF
108 P5=LED(output), P6.b4=LAN_RESET(output)
144 # Reset (P5=LED,P6.b4=LAN_RESET)
/linux-4.1.27/drivers/macintosh/
DKconfig91 bool "Support for the Power/iBook front LED"
96 Support the front LED on Power/iBooks as a generic LED that can
99 and the ide-disk LED trigger and configure appropriately through
103 bool "Use front LED as IDE LED by default"
110 This option makes the front LED default to the IDE trigger
/linux-4.1.27/Documentation/auxdisplay/
Dcfag12864b78 Ground (18)---[GND] [+5v]---(19) LED +
85 Ground (25)---[GND] [GND]---[P2]---[R]---(20) LED -
/linux-4.1.27/Documentation/devicetree/bindings/iio/light/
Dcm36651.txt8 - vled-supply: regulator for the IR LED. IR_LED is a part
/linux-4.1.27/Documentation/sound/alsa/
DHD-Audio-Models.txt257 hp-dv4-1222nr HP dv4-1222nr (with LED support)
281 hp-led HP with broken BIOS for mute LED
282 hp-inv-led HP with broken BIOS for inverted mute LED
283 hp-mic-led HP with mic-mute LED
292 hp-led LED support for HP laptops
DALSA-Configuration.txt2138 - mute_led Bind EAPD bit for turning on/off mute LED
/linux-4.1.27/Documentation/devicetree/bindings/gpio/
Dgpio-lp3943.txt10 Simple LED controls with LP3943 GPIO controller
/linux-4.1.27/arch/m68k/
DKconfig.devices11 bool "Use power LED as a heartbeat" if AMIGA || APOLLO || ATARI || Q40
14 Use the power-on LED on your machine as a load meter. The exact
18 # We have a dedicated heartbeat LED. :-)
/linux-4.1.27/Documentation/video4linux/
Dsi470x.txt122 There is a LED interface, which can be used to override the LED control
123 programmed in the firmware. This can be made available using the LED support
/linux-4.1.27/arch/unicore32/configs/
Dunicore32_defconfig157 # LED Support
161 # LED Triggers
/linux-4.1.27/Documentation/input/
Dwalkera0701.txt26 / O 4 3 O \ pin 3 (GND) LED ________________ 10 ACK
34 I use green LED and BC109 NPN transistor.
Dyealink.txt8 - LED full support, yealink.ko / sysfs API
170 LED
/linux-4.1.27/net/rfkill/
DKconfig13 # LED trigger support
/linux-4.1.27/arch/cris/
DKconfig304 prompt "Network LED behavior"
311 Selecting LED_on_when_link will light the LED when there is a
314 Selecting LED_on_when_activity will light the LED only when
323 Selecting LED_on_when_link will light the LED when there is a
326 Selecting LED_on_when_activity will light the LED only when
/linux-4.1.27/drivers/gpu/drm/panel/
DKconfig41 the host and has a built-in LED backlight.
/linux-4.1.27/Documentation/devicetree/bindings/video/backlight/
Dlp855x.txt65 /* 4V OV, 4 output LED string enabled */
/linux-4.1.27/drivers/usb/
DKconfig155 bool "USB LED Triggers"
158 This option adds LED triggers for USB host and/or gadget activity.
/linux-4.1.27/Documentation/devicetree/bindings/sound/
Dcs35l32.txt20 of the two: Class G or adaptive LED voltage.
/linux-4.1.27/drivers/net/can/
DKconfig56 bool "Enable LED triggers for Netlink based drivers"
60 This option adds two LED triggers for packet receive and transmit
/linux-4.1.27/drivers/input/keyboard/
Dlkkbd.c266 #define CHECK_LED(LK, VAR_ON, VAR_OFF, LED, BITS) do { \ argument
267 if (test_bit(LED, (LK)->dev->led)) \
/linux-4.1.27/drivers/sbus/char/
DKconfig63 This is the driver for the 7-segment display and LED present on
/linux-4.1.27/arch/cris/boot/rescue/
Dkimagerescue.S88 moveq 0, $r1 ; "timer" to clock out a LED red flash
Dhead_v10.S255 moveq 0, $r1 ; "timer" to clock out a LED red flash
/linux-4.1.27/drivers/input/joystick/
DKconfig302 bool "LED Support for Xbox360 controller 'BigX' LED"
305 This option enables support for the LED which surrounds the Big X on
/linux-4.1.27/drivers/pwm/
DKconfig229 Generic PWM framework driver for NXP PCA9685 LED controller.
359 tristate "TWL4030/6030 PWM support for LED drivers"
362 Generic PWM framework driver for TWL4030/6030 LED terminals.
/linux-4.1.27/drivers/net/wireless/b43legacy/
DKconfig37 # LED support
/linux-4.1.27/firmware/keyspan_pda/
Dxircom_pgs.S757 mov a, #0x20 ; Turn off the green LED
765 mov a, #0x20 ; Turn off the green LED
787 mov a, #0x10 ; Turn the green LED
837 mov a, #0x20 ; Turn off the green LED
1053 mov a, #0x10 ; Turn the green LED
/linux-4.1.27/Documentation/devicetree/bindings/arm/
Dvexpress-sysreg.txt30 - for sys_led : 0..7 = LED 0..7
/linux-4.1.27/net/mac80211/
DKconfig85 bool "Enable LED triggers"
90 This option enables a few LED triggers for different
/linux-4.1.27/Documentation/power/
Dpower_supply_class.txt23 It also integrates with LED framework, for the purpose of providing
27 user and/or specific machine defaults, per design principles of LED
/linux-4.1.27/Documentation/ptp/
Dptp.txt81 - 6 GPIOs with dedicated functions (LED/JTAG/clock) can also be
/linux-4.1.27/drivers/platform/x86/
DKconfig34 exposes the mail LED and LCD backlight.
406 Overriding LED state on ThinkPads can mask important
411 LED control on the ThinkPad is write-only (with very few
414 be lost when one changes LED state.
417 and the driver will allow control of every LED, including
809 function keys, wireless LED, LCD backlight level.
/linux-4.1.27/drivers/media/usb/gspca/
Dsonixj.c116 #define LED 0x08 /* output to pin LED */ macro
2514 reg01 |= LED; in sd_stopN()
2516 reg01 &= ~(LED | V_TX_EN); in sd_stopN()
2560 reg01 |= LED; in sd_stopN()
/linux-4.1.27/arch/arm/mach-omap1/
DKconfig76 touchscreen, PDA-ish buttons, a resume button, bicolor LED,
/linux-4.1.27/drivers/usb/misc/
DKconfig42 tristate "USB 7-Segment LED Display"
83 tristate "USB LED driver support"
/linux-4.1.27/arch/mips/boot/dts/cavium-octeon/
Docteon_3xxx.dts64 /* Adjust LED drive. */
76 /* Adjust LED drive. */
Docteon_68xx.dts65 /* Adjust LED drive. */
/linux-4.1.27/net/netfilter/
DKconfig739 tristate '"LED" target support'
743 This option adds a `LED' target, which allows you to blink LEDs in
746 This can be used to turn a spare LED into a network activity LED,
748 you could have an LED which lights up for a minute or two every time
753 To create an LED trigger for incoming SSH traffic:
754 iptables -A INPUT -p tcp --dport 22 -j LED --led-trigger-id ssh --led-delay 1000
756 Then attach the new trigger to an LED on your system:
/linux-4.1.27/drivers/hid/
DKconfig276 tristate "MSI GT68xR LED support"
776 tristate "ThingM blink(1) USB RGB LED"
780 Support for the ThingM blink(1) USB RGB LED. This driver registers a
781 Linux LED class instance, plus additional sysfs attributes to control
/linux-4.1.27/Documentation/scsi/
Dsym53c8xx_2.txt36 10.2.3 LED support
459 10.2.3 LED support
460 led=1 enable LED support
461 led=0 disable LED support
462 Do not enable LED support if your scsi board does not use SDMS BIOS.
DChangeLog.sym53c8xx_294 - Add Tekram 390 U2B/U2W SCSI LED handling.
Dncr53c8xx.txt45 10.2.12 LED support
596 Genuine SYMBIOS boards use GPIO0 in output for controller LED and GPIO3
764 10.2.12 LED support
765 led:1 enable LED support
766 led:0 disable LED support
767 Donnot enable LED support if your scsi board does not use SDMS BIOS.
872 LED support disabled led:0
Dlibsas.txt343 you e.g., change the meaning of the READY LED MEANING
Daic79xx.txt139 - Add a firmware workaround to make the LED blink
DChangeLog.sym53c8xx510 - Add support for hardware LED control of the 896.
DChangeLog.1992-1997136 status bytes. Added blink LED state checks for ISA and EISA HBAs.
/linux-4.1.27/Documentation/devicetree/bindings/i2c/
Dtrivial-devices.txt93 skyworks,sky81452 Skyworks SKY81452: Six-Channel White LED Driver with Touch Panel Bias Supply
/linux-4.1.27/Documentation/devicetree/bindings/pinctrl/
Drenesas,pfc-pinctrl.txt122 Example 2: A GPIO LED node that references a GPIO
/linux-4.1.27/arch/m68k/q40/
DREADME81 keyboard interface, 1 Programmable LED, 2x8bit DACs and up to 1MB ROM, 1MB
/linux-4.1.27/Documentation/gpio/
Dgpio-legacy.txt52 a LED, configuring a transceiver, bitbanging a serial bus, poking a hardware
361 { 32, GPIOF_OUT_INIT_HIGH, "Power LED" }, /* default to ON */
362 { 33, GPIOF_OUT_INIT_LOW, "Green LED" }, /* default to OFF */
363 { 34, GPIOF_OUT_INIT_LOW, "Red LED" }, /* default to OFF */
364 { 35, GPIOF_OUT_INIT_LOW, "Blue LED" }, /* default to OFF */
Dgpio.txt65 a LED, configuring a transceiver, bit-banging a serial bus, poking a hardware
Dconsumer.txt35 If a function is implemented by using several GPIOs together (e.g. a simple LED
/linux-4.1.27/arch/sparc/
DKconfig362 tristate "Sun4m LED driver"
365 This driver toggles the front-panel LED on sun4m systems
/linux-4.1.27/arch/arm/plat-samsung/
DKconfig265 bool "SMDK LED suspend/resume debugging"
/linux-4.1.27/drivers/input/
Dinput.c1478 INPUT_DEV_CAP_ATTR(LED, led);
1646 INPUT_DO_TOGGLE(dev, LED, led, activate); in input_dev_toggle()
2019 INPUT_CLEANSE_BITMASK(dev, LED, led); in input_cleanse_bitmasks()
/linux-4.1.27/Documentation/driver-model/
Ddevres.txt293 LED
/linux-4.1.27/Documentation/arm/Samsung-S3C24XX/
DOverview.txt258 in the LED subsystem.
/linux-4.1.27/Documentation/usb/
Dgadget_hid.txt109 to the caps lock LED status.
/linux-4.1.27/drivers/scsi/aic7xxx/
Daic79xx.seq126 * On Rev A. hardware, the busy LED is only
128 * and re-selections. Make the LED status
620 * On Rev A. hardware, the busy LED is only
622 * and re-selections. Make the LED status
673 * On Rev A. hardware, the busy LED is only
675 * and re-selections. Make the LED status
/linux-4.1.27/Documentation/dvb/
DREADME.dvb-usb156 the right place and the device is connected, the "Power"-LED should be
/linux-4.1.27/drivers/video/backlight/
DKconfig382 This supports TI LM3639 Backlight + 1.5A Flash LED Driver
/linux-4.1.27/Documentation/fmc/
Dcarrier.txt277 If, for example, a driver requires a free LED and a test point (for a
/linux-4.1.27/Documentation/hid/
Dhid-transport.txt119 to device and may include LED requests, rumble requests or more. Output
/linux-4.1.27/drivers/net/ethernet/qlogic/qlge/
Dqlge.h804 LED = 0x18, enumerator
/linux-4.1.27/Documentation/
D00-INDEX285 - directory with info about LED handling under Linux.
Dkernel-parameters.txt2070 LED. This parameter is not necessary when using the
/linux-4.1.27/drivers/input/misc/
DKconfig395 rotation. The dial also acts as a pushbutton. The base contains an LED
/linux-4.1.27/
DCREDITS839 D: PA-RISC Linux hacker, LASI-, ASP-, WAX-, LCD/LED-driver
1404 D: fixed keyboard driver to separate LED and locking status
3721 D: Author of PCA9532 LED and Fintek f75375s hwmon driver
DMAINTAINERS1652 AS3645A LED FLASH CONTROLLER DRIVER
2050 BLINKM RGB LED DRIVER
5821 LED SUBSYSTEM
7461 PCA9532 LED DRIVER
9184 SOEKRIS NET48XX LED SUPPORT
9841 THINGM BLINK(1) USB RGB LED DRIVER
/linux-4.1.27/arch/x86/
DKconfig2425 bool "PCEngines ALIX System Support (LED setup)"
2433 Note: You must still enable the drivers for GPIO and LED support