Registered User (Created page with "{{ApplicableFor |MPUs list=STM32MP15x |MPUs checklist=STM32MP15x }} == Article purpose == This article explains how to configure the HSEM internal peripheral|'''HSEM''' inte...") |
Registered User No edit summary |
||
| (6 intermediate revisions by 3 users not shown) | |||
| Line 1: | Line 1: | ||
{{ApplicableFor | {{ApplicableFor | ||
|MPUs list=STM32MP15x | |MPUs list=STM32MP15x | ||
|MPUs checklist=STM32MP15x | |MPUs checklist=STM32MP13x, STM32MP15x, STM32MP21x, STM32MP23x, STM32MP25x | ||
}} | }} | ||
<noinclude></noinclude> | |||
== Article purpose == | == Article purpose == | ||
This article explains how to configure the [[HSEM internal peripheral|'''HSEM''' internal peripheral]] controlled by the Linux<sup>® </sup> | This article explains how to configure the [[HSEM internal peripheral|'''HSEM''' internal peripheral]] controlled by the Linux<sup>® </sup> | ||
| Line 20: | Line 21: | ||
===DT configuration (STM32 level) === | ===DT configuration (STM32 level) === | ||
The HSEM peripheral node is located in ''stm32mp151.dtsi'' <ref>{{CodeSource | Linux kernel | arch/arm/boot/dts/stm32mp151.dtsi | arch/arm/boot/dts/stm32mp151.dtsi}}</ref> file. | The HSEM peripheral node is located in ''stm32mp151.dtsi'' <ref>{{CodeSource | Linux kernel | arch/arm/boot/dts/st/stm32mp151.dtsi | arch/arm/boot/dts/st/stm32mp151.dtsi}}</ref> file. | ||
<pre> | <pre> | ||
hsem: hwspinlock@4c000000 { | hsem: hwspinlock@4c000000 { | ||
| Line 43: | Line 44: | ||
... | ... | ||
</pre> | </pre> | ||
The pincrl device uses the semaphore ID 0 (first number) and this semaphore can be shared (second number = 1, meaning shared usage), | The pincrl device uses the semaphore ID 0 (first number) and this semaphore can be shared (second number = 1, meaning shared usage), which means it is used by another device. | ||
==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. | ||
==References== | ==References== | ||
Refer to the following links for additional information: | |||
<references /> | <references /> | ||
| Line 56: | Line 57: | ||
<noinclude> | <noinclude> | ||
[[Category:Hardware spinlock|0]] | [[Category:Hardware spinlock|0]] | ||
{{PublicationRequestId | 22725 | 03/03/2022| }} | |||
{{ArticleBasedOnModel | Peripheral or framework device tree configuration model}} | {{ArticleBasedOnModel | Peripheral or framework device tree configuration model}} | ||
</noinclude> | </noinclude> | ||
Latest revision as of 11:42, 24 October 2024
1. Article purpose[edit | edit source]
This article explains how to configure the HSEM internal peripheral controlled by the Linux® Hardware spinlock framework.
The configuration is performed using the device tree mechanism that provides a hardware description of the HSEM peripheral, used by the STM32 HSEM Linux driver.
2. DT bindings documentation[edit | edit source]
The HSEM internal peripheral is represented by:
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 HSEM peripheral node is located in stm32mp151.dtsi [3] file.
hsem: hwspinlock@4c000000 { compatible = "st,stm32-hwspinlock"; #hwlock-cells = <2>; reg = <0x4c000000 0x400>; clocks = <&rcc HSEM>; clock-names = "hsem"; };
|
This device tree part is related to STM32 microprocessors. It must be kept as is, without being modified by the end-user. |
3.2. DT configuration (board level)[edit | edit source]
No board device tree configuration is required.
3.3. DT configuration examples[edit | edit source]
Below is an example of an HSEM user device:
pinctrl: pin-controller@50002000 {
...
hwlocks = <&hsem 0 1>;
...
The pincrl device uses the semaphore ID 0 (first number) and this semaphore can be shared (second number = 1, meaning shared usage), which means it is used by another device.
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]
Refer to the following links for additional information:
- ↑ Documentation/devicetree/bindings/hwlock/hwlock.txt , Generic hwlock device tree bindings
- ↑ Documentation/devicetree/bindings/hwlock/st,stm32-hwspinlock.yaml , STM32 Hardware Spinlock device tree bindings
- ↑ arch/arm/boot/dts/st/stm32mp151.dtsi