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 v2 3/5] arm64: dts: imx8qxp: Add MIPI-LVDS combo subsystems
Date: Wed, 14 Oct 2026 11:25:36 +0200	[thread overview]
Message-ID: <5262517.31r3eYUQgx@steina-w> (raw)
In-Reply-To: <sashiko-outbox-170941@kernel.org>

Am Mittwoch, 14. Oktober 2026, 09:29:25 Mitteleuropäische Sommerzeit schrieb sashiko-bot@kernel.org:
> Thank you for your contribution! Sashiko AI review found 2 potential issue(s) to consider:
> - [Low] dts: simple-pm-bus node specifies address cells but lacks memory-mapped children
> - [Low] dts: irqsteer evades DT binding by omitting SoC-specific compatible and power-domains
> --
> 
> commit bf42b82f7a33a44c5f4805e13c2e5eb848f29919
> Author: Liu Ying <victor.liu@nxp.com>
> 
> arm64: dts: imx8qxp: Add MIPI-LVDS combo subsystems
> 
> The MIPI-LVDS combo subsystems are peripherals of pixel link MSI bus in
> i.MX8qxp display controller subsystem. Add the MIPI-LVDS combo subsystems.
> 
> > diff --git a/arch/arm64/boot/dts/freescale/imx8qxp-ss-mipi-lvds.dtsi b/arch/arm64/boot/dts/freescale/imx8qxp-ss-mipi-lvds.dtsi
> > new file mode 100644
> > index 0000000000000..67f5392cfc803
> > --- /dev/null
> > +++ b/arch/arm64/boot/dts/freescale/imx8qxp-ss-mipi-lvds.dtsi
> 
> [ ... ]
> 
> > +&dc0_pl_msi_bus {
> > +	mipi_lvds_0_irqsteer: interrupt-controller@56220000 {
> > +		compatible = "fsl,imx-irqsteer";
> 
> [Severity: Low]
> Does this node omit the required SoC-specific compatible and power domains?
> 
> The fsl,irqsteer.yaml DT binding schema strictly requires the power-domains
> property when the fsl,imx8qxp-irqsteer compatible is used. By only specifying
> the generic fsl,imx-irqsteer compatible, this evades the schema's
> enforcement.
> 
> Failing to model the power domain directly on the interrupt controller violates
> the hardware description conventions. The equivalent node in imx8-ss-mipi0.dtsi
> correctly included both the SoC-specific compatible and the power-domains
> property.

That's correct. Proper compatible and power-domain will be added in v3.

> 
> > +		reg = <0x56220000 0x1000>;
> > +		interrupts = <GIC_SPI 59 IRQ_TYPE_LEVEL_HIGH>;
> 
> [ ... ]
> 
> > +	mipi_lvds_0_csr: bus@56221000 {
> > +		compatible = "simple-pm-bus", "syscon";
> > +		reg = <0x56221000 0x1000>;
> > +		clocks = <&mipi_lvds_0_di_mipi_lvds_regs_lpcg IMX_LPCG_CLK_4>;
> > +		clock-names = "ipg";
> > +		#address-cells = <1>;
> > +		#size-cells = <1>;
> > +		ranges;
> > +
> > +		mipi_lvds_0_pxl2dpi: pxl2dpi {
> 
> [Severity: Low]
> Is this simple-pm-bus configuration correct given that it lacks memory-mapped
> children?
> 
> The mipi_lvds_0_csr node specifies #address-cells = <1> and #size-cells = <1>,
> but its children (like pxl2dpi and ldb) do not possess reg properties. The
> device tree compiler (dtc) expects children of simple-pm-bus or simple-bus
> nodes to have reg properties if #address-cells is greater than 0.
> 
> This will trigger simple_bus_reg and avoid_unnecessary_addr_size dtc warnings
> during the build and violates standard DT architecture patterns.

I think that is not correct. mipi_lvds_0_csr is a simple-pm-bus as it needs
clocks and power-domains. AFAIK as it is not a simple-bus the
avoid_unnecessary_addr_size warning is not applicable.

> 
> > +			compatible = "fsl,imx8qxp-pxl2dpi";
> > +			fsl,sc-resource = <IMX_SC_R_MIPI_0>;
> 
> [ ... ]
> 
> > +	mipi_lvds_1_irqsteer: interrupt-controller@56240000 {
> > +		compatible = "fsl,imx-irqsteer";
> 
> [Severity: Low]
> Like the mipi_lvds_0_irqsteer node above, does this irqsteer node also omit
> the fsl,imx8qxp-irqsteer SoC-specific compatible and the power-domains
> property?

That's correct. Proper compatible and power-domain will be added in v3.

Best regards
Alexander

> > +		reg = <0x56240000 0x1000>;
> > +		interrupts = <GIC_SPI 60 IRQ_TYPE_LEVEL_HIGH>;
> 
> 


-- 
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-14  9:51 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-14  7:16 [PATCH v2 0/5] LVDS support for TQMa8Xx Alexander Stein
2026-10-14  7:16 ` [PATCH v2 1/5] dt-bindings: firmware: imx: Add SCU controlled display pixel link nodes Alexander Stein
2026-10-14  7:24   ` sashiko-bot
2026-10-14  9:39     ` Alexander Stein
2026-10-14  7:16 ` [PATCH v2 2/5] arm64: dts: imx8qxp: Add display controller subsystem Alexander Stein
2026-10-14 13:55   ` Frank Li
2026-10-14  7:16 ` [PATCH v2 3/5] arm64: dts: imx8qxp: Add MIPI-LVDS combo subsystems Alexander Stein
2026-10-14  7:29   ` sashiko-bot
2026-10-14  9:25     ` Alexander Stein [this message]
2026-10-14 14:01   ` Frank Li
2026-10-14  7:16 ` [PATCH v2 4/5] arm64: dts: freescale: Add LVDS overlays for TQMa8Xx Alexander Stein
2026-10-14  7:16 ` [PATCH v2 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=5262517.31r3eYUQgx@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