| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/display/panel/ |
| D | tpo,tpg110.yaml | 1 # SPDX-License-Identifier: GPL-2.0
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Linus Walleij <linus.walleij@linaro.org>
11 - Thierry Reding <thierry.reding@gmail.com>
17 and other properties, and has a control interface over 3WIRE
18 SPI. By talking to the TPG110 over SPI, the strapped properties
20 self-describing.
22 +--------+
23 SPI -> | TPO | -> physical display
[all …]
|
| D | kingdisplay,kd035g6-54nt.yaml | 1 # SPDX-License-Identifier: GPL-2.0
3 ---
4 $id: http://devicetree.org/schemas/display/panel/kingdisplay,kd035g6-54nt.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: King Display KD035G6-54NT 3.5" (320x240 pixels) 24-bit TFT LCD panel
10 The panel must obey the rules for a SPI slave device as specified in
11 spi/spi-controller.yaml
14 - Paul Cercueil <paul@crapouillou.net>
17 - $ref: panel-common.yaml#
21 const: kingdisplay,kd035g6-54nt
[all …]
|
| /kernel/linux/linux-5.10/drivers/iio/common/st_sensors/ |
| D | st_sensors_spi.c | 1 // SPDX-License-Identifier: GPL-2.0-only
3 * STMicroelectronics sensors spi library driver
5 * Copyright 2012-2013 STMicroelectronics Inc.
34 * st_sensors_is_spi_3_wire() - check if SPI 3-wire mode has been selected
35 * @spi: spi device reference.
37 * Return: true if SPI 3-wire mode is selected, false otherwise.
39 static bool st_sensors_is_spi_3_wire(struct spi_device *spi) in st_sensors_is_spi_3_wire() argument
42 struct device *dev = &spi->dev; in st_sensors_is_spi_3_wire()
44 if (device_property_read_bool(dev, "spi-3wire")) in st_sensors_is_spi_3_wire()
48 if (pdata && pdata->spi_3wire) in st_sensors_is_spi_3_wire()
[all …]
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/spi/ |
| 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-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 Generic Binding
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-9a-f])*$"
[all …]
|
| /kernel/linux/linux-4.19/Documentation/devicetree/bindings/spi/ |
| 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-bus.txt | 1 SPI (Serial Peripheral Interface) busses
3 SPI busses can be described with a node for the SPI controller device
4 and a set of child nodes for each SPI slave on the bus. The system's SPI
5 controller may be described for use in SPI master mode or in SPI slave mode,
8 The SPI controller node requires the following properties:
9 - compatible - Name of SPI bus controller following generic names
12 In master mode, the SPI controller node requires the following additional
14 - #address-cells - number of cells required to define a chip select
15 address on the SPI bus.
16 - #size-cells - should be zero.
[all …]
|
| /kernel/linux/linux-4.19/Documentation/devicetree/bindings/rtc/ |
| 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 …]
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/rtc/ |
| 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 …]
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/display/ |
| D | multi-inno,mi0283qt.txt | 1 Multi-Inno MI0283QT display panel
4 - compatible: "multi-inno,mi0283qt".
6 The node for this driver must be a child node of a SPI controller, hence
7 all mandatory properties described in ../spi/spi-bus.txt must be specified.
10 - dc-gpios: D/C pin. The presence/absence of this GPIO determines
11 the panel interface mode (IM[3:0] pins):
12 - present: IM=x110 4-wire 8-bit data serial interface
13 - absent: IM=x101 3-wire 9-bit data serial interface
14 - reset-gpios: Reset pin
15 - power-supply: A regulator node for the supply voltage.
[all …]
|
| /kernel/linux/linux-4.19/Documentation/devicetree/bindings/display/ |
| D | multi-inno,mi0283qt.txt | 1 Multi-Inno MI0283QT display panel
4 - compatible: "multi-inno,mi0283qt".
6 The node for this driver must be a child node of a SPI controller, hence
7 all mandatory properties described in ../spi/spi-bus.txt must be specified.
10 - dc-gpios: D/C pin. The presence/absence of this GPIO determines
11 the panel interface mode (IM[3:0] pins):
12 - present: IM=x110 4-wire 8-bit data serial interface
13 - absent: IM=x101 3-wire 9-bit data serial interface
14 - reset-gpios: Reset pin
15 - power-supply: A regulator node for the supply voltage.
[all …]
|
| /kernel/linux/linux-4.19/Documentation/spi/ |
| D | spi-lm70llp | 1 spi_lm70llp : LM70-LLP parport-to-SPI adapter
12 -----------
14 temperature sensor evaluation board to the kernel's SPI core subsystem.
16 This is a SPI master controller driver. It can be used in conjunction with
17 (layered under) the LM70 logical driver (a "SPI protocol driver").
19 into a SPI bus with a single device, which will be driven by the generic
24 --------------------
25 The schematic for this particular board (the LM70EVAL-LLP) is
34 ----------- --------- ----------------
35 D0 2 - -
[all …]
|
| D | butterfly | 1 spi_butterfly - parport-to-butterfly adapter driver
8 sensors, LCD, flash, toggle stick, and more. You can use AVR-GCC to
19 SPI protocol drivers interact with the AVR, and could even let the AVR
21 easily with a "real SPI controller", instead of this bitbanger.
24 The first cable connections will hook Linux up to one SPI bus, with the
27 connector pins (used also on non-Butterfly AVR boards). On the parport
30 Signal Butterfly Parport (DB-25)
31 ------ --------- ---------------
33 RESET = J403.nRST = pin 3/D1
40 (a) flash new firmware that disables SPI (set PRR.2, and disable pullups
[all …]
|
| D | spi-summary | 1 Overview of Linux kernel SPI support
4 02-Feb-2012
6 What is SPI?
7 ------------
8 The "Serial Peripheral Interface" (SPI) is a synchronous four wire serial
11 standardization body. SPI uses a master/slave configuration.
16 clocking modes through which data is exchanged; mode-0 and mode-3 are most
21 SPI masters use a fourth "chip select" line to activate a given SPI slave
23 in parallel. All SPI slaves support chipselects; they are usually active
28 SPI slave functions are usually not interoperable between vendors
[all …]
|
| /kernel/linux/linux-5.10/Documentation/spi/ |
| D | spi-lm70llp.rst | 2 spi_lm70llp : LM70-LLP parport-to-SPI adapter
15 -----------
17 temperature sensor evaluation board to the kernel's SPI core subsystem.
19 This is a SPI master controller driver. It can be used in conjunction with
20 (layered under) the LM70 logical driver (a "SPI protocol driver").
22 into a SPI bus with a single device, which will be driven by the generic
27 --------------------
28 The schematic for this particular board (the LM70EVAL-LLP) is
39 D0 2 - -
40 D1 3 --> V+ 5
[all …]
|
| D | butterfly.rst | 2 spi_butterfly - parport-to-butterfly adapter driver
9 sensors, LCD, flash, toggle stick, and more. You can use AVR-GCC to
20 SPI protocol drivers interact with the AVR, and could even let the AVR
22 easily with a "real SPI controller", instead of this bitbanger.
25 The first cable connections will hook Linux up to one SPI bus, with the
28 connector pins (used also on non-Butterfly AVR boards). On the parport
32 Signal Butterfly Parport (DB-25)
35 RESET J403.nRST pin 3/D1
43 (a) flash new firmware that disables SPI (set PRR.2, and disable pullups
44 by clearing PORTB.[0-3]); (b) configure the mtd_dataflash driver; and
[all …]
|
| 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 master/slave configuration.
17 clocking modes through which data is exchanged; mode-0 and mode-3 are most
22 SPI masters use a fourth "chip select" line to activate a given SPI slave
24 in parallel. All SPI slaves support chipselects; they are usually active
29 SPI slave functions are usually not interoperable between vendors
[all …]
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/ |
| D | trivial-devices.yaml | 1 # SPDX-License-Identifier: GPL-2.0
3 ---
4 $id: http://devicetree.org/schemas/trivial-devices.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: Trivial I2C and SPI devices that have simple device tree bindings
10 - Rob Herring <robh@kernel.org>
13 This is a list of trivial I2C and SPI devices that have simple device tree
28 - enum:
29 … # SMBus/I2C Digital Temperature Sensor in 6-Pin SOT with SMBus Alert and Over Temperature Pin
30 - ad,ad7414
[all …]
|
| /kernel/linux/linux-5.10/arch/arm/boot/dts/ |
| D | ste-nomadik-nhk15.dts | 1 // SPDX-License-Identifier: GPL-2.0
6 /dts-v1/;
7 #include <dt-bindings/interrupt-controller/irq.h>
8 #include <dt-bindings/gpio/gpio.h>
9 #include "ste-nomadik-stn8815.dtsi"
13 compatible = "st,nomadik-nhk-15";
22 stmpe-i2c0 = &stmpe0;
23 stmpe-i2c1 = &stmpe1;
71 disable-sxtalo;
72 disable-mxtalo;
[all …]
|
| /kernel/linux/linux-4.19/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
21 "fsl,mpc5200-<device>".
29 compatible = "fsl,mpc5200b-<device>","fsl,mpc5200-<device>";
34 ie. ethernet on mpc5200: compatible = "fsl,mpc5200-fec";
35 ethernet on mpc5200b: compatible = "fsl,mpc5200b-fec", "fsl,mpc5200-fec";
39 "fsl,mpc5200-psc-i2s", not "fsl,mpc5200-i2s". This convention is chosen to
[all …]
|
| /kernel/linux/linux-5.10/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
21 "fsl,mpc5200-<device>".
29 compatible = "fsl,mpc5200b-<device>","fsl,mpc5200-<device>";
34 ie. ethernet on mpc5200: compatible = "fsl,mpc5200-fec";
35 ethernet on mpc5200b: compatible = "fsl,mpc5200b-fec", "fsl,mpc5200-fec";
39 "fsl,mpc5200-psc-i2s", not "fsl,mpc5200-i2s". This convention is chosen to
[all …]
|
| /kernel/linux/linux-4.19/drivers/iio/dac/ |
| D | ad5758.c | 1 // SPDX-License-Identifier: GPL-2.0+
14 #include <linux/spi/spi.h>
49 #define AD5758_DAC_CONFIG_RANGE_MSK GENMASK(3, 0)
78 #define AD5758_DCDC_CONFIG2_ILIMIT_MSK GENMASK(3, 1)
91 * struct ad5758_state - driver instance specific data
92 * @spi: spi_device
96 * @dc_dc_ilim: variable which stores the dc-to-dc converter current limit
99 * @data: spi transfer buffers
109 struct spi_device *spi; member
116 __be32 d32[3];
[all …]
|
| /kernel/linux/linux-4.19/include/linux/platform_data/ |
| D | st_sensors_pdata.h | 2 * STMicroelectronics sensors platform-data driver
8 * Licensed under the GPL-2.
15 * struct st_sensors_platform_data - Platform data for the ST sensors
20 * @spi_3wire: enable spi-3wire mode.
|
| /kernel/linux/linux-5.10/include/linux/platform_data/ |
| D | st_sensors_pdata.h | 1 /* SPDX-License-Identifier: GPL-2.0-only */
3 * STMicroelectronics sensors platform-data driver
14 * struct st_sensors_platform_data - Platform data for the ST sensors
19 * @spi_3wire: enable spi-3wire mode.
|
| /kernel/linux/linux-5.10/drivers/spi/ |
| D | spi-rb4xx.c | 1 // SPDX-License-Identifier: GPL-2.0-only
3 * SPI controller driver for the Mikrotik RB4xx boards
16 #include <linux/spi/spi.h>
19 #include <asm/mach-ath79/ar71xx_regs.h>
28 return __raw_readl(rbspi->base + reg); in rb4xx_read()
33 __raw_writel(value, rbspi->base + reg); in rb4xx_write()
52 for (i = 7; i >= 0; i--) in do_spi_byte()
81 static void rb4xx_set_cs(struct spi_device *spi, bool enable) in rb4xx_set_cs() argument
83 struct rb4xx_spi *rbspi = spi_master_get_devdata(spi->master); in rb4xx_set_cs()
96 struct spi_device *spi, struct spi_transfer *t) in rb4xx_transfer_one() argument
[all …]
|