Searched +full:matrix +full:- +full:connected (Results 1 – 25 of 36) sorted by relevance
12
| /Documentation/devicetree/bindings/input/ |
| D | gpio-matrix-keypad.txt | 1 * GPIO driven matrix keypad device tree bindings 3 GPIO driven matrix keypad is used to interface a SoC with a matrix keypad. 4 The matrix keypad supports multiple row and column lines, a key can be 5 placed at each intersection of a unique row and a unique column. The matrix 6 keypad can sense a key-press and key-release by means of GPIO lines and 10 - compatible: Should be "gpio-matrix-keypad" 11 - row-gpios: List of gpios used as row lines. The gpio specifier 13 which these row lines are connected. 14 - col-gpios: List of gpios used as column lines. The gpio specifier 16 which these column lines are connected. [all …]
|
| D | matrix-keymap.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) 3 --- 4 $id: http://devicetree.org/schemas/input/matrix-keymap.yaml# 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 7 title: Common Key Matrices on Matrix-connected Key Boards 10 - Olof Johansson <olof@lixom.net> 13 A simple common binding for matrix-connected key boards. Currently targeted at 19 for said properties are "linux,fn-keymap" or with another descriptive 24 $ref: /schemas/types.yaml#/definitions/uint32-array 26 An array of packed 1-cell entries containing the equivalent of row, [all …]
|
| D | st-keyscan.txt | 4 matrix-keymap. 7 - compatible: "st,sti-keyscan" 9 - reg: Register base address and size of st-keyscan controller. 11 - interrupts: Interrupt number for the st-keyscan controller. 13 - clocks: Must contain one entry, for the module clock. 14 See ../clocks/clock-bindings.txt for details. 16 - pinctrl: Should specify pin control groups used for this controller. 17 See ../pinctrl/pinctrl-bindings.txt for details. 19 - linux,keymap: The keymap for keys as described in the binding document 20 devicetree/bindings/input/matrix-keymap.txt. [all …]
|
| D | brcm,bcm-keypad.txt | 3 Broadcom Keypad controller is used to interface a SoC with a matrix-type 6 The keypad controller can sense a key-press and key-release and report the 9 This binding is based on the matrix-keymap binding with the following 12 keypad,num-rows and keypad,num-columns are required. 15 - compatible: should be "brcm,bcm-keypad" 17 - reg: physical base address of the controller and length of memory mapped 20 - interrupts: The interrupt number to the cpu. 23 - keypad,num-rows: Number of row lines connected to the keypad 26 - keypad,num-columns: Number of column lines connected to the 29 - col-debounce-filter-period: The debounce period for the Column filter. [all …]
|
| D | samsung,s3c6410-keypad.yaml | 1 # SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause 3 --- 4 $id: http://devicetree.org/schemas/input/samsung,s3c6410-keypad.yaml# 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 10 Samsung SoC Keypad controller is used to interface a SoC with a matrix-type 13 The keypad controller can sense a key-press and key-release and report the 17 - Krzysztof Kozlowski <krzk@kernel.org> 22 - samsung,s3c6410-keypad 23 - samsung,s5pv210-keypad 31 clock-names: [all …]
|
| /Documentation/devicetree/bindings/mfd/ |
| D | tc3589x.txt | 1 * Toshiba TC3589x multi-purpose expander 3 The Toshiba TC3589x series are I2C-based MFD devices which may expose the 4 following built-in devices: gpio, keypad, rotator (vibrator), PWM (for 7 - TC35890 8 - TC35892 9 - TC35893 10 - TC35894 11 - TC35895 12 - TC35896 15 - compatible : must be "toshiba,tc35890", "toshiba,tc35892", "toshiba,tc35893", [all …]
|
| /Documentation/devicetree/bindings/iio/accel/ |
| D | bosch,bma255.yaml | 1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause) 3 --- 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 10 - Linus Walleij <linus.walleij@linaro.org> 11 - Stephan Gerhold <stephan@gerhold.net> 15 4-wire interface. 20 # bmc150-accel driver in Linux 21 - bosch,bma222 22 - bosch,bma222e 23 - bosch,bma250e [all …]
|
| /Documentation/devicetree/bindings/mmc/ |
| D | mmc-spi-slot.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) 3 --- 4 $id: http://devicetree.org/schemas/mmc/mmc-spi-slot.yaml# 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 7 title: MMC/SD/SDIO slot directly connected to a SPI bus 10 - Ulf Hansson <ulf.hansson@linaro.org> 13 - $ref: mmc-controller.yaml 14 - $ref: /schemas/spi/spi-peripheral-props.yaml 17 The extra properties used by an mmc connected via SPI. 21 const: mmc-spi-slot [all …]
|
| /Documentation/devicetree/bindings/iio/imu/ |
| D | st,lsm6dsx.yaml | 1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause) 3 --- 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 7 title: STM 6-axis (acc + gyro) IMU Mems sensors 10 - Lorenzo Bianconi <lorenzo@kernel.org> 18 - enum: 19 - st,lsm6ds3 20 - st,lsm6ds3h 21 - st,lsm6dsl 22 - st,lsm6dsm [all …]
|
| /Documentation/devicetree/bindings/ |
| D | numa.txt | 6 1 - Introduction 18 2 - numa-node-id 23 a node id is a 32-bit integer. 26 numa-node-id property which contains the node id of the device. 30 numa-node-id = <0>; 33 numa-node-id = <1>; 36 3 - distance-map 39 The optional device tree node distance-map describes the relative 42 - compatible : Should at least contain "numa-distance-map-v1". 44 - distance-matrix [all …]
|
| /Documentation/devicetree/bindings/hwmon/ |
| D | gpio-fan.yaml | 1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause) 3 --- 4 $id: http://devicetree.org/schemas/hwmon/gpio-fan.yaml# 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 7 title: Fan connected to GPIO lines 10 - Rob Herring <robh@kernel.org> 14 const: gpio-fan 19 ordered MSB-->LSB. 23 alarm-gpios: 26 gpio-fan,speed-map: [all …]
|
| /Documentation/devicetree/bindings/thermal/ |
| D | generic-adc-thermal.yaml | 1 # SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause 3 --- 4 $id: http://devicetree.org/schemas/thermal/generic-adc-thermal.yaml# 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 10 - Laxman Dewangan <ldewangan@nvidia.com> 13 On some of platforms, thermal sensor like thermistors are connected to 16 temperature using voltage-temperature lookup table. 18 $ref: thermal-sensor.yaml# 22 const: generic-adc-thermal 24 '#thermal-sensor-cells': [all …]
|
| /Documentation/devicetree/bindings/memory-controllers/ |
| D | atmel,ebi.txt | 5 The EBI provides a glue-less interface to asynchronous memories through the SMC 10 - compatible: "atmel,at91sam9260-ebi" 11 "atmel,at91sam9261-ebi" 12 "atmel,at91sam9263-ebi0" 13 "atmel,at91sam9263-ebi1" 14 "atmel,at91sam9rl-ebi" 15 "atmel,at91sam9g45-ebi" 16 "atmel,at91sam9x5-ebi" 17 "atmel,sama5d3-ebi" 18 "microchip,sam9x60-ebi" [all …]
|
| /Documentation/devicetree/bindings/iio/ |
| D | st,st-sensors.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) 3 --- 4 $id: http://devicetree.org/schemas/iio/st,st-sensors.yaml# 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 9 description: The STMicroelectronics sensor devices are pretty straight-forward 16 - Denis Ciocca <denis.ciocca@st.com> 17 - Linus Walleij <linus.walleij@linaro.org> 22 - description: STMicroelectronics Accelerometers 24 - st,h3lis331dl-accel 25 - st,lis2de12 [all …]
|
| /Documentation/devicetree/bindings/soc/fsl/cpm_qe/ |
| D | fsl,cpm1-tsa.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) 3 --- 4 $id: http://devicetree.org/schemas/soc/fsl/cpm_qe/fsl,cpm1-tsa.yaml# 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 7 title: PowerQUICC CPM Time-slot assigner (TSA) controller 10 - Herve Codina <herve.codina@bootlin.com> 13 The TSA is the time-slot assigner that can be found on some PowerQUICC SoC. 14 Its purpose is to route some TDM time-slots to other internal serial 20 - enum: 21 - fsl,mpc885-tsa [all …]
|
| /Documentation/admin-guide/blockdev/drbd/ |
| D | data-structure-v9.rst | 2 kernel data structure for DRBD-9 5 This describes the in kernel data structure for DRBD-9. Starting with 15 The DRBD objects are interconnected to form a matrix as depicted below; a 19 /--------------+---------------+.....+---------------\ 21 +--------------+---------------+.....+---------------+ 23 +--------------+---------------+.....+---------------+ 26 +--------------+---------------+.....+---------------+ 28 \--------------+---------------+.....+---------------/ 32 their volume number. Objects in the vertical direction are connected by double 36 All resources are in the drbd_resources double-linked list. In addition, all
|
| /Documentation/admin-guide/media/ |
| D | ipu3.rst | 1 .. SPDX-License-Identifier: GPL-2.0 24 ImgU). The CIO2 driver is available as drivers/media/pci/intel/ipu3/ipu3-cio2* 36 Both of the drivers implement V4L2, Media Controller and V4L2 sub-device 37 interfaces. The IPU3 CIO2 driver supports camera sensors connected to the CIO2 38 MIPI CSI-2 interfaces through V4L2 sub-device sensor drivers. 44 interface to the user space. There is a video node for each CSI-2 receiver, 47 The CIO2 contains four independent capture channel, each with its own MIPI CSI-2 48 receiver and DMA engine. Each channel is modelled as a V4L2 sub-device exposed 49 to userspace as a V4L2 sub-device node and has two pads: 53 .. flat-table:: [all …]
|
| /Documentation/devicetree/bindings/sound/ |
| D | ti,tlv320aic3x.yaml | 1 # SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause 4 --- 6 $schema: http://devicetree.org/meta-schemas/core.yaml# 11 TLV320AIC3x are a series of low-power stereo audio codecs with stereo 13 single-ended or fully differential configurations. 16 data bus is programmable for I2S, left/right-justified, DSP, or TDM modes. 44 - Jai Luthra <j-luthra@ti.com> 49 - ti,tlv320aic3x 50 - ti,tlv320aic33 51 - ti,tlv320aic3007 [all …]
|
| /Documentation/devicetree/bindings/leds/ |
| D | awinic,aw200xx.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) 3 --- 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 10 - Martin Kurbanov <mmkurbanov@sberdevices.ru> 13 It is a matrix LED driver programmed via an I2C interface. Devices have 16 - AW20036 (3x12) 36 LEDs 17 - AW20054 (6x9) 54 LEDs 18 - AW20072 (6x12) 72 LEDs 19 - AW20108 (9x12) 108 LEDs 22 aw20036 - https://www.awinic.com/en/productDetail/AW20036QNR#tech-docs [all …]
|
| /Documentation/devicetree/bindings/serial/ |
| D | nvidia,tegra20-hsuart.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) 3 --- 4 $id: http://devicetree.org/schemas/serial/nvidia,tegra20-hsuart.yaml# 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 10 - Thierry Reding <thierry.reding@gmail.com> 11 - Jon Hunter <jonathanh@nvidia.com> 16 - enum: 17 - nvidia,tegra20-hsuart 18 - nvidia,tegra30-hsuart 19 - nvidia,tegra186-hsuart [all …]
|
| /Documentation/devicetree/bindings/arm/ |
| D | arm,coresight-cti.yaml | 1 # SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause 4 --- 5 $id: http://devicetree.org/schemas/arm/arm,coresight-cti.yaml# 6 $schema: http://devicetree.org/meta-schemas/core.yaml# 11 The CoreSight Embedded Cross Trigger (ECT) consists of CTI devices connected 13 a star topology via the Cross Trigger Matrix (CTM), which is not programmable. 18 CTI and the components it is directly connected to, consisting of input and 31 are implementation defined, except when the CTI is connected to an ARM v8 36 architecturally connected CTI an additional compatible string is used to 37 indicate this feature (arm,coresight-cti-v8-arch). [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, LTC2986, LTM2985 Multi-sensor Temperature system 10 - Nuno Sá <nuno.sa@analog.com> 13 Analog Devices LTC2983, LTC2984, LTC2986, LTM2985 Multi-Sensor Digital 16 https://www.analog.com/media/en/technical-documentation/data-sheets/2983fc.pdf 17 https://www.analog.com/media/en/technical-documentation/data-sheets/2984fb.pdf 18 https://www.analog.com/media/en/technical-documentation/data-sheets/29861fa.pdf 19 https://www.analog.com/media/en/technical-documentation/data-sheets/ltm2985.pdf [all …]
|
| /Documentation/devicetree/bindings/net/wireless/ |
| D | mediatek,mt76.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) 2 # Copyright (c) 2018-2019 The Linux Foundation. All rights reserved. 4 --- 6 $schema: http://devicetree.org/meta-schemas/core.yaml# 11 - Felix Fietkau <nbd@nbd.name> 12 - Lorenzo Bianconi <lorenzo@kernel.org> 13 - Ryder Lee <ryder.lee@mediatek.com> 18 node of the PCI controller to which the wireless chip is connected. 25 - mediatek,mt76 26 - mediatek,mt7628-wmac [all …]
|
| /Documentation/trace/coresight/ |
| D | coresight-ect.rst | 1 .. SPDX-License-Identifier: GPL-2.0 11 -------------------- 15 devices and interconnects them via the Cross Trigger Matrix (CTM) to other 21 0 C 0----------->: : +======>(other CTI channel IO) 22 0 P 0<-----------: : v 24 0000000 : CTI :<=========>*CTM*<====>: CTI :---+ 25 ####### in_trigs : : (id 0-3) ***** ::::::: v 26 # ETM #----------->: : ^ ####### 27 # #<-----------: : +---# ETR # 34 activating connected output triggers there, unless filtered by the CTI [all …]
|
| /Documentation/ABI/testing/ |
| D | configfs-usb-gadget-uvc | 1 What: /config/usb-gadget/gadget/functions/uvc.name 13 What: /config/usb-gadget/gadget/functions/uvc.name/control 27 What: /config/usb-gadget/gadget/functions/uvc.name/control/class 32 What: /config/usb-gadget/gadget/functions/uvc.name/control/class/ss 37 What: /config/usb-gadget/gadget/functions/uvc.name/control/class/fs 42 What: /config/usb-gadget/gadget/functions/uvc.name/control/terminal 47 What: /config/usb-gadget/gadget/functions/uvc.name/control/terminal/output 52 What: /config/usb-gadget/gadget/functions/uvc.name/control/terminal/output/default 62 is connected 66 bTerminalID a non-zero id of this terminal [all …]
|
12