Registered User mNo edit summary |
Registered User m (Text replacement - "arch/arm/boot/dts/" to "arch/arm/boot/dts/st/") |
||
(13 intermediate revisions by 6 users not shown) | |||
Line 1: | Line 1: | ||
{{ApplicableFor | |||
|MPUs list=STM32MP13x, STM32MP15x | |||
|MPUs checklist=STM32MP13x, STM32MP15x, STM32MP25x | |||
}} | |||
<noinclude></noinclude> | |||
== Article purpose == | == Article purpose == | ||
This article explains how to configure the [[DMAMUX internal peripheral]] when it is assigned to the Linux<sup>®</sup> OS. In that case, it is controlled by the [[Dmaengine overview]]. | This article explains how to configure the [[DMAMUX internal peripheral]] when it is assigned to the Linux<sup>®</sup> OS. In that case, it is controlled by the [[Dmaengine overview]]. | ||
Line 7: | Line 12: | ||
* STM32 DMAMUX peripheral | * STM32 DMAMUX peripheral | ||
* and STM32 DMAMUX client | * and STM32 DMAMUX client | ||
If the peripheral is assigned to another execution context, refer to [[How to assign an internal peripheral to an execution context]] article for guidelines on peripheral assignment and configuration. | |||
== DT bindings documentation == | == DT bindings documentation == | ||
Complete device tree bindings can be found at this location: <ref>{{CodeSource | Linux kernel | Documentation/devicetree/bindings/dma/stm32-dmamux. | Complete device tree bindings can be found at this location: <ref>{{CodeSource | Linux kernel | Documentation/devicetree/bindings/dma/stm32/st,stm32-dmamux.yaml}}</ref>. | ||
== DT configuration == | == DT configuration == | ||
Line 17: | Line 24: | ||
===DT configuration (STM32 level) === | ===DT configuration (STM32 level) === | ||
The STM32MP1 [[DMAMUX internal peripheral| DMAMUX ]] node is located | |||
* for {{MicroprocessorDevice | device=13}} in stm32mp131.dtsi <ref name="stm32mp131.dtsi">{{CodeSource | Linux kernel | arch/arm/boot/dts/st/stm32mp131.dtsi | stm32mp131.dtsi}}</ref> | |||
* for {{MicroprocessorDevice | device=15}} in stm32mp151.dtsi <ref name="stm32mp151.dtsi">{{CodeSource | Linux kernel | arch/arm/boot/dts/st/stm32mp151.dtsi | stm32mp151.dtsi}}</ref> | |||
For example, at device level, DMAMUX is declared as follows: | |||
<pre> | <pre> | ||
dmamux1: dma-router@48002000 { | dmamux1: dma-router@48002000 { | ||
compatible = "st,stm32h7-dmamux"; | compatible = "st,stm32h7-dmamux"; | ||
reg = <0x48002000 | reg = <0x48002000 0x40>; | ||
#dma-cells = <3>; | #dma-cells = <3>; | ||
dma-requests = <128>; | dma-requests = <128>; | ||
Line 28: | Line 40: | ||
dma-channels = <16>; | dma-channels = <16>; | ||
clocks = <&rcc DMAMUX>; | clocks = <&rcc DMAMUX>; | ||
resets = <&rcc DMAMUX_R>; | |||
}; | }; | ||
</pre> | </pre> | ||
{{Warning|This device tree part is related to STM32 microprocessors. It must be kept as is, without being modified by the end-user.}} | {{Warning|This device tree part is related to STM32 microprocessors. It must be kept as is, without being modified by the end-user.}} | ||
Line 40: | Line 51: | ||
==How to configure the DT using STM32CubeMX== | ==How to configure the DT using STM32CubeMX== | ||
The [[STM32CubeMX]] tool can be used to configure the STM32MPU device and get the corresponding [[Device_tree# | The [[STM32CubeMX]] tool can be used to configure the STM32MPU device and get the corresponding [[Device_tree#STM32_MPU|platform configuration device tree]] files.<br /> | ||
The STM32CubeMX may not support all the properties described in the above [[#DT bindings documentation|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 they are preserved from one generation to another. Refer to [[STM32CubeMX]] user manual for further information. | The STM32CubeMX may not support all the properties described in the above [[#DT bindings documentation|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 they are preserved from one generation to another. Refer to [[STM32CubeMX]] user manual for further information. | ||
Latest revision as of 12:51, 8 October 2024
1. Article purpose[edit | edit source]
This article explains how to configure the DMAMUX internal peripheral when it is assigned to the Linux® OS. In that case, it is controlled by the Dmaengine overview.
The configuration is performed using the Device tree mechanism that provides a hardware description of the DMAMUX internal peripheral, used by the STM32 DMAMUX Linux driver and by the DMA framework.
The hardware description is a combination of:
- STM32 DMAMUX peripheral
- and STM32 DMAMUX client
If the peripheral is assigned to another execution context, refer to How to assign an internal peripheral to an execution context article for guidelines on peripheral assignment and configuration.
2. DT bindings documentation[edit | edit source]
Complete device tree bindings can be found at this location: [1].
3. DT configuration[edit | edit source]
This hardware description is a combination of the STM32 microprocessor device tree files (.dtsi extension) and board device tree files (.dts extension). 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 | edit source]
The STM32MP1 DMAMUX node is located
For example, at device level, DMAMUX is declared as follows:
dmamux1: dma-router@48002000 {
compatible = "st,stm32h7-dmamux";
reg = <0x48002000 0x40>;
#dma-cells = <3>;
dma-requests = <128>;
dma-masters = <&dma1 &dma2>;
dma-channels = <16>;
clocks = <&rcc DMAMUX>;
resets = <&rcc DMAMUX_R>;
};
3.2. DT configuration (board level)[edit | edit source]
No board device tree configuration is required.
The whole configuration remains at STM32 level.
4. How to configure the DT using STM32CubeMX[edit | edit source]
The STM32CubeMX tool can be used to configure the STM32MPU device and get the corresponding platform configuration device tree files.
The 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 they are preserved from one generation to another. Refer to STM32CubeMX user manual for further information.
5. References[edit | edit source]
Please refer to the following links for additional information: