Searched +full:two +full:- +full:wire (Results 1 – 25 of 72) sorted by relevance
123
| /Documentation/devicetree/bindings/interrupt-controller/ |
| D | intel,ce4100-lapic.yaml | 1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause) 3 --- 4 $id: http://devicetree.org/schemas/interrupt-controller/intel,ce4100-lapic.yaml# 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 10 - Rahul Tanwar <rtanwar@maxlinear.com> 28 [1] https://pdos.csail.mit.edu/6.828/2008/readings/ia32/IA32-3A.pdf 32 const: intel,ce4100-lapic 37 interrupt-controller: true 39 '#interrupt-cells': 42 intel,virtual-wire-mode: [all …]
|
| /Documentation/devicetree/bindings/sound/ |
| D | mt6359.yaml | 1 # 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 …]
|
| D | mt6358.txt | 10 - 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>;
|
| D | mediatek,mt8365-afe.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) 3 --- 4 $id: http://devicetree.org/schemas/sound/mediatek,mt8365-afe.yaml# 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 10 - Alexandre Mergnat <amergnat@baylibre.com> 14 const: mediatek,mt8365-afe-pcm 19 "#sound-dai-cells": 24 - description: 26M clock 25 - description: mux for audio clock 26 - description: audio i2s0 mck [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). 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 …]
|
| /Documentation/hwmon/ |
| D | lm85.rst | 79 - Philip Pokorny <ppokorny@penguincomputing.com>, 80 - Frodo Looijaard <frodol@dds.nl>, 81 - Richard Barrington <rich_b_nz@clear.net.nz>, 82 - Margit Schubert-While <margitsw@t-online.de>, 83 - Justin Thiessen <jthiessen@penguincomputing.com> 86 ----------- 92 The LM85 uses the 2-wire interface compatible with the SMBUS 2.0 94 temperatures and five (5) voltages. It has four (4) 16-bit counters for 104 The temperatures measured are one internal diode, and two remote diodes. 127 ---------------- [all …]
|
| D | lm95234.rst | 22 Author: Guenter Roeck <linux@roeck-us.net> 25 ----------- 27 LM95233 and LM95234 are 11-bit digital temperature sensors with a 2-wire 29 that can very accurately monitor the temperature of two (LM95233) 32 graphics processors or diode-connected 2N3904s. The chip's TruTherm 37 is provided within a range of -127 to +255 degrees (+127.875 degrees for 42 affects the hysteresis on all channels. The first two external sensors also
|
| D | tc654.rst | 13 - Chris Packham <chris.packham@alliedtelesis.co.nz> 14 - Masahiko Iwamoto <iwamoto@allied-telesis.co.jp> 17 ----------- 20 The TC654 uses the 2-wire interface compatible with the SMBUS 2.0 21 specification. The TC654 has two (2) inputs for measuring fan RPM and 25 -------------------
|
| D | lm95245.rst | 22 Author: Alexander Stein <alexander.stein@systec-electronic.com> 25 ----------- 27 LM95235 and LM95245 are 11-bit digital temperature sensors with a 2-wire System 34 is given within a range of -127 to +127.875 degrees. Remote temperatures are 35 given within a range of -127 to +255 degrees. Resolution depends on 40 user-space applications, two absolute values are exported, one for each 42 can be set from user-space, and the same delta applies to the remote
|
| D | asc7621.rst | 20 Andigilog has both the PECI and pre-PECI versions of the Heceta-6, as 21 Intel calls them. Heceta-6e has high frequency PWM and Heceta-6p has 23 Heceta-6e part and aSC7621 is the Heceta-6p part. They are both in 28 have used registers below 20h for vendor-specific functions in addition 29 to those in the Intel-specified vendor range. 31 Our conversion process produces a result that is reported as two bytes. 32 The fan speed control uses this finer value to produce a "step-less" fan 33 PWM output. These two bytes are "read-locked" to guarantee that once a 34 high or low byte is read, the other byte is locked-in until after the 37 sheet says 10-bits of resolution, although you may find the lower bits [all …]
|
| D | adt7470.rst | 17 ----------- 22 The ADT7470 uses the 2-wire interface compatible with the SMBus 2.0 24 external temperatures. It has four (4) 16-bit counters for measuring fan speed. 45 ---------------- 47 The ADT7470 has a 8-bit ADC and is capable of measuring temperatures with 1 54 ------------------- 61 * pwm#_auto_point2_pwm and pwm#_auto_point2_temp - 63 - point1: Set the pwm speed at a lower temperature bound. 64 - point2: Set the pwm speed at a higher temperature bound. 67 the temperature is between the two temperature boundaries. PWM values range [all …]
|
| /Documentation/devicetree/bindings/watchdog/ |
| D | zii,rave-sp-wdt.txt | 7 Documentation/devicetree/bindings/mfd/zii,rave-sp.txt) 11 - compatible: Depending on wire protocol implemented by RAVE SP 13 - "zii,rave-sp-watchdog" 14 - "zii,rave-sp-watchdog-legacy" 18 - wdt-timeout: Two byte nvmem cell specified as per 23 rave-sp { 24 compatible = "zii,rave-sp-rdu1"; 25 current-speed = <38400>; 28 wdt_timeout: wdt-timeout@8E { 34 compatible = "zii,rave-sp-watchdog"; [all …]
|
| /Documentation/devicetree/bindings/i2c/ |
| D | i2c-octeon.txt | 1 * Two Wire Serial Interface (TWSI) / I2C 3 - compatible: "cavium,octeon-3860-twsi" 9 compatible: "cavium,octeon-7890-twsi" 13 - reg: The base address of the TWSI/I2C bus controller register bank. 15 - #address-cells: Must be <1>. 17 - #size-cells: Must be <0>. I2C addresses have no size component. 19 - interrupts: A single interrupt specifier. 21 - clock-frequency: The I2C bus clock rate in Hz. 25 #address-cells = <1>; 26 #size-cells = <0>; [all …]
|
| /Documentation/devicetree/bindings/media/i2c/ |
| D | mt9m111.txt | 4 array size of 1280H x 1024V. It is programmable through a simple two-wire serial 8 - compatible: value should be "micron,mt9m111" 9 - clocks: reference to the master clock. 10 - clock-names: shall be "mclk". 13 sub-node for its digital output video port, in accordance with the video 15 Documentation/devicetree/bindings/media/video-interfaces.txt 18 - pclk-sample: For information see ../video-interfaces.txt. The value is set to 28 clock-names = "mclk"; 32 remote-endpoint = <&pxa_camera>; 33 pclk-sample = <1>;
|
| D | mt9v032.txt | 1 * Aptina 1/3-Inch WVGA CMOS Digital Image Sensor 3 The Aptina MT9V032 is a 1/3-inch CMOS active pixel digital image sensor with 5 two-wire serial interface. 9 - compatible: value should be either one among the following 21 - link-frequencies: List of allowed link frequencies in Hz. Each frequency is 22 expressed as a 64-bit big-endian integer. 23 - reset-gpios: GPIO handle which is connected to the reset pin of the chip. 24 - standby-gpios: GPIO handle which is connected to the standby pin of the chip. 27 Documentation/devicetree/bindings/media/video-interfaces.txt. 37 link-frequencies = /bits/ 64
|
| D | aptina,mt9p031.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: Aptina 1/2.5-Inch 5Mp CMOS Digital Image Sensor 10 - Laurent Pinchart <laurent.pinchart@ideasonboard.com> 13 The Aptina MT9P031 is a 1/2.5-inch CMOS active pixel digital image sensor 15 simple two-wire serial interface. 20 - aptina,mt9p006 21 - aptina,mt9p031 22 - aptina,mt9p031m [all …]
|
| D | sony,imx296.yaml | 1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause) 3 --- 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 7 title: Sony IMX296 1/2.8-Inch CMOS Image Sensor 10 - Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org> 11 - Laurent Pinchart <laurent.pinchart@ideasonboard.com> 13 description: |- 14 The Sony IMX296 is a 1/2.9-Inch active pixel type CMOS Solid-state image 16 features a global shutter with variable charge-integration time. It is 17 programmable through I2C and 4-wire interfaces. The sensor output is [all …]
|
| D | ovti,ov8856.yaml | 1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause) 4 --- 6 $schema: http://devicetree.org/meta-schemas/core.yaml# 11 - Sakari Ailus <sakari.ailus@linux.intel.com> 13 description: |- 14 The Omnivision OV8856 is a high performance, 1/4-inch, 8 megapixel, CMOS 15 image sensor that delivers 3264x2448 at 30fps. It provides full-frame, 16 sub-sampled, and windowed 10-bit MIPI images in various formats via the 18 through I2C and two-wire SCCB. The sensor output is available via CSI-2 19 serial data output (up to 4-lane). [all …]
|
| D | ovti,ov5675.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) 4 --- 6 $schema: http://devicetree.org/meta-schemas/core.yaml# 11 - Quentin Schulz <quentin.schulz@theobroma-systems.com> 14 - $ref: /schemas/media/video-interface-devices.yaml# 17 The Omnivision OV5675 is a high performance, 1/5-inch, 5 megapixel, CMOS 18 image sensor that delivers 2592x1944 at 30fps. It provides full-frame, 19 sub-sampled, and windowed 10-bit MIPI images in various formats via the 22 This chip is programmable through I2C and two-wire SCCB. The sensor output 23 is available via CSI-2 serial data output (up to 2-lane). [all …]
|
| /Documentation/i2c/ |
| D | summary.rst | 6 a protocol developed by Philips. It is a two-wire protocol with variable 12 e.g. TWI (Two Wire Interface), IIC. 14 The latest official I2C specification is the `"I²C-bus specification and user 15 manual" (UM10204) <https://www.nxp.com/docs/en/user-guide/UM10204.pdf>`_ 36 .. kernel-figure:: i2c_bus.svg 59 video-related chips. 66 -------- 75 -------------------- 82 target. Work to replace the old terminology in the Linux Kernel is on-going.
|
| /Documentation/driver-api/ |
| D | i2c.rst | 5 the "Inter-IC" bus, a simple bus protocol which is widely used where low 7 some vendors use another name (such as "Two-Wire Interface", TWI) for 8 the same bus. I2C only needs two signals (SCL for clock, SDA for data), 12 I2C is a multi-master bus; open drain signaling is used to arbitrate 18 structured around two kinds of driver, and two kinds of device. An I2C 38 .. kernel-doc:: include/linux/i2c.h 41 .. kernel-doc:: drivers/i2c/i2c-boardinfo.c 44 .. kernel-doc:: drivers/i2c/i2c-core-base.c 47 .. kernel-doc:: drivers/i2c/i2c-core-smbus.c
|
| /Documentation/devicetree/bindings/fsi/ |
| D | fsi-controller.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) 3 --- 4 $id: http://devicetree.org/schemas/fsi/fsi-controller.yaml# 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 10 - Eddie James <eajames@linux.ibm.com> 13 FSI (FRU (Field Replaceable Unit) Service Interface) is a two wire bus. The 18 "#address-cells": 21 "#size-cells": 24 '#interrupt-cells': 27 bus-frequency: [all …]
|
| /Documentation/devicetree/bindings/net/ |
| D | adi,adin1110.yaml | 1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause) 3 --- 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 7 title: ADI ADIN1110 MAC-PHY 10 - Alexandru Tachici <alexandru.tachici@analog.com> 13 The ADIN1110 is a low power single port 10BASE-T1L MAC- 18 The ADIN2111 is a low power, low complexity, two-Ethernet ports 19 switch with integrated 10BASE-T1L PHYs and one serial peripheral 22 with the IEEE 802.3cg-2019 Ethernet standard for long reach 25 The device has a 4-wire SPI interface for communication [all …]
|
| /Documentation/devicetree/bindings/powerpc/fsl/ |
| D | mpc5200.txt | 2 ---------------------------- 4 (c) 2006-2009 Secret Lab Technologies Ltd 8 ------------------ 9 For mpc5200 on-chip devices, the format for each compatible value is 10 <chip>-<device>[-<mode>]. The OS should be able to match a device driver 11 to the device based solely on the compatible value. If two drivers 21 "fsl,mpc5200-<device>". 28 should have two items in the compatible list: 29 compatible = "fsl,mpc5200b-<device>","fsl,mpc5200-<device>"; 34 ie. ethernet on mpc5200: compatible = "fsl,mpc5200-fec"; [all …]
|
| /Documentation/w1/slaves/ |
| D | w1_ds2413.rst | 7 * Maxim DS2413 1-Wire Dual Channel Addressable Switch 18 ----------- 20 The DS2413 chip has two open-drain outputs (PIO A and PIO B). 24 ------------- 25 The "state" file provides one-byte value which is in the same format as for 33 Bit 4-7: Complement of Bit 3 to Bit 0 (verified by the kernel module) 39 -------------- 41 It is writable, you can write one-byte value to this sysfs file. 47 Bit 2-7: No matter (driver will set it to "1"s)
|
123