Home
last modified time | relevance | path

Searched refs:SPI (Results 1 – 200 of 280) sorted by relevance

12

/linux-4.1.27/drivers/spi/
DKconfig2 # SPI driver configuration
4 # NOTE: the reason this doesn't show SPI slave support is mostly that
8 menuconfig SPI config
9 bool "SPI support"
13 protocol. Chips that support SPI can have data transfer rates
15 controller and a chipselect. Most SPI slaves don't support
18 SPI is widely used by microcontrollers to talk with sensors,
21 MMC and SD cards can be accessed using SPI protocol; and for
22 DataFlash cards used in MMC sockets, SPI must always be used.
24 SPI is one of a family of similar protocols using a four wire
[all …]
Dspi-s3c24xx-fiq.S30 @ fiq_rspi The base of the SPI register block
/linux-4.1.27/Documentation/mtd/
Dspi-nor.txt1 SPI NOR framework
7 SPI bus controllers (drivers/spi/) only deal with streams of bytes; the bus
10 arbitrary streams of bytes, but rather are designed specifically for SPI NOR.
13 find the right LUT sequence. Unfortunately, the SPI subsystem has no notion of
14 opcodes, addresses, or data payloads; a SPI controller simply knows to send or
17 details of the SPI NOR protocol.
22 This framework just adds a new layer between the MTD and the SPI bus driver.
23 With this new layer, the SPI NOR controller driver does not depend on the
32 SPI bus driver
34 SPI NOR chip
[all …]
/linux-4.1.27/Documentation/devicetree/bindings/spi/
Dspi-bus.txt1 SPI (Serial Peripheral Interface) busses
3 SPI busses can be described with a node for the SPI master device
4 and a set of child nodes for each SPI slave on the bus. For this
5 discussion, it is assumed that the system's SPI controller is in
6 SPI master mode. This binding does not describe SPI controllers
9 The SPI master node requires the following properties:
11 address on the SPI bus.
13 - compatible - name of SPI bus controller following generic names
16 No other properties are required in the SPI bus node. It is assumed
17 that a driver for an SPI bus device will understand that it is an SPI bus.
[all …]
Dspi-davinci.txt1 Davinci SPI controller device bindings
10 address on the SPI bus. Should be set to 1.
13 - "ti,dm6441-spi" for SPI used similar to that on DM644x SoC family
14 - "ti,da830-spi" for SPI used similar to that on DA8xx SoC family
15 - reg: Offset and length of SPI controller register space
18 - ti,davinci-spi-intr-line: interrupt line used to connect the SPI
33 SPI slave nodes can contain the following properties.
34 Not all SPI Peripherals from Texas Instruments support this.
35 Please check SPI peripheral documentation for a device before using these.
38 (SPIFMTn.WDELAY, SPIDAT1.WDEL) must be specified in number of SPI module
[all …]
Dqcom,spi-qup.txt1 Qualcomm Universal Peripheral (QUP) Serial Peripheral Interface (SPI)
4 and an input FIFO) for serial peripheral interface (SPI) mini-core.
6 SPI in master mode supports up to 50MHz, up to four chip selects, programmable
23 address on the SPI bus. Should be set to 1.
27 - spi-max-frequency: Specifies maximum SPI clock frequency,
32 The gpios will be referred to as reg = <index> in the SPI child
33 nodes. If unspecified, a single SPI device without a chip
42 SPI slave nodes must be children of the SPI master node and can contain
Dspi_pl022.txt1 ARM PL022 SPI controller
6 - interrupts : Should contain SPI controller interrupt
11 The gpios will be referred to as reg = <index> in the SPI child nodes.
12 If unspecified, a single SPI device without a chip select can be used.
26 SPI slave nodes must be children of the SPI master node and can
30 0: SPI
Dfsl-imx-cspi.txt6 - "fsl,imx1-cspi" for SPI compatible with the one integrated on i.MX1
7 - "fsl,imx21-cspi" for SPI compatible with the one integrated on i.MX21
8 - "fsl,imx27-cspi" for SPI compatible with the one integrated on i.MX27
9 - "fsl,imx31-cspi" for SPI compatible with the one integrated on i.MX31
10 - "fsl,imx35-cspi" for SPI compatible with the one integrated on i.MX35
11 - "fsl,imx51-ecspi" for SPI compatible with the one integrated on i.MX51
Dspi-octeon.txt1 Cavium, Inc. OCTEON SOC SPI master controller.
7 - #address-cells : <1>, as required by generic SPI binding.
8 - #size-cells : <0>, also as required by generic SPI binding.
10 Child nodes as per the generic SPI binding.
Dfsl-spi.txt1 * SPI (Serial Peripheral Interface)
4 - cell-index : QE SPI subblock index.
8 - mode : the SPI operation mode, it can be "cpu" or "cpu-qe".
21 The gpios will be referred to as reg = <index> in the SPI child nodes.
22 If unspecified, a single SPI device without a chip select can be used.
Dspi-meson.txt1 Amlogic Meson SPI controllers
3 * SPIFC (SPI Flash Controller)
5 The Meson SPIFC is a controller optimized for communication with SPI
Dbrcm,bcm2835-spi.txt3 The BCM2835 contains two forms of SPI master controller, one known simply as
4 SPI0, and the other known as the "Universal SPI Master"; part of the
11 - clocks: The clock feeding the SPI controller.
Dsnps,dw-apb-ssi.txt7 - #address-cells : <1>, as required by generic SPI binding.
8 - #size-cells : <0>, also as required by generic SPI binding.
14 Child nodes as per the generic SPI binding.
Dspi-samsung.txt1 * Samsung SPI Controller
3 The Samsung SPI controller is used to interface with various devices such as flash
4 and display controllers using the SPI communication interface.
43 SPI Controller specific data in SPI slave nodes:
59 - All the SPI controller nodes should be represented in the aliases node using
Dspi-img-spfi.txt10 - spfi: SPI operating clock
11 - sys: SPI system interface clock
23 SPI transfers.
Dspi-xtensa-xtfpga.txt1 Cadence Xtensa XTFPGA platform SPI controller.
3 This simple SPI master controller is built into xtfpga bitstreams and is used
Dnvidia,tegra114-spi.txt1 NVIDIA Tegra114 SPI controller.
7 - reg: Should contain SPI registers location and length.
8 - interrupts: Should contain SPI interrupts.
Dspi-sirf.txt6 - interrupts : Should contain SPI interrupt
19 address on the SPI bus. Should be set to 1.
23 - spi-max-frequency: Specifies maximum SPI clock frequency,
Dspi-orion.txt1 Marvell Orion SPI device
6 - cell-index : Which of multiple SPI controllers is this.
Dspi-rockchip.txt1 * Rockchip SPI Controller
3 The Rockchip SPI controller is used to interface with various devices such as flash
4 and display controllers using the SPI communication interface.
Dspi-sun4i.txt1 Allwinner A10 SPI controller
7 - clocks: phandle to the clocks feeding the SPI controller. Two are
Dspi-sun6i.txt1 Allwinner A31 SPI controller
7 - clocks: phandle to the clocks feeding the SPI controller. Two are
Dmxs-spi.txt1 * Freescale MX233/MX28 SSP/SPI
13 - clock-frequency : Input clock frequency to the SPI block in Hz.
Dspi-st-ssc.txt1 STMicroelectronics SSC (SPI) Controller
18 Child nodes represent devices on the SPI bus
Dspi-cadence.txt1 Cadence SPI controller Device Tree Bindings
6 - reg : Physical base address and size of SPI registers map.
Dspi_altera.txt1 Altera SPI
Dspi-fsl-dspi.txt6 - interrupts : Should contain SPI controller interrupt
19 Optional SPI slave node properties:
Dspi_oc_tiny.txt1 OpenCores tiny SPI
Dspi-dw.txt1 Synopsys DesignWare SPI master
Dspi_atmel.txt1 Atmel SPI device
Dspi-gpio.txt1 SPI-GPIO devicetree bindings
Defm32-spi.txt1 * Energy Micro EFM32 SPI
/linux-4.1.27/Documentation/spi/
D00-INDEX6 - AVR Butterfly SPI driver overview and pin configuration.
8 - Basic EP93xx SPI driver configuration.
10 - PXA2xx SPI master controller build by spi_message fifo wq
16 - Connecting an LM70-LLP sensor to the kernel via the SPI subsys.
18 - NXP SC18IS602/603 I2C-bus to SPI bridge
20 - (Linux) SPI overview. If unsure about SPI or SPI in Linux, start here.
22 - SPI testing utility.
Dspi-summary1 Overview of Linux kernel SPI support
6 What is SPI?
8 The "Serial Peripheral Interface" (SPI) is a synchronous four wire serial
11 standardization body. SPI uses a master/slave configuration.
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
29 (except for commodities like SPI memory chips).
31 - SPI may be used for request/response style device protocols, as with
43 - Sometimes SPI is used to daisy-chain devices, like shift registers.
[all …]
Dspidev1 SPI devices have a limited userspace API, supporting basic half-duplex
2 read() and write() access to SPI slave devices. Using ioctl() requests,
17 as SPI slaves, which you may need to change quite often.
29 Set up the other device characteristics (bits per word, SPI clocking,
36 When you do that, the sysfs node for the SPI device will include a child
39 busybox; it's less featureful, but often enough.) For a SPI device with
46 /sys/devices/.../spiB.C ... as usual, the SPI device node will
47 be a child of its SPI master controller.
61 by having kernel code remove the SPI device, probably by removing the driver
62 for its SPI controller (so its spi_master vanishes).
[all …]
Dspi-lm70llp1 spi_lm70llp : LM70-LLP parport-to-SPI adapter
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
47 Note that since the LM70 uses a "3-wire" variant of SPI, the SI/SO pin
50 pin low. This can't be shared with true SPI devices, but other 3-wire
55 spi_write_then_read() call. It performs Mode 0 (SPI/Microwire) bitbanging.
77 o David Brownell for mentoring the SPI-side driver development.
Dbutterfly19 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
40 (a) flash new firmware that disables SPI (set PRR.2, and disable pullups
50 Or you could flash firmware making the AVR into an SPI slave (keeping the
52 the driver for your custom SPI-based protocol.
54 The "USI" controller, using J405, can also be used for a second SPI bus.
55 That would let you talk to the AVR using custom SPI-with-USI firmware,
Dspi-sc18is60215 This driver provides connects a NXP SC18IS602/603 I2C-bus to SPI bridge to the
16 kernel's SPI core subsystem.
29 The maximum SPI message size supported by SC18IS602/603 is 200 bytes. Attempts
32 200 bytes per SPI message (128 bytes of data per message is recommended). This
Dpxa2xx1 PXA2xx SPI on SSP driver HOWTO
4 synchronous serial port into a SPI master controller
15 (pump_transfer) is responsible for queuing SPI transactions and setting up and
20 Typically a SPI master is defined in the arch/.../mach-*/board-*.c as a
35 slave device (chips) attached to this SPI master.
86 Typically each SPI slave (chip) is defined in the arch/.../mach-*/board-*.c
124 dependent on the SPI bus speed ("spi_board_info.max_speed_hz") and the specific
138 NOTE: the SPI driver cannot control the chip select if SSPFRM is used, so the
150 /* Chip Select control for the CS8415A SPI slave device */
159 /* Chip Select control for the CS8405A SPI slave device */
Dep93xx_spi1 Cirrus EP93xx SPI controller driver HOWTO
4 ep93xx_spi driver brings SPI master support for EP93xx SPI controller. Chip
15 arch/arm/mach-ep93xx/*.c). In this example we configure MMC over SPI through
/linux-4.1.27/Documentation/networking/caif/
Dspi_porting.txt1 - CAIF SPI porting -
3 - CAIF SPI basics:
5 Running CAIF over SPI needs some extra setup, owing to the nature of SPI.
8 CAIF over SPI is a SPI slave chip and two GPIOs (more details below).
12 - CAIF SPI framework:
14 To make porting as easy as possible, the CAIF SPI has been divided in
16 generic functionality such as length framing, SPI frame negotiation
17 and SPI frame delivery and transmission. The other part is the CAIF
18 SPI slave device part, which is the module that you have to write if
19 you want to run SPI CAIF on a new hardware. This part takes care of
[all …]
/linux-4.1.27/Documentation/devicetree/bindings/net/
Dqca-qca7000-spi.txt1 * Qualcomm QCA7000 (Ethernet over SPI protocol)
3 Note: The QCA7000 is useable as a SPI device. In this case it must be defined
4 as a child of a SPI master in the device tree.
8 - reg : Should specify the SPI chip select
16 - spi-max-frequency : Maximum frequency of the SPI bus the chip can operate at.
18 the property will set the SPI frequency to 8000000 Hertz.
20 - qca,legacy-mode : Set the SPI data transfer of the QCA7000 to legacy mode.
21 In this mode the SPI master must toggle the chip select between each data
28 /* Freescale i.MX28 SPI master*/
42 spi-cpha; /* SPI mode: CPHA=1 */
[all …]
Dmicrel-ks8851.txt8 Micrel KS8851 Ethernet mac (SPI)
/linux-4.1.27/Documentation/blackfin/
Dbfin-spi-notes.txt1 SPI Chip Select behavior:
3 With the Blackfin on-chip SPI peripheral, there is some logic tied to the CPHA
5 controlled by software (CPHA=1). However, the Linux SPI bus driver assumes that
7 the entire SPI transfer. - And not just bits_per_word duration.
9 In most cases you can utilize SPI MODE_3 instead of MODE_0 to work-around this
10 behavior. If your SPI slave device in question requires SPI MODE_0 or MODE_2
11 timing, you can utilize the GPIO controlled SPI Slave Select option instead.
/linux-4.1.27/drivers/net/can/spi/
DKconfig1 menu "CAN SPI interfaces"
2 depends on SPI
5 tristate "Microchip MCP251x SPI CAN controllers"
8 Driver for the Microchip MCP251x SPI CAN controllers.
/linux-4.1.27/Documentation/devicetree/bindings/gpio/
Dgpio-mcp23s08.txt2 8-/16-bit I/O expander with serial interface (I2C/SPI)
6 - "mcp,mcp23s08" (DEPRECATED) for 8 GPIO SPI version
7 - "mcp,mcp23s17" (DEPRECATED) for 16 GPIO SPI version
11 - "microchip,mcp23s08" for 8 GPIO SPI version
12 - "microchip,mcp23s17" for 16 GPIO SPI version
22 SPI uses this to specify the chipselect line which the chip is
23 connected to. The driver and the SPI variant of the chip support
27 Required device specific properties (only for SPI chips):
29 - microchip,spi-present-mask : This is a present flag, that makes only sense for SPI
30 chips - as the name suggests. Multiple SPI chips can share the same
[all …]
Dspear_spics.txt1 === ST Microelectronics SPEAr SPI CS Driver ===
/linux-4.1.27/drivers/mtd/spi-nor/
DKconfig2 tristate "SPI-NOR device support"
5 This is the framework for the SPI NOR which can be used by the SPI
6 device drivers and the SPI-NOR device driver.
25 tristate "Freescale Quad SPI controller"
28 This enables support for the Quad SPI controller in master mode.
/linux-4.1.27/drivers/staging/iio/accel/
DKconfig8 depends on SPI
20 depends on SPI
32 depends on SPI
44 depends on SPI
56 depends on SPI
67 depends on SPI
79 depends on SPI
84 Say Y here to build SPI support for the ST microelectronics
93 depends on SPI
96 Say Y here to build support for the VTI SCA3000 series of SPI
/linux-4.1.27/drivers/staging/mt29f_spinand/
DKconfig3 depends on MTD_NAND && SPI
5 This enables support for accessing Micron SPI NAND flash
7 If you have Micron SPI NAND chip say yes.
16 Enables Hardware ECC support for Micron SPI NAND.
/linux-4.1.27/arch/arm/mach-u300/
DKconfig33 bool "SSP/SPI dummy chip"
34 select SPI
39 SPI device to be used for loopback tests. Regularly used
40 to test reference designs. If you're not testing SPI,
42 SPI framework and ARM PL022 support.
/linux-4.1.27/drivers/staging/iio/meter/
DKconfig8 depends on SPI
18 depends on SPI
28 depends on SPI
40 depends on SPI
50 depends on SPI || I2C
69 tristate "support SPI bus connection"
70 depends on ADE7854 && SPI
73 Say Y here if you have ADE7854/58/68/78 hooked to a SPI bus.
/linux-4.1.27/drivers/iio/gyro/
DKconfig9 tristate "Analog Devices ADIS16080/100 Yaw Rate Gyroscope with SPI driver"
10 depends on SPI
13 Rate Gyroscope with SPI.
17 depends on SPI
32 tristate "Analog Devices ADIS16260 Digital Gyroscope Sensor SPI driver"
33 depends on SPI
44 tristate "Analog Devices ADXRS450/3 Digital Output Gyroscope SPI driver"
45 depends on SPI
91 - st_gyro_spi (necessary for the SPI devices [optional*]);
/linux-4.1.27/drivers/net/ieee802154/
DKconfig26 depends on SPI
29 Say Y here to enable the at86rf230/231/233/212 SPI 802.15.4 wireless
38 depends on SPI
40 Say Y here to enable the MRF24J20 SPI 802.15.4 wireless
49 depends on SPI
51 Say Y here to enable the CC2520 SPI 802.15.4 wireless
/linux-4.1.27/drivers/pinctrl/
Dpinctrl-xway.c120 MFP_XWAY(GPIO9, GPIO, ASC, SPI, EXIN),
121 MFP_XWAY(GPIO10, GPIO, ASC, SPI, NONE),
122 MFP_XWAY(GPIO11, GPIO, ASC, PCI, SPI),
124 MFP_XWAY(GPIO13, GPIO, EBU, SPI, NONE),
126 MFP_XWAY(GPIO15, GPIO, SPI, JTAG, NONE),
127 MFP_XWAY(GPIO16, GPIO, SPI, NONE, JTAG),
128 MFP_XWAY(GPIO17, GPIO, SPI, NONE, JTAG),
129 MFP_XWAY(GPIO18, GPIO, SPI, NONE, JTAG),
133 MFP_XWAY(GPIO22, GPIO, SPI, NONE, NONE),
178 MFP_XWAY(GPIO7, GPIO, SPI, MII, JTAG),
[all …]
Dpinctrl-falcon.c131 MFP_FALCON(GPIO34, SPI, GPIO, NONE, NONE),
132 MFP_FALCON(GPIO35, SPI, GPIO, NONE, NONE),
133 MFP_FALCON(GPIO36, SPI, GPIO, NONE, NONE),
134 MFP_FALCON(GPIO37, SPI, GPIO, NONE, NONE),
135 MFP_FALCON(GPIO38, SPI, GPIO, NONE, NONE),
197 GRP_MUX("spi", SPI, pins_spi),
198 GRP_MUX("spi cs0", SPI, pins_spi_cs0),
199 GRP_MUX("spi cs1", SPI, pins_spi_cs1),
/linux-4.1.27/sound/spi/
DKconfig1 #SPI drivers
4 bool "SPI sound devices"
5 depends on SPI
8 Support for sound devices connected via the SPI bus.
/linux-4.1.27/drivers/net/caif/
DKconfig17 tristate "CAIF SPI transport driver for slave interface"
21 The CAIF Link layer SPI Protocol driver for Slave SPI interface.
23 platform specific SPI device. A sample CAIF SPI Platform device is
/linux-4.1.27/Documentation/hwmon/
Dlm7025 SPI/Microwire Bus interface.
28 the driver accesses the LM70 using SPI communication: 16 SCLK cycles
32 SPI support.
34 As a real (in-tree) example of this "SPI protocol driver" interfacing
35 with a "SPI master controller driver", see drivers/spi/spi_lm70llp.c
Dadt741119 SPI-compatible 4-wire interface. It provides a 10-bit analog to digital
42 SPI, external temperature sensor and limit registers are not supported yet.
Dadt741049 interface, the ADT7310 and ADT7320 use SPI while the ADT7410 and ADT7420 use
/linux-4.1.27/drivers/staging/iio/gyro/
DKconfig7 tristate "Analog Devices ADIS16060 Yaw Rate Gyroscope with SPI driver"
8 depends on SPI
11 yaw rate gyroscope with SPI.
/linux-4.1.27/Documentation/devicetree/bindings/net/wireless/
Dti,wl1251.txt3 The wl1251 chip can be connected via SPI or via SDIO. This
4 document describes the binding for the SPI connected chip.
9 - spi-max-frequency : Maximum SPI clocking speed of device in Hz
20 for optional SPI connection related properties,
/linux-4.1.27/drivers/iio/dac/
DKconfig21 depends on SPI
45 depends on SPI
76 tristate "Analog Devices AD5504/AD5501 DAC SPI driver"
77 depends on SPI
87 depends on SPI
90 AD5664R converters (DAC). This driver uses the common SPI interface.
93 tristate "Analog Devices AD5686R/AD5685R/AD5684R DAC SPI driver"
94 depends on SPI
125 tristate "Analog Devices AD5760/AD5780/AD5781/AD5790/AD5791 DAC SPI driver"
126 depends on SPI
[all …]
/linux-4.1.27/drivers/video/fbdev/omap2/displays-new/
DKconfig50 depends on SPI && BACKLIGHT_CLASS_DEVICE
56 depends on SPI
68 depends on SPI
74 depends on SPI
80 depends on SPI
/linux-4.1.27/drivers/net/ethernet/micrel/
DKconfig8 depends on (HAS_IOMEM && DMA_ENGINE) || SPI || PCI || HAS_IOMEM || \
39 tristate "Micrel KS8851 SPI"
40 depends on SPI
45 SPI driver for Micrel KS8851 SPI attached network chip.
/linux-4.1.27/Documentation/devicetree/bindings/mfd/
Dcros-ec.txt6 The EC can be connect through various means (I2C, SPI, LPC) and the
16 Required properties (SPI):
18 - reg: SPI chip select
20 Optional properties (SPI):
46 Example for SPI:
Dstmpe.txt8 - reg : I2C/SPI address of the device
Dmt6397.txt10 It is interfaced to host controller using SPI interface by a proprietary hardware
Darizona.txt14 using SPI.
/linux-4.1.27/Documentation/devicetree/bindings/soc/mediatek/
Dpwrap.txt5 On MediaTek SoCs the PMIC is connected via SPI. The SPI master interface
8 optionally be encrypted. Also a non standard Dual IO SPI mode can be
14 The signals of these pins are routed over the SPI bus using the pwrap
33 "spi": SPI bus clock
/linux-4.1.27/net/nfc/nci/
DKconfig13 depends on NFC_NCI && SPI
15 bool "NCI over SPI protocol support"
21 Say yes if you use an NCI driver that requires SPI link layer.
/linux-4.1.27/drivers/staging/iio/adc/
DKconfig31 depends on SPI
41 depends on SPI
46 AD7780 and AD7781 SPI analog to digital converters (ADC).
54 depends on SPI
62 depends on SPI
66 AD7192 or AD7195 SPI analog to digital converters (ADC).
74 depends on SPI
/linux-4.1.27/Documentation/devicetree/bindings/iio/proximity/
Das3935.txt5 - reg: SPI chip select number for the device
6 - spi-cpha: SPI Mode 1. Refer to spi/spi-bus.txt for generic SPI
/linux-4.1.27/drivers/clk/qcom/
DKconfig13 Say Y if you want to use peripheral devices such as UART, SPI,
30 Say Y if you want to use peripheral devices such as UART, SPI,
47 Say Y if you want to use peripheral devices such as UART, SPI,
55 Say Y if you want to use devices such as UART, SPI i2c, USB,
63 Say Y if you want to use peripheral devices such as UART, SPI,
89 Say Y if you want to use peripheral devices such as UART, SPI,
/linux-4.1.27/drivers/net/wireless/cw1200/
DKconfig23 tristate "Support SPI platforms"
24 depends on CW1200 && SPI
26 Enables support for the CW1200 connected via a SPI bus. You will
/linux-4.1.27/drivers/net/wireless/ti/wl1251/
DKconfig14 tristate "TI wl1251 SPI support"
17 This module adds support for the SPI interface of adapters using
19 the SPI bus.
/linux-4.1.27/Documentation/devicetree/bindings/misc/
Dat25.txt1 EEPROMs (SPI) compatible with Atmel at25.
12 - spi-cpha : SPI shifted clock phase, as per spi-bus bindings.
13 - spi-cpol : SPI inverse clock polarity, as per spi-bus bindings.
Dlis302.txt7 Required properties for the SPI bindings:
65 Example for a SPI device node:
/linux-4.1.27/drivers/staging/iio/addac/
DKconfig17 tristate "support SPI bus connection"
18 depends on SPI && ADT7316
21 Say yes here to build SPI bus support for Analog Devices ADT7316/7/8
/linux-4.1.27/drivers/net/wireless/libertas/
DKconfig30 tristate "Marvell Libertas 8686 SPI 802.11b/g cards"
31 depends on LIBERTAS && SPI
33 A driver for Marvell Libertas 8686 SPI devices.
/linux-4.1.27/drivers/staging/iio/resolver/
DKconfig8 depends on SPI
18 depends on SPI
30 depends on SPI
/linux-4.1.27/Documentation/devicetree/bindings/sound/
Dpcm1792a.txt3 This driver supports the SPI bus.
9 For required properties on SPI, please consult
Dwm8728.txt3 This device supports both I2C and SPI (configured with pin strapping
11 number for SPI.
Dwm8741.txt3 This device supports both I2C and SPI (configured with pin strapping
11 number for SPI.
Dwm8737.txt3 This device supports both I2C and SPI (configured with pin strapping
11 number for SPI.
Dwm8711.txt3 This device supports both I2C and SPI (configured with pin strapping
11 number for SPI.
Dwm8776.txt3 This device supports both I2C and SPI (configured with pin strapping
11 number for SPI.
Dwm8510.txt3 This device supports both I2C and SPI (configured with pin strapping
11 number for SPI.
Dwm8750.txt3 These devices support both I2C and SPI (configured with pin strapping
11 number for SPI.
Dak4104.txt3 This device supports SPI mode only.
9 - reg : The chip select number on the SPI bus
Dwm8753.txt3 This device supports both I2C and SPI (configured with pin strapping
11 number for SPI.
Dadi,ssm2602.txt3 SSM2602 support both I2C and SPI as the configuration interface,
12 number for SPI.
Dwm8804.txt3 This device supports both I2C and SPI (configured with pin strapping
11 number for SPI.
Dwm8731.txt3 This device supports both I2C and SPI (configured with pin strapping
11 number for SPI.
Des8328.txt3 This device supports both I2C and SPI.
13 - reg : the I2C address of the device for I2C, the chip select number for SPI
Dcs4271.txt3 This driver supports both the I2C and the SPI bus.
9 For required properties on SPI, please consult
Dpcm512x.txt3 These devices support both I2C and SPI (configured with pin strapping
12 number for SPI.
Dwm8770.txt3 This device supports SPI.
Dwm8994.txt3 These devices support both I2C and SPI (configured with pin strapping
11 number for SPI.
/linux-4.1.27/Documentation/devicetree/bindings/rtc/
Dnxp,rtc-2123.txt1 NXP PCF2123 SPI Real Time Clock
5 - reg: should be the SPI slave chipselect address
/linux-4.1.27/drivers/misc/lis3lv02d/
DKconfig6 tristate "STMicroeletronics LIS3LV02Dx three-axis digital accelerometer (SPI)"
12 via SPI. The accelerometer data is readable via
19 will be called lis3lv02d and a specific module for the SPI transport
/linux-4.1.27/drivers/net/wireless/ti/wlcore/
DKconfig15 tristate "TI wlcore SPI support"
19 This module adds support for the SPI interface of adapters using
21 the SPI bus.
/linux-4.1.27/drivers/iio/adc/
DKconfig35 depends on SPI
47 depends on SPI
53 AD7495, AD7910, AD7920, AD7920 SPI analog to digital converters (ADC).
62 depends on SPI
66 AD7790 and AD7791 SPI analog to digital converters (ADC). If unsure, say
74 depends on SPI
78 AD7794 and AD7795 SPI analog to digital converters (ADC).
86 depends on SPI
91 AD7887 SPI analog to digital converter (ADC).
99 depends on SPI
[all …]
/linux-4.1.27/Documentation/devicetree/bindings/mtd/
Djedec,spi-nor.txt1 * MTD SPI driver for ST M25Pxx (and similar) serial flash chips
11 Must also include "jedec,spi-nor" for any SPI NOR flash that can
14 - spi-max-frequency : Maximum frequency of the SPI bus the chip can operate at
Dst-fsm.txt1 * ST-Microelectronics SPI FSM Serial (NOR) Flash Controller
/linux-4.1.27/drivers/iio/imu/
DKconfig9 tristate "Analog Devices ADIS16400 and similar IMU SPI driver"
10 depends on SPI
21 depends on SPI
/linux-4.1.27/drivers/iio/amplifiers/
DKconfig10 depends on SPI
14 SPI Dual-Digital Variable Gain Amplifier (VGA).
/linux-4.1.27/Documentation/devicetree/bindings/panel/
Dsamsung,ld9040.txt1 Samsung LD9040 AMOLED LCD parallel RGB panel with SPI control bus
5 - reg: address of the panel on SPI bus
11 The panel must obey rules for SPI slave device specified in document [2].
/linux-4.1.27/arch/powerpc/boot/dts/
Dp1010rdb.dtsi121 label = "SPI Flash U-Boot Image";
128 label = "SPI Flash DTB Image";
134 label = "SPI Flash Linux Kernel Image";
140 label = "SPI Flash Compressed RFSImage";
146 label = "SPI Flash JFFS2 RFS";
Dp2020rdb.dts165 label = "SPI (RO) U-Boot Image";
172 label = "SPI (RO) DTB Image";
179 label = "SPI (RO) Linux Kernel Image";
186 label = "SPI (RO) Compressed RFS Image";
193 label = "SPI (RW) JFFS2 RFS";
Dp1024rdb.dtsi139 label = "SPI U-Boot Image";
146 label = "SPI DTB Image";
152 label = "SPI Linux Kernel Image";
158 label = "SPI Compressed RFS Image";
164 label = "SPI JFFS2 RFS";
Dp2020rdb-pc.dtsi161 label = "SPI U-Boot Image";
168 label = "SPI DTB Image";
174 label = "SPI Linux Kernel Image";
180 label = "SPI Compressed RFS Image";
186 label = "SPI JFFS2 RFS";
Dp1021rdb-pc.dtsi160 label = "SPI Flash U-Boot Image";
167 label = "SPI Flash DTB Image";
173 label = "SPI Flash Linux Kernel Image";
179 label = "SPI Flash Compressed RFSImage";
185 label = "SPI Flash JFFS2 RFS";
Dc293pcie.dts178 label = "SPI Flash U-Boot Image";
185 label = "SPI Flash DTB Image";
191 label = "SPI Flash Linux Kernel Image";
197 label = "SPI Flash RFS Image";
Dp1020rdb-pd.dts166 label = "SPI U-Boot Image";
173 label = "SPI DTB Image";
179 label = "SPI Linux Kernel Image";
185 label = "SPI File System Image";
Dac14xx.dts308 /* PSC4 in SPI mode */
332 /* PSC5 in SPI mode */
/linux-4.1.27/drivers/staging/iio/frequency/
DKconfig8 depends on SPI
18 depends on SPI
/linux-4.1.27/Documentation/devicetree/bindings/iio/dac/
Dad7303.txt5 - reg: SPI chip select number for the device
6 - spi-max-frequency: Max SPI frequency to use (< 30000000)
/linux-4.1.27/drivers/iio/proximity/
DKconfig11 depends on SPI
13 Say Y here to build SPI interface support for the Austrian
/linux-4.1.27/arch/cris/arch-v32/drivers/
DKconfig360 select SPI
364 # independent of MMC_SPI, so we'll keep SPI non-dependent on the
366 # for the board-info file until a separate non-MMC SPI board file
369 # configure non-MMC SPI ports together with MMC_SPI ports (if multiple
370 # SPI ports are enabled).
378 SPI master controller on Axis ETRAX FS and later. The
386 This enables using GPIO pins port as a SPI master controller
391 tristate "SPI using synchronous serial port 0 (sser0)"
399 or for devices using the SPI protocol on that port. Say m if you
404 tristate "SPI using synchronous serial port 1 (sser1)"
[all …]
/linux-4.1.27/Documentation/devicetree/bindings/input/touchscreen/
Dtsc2005.txt5 - reg : SPI device address
6 - spi-max-frequency : Maximal SPI speed
/linux-4.1.27/drivers/char/tpm/st33zp24/
DKconfig23 tristate "TPM 1.2 ST33ZP24 SPI support"
25 depends on SPI
/linux-4.1.27/Documentation/acpi/
Denumeration.txt25 The ACPI implementation enumerates devices behind busses (platform, SPI and
140 SPI serial bus support
142 Slave devices behind SPI bus have SpiSerialBus resource attached to them.
143 This is extracted automatically by the SPI core and the slave devices are
146 Here is what the ACPI namespace for a SPI slave might look like:
164 The SPI device drivers only need to add ACPI IDs in a similar way than with
166 to at25 SPI eeprom driver (this is meant for the above ACPI snippet):
204 Then the at25 SPI driver can get this configuration by calling _DSM on its
225 with the platform and SPI drivers. The I2C core automatically enumerates
/linux-4.1.27/drivers/iio/frequency/
DKconfig15 depends on SPI
33 depends on SPI
/linux-4.1.27/drivers/net/ethernet/microchip/
DKconfig8 depends on SPI
23 depends on SPI
/linux-4.1.27/drivers/net/wireless/p54/
DKconfig8 This module does nothing by itself - the USB/PCI/SPI front-ends
43 tristate "Prism54 SPI (stlc45xx) support"
56 Unlike the PCI or USB devices, the SPI variants don't have
/linux-4.1.27/drivers/misc/eeprom/
DKconfig31 tristate "SPI EEPROMs from most vendors"
32 depends on SPI && SYSFS
34 Enable this driver to get read/write support to most SPI EEPROMs,
76 depends on SPI && SYSFS
/linux-4.1.27/Documentation/devicetree/bindings/dma/
Dste-dma40.txt62 0: SPI controller 0
95 33: SPI controller 2
97 35: SPI controller 1
102 40: SPI controller 3
/linux-4.1.27/drivers/gpu/drm/panel/
DKconfig22 tristate "LD9040 RGB/SPI panel"
23 depends on OF && SPI
/linux-4.1.27/sound/soc/codecs/
DKconfig1 # Helper to resolve issues with configs that have SPI enabled but I2C
4 # setting - SPI can't be modular so that case doesn't need to be covered.
27 select SND_SOC_ADAU1761_SPI if SPI
29 select SND_SOC_ADAU1781_SPI if SPI
390 tristate "Cirrus Logic CS4271 CODEC (SPI)"
492 tristate "Texas Instruments PCM512x CODECs - SPI"
537 default SND_SOC_RT5677 && SPI
576 tristate "Analog Devices SSM2602 CODEC - SPI"
627 tristate "Texas Instruments TLV320AIC23 audio CODEC - SPI"
633 depends on SPI
[all …]
/linux-4.1.27/drivers/mtd/devices/
DKconfig57 This enables access to AT45xxx DataFlash chips, using SPI.
82 tristate "Support most SPI Flash chips (AT26DF, M25P, W25X, ...)"
85 This enables access to most modern SPI flash chips, used for
106 tristate "Support SST25L (non JEDEC) SPI Flash chips"
109 This enables access to the non JEDEC SST25L SPI flash chips, used
214 tristate "ST Microelectronics SPI FSM Serial Flash Controller"
218 SPI Fast Sequence Mode (FSM) Serial Flash Controller and support
/linux-4.1.27/arch/blackfin/mach-bf533/
DKconfig17 int "SPI ERROR"
52 int "DMA5 (SPI)"
/linux-4.1.27/Documentation/devicetree/bindings/arm/
Dgic.txt4 interrupts (PPI), shared processor interrupts (SPI) and software
27 The 1st cell is the interrupt type; 0 for SPI interrupts, 1 for PPI
31 SPI interrupts are in the range [0-987]. PPI interrupts are in the
118 value, this property should contain the SPI base of
Dgic-v3.txt4 Peripheral Interrupts (PPI), Shared Peripheral Interrupts (SPI),
15 The 1st cell is the interrupt type; 0 for SPI interrupts, 1 for PPI
19 SPI interrupts are in the range [0-987]. PPI interrupts are in the
Dpmu.txt34 a single SPI.
/linux-4.1.27/drivers/video/backlight/
DKconfig41 SPI driver for Epson L4F00242T03. This provides basic support
48 SPI driver for Samsung LMS283GF05. This provides basic support
64 depends on SPI
71 depends on SPI
99 depends on I2C && SPI && MACH_TOSA
114 depends on SPI && BACKLIGHT_CLASS_DEVICE
122 depends on SPI && BACKLIGHT_CLASS_DEVICE
130 depends on SPI && BACKLIGHT_CLASS_DEVICE
138 depends on SPI
146 depends on SPI
/linux-4.1.27/Documentation/devicetree/bindings/media/
Dsamsung-s5c73m3.txt5 data busses. The I2C bus is the main control bus and additionally the SPI bus
53 SPI device node
60 For more details see description of the SPI busses bindings
Dexynos4-fimc-is.txt6 and SPI bus controllers, PWM and ADC.
/linux-4.1.27/Documentation/devicetree/bindings/iio/
Dst-sensors.txt4 SPI devices, all sharing the same device tree descriptions no matter what
9 - reg: the I2C or SPI address the device will respond to
Dsensorhub.txt8 - spi-max-frequency: max SPI clock frequency
/linux-4.1.27/drivers/media/usb/msi2500/
DKconfig3 depends on VIDEO_V4L2 && SPI
/linux-4.1.27/drivers/iio/pressure/
DKconfig74 tristate "support SPI bus connection"
77 Say Y here to build SPI bus support for MS5611.
97 - st_pressure_spi (necessary for the SPI devices [optional*]);
/linux-4.1.27/Documentation/zh_CN/
Dgpio.txt47 匮乏的 SOC。同时还有通过 I2C 或 SPI 串行总线连接的“GPIO扩展器”
186 函数可以使得模拟接口(译者注:例如 GPIO 模拟 I2C、1-wire 或 SPI)的
192 某些 GPIO 控制器必须通过基于总线(如 I2C 或 SPI)的消息访问。读或写这些
512 对于外部 GPIO 控制器(例如 I2C 或 SPI 扩展器、专用芯片、多功能器件、FPGA
/linux-4.1.27/drivers/iio/accel/
DKconfig65 - st_accel_spi (necessary for the SPI devices [optional*]);
81 depends on SPI
84 Currently this only supports the device via an SPI interface.
/linux-4.1.27/Documentation/arm/Samsung-S3C24XX/
DS3C2412.txt105 SPI
108 No current support for the SPI interfaces.
/linux-4.1.27/drivers/soc/qcom/
DKconfig10 functions for connecting the underlying serial UART, SPI, and I2C
/linux-4.1.27/Documentation/devicetree/bindings/iio/adc/
Dmcp320x.txt3 The node for this driver must be a child node of a SPI controller, hence
Dmax1027-adc.txt5 - reg: SPI chip select number for the device
/linux-4.1.27/arch/sh/kernel/cpu/sh4a/
Dsetup-sh7734.c372 SPI, enumerator
446 INTC_GROUP(SPI, HSPI, RSPI, QSPI),
493 SPI, /* HSPI, RSPI, QSPI */
515 { VIN0, SPI, _2DG, LBSCATA } },
Dsetup-sh7770.c366 TMU, DMAC, I2S, SRC, GFX3D, SPI, SCIF, BBDMAC, enumerator
425 INTC_GROUP(SPI, SPI0, SPI1),
435 { 0, BBDMAC, ADC, SCIF, SPI, EXBUS_ATA, GFX3D, GFX2D,
446 { 0xffe00014, 0, 32, 8, /* INT2PRI5 */ { 0, GFX3D, EXBUS_ATA, SPI } },
/linux-4.1.27/arch/avr32/boards/atstk1000/
DKconfig74 All the signals for the second SPI controller are available on
76 here to configure that SPI controller.
/linux-4.1.27/drivers/base/regmap/
DKconfig21 depends on SPI
/linux-4.1.27/drivers/misc/
DKconfig15 depends on (I2C || SPI) && SYSFS
44 tristate "support SPI bus connection"
47 Say Y here if you have a digital potentiometers hooked to an SPI bus.
200 communications, i.e. I2S, SPI, etc.
397 depends on SPI && SYSFS
448 tristate "BMP085 digital pressure sensor on SPI"
454 sensor hooked to an SPI bus.
490 tristate "Lattice ECP3 FPGA bitstream configuration via SPI"
491 depends on SPI && SYSFS
496 or loading) of the Lattice ECP3 FPGA family via SPI.
/linux-4.1.27/Documentation/devicetree/bindings/i2c/
Di2c-riic.txt6 - interrupts : 8 interrupts (TEI, RI, TI, SPI, STI, NAKI, ALI, TMOI)
/linux-4.1.27/Documentation/devicetree/bindings/net/can/
Dmicrochip,mcp251x.txt7 - reg: SPI chip select.
/linux-4.1.27/Documentation/i2c/busses/
Di2c-diolan-u2c17 connectivity to SPI devices.
/linux-4.1.27/Documentation/devicetree/bindings/leds/
Dleds-lp8860.txt6 signal, a SPI/I2C master, or both.
/linux-4.1.27/drivers/iio/common/ssp_sensors/
DKconfig18 depends on SPI
/linux-4.1.27/Documentation/devicetree/bindings/serial/
Ddigicolor-usart.txt4 UART. USART also support synchronous serial protocols like SPI and I2S. Use
Dmaxim,max310x.txt9 - reg: SPI chip select number.
/linux-4.1.27/Documentation/devicetree/bindings/iio/frequency/
Dadf4350.txt7 - reg: SPI chip select numbert for the device
8 - spi-max-frequency: Max SPI frequency to use (< 20000000)
/linux-4.1.27/Documentation/devicetree/bindings/security/tpm/
Dst33zp24-spi.txt5 - spi-max-frequency: Maximum SPI frequency (<= 10000000).
/linux-4.1.27/drivers/net/ethernet/qualcomm/
DKconfig24 This SPI protocol driver supports the Qualcomm Atheros QCA7000.
/linux-4.1.27/Documentation/devicetree/bindings/arm/mediatek/
Dmediatek,sysirq.txt3 Mediatek SOCs sysirq support controllable irq inverter for each GIC SPI
/linux-4.1.27/arch/blackfin/mach-bf561/
DKconfig46 int "SPI Error Interrupt"
103 int "DMA2 4 (SPI)"
/linux-4.1.27/Documentation/devicetree/bindings/input/
Dads7846.txt2 SPI driven touch screen controllers.
4 The node for this driver must be a child node of a SPI controller, hence
/linux-4.1.27/drivers/staging/iio/magnetometer/
DKconfig26 tristate "Honeywell HMC5983 3-Axis Magnetometer (SPI)"
/linux-4.1.27/Documentation/devicetree/bindings/mmc/
Dmmc-spi-slot.txt1 MMC/SD/SDIO slot directly connected to a SPI bus
/linux-4.1.27/Documentation/nfc/
Dnfc-pn544.txt11 Host Interfaces: I2C, SPI and HSU, this driver supports currently only I2C.
/linux-4.1.27/Documentation/devicetree/bindings/net/nfc/
Dtrf7970a.txt5 - spi-max-frequency: Maximum SPI frequency (<= 2000000).
/linux-4.1.27/arch/arm/plat-samsung/
DKconfig190 SPI controller 0
196 SPI controller 1
202 SPI controller 2
/linux-4.1.27/Documentation/devicetree/bindings/clock/
Dste-u300-syscon-clock.txt32 1 6 SPI clock
/linux-4.1.27/drivers/mfd/
DKconfig114 tristate "ChromeOS Embedded Controller (SPI)"
115 depends on MFD_CROS_EC && SPI && OF
119 through a SPI bus, using a byte-level protocol. Since the EC's
147 bool "Dialog Semiconductor DA9052/53 PMIC variants with SPI"
154 when controlled using SPI. This driver provides common support
215 This adds support for Diolan USB-I2C/SPI/GPIO Master Adapter
232 tristate "Freescale MC13783 and MC13892 SPI interface"
237 Select this if your MC13xxx is connected via an SPI bus.
860 chip. This connects to U8500 either on the SSP/SPI bus (deprecated
926 bool "STMicroelectronics STMPE SPI Interface"
[all …]
/linux-4.1.27/arch/powerpc/platforms/8xx/
DKconfig162 bool "I2C/SPI relocation patch"
167 bool "I2C/SPI/SMC1 relocation patch"
/linux-4.1.27/arch/blackfin/mach-bf537/
DKconfig17 int "IRQ_ERROR: PPI CAN MAC SPORT0 SPORT1 SPI UART0 UART1"
/linux-4.1.27/Documentation/networking/
Dxfrm_proc.txt23 i.e. Either inbound SPI, address, or IPsec protocol at SA is wrong
/linux-4.1.27/arch/arm/boot/dts/
Dste-hrefprev60.dtsi57 * On the first generation boards, this SSP/SPI port was connected
Domap4-var-som-om44.dtsi186 /* SPI = 0, IRQ# = 7, 4 = active high level-sensitive */
197 /* SPI = 0, IRQ# = 119, 4 = active high level-sensitive */
Dkirkwood-nas2big.dts48 * A NAND flash is used instead of an SPI flash for
Dimx6qdl-dfi-fs700-m60.dtsi152 MX6QDL_PAD_DISP0_DAT3__GPIO4_IO24 0x80000000 /* SPI NOR chipselect */
Dimx6qdl-tx6.dtsi389 MX6QDL_PAD_EIM_EB2__GPIO2_IO30 0x0b0b0 /* SPI CS0 */
390 MX6QDL_PAD_EIM_D19__GPIO3_IO19 0x0b0b0 /* SPI CS1 */
/linux-4.1.27/drivers/iio/magnetometer/
DKconfig65 - st_magn_spi (necessary for the SPI devices [optional*]);
/linux-4.1.27/Documentation/devicetree/bindings/pinctrl/
Dabilis,tb10x-iomux.txt35 - SPI ports: spi1, spi3
Dpinctrl-vt8500.txt4 either a GPIO in, GPIO out or as an alternate function (I2C, SPI etc).
/linux-4.1.27/drivers/input/misc/
DKconfig66 tristate "support SPI bus connection"
67 depends on INPUT_AD714X && SPI
70 Say Y here if you have AD7142/AD7147 hooked to a SPI bus.
661 This driver can use either I2C or SPI communication to the
681 tristate "support SPI bus connection"
682 depends on INPUT_ADXL34X && SPI
685 Say Y here if you have ADXL345/6 hooked to a SPI bus.
/linux-4.1.27/drivers/input/touchscreen/
DKconfig38 table of SPI devices.
55 code includes that in its table of SPI devices.
83 tristate "support SPI bus connection"
86 Say Y here if you have AD7879-1/AD7889-1 hooked to a SPI bus.
192 tristate "support SPI bus connection"
195 Say Y here if the touchscreen is connected via SPI bus.
222 tristate "support SPI bus connection"
225 Say Y here if the touchscreen is connected via SPI bus.
/linux-4.1.27/Documentation/input/
Dcma3000_d0x.txt29 CMA3000 chip supports mutually exclusive I2C and SPI interfaces for
/linux-4.1.27/drivers/nfc/
DKconfig31 depends on SPI && NFC_DIGITAL
/linux-4.1.27/drivers/staging/iio/Documentation/
Doverview.txt15 A typical device falling into this category would be connected via SPI
/linux-4.1.27/drivers/gpio/
DKconfig93 # This symbol is selected by both I2C and SPI expanders
384 bool "ST SPEAr13xx SPI Chip Select as GPIO support"
388 Say yes here to support ST SPEAr SPI Chip Select as GPIO device
939 menu "SPI GPIO expanders"
955 GPIO driver for Maxim MAX7301 SPI-based GPIO expander.
961 SPI/I2C driver for Microchip MCP23S08/MCP23S17/MCP23008/MCP23017
970 SPI driver for Freescale MC33880 high-side/low-side switch.
/linux-4.1.27/Documentation/devicetree/bindings/powerpc/nintendo/
Dgamecube.txt102 Represents the multi-channel SPI-like interface.
/linux-4.1.27/sound/pci/ca0106/
Dca0106.h493 #define SPI 0x7a /* SPI: Serial Interface Register */ macro
/linux-4.1.27/arch/blackfin/kernel/
Ddebug-mmrs.c417 char buf[32], *_buf = REGS_STR_PFX(buf, SPI, num); in bfin_debug_mmrs_spi()
426 #define SPI(num) bfin_debug_mmrs_spi(parent, SPI##num##_REGBASE, num) macro
1523 SPI(0); in bfin_debug_mmrs_init()
1526 SPI(1); in bfin_debug_mmrs_init()
1529 SPI(2); in bfin_debug_mmrs_init()
/linux-4.1.27/drivers/message/fusion/
DKconfig15 tristate "Fusion MPT ScsiHost drivers for SPI"
Dmptscsih.c830 if (ioc->bus_type == SPI) { in mptscsih_io_done()
901 if ((ioc->bus_type == SPI) && in mptscsih_io_done()
1671 case SPI: in mptscsih_get_tm_timeout()
2329 if (ioc->bus_type == SPI) { in mptscsih_change_queue_depth()
2372 if (ioc->bus_type == SPI) in mptscsih_slave_configure()
2384 if (ioc->bus_type == SPI) in mptscsih_slave_configure()
2596 (ioc->bus_type == SPI) && (ioc->soft_resets < -1)) in mptscsih_event_process()
/linux-4.1.27/arch/m32r/platforms/oaks32r/
Ddot.gdbinit.nommu82 printf "PSW[0x%08lX] CBR[0x%08lX] SPI[0x%08lX] SPU[0x%08lX]\n",$psw,$cbr,$spi,$spu
/linux-4.1.27/Documentation/
Dpinctrl.txt122 For example, say that we have a group of pins dealing with an SPI interface
436 In this 8x8 BGA package the pins { A8, A7, A6, A5 } can be used as an SPI port
440 we cannot use the SPI port and I2C port at the same time. However in the inside
441 of the package the silicon performing the SPI logic can alternatively be routed
447 { A1, B1, C1, D1 } or all of them. If we use all 8 bits, we cannot use the SPI
452 contain several I2C, SPI, SDIO/MMC, etc silicon blocks that can be routed to
812 | +- SPI
837 | +- SPI
846 e.g. a GPIO input can be used to "spy" on the SPI/I2C/MMC signal while it is
1358 an SPI port from one set of pins to another set of pins. Say for example for
[all …]
/linux-4.1.27/sound/soc/fsl/
DKconfig245 depends on OF && (I2C || SPI)
253 via SSI/I2S over either SPI or I2C.
/linux-4.1.27/drivers/staging/fbtft/
DKconfig3 depends on FB && SPI && GPIOLIB

12