Serial Peripheral Interface (SPI) Bus

Overview

Terminology

The Zephyr SPI API uses the inclusive terminology selected by Rule A.2: Inclusive Language, following the OSHWA resolution to redefine SPI signal names:

• The device driving the clock is the controller, devices it addresses are peripherals (see SPI_OP_MODE_CONTROLLER and SPI_OP_MODE_PERIPHERAL).

• Data signals are named from each device’s own perspective: SDO (Serial Data Out) and SDI (Serial Data In), with CS (Chip Select) for the select line.

The former master/slave and MOSI/MISO names remain available as compatibility aliases. They are deprecated since Zephyr v4.5 and will be removed in Zephyr v5.0.

API Reference

SPI

Related code samples

• Enhanced Serial Peripheral Interface (eSPI)Use eSPI to connect to a slave device and exchange virtual wire packets.
• HCI SPIExpose a Bluetooth controller to another device or CPU over SPI.
• SPI bitbangUse the bitbang SPI driver for communicating with a peripheral.
• SPI RTIO loopbackPerform SPI transfers between SPI controller and SPI target using RTIO.
• SPIS wake upReduce current consumption by handling the wake line while using an SPIS.