Last edited 10 months ago

ADC device tree configuration

Applicable for STM32MP13x lines, STM32MP15x lines

1 Article purpose[edit source]

The purpose of this article is to explain how to configure the analog-to-digital converter (ADC)[1] when the peripheral is assigned to Linux® OS, and in particular:

  • how to configure the ADC peripheral
  • how to configure the board, e.g. the ADC voltage reference regulator, channels, pins and sampling time.

The configuration is performed using the device tree mechanism[2].

It is used by the ADC Linux driver that registers relevant information in IIO framework, such as IIO devices, channels and voltage scale for each ADC.

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.

2 DT bindings documentation[edit source]

STM32 ADC device tree bindings[3] describe all the required and optional functions.

3 DT configuration[edit source]

This hardware description is a combination of STM32 microprocessor and board device tree files. See Device tree for more 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.

ADC common resourcesADC common resourcesADC common resourcesADC private resourcesADC private resourcesRegulatorPinctrlHow to setup TIM or LPTIM triggers
ADC DT configuration

3.1 DT configuration (STM32 level)[edit source]

On STM32MP13x lines More info.png The ADC nodes are declared in stm32mp131.dtsi[4] and in stm32mp133.dtsi[5].
On STM32MP15x lines More info.png The ADC nodes are declared in stm32mp151.dtsi[6].

  • DT root node ('adc') describes the ADC hardware block parameters such as register areas, clocks and interrupts.
  • DT child nodes ('adc1' and/or 'adc2') describe ADC1 and ADC2 independently.
adc: adc@address {
	compatible = "st,stm32mp1-adc-core";
	...                                      /* common resources in 'adc' root node. */
	adc1: adc@0 {
		compatible = "st,stm32mp1-adc";
		...                              /* private resources in 'adc1' child node. */
	};
	adc2: adc@100 {
		compatible = "st,stm32mp1-adc";
		...                              /* private resources in 'adc2' child node. */
	};
};
Warning white.png Warning
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 source]

Follow the sequences described in the below chapters to configure and enable the ADC on your board.

3.2.1 Common resources for all ADCs[edit source]

The DT root node ('adc') must be filled in:

  • Enable the ADC block by setting status = "okay".
  • Configure the pins in use via pinctrl, through pinctrl-0 and pinctrl-names.
  • Configure the analog supply voltage regulator[7] by setting vdda-supply = <&your_vdda_regulator>.
  • Configure the analog reference voltage regulator[7] by setting vref-supply = <&your_vref_regulator>.
Info white.png Information
The ADC can use the internal VREFBUF[8] or any other external regulator[7] wired to VREF+ pin.

The DT child nodes ('adc1' or 'adc2') must be filled in with ADC block properties and channels properties.

3.2.2 Resources dedicated to an ADC block[edit source]

3.2.2.1 ADC block properties[edit source]
  • Enable ADC block by setting status = "okay".
  • Set ADC block resolution by setting assigned-resolution-bits = <12> (optional).
3.2.2.2 Channel properties (for ecosystem release ≥ v3.1.0 )[edit source]

Each channel is described by a dedicated DT sub node, filled in with properties documented in Generic IIO bindings for ADC channels[9].

  • Define channel index 'x' by setting reg = <x>.
  • Identifiy the channel by setting its name with label = "xxx" (optional).
    Reserved label "vrefint", "vddcore" and "vbat" allow to identify internal channels.
  • Enable differential channel pair (<vinp vinn>) by setting diff-channels = <x y> (optional).
  • Set the minimum sampling time st,min-sample-time-nsecs by setting st,min-sample-time-nsecs = <10000> (optional).
3.2.2.3 Legacy channel properties (for ecosystem release ≤ v3.0.0 )[edit source]

These properties are deprecated, but are still supported for backward compatibility. The properties introduced in v3.1.0 should be used instead, whenever possible.

  • Enable single-ended channel(s) (<vinp...>) by setting st,adc-channels = <0 1 2...>.
  • Enable differential channel(s) pairs (<vinp vinn>, ...) by setting st,adc-diff-channels = <1 0>, <2 6>, ....
  • Set the minimum sampling time [10] for each or all channels by setting st,min-sample-time-nsecs = <10000> (optional).

3.3 DT configuration example[edit source]

The example below shows how to configure ADC1:

  • Input pin: use Pinctrl device tree configuration to configure PF12 as analog input.
  • Analog supply: it is provided by one of the PMIC LDO regulators.
  • Voltage reference: it is provided by the VREFBUF internal regulator.
  • Input channel: configure ADC1_IN6 (e.g on PF12).
  • Sampling time: the minimum sampling time is 10 µs.
# part of pin-controller dt node
adc1_in6_pins_a: adc1-in6 {
	pins {
		pinmux = <STM32_PINMUX('F', 12, ANALOG)>; /* configure 'PF12' as ANALOG */
	};
};

3.3.1 For ecosystem release ≥ v3.1.0[edit source]

&adc {
	/* ADC1 & ADC2 common resources */
	pinctrl-names = "default";
	pinctrl-0 = <&adc1_in6_pins_a>;              /* Use PF12 pin as ANALOG */
	vdda-supply = <&vdda>;                       /* Example to supply vdda pin by using a PMIC regulator
	vref-supply = <&vrefbuf>;                    /* Example to use VREFBUF (It needs to be enabled as well) */
	status = "okay";                             /* Enable ADC12 block */
	adc1: adc@0 {
		/* private resources for ADC1 */
		status = "okay";                     /* Enable ADC1 */
		channel@6 {
			reg = <6>;               /* ADC1 in6 channel is used */
			st,min-sample-time-nsec = <10000>;  /* 10µs sampling time */
		};
	};
	adc2: adc@100 {
		/* private resources for ADC2 */
		...
	};
};

3.3.2 For ecosystem release ≤ v3.0.0[edit source]

&adc {
	/* ADC1 & ADC2 common resources */
	pinctrl-names = "default";
	pinctrl-0 = <&adc1_in6_pins_a>;              /* Use PF12 pin as ANALOG */
	vdda-supply = <&vdda>;                       /* Example to supply vdda pin by using a PMIC regulator
	vref-supply = <&vrefbuf>;                    /* Example to use VREFBUF (It needs to be enabled as well) */
	status = "okay";                             /* Enable ADC12 block */
	adc1: adc@0 {
		/* private resources for ADC1 */
		st,adc-channels = <6>;               /* ADC1 in6 channel is used */
		st,min-sample-time-nsecs = <10000>;  /* 10µs sampling time */
		status = "okay";                     /* Enable ADC1 */
	};
	adc2: adc@100 {
		/* private resources for ADC2 */
		...
	};
};

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]

For additional information, refer to the following links: