HASH device tree configuration




1 Article purpose[edit]

This article explains how to configure the HASH internal peripheral when it is assigned to the Linux® OS. In that case, it is controlled by the Crypto framework.

The configuration is performed using the device tree mechanism that provides a hardware description of the HASH peripheral, used by the STM32 HASH Linux driver.

2 DT bindings documentation[edit]

The HASH is represented by the STM32 HASH device tree bindings[1]

3 DT configuration[edit]

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]

The HASH node is declared in stm32mp157c.dtsi[2]. It describes the hardware register address, clock, interrupt, reset and dma.

 hash1: hash@54002000 {                                                         Comments
 	compatible = "st,stm32f756-hash";
 	reg = <0x54002000 0x400>;                                               --> Register location and length
 	interrupts = <GIC_SPI 80 IRQ_TYPE_LEVEL_HIGH>;                          --> The interrupt number used
 	clocks = <&rcc HASH1>;
 	resets = <&rcc HASH1_R>;
 	dmas = <&mdma1 31 0x10 0x1000A02 0x0 0x0 0x0>;                          --> DMA specifiers[3]
 	dma-names = "in";
 	dma-maxburst = <2>;
 	status = "disabled";
 };
Warning.png 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]

This part is used to enable the HASH used on a board which is done by setting the status property to okay.

3.3 DT configuration examples[edit]

&hash1 {
	status = "okay";
};

4 How to configure the DT using STM32CubeMX[edit]

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]

Please refer to the following links for additional information:

Operating System

Device Tree

Generic Interrupt Controller

Serial Peripheral Interface

Direct Memory Access

Attachments

Discussions