Searched +full:number +full:- +full:of +full:- +full:wires (Results 1 – 18 of 18) sorted by relevance
/Documentation/devicetree/bindings/mfd/ |
D | mxs-lradc.txt | 4 - compatible: Should be "fsl,imx23-lradc" for i.MX23 SoC and "fsl,imx28-lradc" 6 - reg: Address and length of the register set for the device 7 - interrupts: Should contain the LRADC interrupts 10 - fsl,lradc-touchscreen-wires: Number of wires used to connect the touchscreen 13 disabled. 5 wires is valid for i.MX28 SoC only. 14 - fsl,ave-ctrl: number of samples per direction to calculate an average value. 16 - fsl,ave-delay: delay between consecutive samples. Allowed value is 17 2 ... 2048. It is used if 'fsl,ave-ctrl' > 1, counts at 19 - fsl,settling: delay between plate switch to next sample. Allowed value is 26 compatible = "fsl,imx23-lradc"; [all …]
|
/Documentation/devicetree/bindings/input/touchscreen/ |
D | ti-tsc-adc.txt | 1 * TI - TSC ADC (Touschscreen and analog digital converter) 5 - mfd 7 "ti,am3359-tscadc" for AM335x/AM437x SoCs 8 "ti,am654-tscadc", "ti,am3359-tscadc" for AM654 SoCs 9 - child "tsc" 10 compatible: Should be "ti,am3359-tsc". 11 ti,wires: Wires refer to application modes i.e. 4/5/8 wire touchscreen 13 ti,x-plate-resistance: X plate resistance 14 ti,coordinate-readouts: The sequencer supports a total of 16 19 A value of 5 means, 5 reads for X, 5 for [all …]
|
D | fsl-mx25-tcq.txt | 3 mx25 touchscreen conversion queue module which controls the ADC unit of the 7 - 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 29 compatible = "fsl,imx25-tcq"; 31 interrupt-parent = <&tscadc>; [all …]
|
/Documentation/devicetree/bindings/iio/adc/ |
D | at91_adc.txt | 4 - 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 18 - atmel,adc-res-names: Contains one identifier string for each resolution [all …]
|
/Documentation/devicetree/bindings/display/tilcdc/ |
D | tilcdc.txt | 1 Device-Tree bindings for tilcdc DRM driver 4 - compatible: value should be one of the following: 5 - "ti,am33xx-tilcdc" for AM335x based boards 6 - "ti,da850-tilcdc" for DA850/AM18x/OMAP-L138 based boards 7 - interrupts: the interrupt number 8 - reg: base address and size of the LCDC device 11 - ti,hwmods: Name of the hwmod associated to the LCDC 14 - max-bandwidth: The maximum pixels per second that the memory 16 - max-width: The maximum horizontal pixel width supported by 18 - max-pixelclock: The maximum pixel clock that can be supported [all …]
|
/Documentation/devicetree/bindings/media/i2c/ |
D | aptina,mt9v111.txt | 2 ---------------------------- 4 The Aptina MT9V111 is a 1/4-Inch VGA-format digital image sensor with a core 7 The sensor has an active pixel array of 640x480 pixels and can output a number 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". [all …]
|
/Documentation/driver-api/gpio/ |
D | drivers-on-gpio.rst | 6 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 27 to the lines for a more permanent solution of this type. 29 - gpio-beeper: drivers/input/misc/gpio-beeper.c is used to provide a beep from [all …]
|
/Documentation/devicetree/bindings/iio/temperature/ |
D | adi,ltc2983.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) 3 --- 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 7 title: Analog Devices LTC2983 Multi-sensor Temperature system 10 - Nuno Sá <nuno.sa@analog.com> 13 Analog Devices LTC2983 Multi-Sensor Digital Temperature Measurement System 14 https://www.analog.com/media/en/technical-documentation/data-sheets/2983fc.pdf 19 - adi,ltc2983 27 adi,mux-delay-config-us: 38 adi,filter-notch-freq: [all …]
|
/Documentation/devicetree/bindings/interrupt-controller/ |
D | marvell,icu.txt | 2 -------------------------------- 5 responsible for collecting all wired-interrupt sources in the CP and 7 requests on input wires to MSG memory mapped transactions to the GIC. 13 - compatible: Should be "marvell,cp110-icu" 15 - reg: Should contain ICU registers location and length. 17 Subnodes: Each group of interrupt is declared as a subnode of the ICU, 22 - compatible: Should be one of: 23 * "marvell,cp110-icu-nsr" 24 * "marvell,cp110-icu-sr" 25 * "marvell,cp110-icu-sei" [all …]
|
/Documentation/devicetree/bindings/bus/ |
D | imx-weim.txt | 4 without wires. It simply means that this module was originally designed for 5 wireless and mobile applications that use low-power technology. 7 The actual devices are instantiated from the child nodes of a WEIM node. 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 [all …]
|
/Documentation/w1/ |
D | w1-generic.rst | 2 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). 9 drain output and by sampling the logic level of the signal line. 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 [all …]
|
/Documentation/input/devices/ |
D | joystick-parport.rst | 3 .. _joystick-parport: 9 :Copyright: |copy| 1998-2000 Vojtech Pavlik <vojtech@ucw.cz> 10 :Copyright: |copy| 1998 Andree Borrmann <a.borrmann@tu-bs.de> 18 Any information in this file is provided as-is, without any guarantee that 27 originally designed for PCs and other computers Linux runs on. Because of 29 port, because of its ability to change single bits at will, and providing 36 Many console and 8-bit computer gamepads and joysticks are supported. The 37 following subsections discuss usage of each. 40 ------------ 51 the output lines of the parallel port are shared, while one of 5 available [all …]
|
/Documentation/spi/ |
D | spi-summary.rst | 2 Overview of Linux kernel SPI support 5 02-Feb-2012 8 ------------ 14 The three signal wires hold a clock (SCK, often on the order of 10 MHz), 17 clocking modes through which data is exchanged; mode-0 and mode-3 are most 23 device, so those three signal wires may be connected to several chips 32 - SPI may be used for request/response style device protocols, as with 35 - It may also be used to stream data in either direction (half duplex), 36 or both of them at the same time (full duplex). 38 - Some devices may use eight bit words. Others may use different word [all …]
|
/Documentation/driver-api/ |
D | xillybus.rst | 10 - Introduction 11 -- Background 12 -- Xillybus Overview 14 - Usage 15 -- User interface 16 -- Synchronization 17 -- Seekable pipes 19 - Internals 20 -- Source code organization 21 -- Pipe attributes [all …]
|
/Documentation/ide/ |
D | ide.rst | 9 ------------------------------------------------------------------------------- 15 PCI versions of the CMD640 and RZ1000 interfaces are now detected 18 Linux disables the "prefetch" ("readahead") mode of the RZ1000 21 For the CMD640, linux disables "IRQ unmasking" (hdparm -u1) on any 22 drive for which the "prefetch" mode of the CMD640 is turned on. 23 If "prefetch" is disabled (hdparm -p8), then "IRQ unmasking" can be 26 For the CMD640, linux disables "32bit I/O" (hdparm -c1) on any drive 27 for which the "prefetch" mode of the CMD640 is turned off. 28 If "prefetch" is enabled (hdparm -p9), then "32bit I/O" can be 35 Use of the "serialize" option is no longer necessary. [all …]
|
/Documentation/networking/device_drivers/wifi/intel/ |
D | ipw2200.rst | 1 .. SPDX-License-Identifier: GPL-2.0 11 - Intel(R) PRO/Wireless 2200BG Network Connection 12 - Intel(R) PRO/Wireless 2915ABG Network Connection 20 Copyright |copy| 2004-2006, Intel Corporation 32 1.1. Overview of features 37 2. Ad-Hoc Networking 69 of the software provided in binary format with the wireless WLAN 75 ensuring the regulatory compliance of the products, (ii) Intel will bear 76 no liability, under any theory of liability for any issues associated 78 the warranty and/or issues arising from regulatory non-compliance, and [all …]
|
/Documentation/admin-guide/media/ |
D | i2c-cardlist.rst | 1 .. SPDX-License-Identifier: GPL-2.0 6 The I²C (Inter-Integrated Circuit) bus is a three-wires bus used internally 13 One of the problems with I²C devices is that sometimes the same device may 17 different tuner number in order to address such issue. 19 The current supported of I²C drivers (not including staging drivers) are 23 ------------------------------------- 32 sony-btf-mpx Sony BTF's internal MPX 47 ----------------------------- 52 saa6752hs Philips SAA6752HS MPEG-2 Audio/Video Encoder 56 --------------------- [all …]
|
/Documentation/networking/ |
D | arcnet-hardware.rst | 1 .. SPDX-License-Identifier: GPL-2.0 11 2) This file is no longer Linux-specific. It should probably be moved out 12 of the kernel sources. Ideas? 16 some cabling tips, and a listing of all jumper settings I can find. Please 17 e-mail apenwarr@worldvisions.ca with any settings for your particular card, 27 First of all, you can get ARCnet cards in at least two speeds: 2.5 Mbps 36 You also cannot connect an ARCnet card to any kind of Ethernet card and 39 There are two "types" of ARCnet - STAR topology and BUS topology. This 46 well-designed standard. It uses something called "modified token passing" 47 which makes it completely incompatible with so-called "Token Ring" cards, [all …]
|