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 2/5] arm64: dts: imx8qxp: Add display controller subsystem
Date: Tue, 13 Oct 2026 16:05:12 +0200 [thread overview]
Message-ID: <5866247.LvFx2qVVIh@steina-w> (raw)
In-Reply-To: <sashiko-outbox-169627@kernel.org>
Am Dienstag, 13. Oktober 2026, 13:29:55 Mitteleuropäische Sommerzeit schrieb sashiko-bot@kernel.org:
> Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
> - [Medium] arm64: dts: Missing power-domains and compatible override for dc0_irqsteer
> --
>
> commit ae70e9d2f5935bf44872ed0bd30be554653b06e0
> Author: Liu Ying <victor.liu@nxp.com>
>
> arm64: dts: imx8qxp: Add display controller subsystem
>
> Add display controller subsystem in i.MX8qxp SoC.
>
> > diff --git a/arch/arm64/boot/dts/freescale/imx8-ss-dc0.dtsi b/arch/arm64/boot/dts/freescale/imx8-ss-dc0.dtsi
> > new file mode 100644
> > --- /dev/null
> > +++ b/arch/arm64/boot/dts/freescale/imx8-ss-dc0.dtsi
> [ ... ]
> > +dc0_subsys: bus@56000000 {
> [ ... ]
> > + dc0_irqsteer: interrupt-controller@56000000 {
> > + compatible = "fsl,imx-irqsteer";
> > + reg = <0x56000000 0x1000>;
> > + interrupt-controller;
> > + interrupt-parent = <&gic>;
> > + #interrupt-cells = <1>;
> [ ... ]
> > + clocks = <&dc0_lis_lpcg IMX_LPCG_CLK_4>;
> > + clock-names = "ipg";
> > + fsl,channel = <0>;
> > + fsl,num-irqs = <512>;
> > + };
>
> [Severity: Medium]
> Is the dc0_irqsteer node missing a power-domains property?
>
> If it lacks power-domains = <&pd IMX_SC_R_DC_0>;, could this trigger a bus
> fault (SError) during boot or suspend/resume cycles if the irqsteer driver
> accesses its registers when the IMX_SC_R_DC_0 power domain is off?
I cannot test suspend/resume but adding the power-domain is reasonable.
Will be added in v2.
> > diff --git a/arch/arm64/boot/dts/freescale/imx8qxp-ss-dc.dtsi b/arch/arm64/boot/dts/freescale/imx8qxp-ss-dc.dtsi
> > new file mode 100644
> > --- /dev/null
> > +++ b/arch/arm64/boot/dts/freescale/imx8qxp-ss-dc.dtsi
> > @@ -0,0 +1,236 @@
> > +// SPDX-License-Identifier: GPL-2.0+
> > +/*
> > + * Copyright 2024 NXP
> > + */
> > +
> > +&dc0 {
> > + compatible = "fsl,imx8qxp-dc";
> > +};
>
> [Severity: Medium]
> Should there be an override for &dc0_irqsteer in this file to set its
> SoC-specific compatible string?
>
> For example, setting compatible = "fsl,imx8qxp-irqsteer", "fsl,imx-irqsteer";
> here would ensure the node matches correctly. Omitting the SoC-specific
> compatible string might mask the missing power domain violation from
> dtbs_check and prevent SoC-specific driver quirks from applying.
This is a good idea. I removed the "default" compatible, similar to the
other dc nodes.
> &dc0_irqsteer {
> compatible = "fsl,imx8qxp-irqsteer", "fsl,imx-irqsteer";
> };
This is added in imx8qxp-ss-dc.dtsi instead in v2.
Best regards,
Alexander
--
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/
next prev parent reply other threads:[~2026-10-13 14:05 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 [this message]
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
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=5866247.LvFx2qVVIh@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