| /Linux-v5.4/include/dt-bindings/clock/ |
| D | tegra186-clock.h | 376 /** @brief output branch of PLL_C for ISP, controlled by gate CLK_ENB_PLLC_OUT_ISP */
378 /** @brief output branch of PLL_C for VI, controlled by gate CLK_ENB_PLLC_OUT_VE */
380 /** @brief output branch of PLL_C for AON domain, controlled by gate CLK_ENB_PLLC_OUT_AON */
384 /** @brief output of mux controlled by CLK_RST_CONTROLLER_CLK_SOURCE_I2S2 */
386 /** @brief output of mux controlled by CLK_RST_CONTROLLER_CLK_SOURCE_I2S3 */
388 /** @brief output of mux controlled by CLK_RST_CONTROLLER_CLK_SOURCE_SPDF_IN */
398 /** @brief output of mux controlled by CLK_RST_CONTROLLER_CLK_SOURCE_SPI1 */
400 /** @brief output of mux controlled by CLK_RST_CONTROLLER_CLK_SOURCE_ISP */
402 /** @brief output of mux controlled by CLK_RST_CONTROLLER_CLK_SOURCE_VI */
404 /** @brief output of mux controlled by CLK_RST_CONTROLLER_CLK_SOURCE_SDMMC1 */
[all …]
|
| /Linux-v5.4/Documentation/devicetree/bindings/leds/ |
| D | leds-bcm6328.txt | 6 controller), which can either be controlled by software (exporting the 74x164
9 Some of these Serial LEDs are hardware controlled (e.g. ethernet LEDs) and
11 controlled, so the only chance to keep them working is by using this driver.
14 should be controlled by a hardware signal instead of the MODE register value,
19 controlled you are still able to make it blink or light it up if it isn't,
21 reason, hardware controlled LEDs aren't registered as LED class devices.
47 a) Optional properties for sub-nodes related to software controlled LEDs:
56 b) Optional properties for sub-nodes related to hardware controlled LEDs:
57 - brcm,hardware-controlled : Boolean, makes this LED hardware controlled.
98 brcm,hardware-controlled;
[all …]
|
| D | leds-lm3697.txt | 21 - reg : 0 - LED is Controlled by bank A
22 1 - LED is Controlled by bank B
39 HVLED string 1 and 3 are controlled by control bank A and HVLED 2 string is
40 controlled by control bank B.
|
| D | leds-lm3532.txt | 53 - reg : Indicates control bank the LED string is controlled by
55 - ti,led-mode : Defines if the LED strings are manually controlled or
56 if the LED strings are controlled by the ALS.
57 0x00 - LED strings are I2C controlled via full scale
59 0x01 - LED strings are ALS controlled
|
| D | leds-lm36274.txt | 6 the I2C bus and/or controlled via a logic level PWM input from 60 uA to 30 mA.
31 HVLED string 1 and 3 are controlled by control bank A and HVLED 2 string is
32 controlled by control bank B.
|
| /Linux-v5.4/drivers/leds/trigger/ |
| D | Kconfig | 15 This allows LEDs to be controlled by a programmable timer
26 controlled via sysfs. It's useful to notify the user on
39 This allows LEDs to be controlled by disk activity.
46 This allows LEDs to be controlled by MTD activity.
52 This allows LEDs to be controlled by a CPU load average.
60 This allows LEDs to be controlled as a backlight device: they
68 This allows LEDs to be controlled by active CPUs. This shows
77 This allows LEDs to be controlled by an immediate CPU usage.
86 This allows LEDs to be controlled by gpio events. It's good
113 This allows LEDs to be controlled as a camera flash/torch device.
[all …]
|
| /Linux-v5.4/drivers/pinctrl/nomadik/ |
| D | pinctrl-ab8500.c | 392 ALTERNATE_FUNCTIONS(1, 0, UNUSED, UNUSED, 0, 0, 0), /* GPIO1, altA controlled by bit 0 */
393 ALTERNATE_FUNCTIONS(2, 1, UNUSED, UNUSED, 0, 0, 0), /* GPIO2, altA controlled by bit 1 */
394 ALTERNATE_FUNCTIONS(3, 2, UNUSED, UNUSED, 0, 0, 0), /* GPIO3, altA controlled by bit 2*/
395 ALTERNATE_FUNCTIONS(4, 3, UNUSED, UNUSED, 0, 0, 0), /* GPIO4, altA controlled by bit 3*/
398 ALTERNATE_FUNCTIONS(6, 5, UNUSED, UNUSED, 0, 0, 0), /* GPIO6, altA controlled by bit 5*/
399 ALTERNATE_FUNCTIONS(7, 6, UNUSED, UNUSED, 0, 0, 0), /* GPIO7, altA controlled by bit 6*/
400 ALTERNATE_FUNCTIONS(8, 7, UNUSED, UNUSED, 0, 0, 0), /* GPIO8, altA controlled by bit 7*/
402 ALTERNATE_FUNCTIONS(9, 0, UNUSED, UNUSED, 0, 0, 0), /* GPIO9, altA controlled by bit 0*/
403 …ALTERNATE_FUNCTIONS(10, 1, 0, UNUSED, 0, 1, 0), /* GPIO10, altA and altB controlled by bi…
404 …ALTERNATE_FUNCTIONS(11, 2, 1, UNUSED, 0, 1, 0), /* GPIO11, altA and altB controlled by bi…
[all …]
|
| D | pinctrl-ab8505.c | 274 ALTERNATE_FUNCTIONS(1, 0, UNUSED, UNUSED, 0, 0, 0), /* GPIO1, altA controlled by bit 0 */
275 ALTERNATE_FUNCTIONS(2, 1, UNUSED, UNUSED, 0, 0, 0), /* GPIO2, altA controlled by bit 1 */
276 ALTERNATE_FUNCTIONS(3, 2, UNUSED, UNUSED, 0, 0, 0), /* GPIO3, altA controlled by bit 2*/
284 …ALTERNATE_FUNCTIONS(10, 1, 0, UNUSED, 1, 0, 0), /* GPIO10, altA and altB controlled by b…
285 ALTERNATE_FUNCTIONS(11, 2, 1, UNUSED, 0, 0, 0), /* GPIO11, altA controlled by bit 2 */
287 …ALTERNATE_FUNCTIONS(13, 4, 3, 4, 1, 0, 2), /* GPIO13, altA altB and altC controlled…
288 ALTERNATE_FUNCTIONS(14, 5, UNUSED, UNUSED, 0, 0, 0), /* GPIO14, altA controlled by bit 5 */
296 ALTERNATE_FUNCTIONS(17, 0, UNUSED, UNUSED, 0, 0, 0), /* GPIO17, altA controlled by bit 0 */
297 ALTERNATE_FUNCTIONS(18, 0, UNUSED, UNUSED, 0, 0, 0), /* GPIO18, altA controlled by bit 0 */
298 ALTERNATE_FUNCTIONS(19, 0, UNUSED, UNUSED, 0, 0, 0), /* GPIO19, altA controlled by bit 0 */
[all …]
|
| /Linux-v5.4/arch/mips/boot/dts/brcm/ |
| D | bcm63268-comtrend-vr-3032u.dts | 29 brcm,hardware-controlled;
35 brcm,hardware-controlled;
66 brcm,hardware-controlled;
71 brcm,hardware-controlled;
76 brcm,hardware-controlled;
81 brcm,hardware-controlled;
86 brcm,hardware-controlled;
91 brcm,hardware-controlled;
96 brcm,hardware-controlled;
|
| /Linux-v5.4/drivers/mux/ |
| D | Kconfig | 35 tristate "GPIO-controlled Multiplexer"
38 GPIO-controlled Multiplexer controller.
49 tristate "MMIO/Regmap register bitfield-controlled Multiplexer"
52 MMIO/Regmap register bitfield-controlled Multiplexer controller.
|
| /Linux-v5.4/Documentation/devicetree/bindings/dma/ |
| D | qcom_bam_dma.txt | 16 - qcom,controlled-remotely : optional, indicates that the bam is controlled by
19 remotely controlled bam.
21 in a remotely controlled bam.
|
| /Linux-v5.4/Documentation/leds/ |
| D | leds-lm3556.rst | 26 LM3556 Flash can be controlled through sys/class/leds/flash/brightness file
29 ON / OFF will be controlled by STROBE pin.
54 LM3556 torch can be controlled through sys/class/leds/torch/brightness file.
56 and ON / OFF will be controlled by TORCH pin.
98 Indicator brightness can be controlled through
|
| /Linux-v5.4/drivers/i2c/muxes/ |
| D | Kconfig | 28 I2C busses connected through a MUX, which is controlled
41 I2C busses connected through a MUX, which in turn is controlled
96 I2C busses connected through a MUX, which is controlled
116 I2C busses connected through a MUX, which is controlled
|
| /Linux-v5.4/drivers/staging/iio/Documentation/ |
| D | sysfs-bus-iio-dds | 8 which allows for pin controlled FSK Frequency Shift Keying
38 allows for pin controlled PSK Phase Shift Keying
68 phase is controlled by the respective phase and frequency
81 controlled together.
|
| /Linux-v5.4/Documentation/fault-injection/ |
| D | notifier-error-inject.rst | 16 This feature is controlled through debugfs interface
35 This feature is controlled through debugfs interface
53 This feature is controlled through debugfs interface
66 This feature is controlled through debugfs interface
|
| /Linux-v5.4/include/linux/mfd/samsung/ |
| D | s2mps14.h | 118 * controlled however it does not specify which register is used for that.
127 /* On/Off controlled by PWREN */
129 /* On/Off controlled by LDO10EN or EMMCEN */
|
| /Linux-v5.4/drivers/clk/berlin/ |
| D | berlin2-div.c | 33 * (A) input pll clock mux controlled by <PllSelect[1:n]>
34 * (B) input pll bypass mux controlled by <PllSwitch>
35 * (C) programmable clock divider controlled by <Select[1:n]>
37 * (E) programmable clock divider bypass controlled by <Switch>
38 * (F) constant div-by-3 clock mux controlled by <D3Switch>
39 * (G) clock gate controlled by <Enable>
|
| /Linux-v5.4/Documentation/devicetree/bindings/pinctrl/ |
| D | pinctrl-zx.txt | 37 controlled by TOP_PMM block only, and this type of pins are meant by term
38 'TOP pins'. For pins like KEY_ROW2, the pinmux is controlled by both
42 types of pins. Both are controlled by auxiliary controller, i.e. AON_IOCFG
|
| /Linux-v5.4/drivers/regulator/ |
| D | Kconfig | 52 There are some classes of devices that are controlled entirely
64 They provide two I2C-controlled DC/DC step-down converters with
278 converter 12A DC-DC Buck controlled through an I2C
289 step down converter 12A or 16A DC-DC Buck controlled through an I2C
300 This driver supports the voltage domain regulators controlled by the
319 controlled via gpios.
440 8-output regulators controlled via I2C.
448 8-output regulators controlled via I2C.
719 This driver supports PWM controlled voltage regulators. PWM
774 outputs which can be controlled by i2c communication.
[all …]
|
| /Linux-v5.4/drivers/gpu/drm/msm/disp/dpu1/ |
| D | dpu_hw_ctl.h | 56 * kickoff hw operation for Sw controlled interfaces
57 * DSI cmd mode and WB interface are SW controlled
64 * controlled interfaces: DSI cmd mode and WB interface
65 * are SW controlled
|
| /Linux-v5.4/Documentation/devicetree/bindings/pwm/ |
| D | google,cros-ec-pwm.txt | 1 * PWM controlled by ChromeOS EC
4 (EC) and controlled via a host-command interface.
|
| /Linux-v5.4/Documentation/devicetree/bindings/thermal/ |
| D | rockchip-thermal.txt | 30 - rockchip,hw-tshut-temp : The hardware-controlled shutdown temperature value.
31 - rockchip,hw-tshut-mode : The hardware-controlled shutdown mode 0:CRU 1:GPIO.
32 - rockchip,hw-tshut-polarity : The hardware-controlled active polarity 0:LOW
|
| /Linux-v5.4/Documentation/devicetree/bindings/regulator/ |
| D | as3722-regulator.txt | 36 1: Rail is controlled by ENABLE1 input pin.
37 2: Rail is controlled by ENABLE2 input pin.
38 3: Rail is controlled by ENABLE3 input pin.
|
| /Linux-v5.4/Documentation/devicetree/bindings/clock/ |
| D | maxim,max77686.txt | 10 The MAX77686 contains three 32.768khz clock outputs that can be controlled
15 The MAX77802 contains two 32.768khz clock outputs that can be controlled
19 The MAX77686 contains one 32.768khz clock outputs that can be controlled
|
| /Linux-v5.4/Documentation/devicetree/bindings/sound/ |
| D | google,cros-ec-codec.txt | 1 * Audio codec controlled by ChromeOS EC
4 Embedded Controller (EC) and is controlled via a host-command interface.
|
