From: Marek Vasut <marek.vasut@mailbox.org>
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>,
Christoph Niedermaier <cniedermaier@dh-electronics.com>,
devicetree@vger.kernel.org, imx@lists.linux.dev,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, kernel@dh-electronics.com
Subject: Re: [PATCH 1/8] ARM: dts: imx: add power-supply for lcd panel
Date: Wed, 15 Oct 2025 01:29:41 +0200 [thread overview]
Message-ID: <24287186-1b97-434f-929f-a391a2fd9784@mailbox.org> (raw)
In-Reply-To: <aO7IOCdq013j3rre@lizhi-Precision-Tower-5810>
On 10/15/25 12:01 AM, Frank Li wrote:
> On Tue, Oct 14, 2025 at 10:46:56PM +0200, Marek Vasut wrote:
>> On 10/14/25 9:38 PM, Frank Li wrote:
>>> Add power-supply for lcd panel to fix below CHECK_DTBS warnings:
>>> arch/arm/boot/dts/nxp/imx/imx6q-evi.dtb: panel (sharp,lq101k1ly04): 'power-supply' is a required property
>>
>> ...
>>
>>> diff --git a/arch/arm/boot/dts/nxp/imx/imx6ull-dhcom-pdk2.dts b/arch/arm/boot/dts/nxp/imx/imx6ull-dhcom-pdk2.dts
>>> index b29713831a74489e8cc0e651c18a40d85f9f9113..04e570d76e42cd67a38e0f3b2301598f712e6bd4 100644
>>> --- a/arch/arm/boot/dts/nxp/imx/imx6ull-dhcom-pdk2.dts
>>> +++ b/arch/arm/boot/dts/nxp/imx/imx6ull-dhcom-pdk2.dts
>>> @@ -199,7 +199,7 @@ touchscreen@38 {
>>> reg = <0x38>;
>>> interrupt-parent = <&gpio5>;
>>> interrupts = <4 IRQ_TYPE_EDGE_FALLING>; /* GPIO E */
>>> - power-supply = <®_panel_3v3>;
>>> + vcc-supply = <®_panel_3v3>;
>> This looks like a different kind of change ?
>
> It is touchscreen, It needs sperate patch fix it to align
> edt-ft5x06.yaml.
Can you please split this fix from the series, include the error message
you get from DT check, and possibly add Fixes: tag ?
Thank you
next prev parent reply other threads:[~2025-10-14 23:29 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-14 19:38 [PATCH 0/8] ARM: dtb: imx6 DTB WARNING cleanup 2 Frank Li
2025-10-14 19:38 ` [PATCH 1/8] ARM: dts: imx: add power-supply for lcd panel Frank Li
2025-10-14 20:46 ` Marek Vasut
2025-10-14 22:01 ` Frank Li
2025-10-14 23:29 ` Marek Vasut [this message]
2025-10-14 19:38 ` [PATCH 2/8] ARM: dts: imx: remove redundant linux,phandle Frank Li
2025-10-14 19:38 ` [PATCH 3/8] ARM: dts: imx6qdl-skov-cpu fix typo interrupt Frank Li
2025-10-14 19:38 ` [PATCH 4/8] ARM: dts: imx6q-cm-fx6.dts: add supplies for wm8731 Frank Li
2025-10-14 19:38 ` [PATCH 5/8] ARM: dts: Add bus type for parallel ov5640 Frank Li
2025-10-14 19:38 ` [PATCH 6/8] ARM: dts: add device_type for memory node Frank Li
2025-10-14 19:38 ` [PATCH 7/8] ARM: dts: remove undocumented clock-names for ov5642 Frank Li
2025-10-14 19:38 ` [PATCH 8/8] ARM: dts: imx7ulp: remove bias-pull-up Frank Li
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=24287186-1b97-434f-929f-a391a2fd9784@mailbox.org \
--to=marek.vasut@mailbox.org \
--cc=Frank.li@nxp.com \
--cc=cniedermaier@dh-electronics.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=imx@lists.linux.dev \
--cc=kernel@dh-electronics.com \
--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).