1. Article purpose[edit source]
This article explains how to configure the SPI/I2S internal peripheral when it is assigned to the Linux® OS. In that case, it is controlled by the ALSA framework.
The configuration is performed using the device tree mechanism that provides a hardware description of the I2S peripheral, used by the I2S linux driver.
If the peripheral is assigned to another execution context, refer to How to assign an internal peripheral to a runtime context article for guidelines on peripheral assignment and configuration.
2. DT bindings documentation[edit source]
STM32 I2S device tree bindings [1] describes all the required and optional configuration properties.
3. DT configuration[edit source]
This hardware description is a combination of STM32 microprocessor [2] and board device tree files. See the Device tree for an explanation of the device tree file split.
STM32CubeMX can be used to generate the board device tree. Refer to How to configure the DT using STM32CubeMX for more details.
3.1. DT configuration (STM32 level)[edit source]
The I2S node is declared in stm32mp157c.dtsi[2]. It describes the hardware parameters such as register addresses, interrupt, clock, and DMA. This set of properties may not vary for a given STM32MPU.
3.2. DT configuration (board level)[edit source]
The I2S is an audio peripheral, which can be used as a component of a soundcard through Linux® kernel ALSA framework. This part of the device tree allows the configuration of the I2S to implement a soundcard. Refer to soundcard configuration for examples of I2S configuration for various boards.
4. How to configure the DT using STM32CubeMX[edit source]
The STM32CubeMX tool can be used to configure the STM32MPU device and get the corresponding platform configuration device tree files.
STM32CubeMX may not support all the properties described in the above DT bindings documentation paragraph. If so, the tool inserts user sections in the generated device tree. These sections can then be edited to add some properties and are preserved from one generation to another. Refer to the STM32CubeMX user manual for further information.
5. References[edit source]