Home
last modified time | relevance | path

Searched +full:two +full:- +full:wires (Results 1 – 25 of 75) sorted by relevance

123

/kernel/linux/linux-6.6/Documentation/devicetree/bindings/sound/
Dmt6359.yaml1 # SPDX-License-Identifier: GPL-2.0
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Eason Yen <eason.yen@mediatek.com>
11 - Jiaxin Yu <jiaxin.yu@mediatek.com>
12 - Shane Chien <shane.chien@mediatek.com>
20 mediatek,dmic-mode:
23 Indicates how many data pins are used to transmit two channels of PDM
24 signal. 0 means two wires, 1 means one wire. Default value is 0.
26 - 0 # two wires
[all …]
Dmt6358.txt10 - compatible - "string" - One of:
11 "mediatek,mt6358-sound"
12 "mediatek,mt6366-sound"
13 - Avdd-supply : power source of AVDD
16 - mediatek,dmic-mode : Indicates how many data pins are used to transmit two
17 channels of PDM signal. 0 means two wires, 1 means one wire. Default
23 compatible = "mediatek,mt6358-sound";
24 Avdd-supply = <&mt6358_vaud28_reg>;
25 mediatek,dmic-mode = <0>;
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/sound/
Dmt6359.yaml1 # SPDX-License-Identifier: GPL-2.0
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Eason Yen <eason.yen@mediatek.com>
11 - Jiaxin Yu <jiaxin.yu@mediatek.com>
12 - Shane Chien <shane.chien@mediatek.com>
20 mediatek,dmic-mode:
23 Indicates how many data pins are used to transmit two channels of PDM
24 signal. 0 means two wires, 1 means one wire. Default value is 0.
26 - 0 # one wire
[all …]
Dmt6358.txt10 - compatible : "mediatek,mt6358-sound".
11 - Avdd-supply : power source of AVDD
14 - mediatek,dmic-mode : Indicates how many data pins are used to transmit two
15 channels of PDM signal. 0 means two wires, 1 means one wire. Default
21 compatible = "mediatek,mt6358-sound";
22 Avdd-supply = <&mt6358_vaud28_reg>;
23 mediatek,dmic-mode = <0>;
/kernel/linux/linux-6.6/Documentation/driver-api/gpio/
Ddrivers-on-gpio.rst6 the right in-kernel and userspace APIs/ABIs for the job, and that these
10 - leds-gpio: drivers/leds/leds-gpio.c will handle LEDs connected to GPIO
13 - ledtrig-gpio: drivers/leds/trigger/ledtrig-gpio.c will provide a LED trigger,
15 (and that LED may in turn use the leds-gpio as per above).
17 - gpio-keys: drivers/input/keyboard/gpio_keys.c is used when your GPIO line
20 - gpio-keys-polled: drivers/input/keyboard/gpio_keys_polled.c is used when your
24 - gpio_mouse: drivers/input/mouse/gpio_mouse.c is used to provide a mouse with
26 mouse cable and connect the wires to GPIO lines or solder a mouse connector
29 - gpio-beeper: drivers/input/misc/gpio-beeper.c is used to provide a beep from
32 - extcon-gpio: drivers/extcon/extcon-gpio.c is used when you need to read an
[all …]
/kernel/linux/linux-5.10/Documentation/driver-api/gpio/
Ddrivers-on-gpio.rst6 the right in-kernel and userspace APIs/ABIs for the job, and that these
10 - leds-gpio: drivers/leds/leds-gpio.c will handle LEDs connected to GPIO
13 - ledtrig-gpio: drivers/leds/trigger/ledtrig-gpio.c will provide a LED trigger,
15 (and that LED may in turn use the leds-gpio as per above).
17 - gpio-keys: drivers/input/keyboard/gpio_keys.c is used when your GPIO line
20 - gpio-keys-polled: drivers/input/keyboard/gpio_keys_polled.c is used when your
24 - gpio_mouse: drivers/input/mouse/gpio_mouse.c is used to provide a mouse with
26 mouse cable and connect the wires to GPIO lines or solder a mouse connector
29 - gpio-beeper: drivers/input/misc/gpio-beeper.c is used to provide a beep from
32 - extcon-gpio: drivers/extcon/extcon-gpio.c is used when you need to read an
[all …]
/kernel/linux/linux-6.6/Documentation/devicetree/bindings/input/touchscreen/
Dfsl-mx25-tcq.txt7 - compatible: Should be "fsl,imx25-tcq".
8 - reg: Memory range of the device.
9 - interrupts: Should be the interrupt number associated with this module within
11 - fsl,wires: Should be '<4>' or '<5>'
14 - fsl,pen-debounce-ns: Pen debounce time in nanoseconds.
15 - fsl,pen-threshold: Pen-down threshold for the touchscreen. This is a value
20 - fsl,settling-time-ns: Settling time in nanoseconds. The settling time is before
24 This device includes two conversion queues which can be added as subnodes.
29 compatible = "fsl,imx25-tcq";
31 interrupt-parent = <&tscadc>;
[all …]
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/input/touchscreen/
Dfsl-mx25-tcq.txt7 - compatible: Should be "fsl,imx25-tcq".
8 - reg: Memory range of the device.
9 - interrupts: Should be the interrupt number associated with this module within
11 - fsl,wires: Should be '<4>' or '<5>'
14 - fsl,pen-debounce-ns: Pen debounce time in nanoseconds.
15 - fsl,pen-threshold: Pen-down threshold for the touchscreen. This is a value
20 - fsl,settling-time-ns: Settling time in nanoseconds. The settling time is before
24 This device includes two conversion queues which can be added as subnodes.
29 compatible = "fsl,imx25-tcq";
31 interrupt-parent = <&tscadc>;
[all …]
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/iio/adc/
Dat91_adc.txt4 - compatible: Should be "atmel,<chip>-adc"
6 - reg: Should contain ADC registers location and length
7 - interrupts: Should contain the IRQ line for the ADC
8 - clock-names: tuple listing input clock names.
10 - clocks: phandles to input clocks.
11 - atmel,adc-channels-used: Bitmask of the channels muxed and enabled for this
13 - atmel,adc-startup-time: Startup Time of the ADC in microseconds as
15 - atmel,adc-vref: Reference voltage in millivolts for the conversions
16 - atmel,adc-res: List of resolutions in bits supported by the ADC. List size
17 must be two at least.
[all …]
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/media/i2c/
Daptina,mt9v111.txt2 ----------------------------
4 The Aptina MT9V111 is a 1/4-Inch VGA-format digital image sensor with a core
8 of image resolution and formats controllable through a simple two-wires
12 --------------------
14 - compatible: shall be "aptina,mt9v111".
15 - clocks: reference to the system clock input provider.
18 --------------------
20 - enable-gpios: output enable signal, pin name "OE#". Active low.
21 - standby-gpios: low power state control signal, pin name "STANDBY".
23 - reset-gpios: chip reset signal, pin name "RESET#". Active low.
[all …]
/kernel/linux/linux-5.10/Documentation/driver-api/
Dspi.rst6 multiplexed shift register. Its three signal wires hold a clock (SCK,
7 often in the range of 1-20 MHz), a "Master Out, Slave In" (MOSI) data
12 additional chipselect line is usually active-low (nCS); four signals are
22 The programming interface is structured around two kinds of driver, and
23 two kinds of device. A "Controller Driver" abstracts the controller
33 board-specific initialization code. A :c:type:`struct spi_driver
46 .. kernel-doc:: include/linux/spi/spi.h
49 .. kernel-doc:: drivers/spi/spi.c
52 .. kernel-doc:: drivers/spi/spi.c
/kernel/linux/linux-6.6/Documentation/driver-api/
Dspi.rst6 multiplexed shift register. Its three signal wires hold a clock (SCK,
7 often in the range of 1-20 MHz), a "Master Out, Slave In" (MOSI) data
12 additional chipselect line is usually active-low (nCS); four signals are
22 The programming interface is structured around two kinds of driver, and
23 two kinds of device. A "Controller Driver" abstracts the controller
33 board-specific initialization code. A :c:type:`struct spi_driver
46 .. kernel-doc:: include/linux/spi/spi.h
49 .. kernel-doc:: drivers/spi/spi.c
52 .. kernel-doc:: drivers/spi/spi.c
/kernel/linux/linux-6.6/Documentation/devicetree/bindings/media/i2c/
Daptina,mt9v111.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Jacopo Mondi <jacopo@jmondi.org>
13 The Aptina MT9V111 is a 1/4-Inch VGA-format digital image sensor with a core
17 of image resolutions and formats controllable through a simple two-wires
30 enable-gpios:
34 standby-gpios:
39 reset-gpios:
49 - compatible
[all …]
/kernel/linux/linux-5.10/Documentation/input/devices/
Drotary-encoder.rst2 rotary-encoder - a generic driver for GPIO connected devices
8 --------
11 peripherals with two wires. The outputs are phase-shifted by 90 degrees
16 a stable state with both outputs high (half-period mode) and some have
17 a stable state in all steps (quarter-period mode).
19 The phase diagram of these two outputs look like this::
33 |<-------->|
36 |<-->|
37 one step (half-period mode)
40 one step (quarter-period mode)
[all …]
/kernel/linux/linux-6.6/Documentation/input/devices/
Drotary-encoder.rst2 rotary-encoder - a generic driver for GPIO connected devices
8 --------
11 peripherals with two wires. The outputs are phase-shifted by 90 degrees
16 a stable state with both outputs high (half-period mode) and some have
17 a stable state in all steps (quarter-period mode).
19 The phase diagram of these two outputs look like this::
33 |<-------->|
36 |<-->|
37 one step (half-period mode)
40 one step (quarter-period mode)
[all …]
/kernel/linux/linux-5.10/include/linux/spi/
Dspi.h1 /* SPDX-License-Identifier: GPL-2.0-or-later
25 * INTERFACES between SPI master-side drivers and SPI slave protocol handlers,
31 * struct spi_statistics - statistics for spi transfers
34 * @messages: number of spi-messages handled
85 spin_lock_irqsave(&(stats)->lock, flags); \
86 (stats)->field += count; \
87 spin_unlock_irqrestore(&(stats)->lock, flags); \
94 * struct spi_delay - SPI delay information
110 * struct spi_device - Controller side proxy for an SPI slave device
124 * like eight or 12 bits are common. In-memory wordsizes are
[all …]
/kernel/linux/linux-6.6/arch/arm/mach-omap1/
Ddevices.c1 // SPDX-License-Identifier: GPL-2.0-or-later
3 * linux/arch/arm/mach-omap1/devices.c
8 #include <linux/dma-mapping.h>
15 #include <linux/platform_data/omap-wd-timer.h>
16 #include <linux/soc/ti/omap1-io.h>
51 .id = -1,
64 /*-------------------------------------------------------------------------*/
81 if (mmc_controller->slots[0].wires == 4) { in omap1_mmc_mux()
84 if (!mmc_controller->slots[0].nomux) in omap1_mmc_mux()
92 if (!mmc_controller->slots[1].nomux) { in omap1_mmc_mux()
[all …]
/kernel/linux/linux-6.6/Documentation/admin-guide/media/
Dcec.rst1 .. SPDX-License-Identifier: GPL-2.0
12 - Exynos4
13 - Exynos5
14 - STIH4xx HDMI CEC
15 - V4L2 adv7511 (same HW, but a different driver from the drm adv7511)
16 - stm32
17 - Allwinner A10 (sun4i)
18 - Raspberry Pi
19 - dw-hdmi (Synopsis IP)
20 - amlogic (meson ao-cec and ao-cec-g12a)
[all …]
/kernel/linux/linux-6.6/Documentation/w1/
Dw1-generic.rst2 Introduction to the 1-wire (w1) subsystem
5 The 1-wire bus is a simple master-slave bus that communicates via a single
6 signal wire (plus ground, so two wires).
18 - DS9490 usb device
19 - W1-over-GPIO
20 - DS2482 (i2c to w1 bridge)
21 - Emulated devices, such as a RS232 converter, parallel port adapter, etc
25 ------------------------------
29 - sysfs entries for that w1 master are created
30 - the w1 bus is periodically searched for new slave devices
[all …]
/kernel/linux/linux-5.10/Documentation/w1/
Dw1-generic.rst2 Introduction to the 1-wire (w1) subsystem
5 The 1-wire bus is a simple master-slave bus that communicates via a single
6 signal wire (plus ground, so two wires).
18 - DS9490 usb device
19 - W1-over-GPIO
20 - DS2482 (i2c to w1 bridge)
21 - Emulated devices, such as a RS232 converter, parallel port adapter, etc
25 ------------------------------
29 - sysfs entries for that w1 master are created
30 - the w1 bus is periodically searched for new slave devices
[all …]
/kernel/linux/linux-5.10/drivers/input/mouse/
Dvsxxxaa.c1 // SPDX-License-Identifier: GPL-2.0-or-later
3 * Driver for DEC VSXXX-AA mouse (hockey-puck mouse, ball or two rollers)
4 * DEC VSXXX-GA mouse (rectangular mouse, with ball)
5 * DEC VSXXX-AB tablet (digitizer with hair cross or stylus)
7 * Copyright (C) 2003-2004 by Jan-Benedict Glaw <jbglaw@lug-owl.de>
27 * supply at +5V and -12V.
33 * | 4 --- 3 |
35 * -------
38 * 1 (GND) 5 7 -
39 * 2 (RxD) 2 3 -
[all …]
/kernel/linux/linux-6.6/drivers/input/mouse/
Dvsxxxaa.c1 // SPDX-License-Identifier: GPL-2.0-or-later
3 * Driver for DEC VSXXX-AA mouse (hockey-puck mouse, ball or two rollers)
4 * DEC VSXXX-GA mouse (rectangular mouse, with ball)
5 * DEC VSXXX-AB tablet (digitizer with hair cross or stylus)
7 * Copyright (C) 2003-2004 by Jan-Benedict Glaw <jbglaw@lug-owl.de>
24 * supply at +5V and -12V.
30 * | 4 --- 3 |
32 * -------
35 * 1 (GND) 5 7 -
36 * 2 (RxD) 2 3 -
[all …]
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/bus/
Dimx-weim.txt4 without wires. It simply means that this module was originally designed for
5 wireless and mobile applications that use low-power technology.
11 - compatible: Should contain one of the following:
12 "fsl,imx1-weim"
13 "fsl,imx27-weim"
14 "fsl,imx51-weim"
15 "fsl,imx50-weim"
16 "fsl,imx6q-weim"
17 - reg: A resource specifier for the register space
19 - clocks: the clock, see the example below.
[all …]
/kernel/linux/linux-6.6/drivers/gpio/
Dgpio-xtensa.c1 // SPDX-License-Identifier: GPL-2.0
14 * driver treats input and output states as two distinct devices.
24 * different set of IO wires. A theoretical SMP aware version of this driver
127 .base = -1,
136 .base = -1,
155 .name = "xtensa-gpio",
164 pdev = platform_device_register_simple("xtensa-gpio", 0, NULL, 0); in xtensa_gpio_init()
/kernel/linux/linux-5.10/drivers/gpio/
Dgpio-xtensa.c1 // SPDX-License-Identifier: GPL-2.0
14 * driver treats input and output states as two distinct devices.
24 * different set of IO wires. A theoretical SMP aware version of this driver
127 .base = -1,
136 .base = -1,
155 .name = "xtensa-gpio",
164 pdev = platform_device_register_simple("xtensa-gpio", 0, NULL, 0); in xtensa_gpio_init()

123