Searched +full:spi +full:- +full:cs +full:- +full:high (Results 1 – 25 of 29) sorted by relevance
12
| /Documentation/devicetree/bindings/spi/ |
| D | spi-controller.yaml | 1 # SPDX-License-Identifier: GPL-2.0 3 --- 4 $id: http://devicetree.org/schemas/spi/spi-controller.yaml# 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 7 title: SPI Controller Common Properties 10 - Mark Brown <broonie@kernel.org> 13 SPI busses can be described with a node for the SPI controller device 14 and a set of child nodes for each SPI slave on the bus. The system SPI 15 controller may be described for use in SPI master mode or in SPI slave mode, 20 pattern: "^spi(@.*|-([0-9]|[1-9][0-9]+))?$" [all …]
|
| D | icpdas-lp8841-spi-rtc.txt | 1 * ICP DAS LP-8841 SPI Controller for RTC 3 ICP DAS LP-8841 contains a DS-1302 RTC. RTC is connected to an IO 4 memory register, which acts as an SPI master device. 6 The device uses the standard MicroWire half-duplex transfer timing. 13 - #address-cells: should be 1 15 - #size-cells: should be 0 17 - compatible: should be "icpdas,lp8841-spi-rtc" 19 - reg: should provide IO memory address 21 Requirements to SPI slave nodes: 23 - There can be only one slave device. [all …]
|
| D | spi-peripheral-props.yaml | 1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause) 3 --- 4 $id: http://devicetree.org/schemas/spi/spi-peripheral-props.yaml# 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 7 title: Peripheral-specific properties for a SPI bus. 10 Many SPI controllers need to add properties to peripheral devices. They could 11 be common properties like spi-max-frequency, spi-cpha, etc. or they could be 13 need to be defined in the peripheral node because they are per-peripheral and 19 - Mark Brown <broonie@kernel.org> 27 - minimum: 0 [all …]
|
| D | renesas,sh-msiof.yaml | 1 # SPDX-License-Identifier: GPL-2.0 3 --- 4 $id: http://devicetree.org/schemas/spi/renesas,sh-msiof.yaml# 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 7 title: Renesas MSIOF SPI controller 10 - Geert Uytterhoeven <geert+renesas@glider.be> 13 - $ref: spi-controller.yaml# 18 - items: 19 - const: renesas,msiof-sh73a0 # SH-Mobile AG5 20 - const: renesas,sh-mobile-msiof # generic SH-Mobile compatible [all …]
|
| D | brcm,bcm63xx-hsspi.yaml | 1 # SPDX-License-Identifier: GPL-2.0 OR BSD-2-Clause 3 --- 4 $id: http://devicetree.org/schemas/spi/brcm,bcm63xx-hsspi.yaml# 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 7 title: Broadcom Broadband SoC High Speed SPI controller 10 - William Zhang <william.zhang@broadcom.com> 11 - Kursad Oney <kursad.oney@broadcom.com> 12 - Jonas Gorski <jonas.gorski@gmail.com> 15 Broadcom Broadband SoC supports High Speed SPI master controller since the 19 brcm,bcm6328-hsspi compatible string. The recent ARM based chip is required to [all …]
|
| /Documentation/devicetree/bindings/rtc/ |
| D | epson,rx6110.txt | 4 The Epson RX6110 can be used with SPI or I2C busses. The kind of 8 -------- 11 - compatible: should be: "epson,rx6110" 12 - reg : the I2C address of the device for I2C 21 SPI mode 22 -------- 25 - compatible: should be: "epson,rx6110" 26 - reg: chip select number 27 - spi-cs-high: RX6110 needs chipselect high 28 - spi-cpha: RX6110 works with SPI shifted clock phase [all …]
|
| D | maxim-ds1302.txt | 1 * Maxim/Dallas Semiconductor DS-1302 RTC 5 The device uses the standard MicroWire half-duplex transfer timing. 12 - compatible : Should be "maxim,ds1302" 14 Required SPI properties: 16 - reg : Should be address of the device chip select within 19 - spi-max-frequency : DS-1302 has 500 kHz if powered at 2.2V, 22 - spi-3wire : The device has a shared signal IN/OUT line. 24 - spi-lsb-first : DS-1302 requires least significant bit first 27 - spi-cs-high: DS-1302 has active high chip select line. This is 32 spi@901c { [all …]
|
| D | nxp,pcf2123.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: NXP PCF2123 SPI Real Time Clock 10 - Javier Carrasco <javier.carrasco.cruz@gmail.com> 13 - $ref: /schemas/spi/spi-peripheral-props.yaml# 14 - $ref: rtc.yaml# 19 - nxp,pcf2123 28 - compatible 29 - reg [all …]
|
| /Documentation/devicetree/bindings/iio/adc/ |
| D | adi,ad7944.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) 3 --- 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 10 - Michael Hennerich <Michael.Hennerich@analog.com> 11 - Nuno Sá <nuno.sa@analog.com> 14 A family of pin-compatible single channel differential analog to digital 15 converters with SPI support in a LFCSP package. 21 $ref: /schemas/spi/spi-peripheral-props.yaml# 26 - adi,ad7944 27 - adi,ad7985 [all …]
|
| D | adi,ad4000.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) 3 --- 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 10 - Marcelo Schmitt <marcelo.schmitt@analog.com> 13 Analog Devices AD4000 family of Analog to Digital Converters with SPI support. 15 https://www.analog.com/media/en/technical-documentation/data-sheets/ad4000-4004-4008.pdf 16 https://www.analog.com/media/en/technical-documentation/data-sheets/ad4001-4005.pdf 17 https://www.analog.com/media/en/technical-documentation/data-sheets/ad4002-4006-4010.pdf 18 https://www.analog.com/media/en/technical-documentation/data-sheets/ad4003-4007-4011.pdf 19 https://www.analog.com/media/en/technical-documentation/data-sheets/ad4020-4021-4022.pdf [all …]
|
| D | adi,ad4695.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) 3 --- 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 10 - Michael Hennerich <Michael.Hennerich@analog.com> 11 - Nuno Sá <nuno.sa@analog.com> 14 A family of similar multi-channel analog to digital converters with SPI bus. 21 $ref: /schemas/spi/spi-peripheral-props.yaml# 26 - adi,ad4695 27 - adi,ad4696 28 - adi,ad4697 [all …]
|
| D | microchip,mcp3564.yaml | 1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause) 3 --- 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 10 - Marius Cristea <marius.cristea@microchip.com> 13 Bindings for the Microchip family of 153.6 ksps, Low-Noise 16/24-Bit 14 Delta-Sigma ADCs with an SPI interface. Datasheet can be found here: 16 …s/aemDocuments/documents/MSLD/ProductDocuments/DataSheets/MCP3561-2-4-Family-Data-Sheet-DS20006181… 18 …ds/aemDocuments/documents/APID/ProductDocuments/DataSheets/MCP3561_2_4R-Data-Sheet-DS200006391C.pdf 20 …ProductDocuments/DataSheets/MCP3461-2-4-Two-Four-Eight-Channel-153.6-ksps-Low-Noise-16-Bit-Delta-S… 22 …/aemDocuments/documents/APID/ProductDocuments/DataSheets/MCP3461-2-4R-Family-Data-Sheet-DS20006404… [all …]
|
| /Documentation/devicetree/bindings/gpio/ |
| D | spear_spics.txt | 1 === ST Microelectronics SPEAr SPI CS Driver === 4 Cell spi controller through its system registers, which otherwise remains under 7 desired by some of the device protocols above spi which expect (multiple) 17 * compatible: should be defined as "st,spear-spics-gpio" 19 * st-spics,peripcfg-reg: peripheral configuration register offset 20 * st-spics,sw-enable-bit: bit offset to enable sw control 21 * st-spics,cs-value-bit: bit offset to drive chipselect low or high 22 * st-spics,cs-enable-mask: chip select number bit mask 23 * st-spics,cs-enable-shift: chip select number program offset 24 * gpio-controller: Marks the device node as gpio controller [all …]
|
| /Documentation/devicetree/bindings/mfd/ |
| D | motorola-cpcap.txt | 4 - compatible : One or both of "motorola,cpcap" or "ste,6556002" 5 - reg : SPI chip select 6 - interrupts : The interrupt line the device is connected to 7 - interrupt-controller : Marks the device node as an interrupt controller 8 - #interrupt-cells : The number of cells to describe an IRQ, should be 2 9 - #address-cells : Child device offset number of cells, should be 1 10 - #size-cells : Child device size number of cells, should be 0 11 - spi-max-frequency : Typically set to 3000000 12 - spi-cs-high : SPI chip select direction 16 The sub-functions of CPCAP get their own node with their own compatible values, [all …]
|
| /Documentation/iio/ |
| D | ad4000.rst | 1 .. SPDX-License-Identifier: GPL-2.0-only 30 ------------------ 32 Devices of the AD4000 series can be connected to the SPI host controller in a 35 CS mode, 3-wire turbo mode 38 Datasheet "3-wire" mode is what most resembles standard SPI connection which, 39 for these devices, comprises of connecting the controller CS line to device CNV 40 pin and other SPI lines as usual. This configuration is (misleadingly) called 41 "CS Mode, 3-Wire Turbo Mode" connection in datasheets. 42 NOTE: The datasheet definition of 3-wire mode for the AD4000 series is NOT the 43 same of standard spi-3wire mode. [all …]
|
| D | ad4695.rst | 1 .. SPDX-License-Identifier: GPL-2.0-only 25 SPI wiring modes 26 ---------------- 28 The driver currently supports the following SPI wiring configuration: 30 4-wire mode 33 In this mode, CNV and CS are tied together and there is a single SDO line. 35 .. code-block:: 37 +-------------+ +-------------+ 38 | CS |<-+------| CS | 39 | CNV |<-+ | | [all …]
|
| D | ad7944.rst | 1 .. SPDX-License-Identifier: GPL-2.0-only 24 SPI wiring modes 25 ---------------- 27 The driver currently supports three of the many possible SPI wiring configurations. 29 CS mode, 3-wire, without busy indicator 32 .. code-block:: 34 +-------------+ 35 +--------------------| CS | 37 VIO +--------------------+ | HOST | 39 +--->| SDI AD7944 SDO |-------->| SDI | [all …]
|
| /Documentation/devicetree/bindings/eeprom/ |
| D | microchip,93lc46b.yaml | 1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause) 3 --- 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 7 title: Microchip 93xx46 SPI compatible EEPROM family 10 - Cory Tusar <cory.tusar@pid1solutions.com> 15 - atmel,at93c46 16 - atmel,at93c46d 17 - atmel,at93c56 18 - atmel,at93c66 19 - eeprom-93xx46 [all …]
|
| /Documentation/devicetree/bindings/pinctrl/ |
| D | marvell,dove-pinctrl.txt | 3 Please refer to marvell,mvebu-pinctrl.txt in this directory for common binding 7 - compatible: "marvell,dove-pinctrl" 8 - clocks: (optional) phandle of pdma clock 9 - reg: register specifiers of MPP, MPP4, and PMU MPP registers 23 uart1(cts), lcd-spi(cs1), pmu* 25 mpp5 5 gpio, pmu, uart3(cts), sdio1(wp), spi1(cs), pmu* 31 mpp11 11 gpio, pmu, sata(prsnt), sata-1(act), sdio0(ledctrl), 39 mpp16 16 gpio, uart3(rts), sdio0(cd), ac97(sdi1), lcd-spi(cs1) 41 ac97-1(sysclko) 44 mpp20 20 gpio, sdio0(cd), sdio1(cd), spi1(miso), lcd-spi(miso), [all …]
|
| D | qcom,msm8916-pinctrl.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) 3 --- 4 $id: http://devicetree.org/schemas/pinctrl/qcom,msm8916-pinctrl.yaml# 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 10 - Bjorn Andersson <andersson@kernel.org> 11 - Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org> 18 const: qcom,msm8916-pinctrl 26 gpio-reserved-ranges: 30 gpio-line-names: 34 "-state$": [all …]
|
| D | qcom,msm8996-pinctrl.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) 3 --- 4 $id: http://devicetree.org/schemas/pinctrl/qcom,msm8996-pinctrl.yaml# 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 10 - Bjorn Andersson <andersson@kernel.org> 11 - Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org> 18 const: qcom,msm8996-pinctrl 26 gpio-reserved-ranges: 30 gpio-line-names: 34 "-state$": [all …]
|
| /Documentation/devicetree/bindings/net/dsa/ |
| D | microchip,ksz.yaml | 1 # SPDX-License-Identifier: GPL-2.0-only 3 --- 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 10 - Marek Vasut <marex@denx.de> 11 - Woojung Huh <Woojung.Huh@microchip.com> 14 - $ref: /schemas/spi/spi-peripheral-props.yaml# 21 - microchip,ksz8765 22 - microchip,ksz8794 23 - microchip,ksz8795 24 - microchip,ksz8863 [all …]
|
| /Documentation/spi/ |
| D | spi-summary.rst | 2 Overview of Linux kernel SPI support 5 02-Feb-2012 7 What is SPI? 8 ------------ 9 The "Serial Peripheral Interface" (SPI) is a synchronous four wire serial 12 standardization body. SPI uses a host/target configuration. 17 clocking modes through which data is exchanged; mode-0 and mode-3 are most 22 SPI hosts use a fourth "chip select" line to activate a given SPI target 24 in parallel. All SPI targets support chipselects; they are usually active 29 SPI target functions are usually not interoperable between vendors [all …]
|
| /Documentation/devicetree/bindings/sound/ |
| D | cirrus,cs42l43.yaml | 1 # SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause 3 --- 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 10 - patches@opensource.cirrus.com 14 (Version 1.2.1 compliant), I2C, SPI, and I2S/TDM interfaces designed 15 for portable applications. It provides a high dynamic range, stereo 21 - $ref: dai-common.yaml# 26 - cirrus,cs42l43 31 vdd-p-supply: 33 Power supply for the high voltage interface. [all …]
|
| /Documentation/firmware-guide/acpi/ |
| D | gpio-properties.rst | 1 .. SPDX-License-Identifier: GPL-2.0 31 ToUUID("daffd814-6eba-4d8c-8a91-bc9bbf4aa301"), 34 Package () { "reset-gpios", Package () { ^BTH, 1, 1, 0 } }, 35 Package () { "shutdown-gpios", Package () { ^BTH, 0, 0, 0 } }, 55 active low or high, the "active_low" argument can be used here. Setting 61 In our Bluetooth example the "reset-gpios" refers to the second GpioIo() 70 +-------------+-------------+-----------------------------------------------+ 74 +-------------+-------------+-----------------------------------------------+ 76 +-------------+-------------+-----------------------------------------------+ 78 +-------------+-------------+-----------------------------------------------+ [all …]
|
12