From: sashiko-bot@kernel.org
To: "Alexander Stein" <alexander.stein@ew.tq-group.com>
Cc: devicetree@vger.kernel.org, robh@kernel.org, Frank.Li@kernel.org,
imx@lists.linux.dev, conor+dt@kernel.org,
wsa+renesas@sang-engineering.com
Subject: Re: [PATCH v4 4/4] arm64: dts: freescale: Add dual-channel LVDS overlay for TQMa8MPxS
Date: Wed, 03 Jun 2026 10:23:31 +0000 [thread overview]
Message-ID: <20260603102331.C2F881F00893@smtp.kernel.org> (raw)
In-Reply-To: <20260603093621.2504490-4-alexander.stein@ew.tq-group.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] Missing deletion of the original 'port' node when adding 'ports' to 'panel_lvds0', causing DT schema violations and broken bidirectional links.
--
commit f3c8e1f6a8535dc5df481fba1097371fa89698ff
Author: Alexander Stein <alexander.stein@ew.tq-group.com>
arm64: dts: freescale: Add dual-channel LVDS overlay for TQMa8MPxS
This adds an overlay for the supported LVDS display AUO G133HAN01.
Configure the video PLL frequency to exactly match typical pixel clock of
141.200 MHz.
> diff --git a/arch/arm64/boot/dts/freescale/imx8mp-tqma8mpqs-mb-smarc-2-lvds-g133han01.dtso b/arch/arm64/boot/dts/freescale/imx8mp-tqma8mpqs-mb-smarc-2-lvds-g133han01.dtso
> new file mode 100644
> index 0000000000000..9595cf4d43cd0
> --- /dev/null
> +++ b/arch/arm64/boot/dts/freescale/imx8mp-tqma8mpqs-mb-smarc-2-lvds-g133han01.dtso
[ ... ]
> +&panel_lvds0 {
> + compatible = "auo,g133han01";
> + status = "okay";
> +
> + ports {
[Severity: Low]
Does this overlay need to explicitly remove the original port node using
/delete-node/ port;?
The base device tree defines panel_lvds0 with a single port node. Because
device tree overlays merge rather than overwrite nodes, the original port
node remains in the merged tree alongside this new ports node.
This violates the OF graph device tree schema which enforces
oneOf: [port, ports]. It also breaks the OF graph bidirectional link
requirement, as the old endpoint points to ldb_lvds_ch0, but ldb_lvds_ch0
no longer points back to it, triggering a remote-endpoint is not
bidirectional error in dtbs_check.
> + #address-cells = <1>;
> + #size-cells = <0>;
> +
> + port@0 {
> + reg = <0>;
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260603093621.2504490-1-alexander.stein@ew.tq-group.com?part=4
next prev parent reply other threads:[~2026-06-03 10:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-03 9:36 [PATCH v4 1/4] dt-bindings: arm: fsl: add TQMa8MPxS board Alexander Stein
2026-06-03 9:36 ` [PATCH v4 2/4] arm64: dts: freescale: add initial device tree for TQMa8MPQS with i.MX8MP Alexander Stein
2026-06-03 10:05 ` sashiko-bot
2026-06-03 17:41 ` Frank Li
2026-06-03 9:36 ` [PATCH v4 3/4] arm64: dts: freescale: add LVDS overlays for TQMa8MPxS Alexander Stein
2026-06-03 9:36 ` [PATCH v4 4/4] arm64: dts: freescale: Add dual-channel LVDS overlay " Alexander Stein
2026-06-03 10:23 ` sashiko-bot [this message]
2026-06-03 12:56 ` [PATCH v4 1/4] dt-bindings: arm: fsl: add TQMa8MPxS board Wolfram Sang
2026-06-03 13:05 ` Geert Uytterhoeven
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=20260603102331.C2F881F00893@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=Frank.Li@kernel.org \
--cc=alexander.stein@ew.tq-group.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=imx@lists.linux.dev \
--cc=robh@kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
--cc=wsa+renesas@sang-engineering.com \
/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