Devicetree
 help / color / mirror / Atom feed
From: Alexander Stein <alexander.stein@ew.tq-group.com>
To: sashiko-reviews@lists.linux.dev
Cc: imx@lists.linux.dev, devicetree@vger.kernel.org, robh@kernel.org,
	conor+dt@kernel.org, Frank.Li@kernel.org
Subject: Re: [PATCH 4/5] arm64: dts: freescale: Add LVDS overlays for TQMa8Xx
Date: Tue, 13 Oct 2026 15:03:31 +0200	[thread overview]
Message-ID: <14085313.O9o76ZdvQC@steina-w> (raw)
In-Reply-To: <sashiko-outbox-169626@kernel.org>

Am Dienstag, 13. Oktober 2026, 13:28:27 Mitteleuropäische Sommerzeit schrieb sashiko-bot@kernel.org:
> Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
> - [High] dts: unit address mismatch in dc0_pc channel@1 breaks LVDS1 hardware mapping
> --
> 
> commit 9e71d1e0ae4bcdbdae19947de71699d2eb47af70
> Author: Alexander Stein <alexander.stein@ew.tq-group.com>
> 
> arm64: dts: freescale: Add LVDS overlays for TQMa8Xx
> 
> Add overlays for the supported LVDS display tianma tm070jvhg33 on both
> LVDS0 and LVDS1 channels on connector X14 (+ control on X22).
> The corresponding display controller PLL is configured with 10x the
> pixelclock.
> 
> > diff --git a/arch/arm64/boot/dts/freescale/mba8xx-lvds1-tm070jvhg33.dtso b/arch/arm64/boot/dts/freescale/mba8xx-lvds1-tm070jvhg33.dtso
> > new file mode 100644
> > index 0000000000000..4a8ba61962725
> > --- /dev/null
> > +++ b/arch/arm64/boot/dts/freescale/mba8xx-lvds1-tm070jvhg33.dtso
> 
> [ ... ]
> 
> > +&dc0_pc {
> > +	#address-cells = <1>;
> > +	#size-cells = <0>;
> > +	status = "okay";
> > +
> > +	channel@1 {
> > +		reg = <0>;
> 
> [Severity: High]
> Does this reg value incorrectly map channel@1 to hardware index 0 instead of 1?
> 
> It appears this overrides the channel@1 child node of &dc0_pc but explicitly
> sets reg = <0>. This will incorrectly update hardware channel 0, overriding the
> base device tree which expects channel 1, and will also trigger a DTC unit
> address mismatch warning.
> 
> This can cause the LVDS1 display output to not function correctly because its
> pixel combiner channel configuration is applied to channel 0 instead of
> channel 1.

Ah, that's true. Will fix in v2.
Actually I would like to skip those "overwrites" as the value are already set
in base .dtsi. But then dtbs_check complains like this:
> /fragment@3/__overlay__/channel@1: node has a unit name, but no reg or ranges property

Best regards,
Alexander

> > +		status = "okay";
> > +	};
> > +};
> 
> 


-- 
TQ-Systems GmbH | Mühlstraße 2, Gut Delling | 82229 Seefeld, Germany
Amtsgericht München, HRB 105018
Geschäftsführer: Detlef Schneider, Rüdiger Stahl, Stefan Schneider
http://www.tq-group.com/



  reply	other threads:[~2026-10-13 13:03 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-13 11:17 [PATCH 0/5] LVDS support for TQMa8Xx Alexander Stein
2026-10-13 11:17 ` [PATCH 1/5] dt-bindings: firmware: imx: Add SCU controlled display pixel link nodes Alexander Stein
2026-10-13 11:17 ` [PATCH 2/5] arm64: dts: imx8qxp: Add display controller subsystem Alexander Stein
2026-10-13 11:29   ` sashiko-bot
2026-10-13 14:05     ` Alexander Stein
2026-10-13 11:17 ` [PATCH 3/5] arm64: dts: imx8qxp: Add MIPI-LVDS combo subsystems Alexander Stein
2026-10-13 11:17 ` [PATCH 4/5] arm64: dts: freescale: Add LVDS overlays for TQMa8Xx Alexander Stein
2026-10-13 11:28   ` sashiko-bot
2026-10-13 13:03     ` Alexander Stein [this message]
2026-10-13 11:17 ` [PATCH 5/5] arm64: dts: freescale: Add dual-channel LVDS overlay " Alexander Stein

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=14085313.O9o76ZdvQC@steina-w \
    --to=alexander.stein@ew.tq-group.com \
    --cc=Frank.Li@kernel.org \
    --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 \
    /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