From: Olivier Moysan <olivier.moysan@foss.st.com>
To: Alexandre Torgue <alexandre.torgue@foss.st.com>,
Fabrice Gasnier <fabrice.gasnier@st.com>,
Jonathan Cameron <jic23@kernel.org>,
"Lars-Peter Clausen" <lars@metafoo.de>,
Maxime Coquelin <mcoquelin.stm32@gmail.com>,
Olivier Moysan <olivier.moysan@foss.st.com>,
Rob Herring <robh+dt@kernel.org>
Cc: <devicetree@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-iio@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<linux-stm32@st-md-mailman.stormreply.com>
Subject: [PATCH v4 2/7] dt-bindings: iio: stm32-adc: add nvmem support for vrefint internal channel
Date: Mon, 11 Oct 2021 17:57:12 +0200 [thread overview]
Message-ID: <20211011155717.1594-3-olivier.moysan@foss.st.com> (raw)
In-Reply-To: <20211011155717.1594-1-olivier.moysan@foss.st.com>
Add support of nvmem. This allows to retrieve calibration data from OTP
for vrefint internal channel.
Signed-off-by: Olivier Moysan <olivier.moysan@foss.st.com>
Reviewed-by: Fabrice Gasnier <fabrice.gasnier@foss.st.com>
Acked-by: Rob Herring <robh@kernel.org>
---
.../devicetree/bindings/iio/adc/st,stm32-adc.yaml | 8 ++++++++
1 file changed, 8 insertions(+)
diff --git a/Documentation/devicetree/bindings/iio/adc/st,stm32-adc.yaml b/Documentation/devicetree/bindings/iio/adc/st,stm32-adc.yaml
index ece1864fdcd9..7dfdddee8de0 100644
--- a/Documentation/devicetree/bindings/iio/adc/st,stm32-adc.yaml
+++ b/Documentation/devicetree/bindings/iio/adc/st,stm32-adc.yaml
@@ -301,6 +301,14 @@ patternProperties:
$ref: /schemas/types.yaml#/definitions/uint32-array
deprecated: true
+ nvmem-cells:
+ items:
+ - description: Phandle to the calibration vrefint data provided by otp
+
+ nvmem-cell-names:
+ items:
+ - const: vrefint
+
patternProperties:
"^channel@([0-9]|1[0-9])$":
type: object
--
2.17.1
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2021-10-11 16:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-11 15:57 [PATCH v4 0/7] iio: adc: stm32-adc: add internal channels support Olivier Moysan
2021-10-11 15:57 ` [PATCH v4 1/7] dt-bindings: iio: stm32-adc: add generic channel binding Olivier Moysan
2021-10-11 23:13 ` Rob Herring
2021-10-11 15:57 ` Olivier Moysan [this message]
2021-10-11 15:57 ` [PATCH v4 3/7] iio: adc: stm32-adc: split channel init into several routines Olivier Moysan
2021-10-11 15:57 ` [PATCH v4 4/7] iio: adc: stm32-adc: add support of generic channels binding Olivier Moysan
2021-10-11 15:57 ` [PATCH v4 5/7] iio: adc: stm32-adc: add support of internal channels Olivier Moysan
2021-10-12 9:42 ` [Linux-stm32] " Fabrice Gasnier
2021-10-12 13:19 [PATCH v4 0/7] iio: adc: stm32-adc: add internal channels support Olivier Moysan
2021-10-12 13:19 ` [PATCH v4 2/7] dt-bindings: iio: stm32-adc: add nvmem support for vrefint internal channel 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=20211011155717.1594-3-olivier.moysan@foss.st.com \
--to=olivier.moysan@foss.st.com \
--cc=alexandre.torgue@foss.st.com \
--cc=devicetree@vger.kernel.org \
--cc=fabrice.gasnier@st.com \
--cc=jic23@kernel.org \
--cc=lars@metafoo.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-iio@vger.kernel.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).