| /linux/Documentation/sound/ |
| H A D | utimers.rst | 4 Userspace-driven timers
12 This document describes the userspace-driven timers: virtual ALSA timers
21 Enabling userspace-driven timers
24 The userspace-driven timers could be enabled in the kernel using the
28 Userspace-driven timers API
31 Userspace application can create a userspace-driven ALSA timer by
51 applications. There could be up to 128 userspace-driven timers in the
96 Userspace-driven timers and snd-aloop
99 Userspace-driven timers could be easily used with ``snd-aloop`` module
106 not when the certain amount of jiffies elapses. Userspace-driven ALSA
[all …]
|
| /linux/drivers/gpio/ |
| H A 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 …]
|
| /linux/Documentation/devicetree/bindings/power/reset/ |
| H A 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
|
| /linux/drivers/leds/rgb/ |
| H A D | Kconfig | 12 and driven by a controller that doesn't have multi-color support.
41 tristate "PWM driven multi-color LED Support"
44 This option enables support for PWM driven monochrome LEDs that are
|
| /linux/Documentation/driver-api/gpio/ |
| H A D | intro.rst | 37 options about how that value is driven, so that for example only one
38 value might be driven, supporting "wire-OR" and similar schemes for the
83 level is actually driven), or "open source" (where only the high signal level is
84 driven) signaling. That term applies to CMOS transistors; "open collector" is
|
| /linux/Documentation/driver-api/thermal/ |
| H A 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.
|
| /linux/Documentation/devicetree/bindings/pinctrl/ |
| H A 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
|
| H A D | marvell,dove-pinctrl.txt | 64 pmu-nc Pin not driven by any PM function
65 pmu-low Pin driven low (0)
66 pmu-high Pin driven high (1)
|
| /linux/drivers/gpu/drm/amd/display/dc/gpio/ |
| H A 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()
|
| /linux/include/linux/ |
| H A 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
|
| H A D | scx200_gpio.h | 28 /* 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/Documentation/hwmon/ |
| H A 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.
|
| /linux/Documentation/devicetree/bindings/display/ |
| H A D | solomon,ssd-common.yaml | 30 Height in pixel of the screen driven by the controller.
36 Width in pixel of the screen driven by the controller.
|
| /linux/arch/arm64/boot/dts/freescale/ |
| H A 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)
|
| H A 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)
|
| H A 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)
|
| H A 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)
|
| /linux/Documentation/peci/ |
| H A D | peci.rst | 30 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/Documentation/devicetree/bindings/iio/adc/ |
| H A D | microchip,pac1921.yaml | 43 the INTEGRATE state when driven high, or in the READ state when driven low.
|
| /linux/Documentation/devicetree/bindings/soc/fsl/cpm_qe/qe/ |
| H A D | pincfg.txt | 18 0 = The pin is actively driven as an output
20 driven active-low, otherwise it is three-stated.
|
| /linux/Documentation/devicetree/bindings/display/panel/ |
| H A D | panel-dsi-cm.yaml | 15 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
|
| H A D | sharp,lq101r1sx01.yaml | 18 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).
|
| /linux/Documentation/devicetree/bindings/nvmem/ |
| H A D | nvmem.yaml | 37 The write-protect GPIO is asserted, when it's driven high
39 when it's driven low (logical '0') to allow writing.
|
| /linux/Documentation/leds/ |
| H A D | leds-class.rst | 172 Hardware driven LEDs
175 Some LEDs can be programmed to be driven by hardware. This is not
180 With hw control we refer to the LED driven by hardware.
206 a set of mode and setup the LED to be driven by hardware
|
| /linux/Documentation/admin-guide/ |
| H A D | parport.rst | 253 - 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.
|