From: Olivier Moysan <olivier.moysan@foss.st.com>
To: Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Maxime Coquelin <mcoquelin.stm32@gmail.com>,
Alexandre Torgue <alexandre.torgue@foss.st.com>
Cc: Olivier Moysan <olivier.moysan@foss.st.com>,
<devicetree@vger.kernel.org>,
<linux-stm32@st-md-mailman.stormreply.com>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>
Subject: [PATCH 03/10] ARM: dts: stm32: add vrefint support to adc2 on stm32mp15
Date: Thu, 12 Jan 2023 11:44:38 +0100 [thread overview]
Message-ID: <20230112104446.1140551-4-olivier.moysan@foss.st.com> (raw)
In-Reply-To: <20230112104446.1140551-1-olivier.moysan@foss.st.com>
Set STM32 ADC2 as a consumer of BSEC on STM32MP15, to retrieve
vrefint calibration data savec in OTP.
During the calibration process vrefp is set to 3.3V and the data
acquired is saved to the OTP. This data is used by the ADC driver
to calculated the actual value of vrefp according to the formula:
vrefp = 3.3 x vrefint_cal / vrefint_data
The vrefint channel provides the actual value of vrefp,
which can be used to correct ADC acquisition data.
Signed-off-by: Olivier Moysan <olivier.moysan@foss.st.com>
---
arch/arm/boot/dts/stm32mp151.dtsi | 2 ++
1 file changed, 2 insertions(+)
diff --git a/arch/arm/boot/dts/stm32mp151.dtsi b/arch/arm/boot/dts/stm32mp151.dtsi
index eec5e9992bff..472fc3b94f33 100644
--- a/arch/arm/boot/dts/stm32mp151.dtsi
+++ b/arch/arm/boot/dts/stm32mp151.dtsi
@@ -1113,6 +1113,8 @@ adc2: adc@100 {
interrupts = <1>;
dmas = <&dmamux1 10 0x400 0x01>;
dma-names = "rx";
+ nvmem-cells = <&vrefint>;
+ nvmem-cell-names = "vrefint";
status = "disabled";
channel@13 {
reg = <13>;
--
2.25.1
next prev parent reply other threads:[~2023-01-12 10:55 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-12 10:44 [PATCH 00/10] ARM: dts: stm32: add adc internal channels on stm32mp15 Olivier Moysan
2023-01-12 10:44 ` [PATCH 01/10] ARM: dts: stm32: add adc internal channels to stm32mp15 Olivier Moysan
2023-01-12 10:44 ` [PATCH 02/10] ARM: dts: stm32: add vrefint calibration on stm32mp15 Olivier Moysan
2023-01-12 11:46 ` Krzysztof Kozlowski
2023-01-12 10:44 ` Olivier Moysan [this message]
2023-01-12 10:44 ` [PATCH 04/10] ARM: dts: stm32: enable adc on stm32mp15xx-dkx boards Olivier Moysan
2023-01-12 10:44 ` [PATCH 05/10] ARM: dts: stm32: adopt generic iio bindings for adc channels on stm32mp157c-ed1 Olivier Moysan
2023-01-12 10:44 ` [PATCH 06/10] ARM: dts: stm32: adopt generic iio bindings for adc channels on avenger96 Olivier Moysan
2023-01-12 14:28 ` Marek Vasut
2023-01-12 10:44 ` [PATCH 07/10] ARM: dts: stm32: adopt generic iio bindings for adc channels on emstamp-argon Olivier Moysan
2023-01-12 10:44 ` [PATCH 08/10] ARM: dts: stm32: adopt generic iio bindings for adc channels on dhcom Olivier Moysan
2023-01-12 10:44 ` [PATCH 09/10] ARM: dts: stm32: adopt generic iio bindings for adc channels on dhcor-drc Olivier Moysan
2023-01-12 10:44 ` [PATCH 10/10] ARM: dts: stm32: adopt generic iio bindings for adc channels on dhcor-testbench Olivier Moysan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20230112104446.1140551-4-olivier.moysan@foss.st.com \
--to=olivier.moysan@foss.st.com \
--cc=alexandre.torgue@foss.st.com \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=mcoquelin.stm32@gmail.com \
--cc=robh+dt@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).