Home
last modified time | relevance | path

Searched +full:sub +full:- +full:led (Results 1 – 25 of 100) sorted by relevance

1234

/linux/include/media/
H A Dv4l2-flash-led-class.h1 /* SPDX-License-Identifier: GPL-2.0-only */
3 * V4L2 flash LED sub-device registration helpers.
12 #include <media/v4l2-ctrls.h>
13 #include <media/v4l2-subdev.h>
21 * struct v4l2_flash_ctrl_data - flash control initialization data, filled
22 * basing on the features declared by the LED flash
34 * struct v4l2_flash_ops - V4L2 flash operations
53 * struct v4l2_flash_config - V4L2 Flash sub-device initialization data
56 * @intensity: non-flash strobe constraints for the LED
57 * @flash_faults: bitmask of flash faults that the LED flash class
[all …]
/linux/Documentation/leds/
H A Dleds-class-flash.rst2 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.rst)
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:
16 (see Documentation/ABI/testing/sysfs-class-led-flash)
18 - flash_brightness
19 - max_flash_brightness
[all …]
/linux/Documentation/devicetree/bindings/mfd/
H A Dtps6105x.txt3 The TP61050/TPS61052 is a high-power "white LED driver". The
4 device provides LED, GPIO and regulator functionalities.
7 - compatible: "ti,tps61050" or "ti,tps61052"
8 - reg: Specifies the I2C slave address
10 Optional sub-node:
15 - regulator: presence of this sub-node puts the chip in regulator mode.
18 - led: presence of this sub-node puts the chip in led mode.
20 - function : see ../leds/common.txt
21 - color : see ../leds/common.txt
22 - label : see ../leds/common.txt
[all …]
H A Dmediatek,mt6360.yaml1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Gene Chen <gene_chen@richtek.com>
13 MT6360 is a PMIC device with the following sub modules.
16 This document describes the binding for PMIC device and its sub module.
25 wakeup-source: true
30 interrupt-names:
33 interrupt-controller: true
35 "#interrupt-cells":
[all …]
H A D88pm860x.txt4 - compatible : "marvell,88pm860x"
5 - reg : the I2C slave address for the 88pm860x chip
6 - interrupts : IRQ line for the 88pm860x chip
7 - interrupt-controller: describes the 88pm860x as an interrupt controller (has its own domain)
8 - #interrupt-cells : should be 1.
9 - The cell is the 88pm860x local IRQ number
12 - marvell,88pm860x-irq-read-clr: inicates whether interrupt status is cleared by read
13 - marvell,88pm860x-slave-addr: 88pm860x are two chips solution. <reg> stores the I2C address
17 88pm860x consists of a large and varied group of sub-devices:
20 ------ ------------ -----------
[all …]
/linux/Documentation/devicetree/bindings/leds/
H A Dleds-powernv.txt2 -------------------------------------------------
5 - compatible : Should be "ibm,opal-v3-led".
6 - led-mode : Should be "lightpath" or "guidinglight".
9 form of a sub-node.
11 Required properties for the sub nodes:
12 - led-types : Supported LED types (attention/identify/fault) provided
18 compatible = "ibm,opal-v3-led";
19 led-mode = "lightpath";
21 U78C9.001.RST0027-P1-C1 {
22 led-types = "identify", "fault";
H A Dleds-lt3593.txt1 Bindings for Linear Technologies LT3593 LED controller
4 - compatible: Should be "lltc,lt3593".
5 - lltc,ctrl-gpios: A handle to the GPIO that is connected to the 'CTRL'
8 The hardware supports only one LED. The properties of this LED are
9 configured in a sub-node in the device node.
11 Optional sub-node properties:
12 - function: See Documentation/devicetree/bindings/leds/common.txt
13 - color: See Documentation/devicetree/bindings/leds/common.txt
14 - label: A label for the LED. If none is given, the LED will be
16 - linux,default-trigger: The default trigger for the LED.
[all …]
H A Dleds-spi-byte.txt1 * Single Byte SPI LED Device Driver.
4 - one LED is controlled by a single byte on MOSI
5 - the value of the byte gives the brightness between two values (lowest to
7 - no return value is necessary (no MISO signal)
15 The driver currently only supports one LED. The properties of the LED are
16 configured in a sub-node in the device node.
19 - compatible: should be one of
20 * "ubnt,acb-spi-led" microcontroller (SONiX 8F26E611LA) based device
23 Property rules described in Documentation/devicetree/bindings/spi/spi-bus.txt
26 LED sub-node properties:
[all …]
H A Dleds-lgm.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/leds/leds-lgm.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: Intel Lightning Mountain (LGM) SoC LED Serial Shift Output (SSO) Controller driver
10 - Zhu, Yi Xin <Yixin.zhu@intel.com>
11 - Amireddy Mallikarjuna reddy <mallikarjunax.reddy@intel.com>
15 const: intel,lgm-ssoled
23 clock-names:
25 - const: sso
[all …]
H A Dleds-netxbig.txt5 - compatible: "lacie,netxbig-leds".
6 - gpio-ext: Phandle for the gpio-ext bus.
9 - timers: Timer array. Each timer entry is represented by three integers:
10 Mode (gpio-ext bus), delay_on and delay_off.
12 Each LED is represented as a sub-node of the netxbig-leds device.
14 Required sub-node properties:
15 - mode-addr: Mode register address on gpio-ext bus.
16 - mode-val: Mode to value mapping. Each entry is represented by two integers:
17 A mode and the corresponding value on the gpio-ext bus.
18 - bright-addr: Brightness register address on gpio-ext bus.
[all …]
H A Dleds-gpio.yaml1 # SPDX-License-Identifier: GPL-2.0-only
3 ---
4 $id: http://devicetree.org/schemas/leds/leds-gpio.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Jacek Anaszewski <jacek.anaszewski@gmail.com>
11 - Pavel Machek <pavel@ucw.cz>
14 Each LED is represented as a sub-node of the gpio-leds device. Each
15 node's name represents the name of the corresponding LED.
19 const: gpio-leds
22 # The first form is preferred, but fall back to just 'led' anywhere in the
[all …]
H A Dleds-cr0014114.txt1 Crane Merchandising System - cr0014114 LED driver
2 -------------------------------------------------
4 This LED Board is widely used in vending machines produced
8 - compatible: "crane,cr0014114"
10 Property rules described in Documentation/devicetree/bindings/spi/spi-bus.txt
11 apply. In particular, "reg" and "spi-max-frequency" properties must be given.
13 LED sub-node properties:
14 - function :
16 - color :
18 - label :
[all …]
H A Dleds-max77650.yaml1 # SPDX-License-Identifier: GPL-2.0
3 ---
4 $id: http://devicetree.org/schemas/leds/leds-max77650.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: LED driver for MAX77650 PMIC from Maxim Integrated.
10 - Bartosz Golaszewski <bgolaszewski@baylibre.com>
16 The LED controller is represented as a sub-node of the PMIC node on
23 const: maxim,max77650-led
25 "#address-cells":
28 "#size-cells":
[all …]
H A Dleds-el15203000.txt1 Crane Merchandising System - EL15203000 LED driver
2 --------------------------------------------------
4 This LED Board (aka RED LEDs board) is widely used in
9 Vending area LED encoded with symbol 'V' (hex code 0x56).
12 Screen light tube LED which surrounds vending machine screen and
15 Water Pipe LED encoded with symbol 'P' (hex code 0x50) and
16 actually consists of 5 LEDs that exposed by protocol like one LED.
18 - cascade pattern
19 - inversed cascade pattern
20 - bounce pattern
[all …]
H A Dleds-bcm6328.yaml1 # SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
3 ---
4 $id: http://devicetree.org/schemas/leds/leds-bcm6328.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Álvaro Fernández Rojas <noltari@gmail.com>
17 as spi-gpio. See
21 exporting the 74x164 as spi-gpio prevents those LEDs to be hardware
24 BCM6328 LED controller has a HWDIS register, which controls whether a LED
27 is usually 1:1 for hardware to LED signals, but through the activity/link
29 explained later in brcm,link-signal-sources). Even if a LED is hardware
[all …]
/linux/Documentation/userspace-api/media/v4l/
H A Dmetafmt-d4xx.rst1 .. SPDX-License-Identifier: GFDL-1.1-no-invariants-or-later
4 .. _v4l2-meta-fmt-d4xx:
16 Intel D4xx (D435, D455 and others) cameras include per-frame metadata in their UVC
38 .. flat-table:: D4xx metadata
40 :header-rows: 1
41 :stub-columns: 0
43 * - **Field**
44 - **Description**
45 * - :cspan:`1` *Depth Control*
46 * - __u32 ID
[all …]
/linux/drivers/leds/
H A Dleds-spi-byte.c1 // SPDX-License-Identifier: GPL-2.0
2 // Copyright (c) 2019 Christian Mauderer <oss@c-mauderer.de>
6 * - one LED is controlled by a single byte on MOSI
7 * - the value of the byte gives the brightness between two values (lowest to
9 * - no return value is necessary (no MISO signal)
15 * - "ubnt,acb-spi-led": Microcontroller (SONiX 8F26E611LA) based device used
19 * * Mode: 00 -> set brightness between 0x00 (min) and 0x3F (max)
20 * * Mode: 01 -> pulsing pattern (min -> max -> min) with an interval. From
24 * * Mode: 10 -> same as 01 but with only a ramp from min to max. Again a
26 * * Mode: 11 -> blinking (off -> 25% -> off -> 25% -> ...) with a period of
[all …]
H A Dleds-lt3593.c1 // SPDX-License-Identifier: GPL-2.0
37 gpiod_set_value_cansleep(led_dat->gpiod, 0); in lt3593_led_set()
41 pulses = 32 - (value * 32) / 255; in lt3593_led_set()
44 gpiod_set_value_cansleep(led_dat->gpiod, 0); in lt3593_led_set()
46 gpiod_set_value_cansleep(led_dat->gpiod, 1); in lt3593_led_set()
50 gpiod_set_value_cansleep(led_dat->gpiod, 1); in lt3593_led_set()
52 while (pulses--) { in lt3593_led_set()
53 gpiod_set_value_cansleep(led_dat->gpiod, 0); in lt3593_led_set()
55 gpiod_set_value_cansleep(led_dat->gpiod, 1); in lt3593_led_set()
64 struct device *dev = &pdev->dev; in lt3593_led_probe()
[all …]
/linux/drivers/leds/rgb/
H A Dleds-group-multicolor.c1 // SPDX-License-Identifier: GPL-2.0
3 * Multi-color LED built with monochromatic LED devices
5 * This driver groups several monochromatic LED devices in a single multicolor LED device.
7 * Compared to handling this grouping in user-space, the benefits are:
8 * - The state of the monochromatic LED relative to each other is always consistent.
9 * - The sysfs interface of the LEDs can be used for the group as a whole.
11 * Copyright 2023 Jean-Jacques Hiblot <jjhiblot@traphandler.com>
16 #include <linux/led-class-multicolor.h>
31 const unsigned int group_max_brightness = mc_cdev->led_cdev.max_brightness; in leds_gmc_set()
34 for (i = 0; i < mc_cdev->num_colors; i++) { in leds_gmc_set()
[all …]
/linux/arch/arm/boot/dts/samsung/
H A Dexynos4412-galaxy-s3.dtsi1 // SPDX-License-Identifier: GPL-2.0
9 /dts-v1/;
10 #include <dt-bindings/leds/common.h>
11 #include "exynos4412-midas.dtsi"
19 led-controller {
21 flen-gpios = <&gpj1 1 GPIO_ACTIVE_HIGH>;
22 enset-gpios = <&gpj1 2 GPIO_ACTIVE_HIGH>;
24 pinctrl-names = "default", "host", "isp";
25 pinctrl-0 = <&camera_flash_host>;
26 pinctrl-1 = <&camera_flash_host>;
[all …]
/linux/drivers/mfd/
H A Drt5033.c1 // SPDX-License-Identifier: GPL-2.0-only
5 * RT5033 comprises multiple sub-devices switcing charger, fuel gauge,
6 * flash LED, current source, LDO and BUCK regulators.
17 #include <linux/mfd/rt5033-private.h>
38 { .name = "rt5033-regulator", },
40 .name = "rt5033-charger",
41 .of_compatible = "richtek,rt5033-charger",
43 .name = "rt5033-led",
44 .of_compatible = "richtek,rt5033-led",
60 rt5033 = devm_kzalloc(&i2c->dev, sizeof(*rt5033), GFP_KERNEL); in rt5033_i2c_probe()
[all …]
H A Dsimple-mfd-i2c.c1 // SPDX-License-Identifier: GPL-2.0-only
3 * Simple MFD - I2C
10 * shared by all sub-devices. Children can use their parent's device structure
13 * Once the register map has been successfully initialised, any sub-devices
30 #include "simple-mfd-i2c.h"
44 simple_mfd_data = device_get_match_data(&i2c->dev); in simple_mfd_i2c_probe()
47 if (!simple_mfd_data || !simple_mfd_data->regmap_config) in simple_mfd_i2c_probe()
50 regmap_config = simple_mfd_data->regmap_config; in simple_mfd_i2c_probe()
57 if (!simple_mfd_data || !simple_mfd_data->mfd_cell) in simple_mfd_i2c_probe()
58 return devm_of_platform_populate(&i2c->dev); in simple_mfd_i2c_probe()
[all …]
/linux/drivers/media/v4l2-core/
H A Dv4l2-flash-led-class.c1 // SPDX-License-Identifier: GPL-2.0-only
3 * V4L2 flash LED sub-device registration helpers.
9 #include <linux/led-class-flash.h>
15 #include <media/v4l2-flash-led-class.h>
18 (v4l2_flash && v4l2_flash->ops && v4l2_flash->ops->op)
22 v4l2_flash->ops->op(v4l2_flash, arg) : \
23 -EINVAL)
46 intensity -= ctrl->minimum; in __intensity_to_led_brightness()
47 intensity /= (u32) ctrl->step; in __intensity_to_led_brightness()
53 * the LED subsystem reflects LED_OFF state. in __intensity_to_led_brightness()
[all …]
/linux/include/linux/platform_data/
H A Dwilco-ec.h1 /* SPDX-License-Identifier: GPL-2.0 */
25 * struct wilco_ec_device - Wilco Embedded Controller handle.
34 * @debugfs_pdev: The child platform_device used by the debugfs sub-driver.
35 * @rtc_pdev: The child platform_device used by the RTC sub-driver.
36 * @charger_pdev: Child platform_device used by the charger config sub-driver.
37 * @telem_pdev: The child platform_device used by the telemetry sub-driver.
54 * struct wilco_ec_request - Mailbox request message format.
72 * struct wilco_ec_response - Mailbox response message format.
75 * @result: Result code from the EC. Non-zero indicates an error.
90 * enum wilco_ec_msg_type - Message type to select a set of command codes.
[all …]
/linux/drivers/leds/flash/
H A Dleds-max77693.c1 // SPDX-License-Identifier: GPL-2.0-only
3 * LED Flash class driver for the flash cell of max77693 mfd.
11 #include <linux/led-class-flash.h>
13 #include <linux/mfd/max77693-common.h>
14 #include <linux/mfd/max77693-private.h>
20 #include <media/v4l2-flash-led-class.h>
59 /* corresponding LED Flash class device */
80 /* sub led data */
96 /* bitmask of FLED outputs use state (bit 0. - FLED1, bit 1. - FLED2) */
109 return (ua - FLASH_IOUT_MIN) / FLASH_IOUT_STEP; in max77693_led_iout_to_reg()
[all …]

1234