Home
last modified time | relevance | path

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

12345678910>>...21

/linux-5.10/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-5.10/Documentation/devicetree/bindings/power/reset/
Dgpio-restart.txt7 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
/linux-5.10/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
Dssd1307fb.txt11 - solomon,height: Height in pixel of the screen driven by the controller
12 - solomon,width: Width in pixel of the screen driven by the controller
/linux-5.10/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-5.10/Documentation/devicetree/bindings/pinctrl/
Drenesas,rza1-ports.yaml79 "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
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-5.10/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-5.10/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-5.10/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-5.10/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-5.10/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-5.10/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-5.10/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
Ddai.rst15 The bit clock (BCLK) is always driven by the CODEC (usually 12.288MHz) and the
16 frame (FRAME) (usually 48kHz) is always driven by the controller. Each AC97
/linux-5.10/lib/
Dgen_crc64table.c3 * Generate lookup table for the table-driven CRC64 calculation.
7 * the table-driven CRC64 calculation.
Dcrc64.c10 * algorithm, here the CRC64 code is also inspired by the table-driven
15 * crc64table[256] is the lookup table of a table-driven 64-bit CRC
/linux-5.10/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-5.10/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-5.10/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-5.10/Documentation/devicetree/bindings/nvmem/
Dnvmem.yaml40 The write-protect GPIO is asserted, when it's driven high
42 when it's driven low (logical '0') to allow writing.
/linux-5.10/Documentation/admin-guide/
Dparport.rst253 - interrupt-driven, protocol in software
254 - interrupt-driven, protocol in hardware using PIO
255 - interrupt-driven, protocol in hardware using DMA
273 hardware), to make it use interrupt-driven in-software protocol.
/linux-5.10/drivers/slimbus/
Dmessaging.c108 * (e.g. due to bus lines not being clocked or driven by controller)
292 * or driven by controller)
335 * or driven by controller)
356 * or driven by controller)

12345678910>>...21