Searched full:driven (Results 1 – 25 of 1083) sorted by relevance
12345678910>>...44
| /kernel/linux/linux-6.6/drivers/gpio/ |
| D | gpio-stp-xway.c | 22 * 3 groups of 8 bits can be driven. The hardware is able to allow the DSL modem
58 /* 2 groups of 3 bits can be driven by the phys */
86 u8 dsl; /* the 2 LSBs can be driven by the dsl core */
87 u8 phy1; /* 3 bits can be driven by phy1 */
88 u8 phy2; /* 3 bits can be driven by phy2 */
89 u8 phy3; /* 3 bits can be driven by phy3 */
90 u8 phy4; /* 3 bits can be driven by phy4 */
91 u8 reserved; /* mask out the hw driven bits in gpio_request */
149 * We mask out the HW driven pins
156 dev_err(gc->parent, "GPIO %d is driven by hardware\n", gpio); in xway_stp_request()
[all …]
|
| /kernel/linux/linux-5.10/drivers/gpio/ |
| D | gpio-stp-xway.c | 21 * 3 groups of 8 bits can be driven. The hardware is able to allow the DSL modem
57 /* 2 groups of 3 bits can be driven by the phys */
85 u8 dsl; /* the 2 LSBs can be driven by the dsl core */
86 u8 phy1; /* 3 bits can be driven by phy1 */
87 u8 phy2; /* 3 bits can be driven by phy2 */
88 u8 phy3; /* 3 bits can be driven by phy3 */
89 u8 phy4; /* 3 bits can be driven by phy4 */
90 u8 reserved; /* mask out the hw driven bits in gpio_request */
148 * We mask out the HW driven pins
155 dev_err(gc->parent, "GPIO %d is driven by hardware\n", gpio); in xway_stp_request()
[all …]
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/power/reset/ |
| D | gpio-restart.txt | 7 will be driven in the inactive state. Otherwise its not driven until
11 priority order. The gpio is configured as an output, and driven active,
17 is driven active again. After a delay specified by wait-delay, the
|
| /kernel/linux/linux-6.6/Documentation/devicetree/bindings/power/reset/ |
| D | gpio-restart.yaml | 17 'open-source' is not found, the GPIO line will be driven in the inactive state. Otherwise its
18 not driven until the restart is initiated.
21 is configured as an output, and driven active, triggering a level triggered reset condition.
25 inactive-delay, the GPIO is driven active again. After a delay specified by wait-delay, the
|
| /kernel/linux/linux-6.6/drivers/leds/rgb/ |
| D | Kconfig | 12 and driven by a controller that doesn't have multi-color support.
18 tristate "PWM driven multi-color LED Support"
21 This option enables support for PWM driven monochrome LEDs that are
|
| /kernel/linux/linux-6.6/Documentation/devicetree/bindings/display/ |
| D | truly,nt35597.txt | 20 - ports: This device has two video ports driven by two DSIs. Their connections
23 - port@0: DSI input port driven by master DSI
24 - port@1: DSI input port driven by secondary DSI
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/display/ |
| D | truly,nt35597.txt | 20 - ports: This device has two video ports driven by two DSIs. Their connections
23 - port@0: DSI input port driven by master DSI
24 - port@1: DSI input port driven by secondary DSI
|
| /kernel/linux/linux-6.6/Documentation/driver-api/thermal/ |
| D | nouveau_thermal.rst | 75 Your fan can be driven in different modes:
78 * 1: The fan can be driven in manual (use pwm1 to change the speed);
79 * 2; The fan is driven automatically depending on the temperature.
|
| /kernel/linux/linux-5.10/Documentation/driver-api/thermal/ |
| D | nouveau_thermal.rst | 75 Your fan can be driven in different modes:
78 * 1: The fan can be driven in manual (use pwm1 to change the speed);
79 * 2; The fan is driven automatically depending on the temperature.
|
| /kernel/linux/linux-5.10/drivers/gpu/drm/amd/display/dc/gpio/ |
| D | hw_gpio.c | 111 * So (A) is grounded, output is driven by (EN = 0) in dal_hw_gpio_set_value()
150 * program the pin as GPIO, mask out signal driven by HW */ in dal_hw_gpio_config_mode()
156 * program the pin as GPIO, mask out signal driven by HW */ in dal_hw_gpio_config_mode()
167 /* program the pin as tri-state, pin is driven by HW */ in dal_hw_gpio_config_mode()
|
| /kernel/linux/linux-6.6/Documentation/driver-api/gpio/ |
| D | intro.rst | 49 options about how that value is driven, so that for example only one
50 value might be driven, supporting "wire-OR" and similar schemes for the
95 level is actually driven), or "open source" (where only the high signal level is
96 driven) signaling. That term applies to CMOS transistors; "open collector" is
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/pinctrl/ |
| D | renesas,rza1-ports.yaml | 79 "software IO driven" mode to be specified. To do so use the generic
86 controller driver internally, while software driven IO direction has to
171 * Configure TIOC0A as software driven input
181 * Configure TIOC0B as software driven output
|
| /kernel/linux/linux-6.6/Documentation/devicetree/bindings/pinctrl/ |
| D | renesas,rza1-ports.yaml | 83 "software IO driven" mode to be specified. To do so use the generic
90 controller driver internally, while software driven IO direction has to
171 * Configure TIOC0A as software driven input
181 * Configure TIOC0B as software driven output
|
| /kernel/linux/linux-5.10/Documentation/driver-api/gpio/ |
| D | intro.rst | 49 options about how that value is driven, so that for example only one
50 value might be driven, supporting "wire-OR" and similar schemes for the
95 level is actually driven), or "open source" (where only the high signal level is
96 driven) signaling. That term applies to CMOS transistors; "open collector" is
|
| /kernel/linux/linux-6.6/drivers/gpu/drm/amd/display/dc/gpio/ |
| D | hw_gpio.c | 111 * So (A) is grounded, output is driven by (EN = 0) in dal_hw_gpio_set_value()
150 * program the pin as GPIO, mask out signal driven by HW */ in dal_hw_gpio_config_mode()
156 * program the pin as GPIO, mask out signal driven by HW */ in dal_hw_gpio_config_mode()
167 /* program the pin as tri-state, pin is driven by HW */ in dal_hw_gpio_config_mode()
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/mfd/ |
| D | st,stm32-timers.yaml | 11 - advanced-control timers consist of a 16-bit auto-reload counter driven
15 driven by a programmable prescaler and PWM outputs.
16 - basic timers consist of a 16-bit auto-reload counter driven by a
|
| /kernel/linux/linux-5.10/include/linux/ |
| D | leds-regulator.h | 3 * leds-regulator.h - platform data structure for regulator driven LEDs.
18 * If you have several regulator driven LEDs, you can append a numerical id to
|
| /kernel/linux/linux-6.6/include/linux/ |
| D | leds-regulator.h | 3 * leds-regulator.h - platform data structure for regulator driven LEDs.
18 * If you have several regulator driven LEDs, you can append a numerical id to
|
| /kernel/linux/linux-6.6/Documentation/devicetree/bindings/mfd/ |
| D | st,stm32-timers.yaml | 11 - advanced-control timers consist of a 16-bit auto-reload counter driven
15 driven by a programmable prescaler and PWM outputs.
16 - basic timers consist of a 16-bit auto-reload counter driven by a
|
| /kernel/linux/linux-6.6/Documentation/hwmon/ |
| D | tc654.rst | 32 Setting pwm1_mode to 1 will cause the pwm output to be driven based on
34 driven based on the Vin input.
|
| /kernel/linux/linux-5.10/Documentation/hwmon/ |
| D | tc654.rst | 32 Setting pwm1_mode to 1 will cause the pwm output to be driven based on
34 driven based on the Vin input.
|
| /kernel/linux/linux-6.6/arch/arm64/boot/dts/freescale/ |
| D | imx8mm-venice-gw73xx-0x-rs485.dtso | 7 * - GPIO4_0 rs485_en needs to be driven high (active)
8 * - GPIO4_2 rs485_hd needs to be driven high (active)
|
| D | imx8mm-venice-gw72xx-0x-rs485.dtso | 7 * - GPIO4_0 rs485_en needs to be driven high (active)
8 * - GPIO4_2 rs485_hd needs to be driven high (active)
|
| D | imx8mm-venice-gw73xx-0x-rs422.dtso | 7 * - GPIO4_0 rs485_en needs to be driven high (active)
8 * - GPIO4_2 rs485_hd needs to be driven low (in-active)
|
| D | imx8mm-venice-gw72xx-0x-rs422.dtso | 7 * - GPIO4_0 rs485_en needs to be driven high (active)
8 * - GPIO4_2 rs485_hd needs to be driven low (in-active)
|
12345678910>>...44