| /Linux-v4.19/drivers/spi/ |
| D | Kconfig | 2 # SPI driver configuration
4 menuconfig SPI config
5 bool "SPI support"
9 protocol. Chips that support SPI can have data transfer rates
11 controller and a chipselect. Most SPI slaves don't support
14 SPI is widely used by microcontrollers to talk with sensors,
17 MMC and SD cards can be accessed using SPI protocol; and for
18 DataFlash cards used in MMC sockets, SPI must always be used.
20 SPI is one of a family of similar protocols using a four wire
25 if SPI
[all …]
|
| /Linux-v4.19/drivers/mtd/spi-nor/ |
| D | Kconfig | 2 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.
11 tristate "Mediatek MT81xx SPI NOR flash controller"
14 This enables access to SPI NOR flash, using MT81xx SPI NOR flash
15 controller. This controller does not support generic SPI BUS, it only
16 supports SPI NOR Flash.
33 tristate "Aspeed flash controllers in SPI mode"
38 in the Aspeed AST2500/AST2400 SoCs when attached to SPI NOR chips,
39 and support for the SPI flash memory controller (SPI) for
[all …]
|
| /Linux-v4.19/Documentation/mtd/ |
| D | spi-nor.txt | 1 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 …]
|
| D | intel-spi.txt | 4 Many Intel CPUs like Baytrail and Braswell include SPI serial flash host
6 Since contents of the SPI serial flash is crucial for machine to function,
10 Not all manufacturers protect the SPI serial flash, mainly because it
13 The intel-spi driver makes it possible to read and write the SPI serial
16 partial overwrites. By default the driver exposes SPI serial flash
20 Please keep in mind that overwriting the BIOS image on SPI serial flash
27 1) Download and extract the latest Minnowboard MAX BIOS SPI image
30 2) Install mtd-utils package [2]. We need this in order to erase the SPI
62 7) Erase the SPI serial flash. After this step, do not reboot the
72 9) Verify that the new content of the SPI serial flash matches the new
|
| /Linux-v4.19/Documentation/devicetree/bindings/spi/ |
| 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
15 address on the SPI bus.
18 In slave mode, the SPI controller node requires one additional property:
21 No other properties are required in the SPI bus node. It is assumed
[all …]
|
| D | spi-davinci.txt | 1 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 - "ti,keystone-spi" for SPI used similar to that on Keystone2 SoC
17 - reg: Offset and length of SPI controller register space
20 - ti,davinci-spi-intr-line: interrupt line used to connect the SPI
35 and an args specifier containing the SPI device id
45 SPI slave nodes can contain the following properties.
46 Not all SPI Peripherals from Texas Instruments support this.
[all …]
|
| D | spi-bcm63xx.txt | 1 Binding for Broadcom BCM6348/BCM6358 SPI controller
6 - interrupts: Interrupt for the SPI block.
7 - clocks: phandle of the SPI clock.
9 - #address-cells: <1>, as required by generic SPI binding.
10 - #size-cells: <0>, also as required by generic SPI binding.
16 Child nodes as per the generic SPI binding.
|
| D | spi-bcm63xx-hsspi.txt | 1 Binding for Broadcom BCM6328 High Speed SPI controller
6 - interrupts: Interrupt for the SPI block.
7 - clocks: phandles of the SPI clock and the PLL clock.
9 - #address-cells: <1>, as required by generic SPI binding.
10 - #size-cells: <0>, also as required by generic SPI binding.
16 Child nodes as per the generic SPI binding.
|
| D | brcm,spi-bcm-qspi.txt | 1 Broadcom SPI controller
3 The Broadcom SPI controller is a SPI master found on various SOCs, including
4 BRCMSTB (BCM7XXX), Cygnus, NSP and NS2. The Broadcom Master SPI hw IP consits
6 MSPI : SPI master controller can read and write to a SPI slave device
7 BSPI : Broadcom SPI in combination with the MSPI hw IP provides acceleration
14 use SPI protocol.
19 Must be <1>, as required by generic SPI binding.
22 Must be <0>, also as required by generic SPI binding.
51 - "mspi_done": Indicates that the requested SPI operation is complete.
74 SPI Master (MSPI+BSPI) for SPI-NOR access:
[all …]
|
| /Linux-v4.19/Documentation/networking/caif/ |
| D | spi_porting.txt | 1 - 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-v4.19/Documentation/spi/ |
| D | 00-INDEX | 4 - AVR Butterfly SPI driver overview and pin configuration.
6 - Basic EP93xx SPI driver configuration.
8 - PXA2xx SPI master controller build by spi_message fifo wq
12 - Connecting an LM70-LLP sensor to the kernel via the SPI subsys.
14 - NXP SC18IS602/603 I2C-bus to SPI bridge
16 - (Linux) SPI overview. If unsure about SPI or SPI in Linux, start here.
|
| D | spi-summary | 1 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 …]
|
| D | spidev | 1 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 …]
|
| /Linux-v4.19/drivers/net/can/spi/ |
| D | Kconfig | 1 menu "CAN SPI interfaces"
2 depends on SPI
5 tristate "Holt HI311x SPI CAN controllers"
6 depends on CAN_DEV && SPI && HAS_DMA
8 Driver for the Holt HI311x SPI CAN controllers.
11 tristate "Microchip MCP251x SPI CAN controllers"
14 Driver for the Microchip MCP251x SPI CAN controllers.
|
| /Linux-v4.19/drivers/media/spi/ |
| D | Kconfig | 3 menu "SPI helper chips"
8 depends on SPI && VIDEO_V4L2 && VIDEO_V4L2_SUBDEV_API
16 if SPI
17 menu "Media SPI Adapters"
20 tristate "Sony CXD2880 SPI support"
21 depends on DVB_CORE && SPI
24 Choose if you would like to have SPI interface support for Sony CXD2880.
|
| /Linux-v4.19/Documentation/devicetree/bindings/net/ |
| D | qca,qca7000.txt | 4 be configured either as SPI or UART slave. This configuration is done by
7 (a) Ethernet over SPI
9 In order to use the QCA7000 as SPI device it must be defined as a child of a
10 SPI master in the device tree.
14 - reg : Should specify the SPI chip select
22 - spi-max-frequency : Maximum frequency of the SPI bus the chip can operate at.
24 are invalid. Missing the property will set the SPI
27 - qca,legacy-mode : Set the SPI data transfer of the QCA7000 to legacy mode.
28 In this mode the SPI master must toggle the chip select
34 SPI Example:
[all …]
|
| /Linux-v4.19/drivers/pinctrl/ |
| D | pinctrl-xway.c | 128 MFP_XWAY(GPIO9, GPIO, ASC, SPI, EXIN),
129 MFP_XWAY(GPIO10, GPIO, ASC, SPI, NONE),
130 MFP_XWAY(GPIO11, GPIO, ASC, PCI, SPI),
132 MFP_XWAY(GPIO13, GPIO, EBU, SPI, NONE),
134 MFP_XWAY(GPIO15, GPIO, SPI, JTAG, NONE),
135 MFP_XWAY(GPIO16, GPIO, SPI, NONE, JTAG),
136 MFP_XWAY(GPIO17, GPIO, SPI, NONE, JTAG),
137 MFP_XWAY(GPIO18, GPIO, SPI, NONE, JTAG),
141 MFP_XWAY(GPIO22, GPIO, SPI, NONE, NONE),
255 GRP_MUX("spi", SPI, pins_spi),
[all …]
|
| /Linux-v4.19/Documentation/driver-api/ |
| D | spi.rst | 1 Serial Peripheral Interface (SPI)
4 SPI is the "Serial Peripheral Interface", widely used with embedded
8 line, and a "Master In, Slave Out" (MISO) data line. SPI is a full
15 The SPI bus facilities listed here provide a generalized interface to
16 declare SPI busses and devices, manage them according to the standard
18 only "master" side interfaces are supported, where Linux talks to SPI
20 to support implementing SPI slaves would necessarily look different.)
26 SPI shift register (maximizing throughput). Such drivers bridge between
27 whatever bus they sit on (often the platform bus) and SPI, and expose
28 the SPI side of their device as a :c:type:`struct spi_master
[all …]
|
| /Linux-v4.19/Documentation/devicetree/bindings/mtd/ |
| D | aspeed-smc.txt | 2 * Aspeed SPI Flash Memory Controller
5 three chip selects, two of which are always of SPI type and the third
6 can be SPI or NOR type flash. These bindings only describe SPI.
8 The two SPI flash memory controllers in the AST2500 each support two
14 "aspeed,ast2400-spi" for the AST2400 SPI Flash memory Controller
16 "aspeed,ast2500-spi" for the AST2500 SPI flash memory controllers
27 The child nodes are the SPI flash modules which must have a compatible
30 Optionally, the child node can contain properties for SPI mode (may be
|
| /Linux-v4.19/Documentation/ABI/testing/ |
| D | sysfs-bus-iio-dfsdm-adc-stm32 | 7 This is mandatory if DFSDM is slave on SPI bus, to
8 provide information on the SPI clock frequency during runtime
9 Notice that the SPI frequency should be a multiple of sample
11 if DFSDM input is SPI master
12 Reading SPI clkout frequency,
14 If DFSDM input is SPI Slave:
|
| /Linux-v4.19/Documentation/devicetree/bindings/iio/adc/ |
| D | st,stm32-dfsdm-adc.txt | 10 It features up to 8 serial digital interfaces (SPI or Manchester) and
32 - spi-max-frequency: Requested only for SPI master mode.
33 SPI clock OUT frequency (Hz). This clock must be set according
35 clock frequency. If not, SPI CLKOUT frequency will not be
76 - "SPI_R": SPI with data on rising edge (default)
77 - "SPI_F": SPI with data on falling edge
81 - "CLKIN": external SPI clock (CLKIN x)
82 - "CLKOUT": internal SPI clock (CLKOUT) (default)
83 - "CLKOUT_F": internal SPI clock divided by 2 (falling edge).
84 - "CLKOUT_R": internal SPI clock divided by 2 (rising edge).
[all …]
|
| /Linux-v4.19/drivers/staging/wilc1000/ |
| D | Kconfig | 21 tristate "Atmel WILC1000 SPI (WiFi only)"
22 depends on CFG80211 && INET && SPI
25 This module adds support for the SPI interface of adapters using
27 Interface (SPI) that operates as a SPI slave. This SPI interface can
28 be used for control and for serial I/O of 802.11 data. The SPI is a
31 VDDIO. Select this if your platform is using the SPI bus.
|
| /Linux-v4.19/Documentation/devicetree/bindings/net/nfc/ |
| D | st95hf.txt | 3 ST NFC Transceiver is required to attach with SPI bus.
4 ST95HF node should be defined in DT as SPI slave device of SPI
11 - reg: Address of SPI slave "ST95HF transceiver" on SPI master bus.
15 - spi-max-frequency: Max. operating SPI frequency for ST95HF
|
| /Linux-v4.19/drivers/net/ieee802154/ |
| D | Kconfig | 26 depends on SPI
29 Say Y here to enable the at86rf230/231/233/212 SPI 802.15.4 wireless
45 depends on SPI
48 Say Y here to enable the MRF24J20 SPI 802.15.4 wireless
57 depends on SPI
59 Say Y here to enable the CC2520 SPI 802.15.4 wireless
78 depends on SPI
80 Say Y here to enable the ADF7242 SPI 802.15.4 wireless
90 depends on SPI
92 Say Y here to enable the CA8210 SPI 802.15.4 wireless
[all …]
|
| /Linux-v4.19/drivers/iio/gyro/ |
| D | Kconfig | 9 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
59 select BMG160_SPI if (SPI)
62 driver connected via I2C or SPI. This driver also supports BMI055
[all …]
|
