| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/leds/ |
| D | pca963x.txt | 4 - compatible : should be : "nxp,pca9632", "nxp,pca9633", "nxp,pca9634" or "nxp,pca9635"
7 - nxp,totem-pole : use totem pole (push-pull) instead of open-drain (pca9632 defaults
8 to open-drain, newer chips to totem pole)
9 - nxp,hw-blink : use hardware blinking instead of software blinking
10 - nxp,period-scale : In some configurations, the chip blinks faster than expected.
13 - nxp,inverted-out: invert the polarity of the generated PWM
15 Each led is represented as a sub-node of the nxp,pca963x device.
17 LED sub-node properties:
18 - label : (optional) see Documentation/devicetree/bindings/leds/common.txt
19 - reg : number of LED line (could be from 0 to 3 in pca9632 or pca9633,
[all …]
|
| /kernel/linux/linux-6.6/Documentation/devicetree/bindings/leds/ |
| D | pca963x.txt | 4 - compatible : should be : "nxp,pca9632", "nxp,pca9633", "nxp,pca9634" or "nxp,pca9635"
7 - nxp,totem-pole : use totem pole (push-pull) instead of open-drain (pca9632 defaults
8 to open-drain, newer chips to totem pole)
9 - nxp,hw-blink : use hardware blinking instead of software blinking
10 - nxp,period-scale : In some configurations, the chip blinks faster than expected.
13 - nxp,inverted-out: invert the polarity of the generated PWM
15 Each led is represented as a sub-node of the nxp,pca963x device.
17 LED sub-node properties:
18 - label : (optional) see Documentation/devicetree/bindings/leds/common.txt
19 - reg : number of LED line (could be from 0 to 3 in pca9632 or pca9633,
[all …]
|
| D | leds-aw2013.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/leds/leds-aw2013.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: AWINIC AW2013 3-channel LED Driver
10 - Nikita Travkin <nikitos.tr@gmail.com>
13 The AW2013 is a 3-channel LED driver with I2C interface. It can control
14 LED brightness with PWM output.
25 description: Open-drain, low active interrupt pin "INTN".
26 Used to report completion of operations (power up, LED breath effects).
[all …]
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/pwm/ |
| D | nxp,pca9685-pwm.txt | 1 NXP PCA9685 16-channel 12-bit PWM LED controller
5 - compatible: "nxp,pca9685-pwm"
6 - #pwm-cells: Should be 2. See pwm.yaml in this directory for a description of
12 - invert (bool): boolean to enable inverted logic
13 - open-drain (bool): boolean to configure outputs with open-drain structure;
14 if omitted use totem-pole structure
22 compatible = "nxp,pca9685-pwm";
23 #pwm-cells = <2>;
26 open-drain;
|
| /kernel/linux/linux-6.6/Documentation/devicetree/bindings/pwm/ |
| D | nxp,pca9685-pwm.txt | 1 NXP PCA9685 16-channel 12-bit PWM LED controller
5 - compatible: "nxp,pca9685-pwm"
6 - #pwm-cells: Should be 2. See pwm.yaml in this directory for a description of
12 - invert (bool): boolean to enable inverted logic
13 - open-drain (bool): boolean to configure outputs with open-drain structure;
14 if omitted use totem-pole structure
22 compatible = "nxp,pca9685-pwm";
23 #pwm-cells = <2>;
26 open-drain;
|
| /kernel/linux/linux-6.6/Documentation/devicetree/bindings/net/dsa/ |
| D | qca8k.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - John Crispin <john@phrozen.org>
13 If the QCA8K switch is connect to an SoC's external mdio-bus, each subnode
16 ID. To declare the internal mdio-bus configuration, declare an MDIO node in
18 PHY it is connected to. In this config, an internal mdio-bus is registered and
20 mdio-bus configurations are not supported by the hardware.
27 - enum:
28 - qca,qca8327
[all …]
|
| /kernel/linux/linux-5.10/Documentation/driver-api/gpio/ |
| D | intro.rst | 16 - The descriptor-based interface is the preferred way to manipulate GPIOs,
17 and is described by all the files in this directory excepted gpio-legacy.txt.
18 - The legacy integer-based interface which is considered deprecated (but still
19 usable for compatibility reasons) is documented in gpio-legacy.txt.
21 The remainder of this document applies to the new descriptor-based interface.
22 gpio-legacy.txt contains the same information applied to the legacy
23 integer-based interface.
29 A "General Purpose Input/Output" (GPIO) is a flexible software-controlled
37 System-on-Chip (SOC) processors heavily rely on GPIOs. In some cases, every
38 non-dedicated pin can be configured as a GPIO; and most chips have at least
[all …]
|
| D | board.rst | 7 Note that it only applies to the new descriptor-based interface. For a
8 description of the deprecated integer-based GPIO interface please refer to
9 gpio-legacy.txt (actually, there is no real mapping possible with the old
20 -----------
26 <function>-gpios, where <function> is the function the driver will request
32 led-gpios = <&gpio 15 GPIO_ACTIVE_HIGH>, /* red */
36 power-gpios = <&gpio 1 GPIO_ACTIVE_LOW>;
39 Properties named <function>-gpio are also considered valid and old bindings use
44 "led" function, and GPIO 1 as the "power" GPIO::
48 red = gpiod_get_index(dev, "led", 0, GPIOD_OUT_HIGH);
[all …]
|
| D | legacy.rst | 13 A "General Purpose Input/Output" (GPIO) is a flexible software-controlled
21 System-on-Chip (SOC) processors heavily rely on GPIOs. In some cases, every
22 non-dedicated pin can be configured as a GPIO; and most chips have at least
27 Most PC southbridges have a few dozen GPIO-capable pins (with only the BIOS
32 - Output values are writable (high=1, low=0). Some chips also have
34 value might be driven ... supporting "wire-OR" and similar schemes
35 for the other value (notably, "open drain" signaling).
37 - Input values are likewise readable (1, 0). Some chips support readback
38 of pins configured as "output", which is very useful in such "wire-OR"
40 input de-glitch/debounce logic, sometimes with software controls.
[all …]
|
| D | consumer.rst | 6 it describes the new descriptor-based interface. For a description of the
7 deprecated integer-based GPIO interface please refer to gpio-legacy.txt.
23 - Simple compile coverage with e.g. COMPILE_TEST - it does not matter that
27 - Truly optional GPIOLIB support - where the driver does not really make use
28 of the GPIOs on certain compile-time configurations for certain systems, but
29 will use it under other compile-time configurations. In this case the
33 All the functions that work with the descriptor-based GPIO interface are
43 With the descriptor-based interface, GPIOs are identified with an opaque,
44 non-forgeable handler that must be obtained through a call to one of the
52 If a function is implemented by using several GPIOs together (e.g. a simple LED
[all …]
|
| /kernel/linux/linux-6.6/Documentation/driver-api/gpio/ |
| D | intro.rst | 16 - The descriptor-based interface is the preferred way to manipulate GPIOs,
18 - The legacy integer-based interface which is considered deprecated (but still
21 The remainder of this document applies to the new descriptor-based interface.
23 integer-based interface.
29 A "General Purpose Input/Output" (GPIO) is a flexible software-controlled
37 System-on-Chip (SOC) processors heavily rely on GPIOs. In some cases, every
38 non-dedicated pin can be configured as a GPIO; and most chips have at least
43 Most PC southbridges have a few dozen GPIO-capable pins (with only the BIOS
48 - Output values are writable (high=1, low=0). Some chips also have
50 value might be driven, supporting "wire-OR" and similar schemes for the
[all …]
|
| D | board.rst | 7 Note that it only applies to the new descriptor-based interface. For a
8 description of the deprecated integer-based GPIO interface please refer to
20 -----------
26 <function>-gpios, where <function> is the function the driver will request
32 led-gpios = <&gpio 15 GPIO_ACTIVE_HIGH>, /* red */
36 power-gpios = <&gpio 1 GPIO_ACTIVE_LOW>;
39 Properties named <function>-gpio are also considered valid and old bindings use
44 "led" function, and GPIO 1 as the "power" GPIO::
48 red = gpiod_get_index(dev, "led", 0, GPIOD_OUT_HIGH);
49 green = gpiod_get_index(dev, "led", 1, GPIOD_OUT_HIGH);
[all …]
|
| D | legacy.rst | 13 A "General Purpose Input/Output" (GPIO) is a flexible software-controlled
21 System-on-Chip (SOC) processors heavily rely on GPIOs. In some cases, every
22 non-dedicated pin can be configured as a GPIO; and most chips have at least
27 Most PC southbridges have a few dozen GPIO-capable pins (with only the BIOS
32 - Output values are writable (high=1, low=0). Some chips also have
34 value might be driven ... supporting "wire-OR" and similar schemes
35 for the other value (notably, "open drain" signaling).
37 - Input values are likewise readable (1, 0). Some chips support readback
38 of pins configured as "output", which is very useful in such "wire-OR"
40 input de-glitch/debounce logic, sometimes with software controls.
[all …]
|
| D | consumer.rst | 6 it describes the new descriptor-based interface. For a description of the
7 deprecated integer-based GPIO interface please refer to legacy.rst.
23 - Simple compile coverage with e.g. COMPILE_TEST - it does not matter that
27 - Truly optional GPIOLIB support - where the driver does not really make use
28 of the GPIOs on certain compile-time configurations for certain systems, but
29 will use it under other compile-time configurations. In this case the
33 All the functions that work with the descriptor-based GPIO interface are
43 With the descriptor-based interface, GPIOs are identified with an opaque,
44 non-forgeable handler that must be obtained through a call to one of the
52 If a function is implemented by using several GPIOs together (e.g. a simple LED
[all …]
|
| /kernel/linux/linux-6.6/arch/arm/boot/dts/microchip/ |
| D | at91-kizbox3-hs.dts | 1 // SPDX-License-Identifier: GPL-2.0
3 * at91-kizbox3-hs.dts - Device Tree file for Overkiz KIZBOX3-HS board
11 /dts-v1/;
12 #include "at91-kizbox3_common.dtsi"
15 model = "Overkiz KIZBOX3-HS";
16 compatible = "overkiz,kizbox3-hs", "atmel,sama5d2", "atmel,sama5";
18 led-controller-1 {
21 led-1 {
25 led-2 {
29 led-3 {
[all …]
|
| D | at91-foxg20.dts | 1 // SPDX-License-Identifier: GPL-2.0-or-later
3 * at91-foxg20.dts - Device Tree file for Acme Systems FoxG20 board
9 /dts-v1/;
26 clock-frequency = <32768>;
30 clock-frequency = <18432000>;
38 compatible = "atmel,tcb-timer";
43 compatible = "atmel,tcb-timer";
49 atmel,vbus-gpio = <&pioC 6 GPIO_ACTIVE_HIGH>;
54 pinctrl-0 = <
58 pinctrl-names = "default";
[all …]
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/pinctrl/ |
| D | pinctrl-palmas.txt | 4 the configuration for Pull UP/DOWN, open drain etc.
7 - compatible: It must be one of following:
8 - "ti,palmas-pinctrl" for Palma series of the pincontrol.
9 - "ti,tps65913-pinctrl" for Palma series device TPS65913.
10 - "ti,tps80036-pinctrl" for Palma series device TPS80036.
12 Please refer to pinctrl-bindings.txt in this directory for details of the
19 those pin(s), and various pin configuration parameters, such as pull-up,
20 open drain.
32 - ti,palmas-enable-dvfs1: Enable DVFS1. Configure pins for DVFS1 mode.
35 - ti,palmas-enable-dvfs2: Enable DVFS2. Configure pins for DVFS2 mode.
[all …]
|
| /kernel/linux/linux-6.6/Documentation/devicetree/bindings/pinctrl/ |
| D | pinctrl-palmas.txt | 4 the configuration for Pull UP/DOWN, open drain etc.
7 - compatible: It must be one of following:
8 - "ti,palmas-pinctrl" for Palma series of the pincontrol.
9 - "ti,tps65913-pinctrl" for Palma series device TPS65913.
10 - "ti,tps80036-pinctrl" for Palma series device TPS80036.
12 Please refer to pinctrl-bindings.txt in this directory for details of the
19 those pin(s), and various pin configuration parameters, such as pull-up,
20 open drain.
32 - ti,palmas-enable-dvfs1: Enable DVFS1. Configure pins for DVFS1 mode.
35 - ti,palmas-enable-dvfs2: Enable DVFS2. Configure pins for DVFS2 mode.
[all …]
|
| /kernel/linux/linux-6.6/Documentation/devicetree/bindings/mfd/ |
| D | rohm,bd71828-pmic.yaml | 1 # SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
3 ---
4 $id: http://devicetree.org/schemas/mfd/rohm,bd71828-pmic.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Matti Vaittinen <mazziesaccount@gmail.com>
13 BD71828GW is a single-chip power management IC for battery-powered portable
15 single-cell linear charger. Also included is a Coulomb counter, a real-time
30 gpio-controller: true
32 "#gpio-cells":
41 "#clock-cells":
[all …]
|
| /kernel/linux/linux-5.10/drivers/leds/ |
| D | leds-pca963x.c | 1 // SPDX-License-Identifier: GPL-2.0-only
6 * Author: Peter Meerwald <p.meerwald@bct-electronic.com>
9 * Based on leds-pca955x.c
11 * LED driver for the PCA9633 I2C LED driver (7-bit slave address 0x62)
12 * LED driver for the PCA9634/5 I2C LED driver (7-bit slave address set by hw.)
18 * in identical fashion. The delay_on/delay_off values of the last LED
22 * or by adding the 'nxp,hw-blink' property to the DTS.
36 /* LED select registers determine the source that drives LED outputs */
37 #define PCA963X_LED_OFF 0x0 /* LED driver off */
38 #define PCA963X_LED_ON 0x1 /* LED driver on */
[all …]
|
| /kernel/linux/linux-6.6/drivers/net/wireless/realtek/rtlwifi/rtl8821ae/ |
| D | led.c | 1 // SPDX-License-Identifier: GPL-2.0
2 /* Copyright(c) 2009-2010 Realtek Corporation.*/
7 #include "led.h"
83 if (rtlpriv->ledctl.led_opendrain) { in rtl8821ae_sw_led_off()
129 /*Open-drain arrangement for controlling the LED*/ in rtl8812ae_sw_led_off()
130 if (rtlpriv->ledctl.led_opendrain) { in rtl8812ae_sw_led_off()
136 /*Open-drain arrangement*/ in rtl8812ae_sw_led_off()
149 enum rtl_led_pin pin0 = rtlpriv->ledctl.sw_led0; in _rtl8821ae_sw_led_control()
156 if (rtlhal->hw_type == HARDWARE_TYPE_RTL8812AE) in _rtl8821ae_sw_led_control()
162 if (rtlhal->hw_type == HARDWARE_TYPE_RTL8812AE) in _rtl8821ae_sw_led_control()
[all …]
|
| /kernel/linux/linux-6.6/drivers/leds/ |
| D | leds-pca963x.c | 1 // SPDX-License-Identifier: GPL-2.0-only
6 * Author: Peter Meerwald <p.meerwald@bct-electronic.com>
9 * Based on leds-pca955x.c
11 * LED driver for the PCA9633 I2C LED driver (7-bit slave address 0x62)
12 * LED driver for the PCA9634/5 I2C LED driver (7-bit slave address set by hw.)
18 * in identical fashion. The delay_on/delay_off values of the last LED
22 * or by adding the 'nxp,hw-blink' property to the DTS.
36 /* LED select registers determine the source that drives LED outputs */
37 #define PCA963X_LED_OFF 0x0 /* LED driver off */
38 #define PCA963X_LED_ON 0x1 /* LED driver on */
[all …]
|
| /kernel/linux/linux-5.10/arch/arm/boot/dts/ |
| D | at91-foxg20.dts | 1 // SPDX-License-Identifier: GPL-2.0-or-later
3 * at91-foxg20.dts - Device Tree file for Acme Systems FoxG20 board
9 /dts-v1/;
26 clock-frequency = <32768>;
30 clock-frequency = <18432000>;
38 compatible = "atmel,tcb-timer";
43 compatible = "atmel,tcb-timer";
49 atmel,vbus-gpio = <&pioC 6 GPIO_ACTIVE_HIGH>;
54 pinctrl-0 = <
58 pinctrl-names = "default";
[all …]
|
| /kernel/linux/linux-6.6/Documentation/devicetree/bindings/input/ |
| D | microchip,cap11xx.yaml | 1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 The Microchip CAP1xxx Family of RightTouchTM multiple-channel capacitive
11 touch controllers and LED drivers. The device communication via I2C only.
14 - Rob Herring <robh@kernel.org>
19 - microchip,cap1106
20 - microchip,cap1126
21 - microchip,cap1188
22 - microchip,cap1203
[all …]
|
| /kernel/linux/linux-5.10/drivers/net/wireless/realtek/rtlwifi/rtl8821ae/ |
| D | led.c | 1 // SPDX-License-Identifier: GPL-2.0
2 /* Copyright(c) 2009-2010 Realtek Corporation.*/
7 #include "led.h"
13 pled->hw = hw; in _rtl8821ae_init_led()
14 pled->ledpin = ledpin; in _rtl8821ae_init_led()
15 pled->ledon = false; in _rtl8821ae_init_led()
24 "LedAddr:%X ledpin=%d\n", REG_LEDCFG2, pled->ledpin); in rtl8821ae_sw_led_on()
26 switch (pled->ledpin) { in rtl8821ae_sw_led_on()
41 "switch case %#x not processed\n", pled->ledpin); in rtl8821ae_sw_led_on()
44 pled->ledon = true; in rtl8821ae_sw_led_on()
[all …]
|