From: Shawn Guo <shawnguo2@yeah.net>
To: Frank Li <Frank.Li@nxp.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,
David Lechner <dlechner@baylibre.com>
Subject: Re: [PATCH 0/2] dts: imx: cleanup warning cause by fsl,mpl3115
Date: Tue, 11 Nov 2025 15:32:37 +0800 [thread overview]
Message-ID: <aRLmlQHs5tF2lBb7@dragon> (raw)
In-Reply-To: <20251022-fsl-mpl3115-v1-0-93187d095efc@nxp.com>
On Wed, Oct 22, 2025 at 04:43:20PM -0400, Frank Li wrote:
> After commit f11e4374b(dt-bindings: iio: pressure: add binding for mpl3115 )
> vdd-supply and vddio-supply is required properties.
>
> thread:
> https://lore.kernel.org/imx/0e00bb14-19c7-493a-9629-354bac3a273e@baylibre.com/T/#t
> not prefer change both to optional. So update dts to fix CHECK_DTB
> warnings for both ARM and ARM64 platform.
>
> Signed-off-by: Frank Li <Frank.Li@nxp.com>
> ---
> Frank Li (2):
> arm64: dts: imx8: add vdd-supply and vddio-supply for fsl,mpl3115
> ARM: dts: imx: add vdd-supply and vddio-supply for fsl,mpl3115
Applied both, thanks!
prev parent reply other threads:[~2025-11-11 7:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-22 20:43 [PATCH 0/2] dts: imx: cleanup warning cause by fsl,mpl3115 Frank Li
2025-10-22 20:43 ` [PATCH 1/2] arm64: dts: imx8: add vdd-supply and vddio-supply for fsl,mpl3115 Frank Li
2025-10-22 20:43 ` [PATCH 2/2] ARM: dts: imx: " Frank Li
2025-10-23 13:51 ` [PATCH 0/2] dts: imx: cleanup warning cause by fsl,mpl3115 Rob Herring (Arm)
2025-11-11 7:32 ` Shawn Guo [this message]
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=aRLmlQHs5tF2lBb7@dragon \
--to=shawnguo2@yeah.net \
--cc=Frank.Li@nxp.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dlechner@baylibre.com \
--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=robh@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@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).