1. Article purpose[edit source]
This article explains how to configure the VENC [1] when the peripheral is assigned to the Linux® OS.
The configuration is performed using the device tree mechanism [2].
The Device tree provides a hardware description of the VENC [1] used by the STM32 VENC Linux driver.
2. DT bindings documentation[edit source]
The VENC is represented by the STM32 VENC device tree bindings [3].
3. DT configuration[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/SoC level)[edit source]
The VENC node is located in the device tree file for the software components, supporting the peripheral and listed in the above DT bindings documentation paragraph.
For STM32MP25x lines 
, the VENC device tree node is declared in stm32mp255.dtsi [4].
...
soc@0 {
rifsc: rifsc@42080000 {
...
venc: venc@480e0000 {
compatible = "st,stm32mp25-venc";
reg = <0x480e0000 0x800>;
reset-names = "venc-rst";
resets = <&rcc VENC_R>;
interrupt-names = "venc";
interrupts = <GIC_SPI 167 IRQ_TYPE_LEVEL_HIGH>;
clock-names = "venc-clk";
clocks = <&rcc CK_BUS_VENC>;
feature-domains = <&rifsc STM32MP25_RIFSC_VENC_ID>;
power-domains = <&CLUSTER_PD>;
};
...
3.2. DT configuration (board level)[edit source]
For STM32MP25x lines , the STM32 VENC is already enabled by default in stm32mp255.dtsi [4] so there is no need to enable it at board level.
4. How to configure the DT using STM32CubeMX[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 source]
Please refer to the following links for additional information: