I2S Linux driver: Difference between revisions

VisualWikitext

Latest revision as of 17:34, 10 November 2023

Applicable for

STM32MP13x lines, STM32MP15x lines, Unknown MPU

1. Article purpose[edit | edit source]

This article introduces the I2S Linux^® driver for the SPI/I2S internal peripheral.

2. Short Description[edit | edit source]

The I2S Linux driver is an ASoC CPU DAI driver implemented in the Linux ALSA framework.

Information

The SPI/I2S2 and SPI/I2S3 internal peripherals share the same parent clock, which can result in a conflict on clock configuration if I2S2 and I2S3 are used to run audio streams with incompatible rates (i.e. rates not multiples of each other).

On STM32MP15x lines, the I2S driver does not protect against such conflicts by itself.
On STM32MP25x lines, the I2S driver manages such conflicts by rejecting the incompatible stream.

3. Configuration[edit | edit source]

3.1. Kernel Configuration[edit | edit source]

Activate the I2S Linux driver in the kernel configuration using the Linux Menuconfig tool: Menuconfig or how to configure kernel.

[*] Device Drivers
    [*] Sound card support
        [*] Advanced Linux Sound Architecture
            [*] ALSA for SoC audio support
                STMicroelectronics STM32 SOC audio support
	             [*] STM32 I2S interface (SPI/I2S block) support

3.2. Device tree[edit | edit source]

Refer to the I2S_device_tree_configuration article when configuring the I2S Linux kernel driver.

Information

The I2S peripheral can be configured in transmit only, receive only or full-duplex mode, via its configuration register.

The I2S driver offers the support of transmit only, receive only, or full-duplex use cases. However, the driver always configure the I2S in full-duplex mode in the configuration register, whatever the chosen use case. If a path (transmit or capture) is not used, it is simply discarded. So, there is no property in the I2S device tree bindings to configure the mode of the I2S peripheral.

4. How to use[edit | edit source]

The I2S Linux driver can be accessed from userland through an ALSA device. Refer to ALSA overview for information on how to list and use ALSA devices.

5. How to trace and debug[edit | edit source]

The debugfs and procfs file system can be checked to get information on the I2S driver and the resources it uses. A non-exhaustive list of these file system entries is provided below. Refer to ALSA overview for more details on debugging tools.

debugfs entries:

asoc: refer to ALSA_overview#How_to_monitor
clk: refer to Clock_overview#How_to_monitor_with_debugfs_of_clock_framework to get information on clocks.
pinctrl: refer to Pinctrl_overview#How_to_monitor to get information on pins.
regmap: allow to monitor SPI/I2S peripheral registers.

$ cat /sys/kernel/debug/regmap/xxx.audio-controller/registers

procfs entries:

asound: refer to ALSA_overview#How_to_debug
interrupts: allow to check interrupts.

$ cat /proc/interrupts

6. Source code location[edit | edit source]

sound/soc/stm/stm32_i2s.c : implements the I2S Linux driver.

@@ Line 1: / Line 1: @@
-<noinclude>{{ApplicableFor
+{{ApplicableFor
-|MPUs list=STM32MP13x, STM32MP15x
+|MPUs list=STM32MP13x, STM32MP15x, STM32MP25x
-|MPUs checklist=STM32MP13x,STM32MP15x
+|MPUs checklist=STM32MP13x, STM32MP15x, STM32MP25x
-}}</noinclude>
+}}
+<noinclude></noinclude>
 == Article purpose ==
 This article introduces the I2S Linux<sup>&reg;</sup> driver for the [[SPI internal peripheral|SPI/I2S internal peripheral]].
@@ Line 9: / Line 10: @@
 The I2S Linux driver is an ASoC CPU DAI driver implemented in the Linux [[ALSA_overview|ALSA framework]].
-The I2S driver requests two clocks which can be used as parent clocks of the IS2 peripheral kernel clock.
+{{Info|
-The rates of these parent clocks must be respectively a multiple of 8kHz and 11.025kHz.
+The SPI/I2S2 and SPI/I2S3 internal peripherals share the same parent clock, which can result in a conflict on clock configuration if I2S2 and I2S3 are used to run audio streams with incompatible rates (i.e. rates not multiples of each other).
-One of these two clocks  is selected at run-time through the I2S clock mux, depending on audio stream sampling rate.
-{{Info| The parent clock may not be exactly a multiple of the audio stream rate. A [[ALSA_overview#Dynamic_traces | debug trace]] can be enabled in the I2S Linux driver, to report the clock rate accuracy.  A deviation of 1000 ppm, on the audio stream frequency, might be considered acceptable for most people.}}
-{{Info|  '''Restriction on {{MicroprocessorDevice | device=15}}: ''' </br>
+* On STM32MP15x lines, the I2S driver does not protect against such conflicts by itself.
-The SPI/I2S2 and SPI/I2S3 internal peripherals share the same clock mux. This may result in a conflict on clock mux configuration, if I2S2 and I2S3 are used to run audio streams having incompatible rates (i.e. rates not multiple of each other). The I2S driver does not protect by itself against such conflict.
+* On STM32MP25x lines, the I2S driver manages such conflicts by rejecting the incompatible stream.
 }}
@@ Line 47: / Line 45: @@
 * debugfs entries:
 :* '''asoc''': refer to [[ALSA_overview#How_to_monitor]]
-:* '''clk''': refer to [[Clock_overview#How_to_monitor_with_debugfs]] to get information on clocks.
+:* '''clk''': refer to [[Clock_overview#How_to_monitor_with_debugfs_of_clock_framework]] to get information on clocks.
 :* '''pinctrl''': refer to [[Pinctrl_overview#How_to_monitor]] to get information on pins.
 :* '''regmap''': allow to monitor SPI/I2S peripheral registers.