Registered User mNo edit summary |
Registered User mNo edit summary |
||
| (7 intermediate revisions by 3 users not shown) | |||
| Line 1: | Line 1: | ||
<noinclude>{{ApplicableFor | |||
|MPUs list=STM32MP13x, STM32MP15x | |||
|MPUs checklist=STM32MP13x,STM32MP15x | |||
}}</noinclude> | |||
==Article purpose== | ==Article purpose== | ||
The purpose of this article is to: | The purpose of this article is to: | ||
* briefly introduce the SPDIFRX peripheral and its main features | * briefly introduce the SPDIFRX peripheral and its main features | ||
* indicate the level of security supported by this hardware block | * indicate the level of security supported by this hardware block | ||
* explain how each instance can be allocated to the | * explain how each instance can be allocated to the runtime contexts and linked to the corresponding software components | ||
* explain how to configure the SPDFIRX peripheral. | * explain how to configure the SPDFIRX peripheral. | ||
| Line 10: | Line 14: | ||
===Features=== | ===Features=== | ||
Refer to | Refer to [[STM32MP13 resources#Reference manuals|STM32MP13 reference manuals]] or [[STM32MP15 resources#Reference manuals|STM32MP15 reference manuals]] for the complete feature list, and to the software components, introduced below, to see which features are implemented.<br> | ||
===Security support=== | ===Security support=== | ||
| Line 22: | Line 26: | ||
====Overview==== | ====Overview==== | ||
The SPDIFRX instance can be allocated to: | The SPDIFRX instance can be allocated to: | ||
* the Arm<sup>®</sup> Cortex<sup>®</sup>-A7 non-secure for use in Linux with [[ALSA_overview|ALSA framework]] | * the Arm<sup>®</sup> Cortex<sup>®</sup>-A7 non-secure for use in Linux with [[ALSA_overview|ALSA framework]] on {{MicroprocessorDevice | device=1}} | ||
* the Cortex-M4 for use in STM32Cube with [[STM32CubeMP1 architecture|STM32Cube SPDFIRX driver]] | * the Cortex-M4 for use in STM32Cube with [[STM32CubeMP1 architecture|STM32Cube SPDFIRX driver]] on {{MicroprocessorDevice | device=15}} only | ||
Chapter [[#Peripheral assignment]] exposes which instance can be assigned to which context. | Chapter [[#Peripheral assignment]] exposes which instance can be assigned to which context. | ||
====Software frameworks==== | ====Software frameworks==== | ||
{{: | ===== On {{MicroprocessorDevice | device=13}} ===== | ||
{{:STM32MP13 internal_peripherals_software_table_template}} | |||
| Audio | |||
| [[SPDIFRX internal peripheral|SPDIFRX]] | |||
| | |||
| [[ALSA_overview|ALSA framework]] | |||
| | |||
|- | |||
|} | |||
===== On {{MicroprocessorDevice | device=15}} ===== | |||
{{:STM32MP15_internal_peripherals_software_table_template}} | |||
| Audio | | Audio | ||
| [[SPDIFRX internal peripheral|SPDIFRX]] | | [[SPDIFRX internal peripheral|SPDIFRX]] | ||
| Line 45: | Line 59: | ||
====Peripheral assignment==== | ====Peripheral assignment==== | ||
{{: | ===== On {{MicroprocessorDevice | device=13}} ===== | ||
< | {{:STM32MP13_internal_peripherals_assignment_table_template}} | ||
<section begin=stm32mp13 /> | |||
| rowspan="1" | Audio | |||
| rowspan="1" | [[SPDIFRX internal peripheral|SPDIFRX]] | |||
| SPDIFRX | |||
| | |||
| <span title="assignable peripheral" style="font-size:21px">☐</span> | |||
| Assignment (single choice) | |||
|- | |||
<section end=stm32mp13 /> | |||
|} | |||
===== On {{MicroprocessorDevice | device=15}} ===== | |||
{{:STM32MP15_internal_peripherals_assignment_table_template}} | |||
<section begin=stm32mp15 /> | |||
| rowspan="1" | Audio | | rowspan="1" | Audio | ||
| rowspan="1" | [[SPDIFRX internal peripheral|SPDIFRX]] | | rowspan="1" | [[SPDIFRX internal peripheral|SPDIFRX]] | ||
| Line 55: | Line 82: | ||
| Assignment (single choice) | | Assignment (single choice) | ||
|- | |- | ||
</ | <section end=stm32mp15 /> | ||
|} | |} | ||
Latest revision as of 15:39, 1 February 2022
1. Article purpose[edit source]
The purpose of this article is to:
- briefly introduce the SPDIFRX peripheral and its main features
- indicate the level of security supported by this hardware block
- explain how each instance can be allocated to the runtime contexts and linked to the corresponding software components
- explain how to configure the SPDFIRX peripheral.
2. Peripheral overview[edit source]
The SPDIFRX peripheral, is designed to receive an S/PDIF flow compliant with IEC-60958 and IEC-61937. The SPDIFRX receiver provides two separated paths to retrieve the audio data and the user and channel information.
2.1. Features[edit source]
Refer to STM32MP13 reference manuals or STM32MP15 reference manuals for the complete feature list, and to the software components, introduced below, to see which features are implemented.
2.2. Security support[edit source]
The SPDFIRX is a non secure peripheral.
3. Peripheral usage and associated software[edit source]
3.1. Boot time[edit source]
The SPDFIRX is not used at boot time.
3.2. Runtime[edit source]
3.2.1. Overview[edit source]
The SPDIFRX instance can be allocated to:
- the Arm® Cortex®-A7 non-secure for use in Linux with ALSA framework on STM32MP1 Series
- the Cortex-M4 for use in STM32Cube with STM32Cube SPDFIRX driver on STM32MP15x lines
only
Chapter #Peripheral assignment exposes which instance can be assigned to which context.
3.2.2. Software frameworks[edit source]
3.2.2.1. On STM32MP13x lines [edit source]
| Domain | Peripheral | Software components | Comment | |
|---|---|---|---|---|
| OP-TEE | Linux | |||
| Audio | SPDIFRX | ALSA framework | ||
3.2.2.2. On STM32MP15x lines [edit source]
| Domain | Peripheral | Software components | Comment | ||
|---|---|---|---|---|---|
| OP-TEE | Linux | STM32Cube | |||
| Audio | SPDIFRX | ALSA framework | STM32Cube SPDIFRX driver | ||
3.2.3. Peripheral configuration[edit source]
The configuration is applied by the firmware running in the context to which the peripheral is assigned. The configuration can be done alone via the STM32CubeMX tool for all internal peripherals, and then manually completed (particularly for external peripherals), according to the information given in the corresponding software framework article.
When the Arm® Cortex®-A7 core operates in non-secure access mode, the SPDIFRX is controlled by the Linux kernel framework. Refer to the SPDIFRX Linux driver to drive the SPDIFRX through Linux kernel ALSA framework. Refer to Soundcard configuration and SPDIFRX device tree configuration to configure the SPDIFRX through Linux kernel device tree[1].
3.2.4. Peripheral assignment[edit source]
3.2.4.1. On STM32MP13x lines [edit source]
Click on the right to expand the legend...
| Domain | Peripheral | Runtime allocation | Comment | ||
|---|---|---|---|---|---|
| Instance | Cortex-A7 secure (OP-TEE) |
Cortex-A7 non-secure (Linux) | |||
| Audio | SPDIFRX | SPDIFRX | ☐ | Assignment (single choice) | |
3.2.4.2. On STM32MP15x lines [edit source]
Click on the right to expand the legend...
| Domain | Peripheral | Runtime allocation | Comment | |||
|---|---|---|---|---|---|---|
| Instance | Cortex-A7 secure (OP-TEE) |
Cortex-A7 non-secure (Linux) |
Cortex-M4 (STM32Cube) | |||
| Audio | SPDIFRX | SPDIFRX | ☐ | ☐ | Assignment (single choice) | |
4. How to go further[edit source]
The STM32H7 SPDIFRX training [2], introduces the STM32 S/PDIF Receiver interface on the STM32H7. This training also applies to the STM32 MPU SPDIFRX internal peripheral.
5. References[edit source]
Arm® is a registered trademark of Arm Limited (or its subsidiaries) in the US and/or elsewhere. 