CRYP device tree configuration
目录
Article purpose
The purpose of this article is to explain how to configure the CRYP[1] when the peripheral is assigned to Linux® OS.
The configuration is performed using the device tree mechanism[2].
The Device tree provides a hardware description of the CRYP[1], used by STM32 CRYP Linux driver.
If the peripheral is assigned to another execution context, refer to How to assign an internal peripheral to a runtime context article for guidelines on peripheral assignment and configuration.
DT configuration
This hardware description is a combination of STM32 microprocessor and board device tree files. See Device tree for explanations on device tree file split.
The STM32CubeMX can be used to generate the board device tree. Refer to #How_to_configure_the_DT_using_STM32CubeMX for more details.
DT configuration (STM32 level)
The CRYP node is declared in stm32mp157c.dtsi[4]. It provides the hardware registers base address, clock, interrupt and reset.
cryp1: cryp@54001000 {
compatible = "st,stm32mp1-cryp";
reg = <0x54001000 0x400>;
interrupts = <GIC_SPI 79 IRQ_TYPE_LEVEL_HIGH>;
clocks = <&rcc CRYP1>;
resets = <&rcc CRYP1_R>;
status = "disabled";
};
 |
This device tree part is related to STM32 microprocessors. It should be kept as is, without being modified by the end-user. |
DT configuration (board level)
This part is used to enable the CRYP used on a board. This is done by setting the status property to okay.
DT configuration examples
&cryp1 {
status = "okay";
};
How to configure the DT using STM32CubeMX
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.
References
Please refer to the following links for additional information:
<securetransclude src="ProtectedTemplate:PublicationRequestId" params="8896 | 2018-09-21 | BrunoB"></securetransclude> <securetransclude src="ProtectedTemplate:ArticleBasedOnModel" params="Peripheral or framework device tree configuration model"></securetransclude> <securetransclude src="ProtectedTemplate:ReviewsComments" params="JCT 1840: alignment needed with the last version of the model<br>"></securetransclude>{{#set:Has reviews comments=true}}
