From: Peng Fan <peng.fan@oss.nxp.com>
To: Primoz Fiser <primoz.fiser@norik.com>
Cc: Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Shawn Guo <shawnguo@kernel.org>,
Sascha Hauer <s.hauer@pengutronix.de>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
Fabio Estevam <festevam@gmail.com>,
devicetree@vger.kernel.org, imx@lists.linux.dev,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, upstream@lists.phytec.de
Subject: Re: [PATCH] arm64: dts: freescale: imx93-phyboard-nash: Move ADC vref to SoM
Date: Thu, 5 Jun 2025 10:53:25 +0800 [thread overview]
Message-ID: <20250605025325.GF29462@nxa18884-linux> (raw)
In-Reply-To: <20250602125207.2265222-1-primoz.fiser@norik.com>
On Mon, Jun 02, 2025 at 02:52:07PM +0200, Primoz Fiser wrote:
>Move configuration for ADC voltage reference from board DTS to a SoM
>include file. The SoC ADC reference voltage is connected to a "VDDA_1V8"
>voltage node and supplied by the PMIC's BUCK5 regulator. The reference
>voltage is thus defined by the SoM and cannot be changed by the carrier
>board design and as such belongs into the SoM include file.
>
>Moreover, with this in place, customers designing own carrier boards can
>simply include imx93-phycore-som.dtsi and enable adc1 in their own DTS
>without the need to define dummy ADC vref regulator themselves anymore.
>
>Signed-off-by: Primoz Fiser <primoz.fiser@norik.com>
Reviewed-by: Peng Fan <peng.fan@nxp.com>
next prev parent reply other threads:[~2025-06-05 1:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-02 12:52 [PATCH] arm64: dts: freescale: imx93-phyboard-nash: Move ADC vref to SoM Primoz Fiser
2025-06-05 2:53 ` Peng Fan [this message]
2025-07-01 13:05 ` Shawn Guo
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=20250605025325.GF29462@nxa18884-linux \
--to=peng.fan@oss.nxp.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=imx@lists.linux.dev \
--cc=kernel@pengutronix.de \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=primoz.fiser@norik.com \
--cc=robh@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@kernel.org \
--cc=upstream@lists.phytec.de \
/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).