Approved version. Approved on: 15:35, 21 January 2019
You are viewing an old version of this page. Return to the latest version.
Version of 15:35, 21 January 2019 by Frq08988
Difference between revisions of "SPDIFRX internal peripheral"
| [quality revision] | [quality revision] |
|
m
|
m
|
Template:ArticleMainWriter Template:ArticleApprovedVersion
Contents
- 1 Article purpose
- 2 Peripheral overview
-
3 Peripheral usage and associated software
- 3.1 Boot time
-
3.2 Runtime
- 3.2.1 Overview
- 3.2.2 Software frameworks
- 3.2.3 Peripheral configuration
- 3.2. 3.1 Configuration in Cortex-A7 non-secure software
- 3.2.3.2 Arm® Cortex®-M4 software configuration 3.2.
- 4 Peripheral assignment
- 4 How to go further
- 5 References
1 Article purpose[edit]
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 three runtime contexts and linked to the corresponding software components
- explain how to configure the SPDFIRX peripheral.
2 Peripheral overview[edit]
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]
Refer to the 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]
The SPDFIRX is a non secure peripheral.
3 Peripheral usage and associated software[edit]
3.1 Boot time[edit]
The SPDFIRX is not used at boot time.
3.2 Runtime[edit]
3.2.1 Overview[edit]
The SPDIFRX instance can be allocated to:
- the Arm® Cortex®-A7 non-secure for use in Linux with ALSA framework
- the Cortex-M4 for use in STM32Cube with STM32Cube SPDFIRX driver
Chapter #Peripheral assignment exposes which instance can be assigned to which context.
3.2.2 Software frameworks[edit]
| Domain | Peripheral | Software components | Comment | ||
|---|---|---|---|---|---|
| OP-TEE | Linux | STM32Cube | |||
| Audio | SPDIFRX | ALSA framework | STM32Cube SPDIFRX driver | ||
3.2.3 Peripheral configuration[edit]
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.
3.2.3.1 Configuration in Cortex-A7 non-secure software[edit]
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.
3.2 Arm® Cortex®-M4 software configuration[edit]3.2.4 Peripheral assignment[edit]
Check boxes illustrate the possible peripheral allocations supported by STM32 MPU Embedded Software:
- ☐ means that the peripheral can be assigned (☑) to the given runtime context.
- ✓ is used for system peripherals that cannot be unchecked because they are statically connected in the device.
Refer to How to assign an internal peripheral to a runtime context for more information on how to assign peripherals manually or via STM32CubeMX.
The present chapter describes STMicroelectronics recommendations or choice of implementation. Additional possiblities might be described in STM32MP15 reference manuals.
| 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]
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]
<noinclude> {{ArticleBasedOnModel| [[Internal peripheral article model]]}} {{ArticleMainWriter|OlivierM}} {{ ArticleApprovedVersion| OlivierM | ArnaudP |<No previous approved version>| PhilipS - 18Oct'18 - 8894 | 22Oct'18 }} [[Category:Audio peripherals]]</noinclude> ==Article purpose== 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 three runtime contexts and linked to the corresponding software components * explain how to configure the SPDFIRX peripheral. ==Peripheral overview== 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. ===Features=== Refer to the [[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=== The SPDFIRX is a '''non secure''' peripheral. ==Peripheral usage and associated software== ===Boot time=== The SPDFIRX is not used at boot time. ===Runtime=== ====Overview==== 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 Cortex-M4 for use in STM32Cube with [[STM32CubeMP1 architecture|STM32Cube SPDFIRX driver]] Chapter [[#Peripheral assignment]] exposes which instance can be assigned to which context. ====Software frameworks==== {{:Internal_peripherals_software_table_template}} | Audio | [[SPDIFRX internal peripheral|SPDIFRX]] | | [[ALSA_overview|ALSA framework]] | [[STM32CubeMP1 architecture|STM32Cube SPDIFRX driver]] | |- |} ====Peripheral configuration==== 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. =====Configuration in Cortex-A7 non-secure software=====When the Arm<sup>®</sup> Cortex<sup>®</sup>-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_overview|ALSA framework]]. Refer to [[Soundcard configuration]] and [[SPDIFRX device tree configuration]] to configure the SPDIFRX through Linux kernel device tree<ref>[[Device tree]]</ref>. =====Arm<sup>®</sup> Cortex<sup>®</sup>-M4 software configuration ===== {{ReviewsComments|To be updated}} ====Peripheral assignment==== {{:Internal_peripherals_assignment_table_template}}<onlyinclude> | rowspan="1" | Audio | rowspan="1" | [[SPDIFRX internal peripheral|SPDIFRX]] | SPDIFRX | | <span title="assignable peripheral" style="font-size:21px">☐</span> | <span title="assignable peripheral" style="font-size:21px">☐</span> | Assignment (single choice) |-</onlyinclude> |} ==How to go further== The STM32H7 SPDIFRX training <ref>[httphttps://www.st.com/content/ccc/resource/training/technical/product_training/group0/84/82/cd/52/39/88/44/91/STM32F7_Peripheral_SPDIF_RX/files/STM32F7_Peripheral_SPDIF_9c/27/1b/db/aa/d8/48/c3/STM32H7-Peripheral-SonyPhilips_Digital_Interface_Receiver_SPDIF-RX/files/STM32H7-Peripheral-SonyPhilips_Digital_Interface_Receiver_SPDIF-RX.pdf/_jcr_content/translations/en.STM32F7_STM32H7-Peripheral_SPDIF_RX.pdf|-SonyPhilips_Digital_Interface_Receiver_SPDIF-RX.pdf STM32H7 SPDIFRX training]</ref>, introduces the STM32 S/PDIF Receiver interface on the STM32H7. This training also applies to the STM32 MPU SPDIFRX internal peripheral. ==References==<references/> <noinclude> [[Category:Audio peripherals]] {{PublicationRequestId | 8894 | 2018-10-18 | PhilipS}} {{ArticleBasedOnModel| Internal peripheral article model}}</noinclude>
| (4 intermediate revisions by 3 users not shown) | |||
| Line 1: | Line 1: | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
==Article purpose== |
==Article purpose== |
||
The purpose of this article is to: |
The purpose of this article is to: |
||
| Line 49: | Line 41: | ||
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. |
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<sup>®</sup> Cortex<sup>®</sup>-A7 core operates in non-secure access mode, the SPDIFRX is controlled by the Linux kernel framework. |
When the Arm<sup>®</sup> Cortex<sup>®</sup>-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_overview|ALSA framework]]. Refer to [[Soundcard configuration]] and [[SPDIFRX device tree configuration]] to configure the SPDIFRX through Linux kernel device tree<ref>[[Device tree]]</ref>. |
Refer to the [[SPDIFRX Linux driver]] to drive the SPDIFRX through Linux kernel [[ALSA_overview|ALSA framework]]. Refer to [[Soundcard configuration]] and [[SPDIFRX device tree configuration]] to configure the SPDIFRX through Linux kernel device tree<ref>[[Device tree]]</ref>. |
||
| − | |||
| − | |||
| − | |||
====Peripheral assignment==== |
====Peripheral assignment==== |
||
| Line 72: | Line 60: | ||
==How to go further== |
==How to go further== |
||
| − | The STM32H7 SPDIFRX training <ref>[ |
+ | The STM32H7 SPDIFRX training <ref>[https://www.st.com/content/ccc/resource/training/technical/product_training/group0/9c/27/1b/db/aa/d8/48/c3/STM32H7-Peripheral-SonyPhilips_Digital_Interface_Receiver_SPDIF-RX/files/STM32H7-Peripheral-SonyPhilips_Digital_Interface_Receiver_SPDIF-RX.pdf/_jcr_content/translations/en.STM32H7-Peripheral-SonyPhilips_Digital_Interface_Receiver_SPDIF-RX.pdf STM32H7 SPDIFRX training]</ref>, introduces the STM32 S/PDIF Receiver interface on the STM32H7. This training also applies to the STM32 MPU SPDIFRX internal peripheral. |
==References== |
==References== |
||
<references/> |
<references/> |
||
| + | |||
| + | <noinclude> |
||
| + | [[Category:Audio peripherals]] |
||
| + | {{PublicationRequestId | 8894 | 2018-10-18 | PhilipS}} |
||
| + | {{ArticleBasedOnModel| Internal peripheral article model}} |
||
| + | </noinclude> |
||