Home
last modified time | relevance | path

Searched full:driven (Results 1 – 25 of 553) sorted by relevance

12345678910>>...23

/Linux-v6.1/drivers/gpio/
Dgpio-stp-xway.c21 * 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 …]
/Linux-v6.1/Documentation/devicetree/bindings/power/reset/
Dgpio-restart.yaml17 '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
/Linux-v6.1/Documentation/devicetree/bindings/display/
Dtruly,nt35597.txt20 - 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
/Linux-v6.1/Documentation/driver-api/thermal/
Dnouveau_thermal.rst75 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.
/Linux-v6.1/Documentation/driver-api/gpio/
Dintro.rst49 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
/Linux-v6.1/drivers/gpu/drm/amd/display/dc/gpio/
Dhw_gpio.c111 * 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()
/Linux-v6.1/Documentation/devicetree/bindings/pinctrl/
Drenesas,rza1-ports.yaml83 "software IO driven" mode to be specified. To do so use the generic
90 controller driver internally, while software driven IO direction has to
175 * Configure TIOC0A as software driven input
185 * Configure TIOC0B as software driven output
Dmarvell,dove-pinctrl.txt64 pmu-nc Pin not driven by any PM function
65 pmu-low Pin driven low (0)
66 pmu-high Pin driven high (1)
/Linux-v6.1/drivers/leds/rgb/
DKconfig6 tristate "PWM driven multi-color LED Support"
9 This option enables support for PWM driven monochrome LEDs that are
/Linux-v6.1/Documentation/devicetree/bindings/mfd/
Dst,stm32-timers.yaml11 - 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
/Linux-v6.1/include/linux/
Dleds-regulator.h3 * 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
Dscx200_gpio.h28 /* return the value driven on the GPIO signal (the value that will be
29 driven if the GPIO is configured as an output, it might not be the
/Linux-v6.1/Documentation/hwmon/
Dtc654.rst32 Setting pwm1_mode to 1 will cause the pwm output to be driven based on
34 driven based on the Vin input.
/Linux-v6.1/arch/arm64/boot/dts/freescale/
Dimx8mm-venice-gw72xx-0x-rs422.dts7 * - GPIO4_0 rs485_en needs to be driven high (active)
8 * - GPIO4_2 rs485_hd needs to be driven low (in-active)
Dimx8mm-venice-gw72xx-0x-rs485.dts7 * - GPIO4_0 rs485_en needs to be driven high (active)
8 * - GPIO4_2 rs485_hd needs to be driven high (active)
Dimx8mm-venice-gw73xx-0x-rs422.dts7 * - GPIO4_0 rs485_en needs to be driven high (active)
8 * - GPIO4_2 rs485_hd needs to be driven low (in-active)
Dimx8mm-venice-gw73xx-0x-rs485.dts7 * - GPIO4_0 rs485_en needs to be driven high (active)
8 * - GPIO4_2 rs485_hd needs to be driven high (active)
/Linux-v6.1/Documentation/devicetree/bindings/input/
Dgpio-matrix-keypad.txt1 * GPIO driven matrix keypad device tree bindings
3 GPIO driven matrix keypad is used to interface a SoC with a matrix keypad.
/Linux-v6.1/arch/arm/mach-sa1100/include/mach/
Dshannon.h8 #define SHANNON_GPIO_SPI_FLASH GPIO_GPIO (0) /* Output - Driven low, enables SPI to flash */
9 #define SHANNON_GPIO_SPI_DSP GPIO_GPIO (1) /* Output - Driven low, enables SPI to DSP */
/Linux-v6.1/Documentation/sound/soc/
Dclocking.rst12 Every audio subsystem is driven by a master clock (sometimes referred to as MCLK
24 The Digital Audio Interface is usually driven by a Bit Clock (often referred to
/Linux-v6.1/Documentation/peci/
Dpeci.rst30 bit with a driven, rising edge from an idle near zero volts. The
31 duration of the signal driven high allows to determine whether the bit
/Linux-v6.1/Documentation/devicetree/bindings/soc/fsl/cpm_qe/qe/
Dpincfg.txt18 0 = The pin is actively driven as an output
20 driven active-low, otherwise it is three-stated.
/Linux-v6.1/Documentation/devicetree/bindings/display/panel/
Dsharp,lq101r1sx01.yaml18 driven by the first link (DSI-LINK1), left or even, is considered the primary
20 to the peripheral driven by the second link (DSI-LINK2, right or odd).
Dpanel-dsi-cm.yaml15 are usually driven in command mode. If no backlight is
45 because all its power rails can be driven by the same supply. In that case
/Linux-v6.1/Documentation/devicetree/bindings/gpio/
Dnxp,pcf8575.yaml14 driven high by a pull-up current source or driven low to ground. This

12345678910>>...23