Difference between revisions of "MDMA internal peripheral"

[quality revision] [quality revision]
m
m
 
Applicable for STM32MP13x lines, STM32MP15x lines

1 Article purpose[edit]

The purpose of this article is to:

  • briefly introduce the MDMA 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, when necessary, how to configure the MDMA peripheral.

2 Peripheral overview[edit]

The MDMA is used to perform high-speed data transfers between memory and memory or between peripherals and memory. The MDMA controller offers 32 channels. The selection of the device connected to each channel and controlling DMA transfers is done in MDMA peripheral.

Among all the requestor lines described in the reference manual (accessible via the following paragraph), DMA channels are the only lines that allow to perform transfers with chained DMA and MDMA (refer to DMA internal peripheral article). As a result, when a device is not connected to the MDMA, it is anyway possible to operate in DMA mode via the DMA controller and chain DMA and MDMA.

2.1 Features[edit]

Refer to STM32MP13 reference manuals or STM32MP15 reference manuals for the complete list of features, and to the software components, introduced below, to see which features are implemented.

2.2 Security support[edit]

The MDMA is a secure peripheral. This means that it performs each transfer in the context of the master that requested it:

  • a transfer requested by the Arm® Cortex®-A7 non-secure core propagates non-secure accesses to the targeted device and/or memory.
  • a transfer requested by Arm Cortex-A7 secure core propagates secure accesses to the targeted device and/or memory.

3 Peripheral usage and associated software[edit]

3.1 Boot time[edit]

The MDMA is used at boot time by the FMC.

3.2 Runtime[edit]

3.2.1 Overview[edit]

As stated in the 'Security support' chapter above, the MDMA is a secure peripheral. This means that its channels have to be allocated to:

  • the Arm Cortex-A7 non-secure core to be controlled in Linux® by the dmaengine framework

and

  • the Arm Cortex-A7 secure core to be controlled by a MDMA OP-TEE driver, not supported yet by OpenSTLinux.

STM32CubeMX allows to distinguish between non-secure and secure channels, among all the available channels.

On STM32MP15x lines More info.png, the MDMA is visible from the Arm Cortex-M4 core. However, it is not supported in this context by STM32MPU Embedded Software distribution.

3.2.2 Software frameworks[edit]

3.2.2.1 On STM32MP13x lines Warning.png[edit]
Domain Peripheral Software components Comment
OP-TEE Linux
Core/DMA MDMA OP-TEE MDMA driver Linux dmaengine framework
3.2.2.2 On STM32MP15x lines More info.png[edit]

Internal peripherals software table template

|
Domain Peripheral Software components Comment
OP-TEE Linux STM32Cube
Core/DMA
| MDMA |
MDMA OP-TEE
MDMA
driver
|
Linux
dmaengine
framework
| | |- |}

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.4 Peripheral assignment[edit]

3.2.4.1 On STM32MP13x lines Warning.png[edit]

Click on the right to expand the legend...

STM32MP13IPsOverview.png

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.
  • means that the peripheral can be assigned to the given runtime context, but this configuration is not supported in STM32 MPU Embedded Software distribution.
  • 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 STM32MP13 reference manuals.

Domain Peripheral Runtime allocation Comment
Instance Cortex-A7
secure
(OP-TEE)
Cortex-A7
non-secure
(Linux)
Core/DMA MDMA MDMA Shareable (multiple choices supported)
3.2.4.2 On STM32MP15x lines More info.png[edit]
Internal peripherals assignment table template
| rowspan="1" | Core/DMA
| rowspan="1" | MDMA
| MDMA
| 
| 
|
| Shareable (multiple choices supported)
|-

|}

Click on the right to expand the legend...

STM32MP15 internal peripherals

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.
  • means that the peripheral can be assigned to the given runtime context, but this configuration is not supported in STM32 MPU Embedded Software distribution.
  • 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)
Core/DMA MDMA MDMA Shareable (multiple choices supported)


<noinclude>{{ApplicableFor
|MPUs list=STM32MP13x, STM32MP15x
|MPUs checklist=STM32MP13x,STM32MP15x
}}</noinclude>

==Article purpose==
The purpose of this article is to:
* briefly introduce the MDMA 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, when necessary, how to configure the MDMA peripheral.

==Peripheral overview==
The '''MDMA''' is used to perform high-speed data transfers between memory and memory or between peripherals and memory. The MDMA controller offers 32 channels. The selection of the device connected to each channel and controlling DMA transfers is done in MDMA peripheral. <br />


Among all the requestor lines described in the reference manual (accessible via the [[#Features | following paragraph]]), [[DMA internal peripheral|DMA]] channels are the only lines that allow to perform transfers with chained [[DMA internal peripheral|DMA]] and MDMA (refer to [[DMA internal peripheral]] article). As a result, when a device is not connected to the MDMA, it is anyway possible to operate in DMA mode via the [[DMA internal peripheral|DMA]] controller and chain [[DMA internal peripheral|DMA]] and MDMA. 

===Features===
Refer to [[STM32MP13 resources#Reference manuals|STM32MP13 reference manuals]] or [[STM32MP15 resources#Reference manuals|STM32MP15 reference manuals]] for the complete list of features, and to the software components, introduced below, to see which features are implemented.<br>


===Security support===
The MDMA is a '''secure''' peripheral. 
This means that it performs each transfer in the context of the master that requested it:
* a transfer requested by the Arm<sup>&reg;</sup> Cortex<sup>&reg;</sup>-A7 '''non-secure''' core propagates '''non-secure accesses''' to the targeted device and/or memory.
* a transfer requested by Arm Cortex-A7 '''secure''' core propagates '''secure accesses''' to the targeted device and/or memory.

==Peripheral usage and associated software==
===Boot time===
The MDMA is used at boot time by the FMC.

===Runtime===
====Overview====
As stated in the 'Security support' chapter above, the MDMA is a secure peripheral. This means that its channels have to be allocated to: 
* the Arm Cortex-A7 non-secure core to be controlled in Linux<sup>&reg;</sup>  by the [[Dmaengine overview|dmaengine]] framework
and
* the Arm Cortex-A7 secure core to be controlled by a MDMA [[OP-TEE overview|OP-TEE]] driver, not supported yet by OpenSTLinux.<br />


[[STM32CubeMX]] allows to distinguish between non-secure and secure channels, among all the available channels.

On {{MicroprocessorDevice | device=15}}, the MDMA is visible from the Arm Cortex-M4 core. However, it is not supported in this context by [[STM32MPU Embedded Software distribution|STM32MPU Embedded Software distribution]].<br /><br />


====Software frameworks====
===== On {{MicroprocessorDevice | device=13}} =====
{{:STM32MP13 internal_peripherals_software_table_template}}
 | Core/DMA
 | [[MDMA internal peripheral|MDMA]]
 | [[OP-TEE_overview|OP-TEE MDMA driver]]
 | [[Dmaengine overview|Linux dmaengine framework]]
 |
 |-
 |}
===== On {{MicroprocessorDevice | device=15}} =====
{{:Internal_STM32MP15_internal_peripherals_software_table_template}}
 | Core/DMA
 | [[MDMA internal peripheral|MDMA]]
 | [[OP-TEE_overview|OP-TEE MDMA driver]]
 | [[Dmaengine overview|Linux dmaengine framework]]
 | 
 |
 |-
 |}

====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.

====Peripheral assignment====
===== On {{MicroprocessorDevice | device=13}} =====
{{:STM32MP13 internal_peripherals_assignment_table_template}}<section begin=stm32mp13 />

 | rowspan="1" | Core/DMA
 | rowspan="1" | [[MDMA internal peripheral|MDMA]]
 | MDMA
 | <span title="assignable peripheral but not supported" style="font-size:21px"></span>

 | <span title="assignable peripheral" style="font-size:21px"></span>

 | Shareable (multiple choices supported)
 |-<section end=stm32mp13 />

 |}
===== On {{MicroprocessorDevice | device=15}} =====
{{:Internal_STM32MP15_internal_peripherals_assignment_table_template}}<section begin=stm32mp15 />

 | rowspan="1" | Core/DMA
 | rowspan="1" | [[MDMA internal peripheral|MDMA]]
 | MDMA
 | <span title="assignable peripheral" style="font-size:21px"></span>

 | <span title="assignable peripheral" style="font-size:21px"></span>

 |
 | Shareable (multiple choices supported)
 |-<section end=stm32mp15 />

 |}
<noinclude>

[[Category:DMA peripherals]]
{{PublicationRequestId | 8859 | 2018-09-21 | AnneJ}}
{{ArticleBasedOnModel| Internal peripheral article model}}</noinclude>
Line 50: Line 50:
 
  |}
 
  |}
 
===== On {{MicroprocessorDevice | device=15}} =====
 
===== On {{MicroprocessorDevice | device=15}} =====
{{:Internal_peripherals_software_table_template}}
+
{{:STM32MP15_internal_peripherals_software_table_template}}
 
  | Core/DMA
 
  | Core/DMA
 
  | [[MDMA internal peripheral|MDMA]]
 
  | [[MDMA internal peripheral|MDMA]]
Line 77: Line 77:
 
  |}
 
  |}
 
===== On {{MicroprocessorDevice | device=15}} =====
 
===== On {{MicroprocessorDevice | device=15}} =====
{{:Internal_peripherals_assignment_table_template}}
+
{{:STM32MP15_internal_peripherals_assignment_table_template}}
 
<section begin=stm32mp15 />
 
<section begin=stm32mp15 />
 
  | rowspan="1" | Core/DMA
 
  | rowspan="1" | Core/DMA