From: sashiko-bot@kernel.org
To: Frank.Li@oss.nxp.com
Cc: devicetree@vger.kernel.org, conor+dt@kernel.org, robh@kernel.org,
Frank.Li@kernel.org, imx@lists.linux.dev
Subject: Re: [PATCH 1/4] arm64: dts: imx8qm-ss-dma: add lpuart4 node
Date: Mon, 06 Jul 2026 22:00:51 +0000 [thread overview]
Message-ID: <20260706220051.C19FA1F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260706-qm_dts-v1-1-14117a48fbdb@nxp.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] The newly added `lpuart4` node includes a `power-domain-names` property which is undocumented in the `fsl-lpuart.yaml` device tree binding, causing a devicetree schema validation failure.
--
--- Patch [1]: [PATCH 1/4] arm64: dts: imx8qm-ss-dma: add lpuart4 node ---
commit 5d53e06892d921423b269317c3426f0a50c063e7
Author: Frank Li <Frank.Li@nxp.com>
arm64: dts: imx8qm-ss-dma: add lpuart4 node
This commit adds the lpuart4 node for the imx8qm SoC to the imx8qm-ss-dma.dtsi
device tree source.
> diff --git a/arch/arm64/boot/dts/freescale/imx8qm-ss-dma.dtsi b/arch/arm64/boot/dts/freescale/imx8qm-ss-dma.dtsi
> --- a/arch/arm64/boot/dts/freescale/imx8qm-ss-dma.dtsi
> +++ b/arch/arm64/boot/dts/freescale/imx8qm-ss-dma.dtsi
> @@ -8,6 +8,22 @@
> /delete-node/ &adma_pwm_lpcg;
>
> &dma_subsys {
> + lpuart4: serial@5a0a0000 {
> + compatible = "fsl,imx8qm-lpuart", "fsl,imx8qxp-lpuart";
> + reg = <0x5a0a0000 0x1000>;
[ ... ]
> + assigned-clocks = <&clk IMX_SC_R_UART_4 IMX_SC_PM_CLK_PER>;
> + assigned-clock-rates = <80000000>;
> + power-domains = <&pd IMX_SC_R_UART_4>;
> + power-domain-names = "uart";
[Severity: Low]
Is this power-domain-names property strictly necessary here?
This property is undocumented in the fsl-lpuart.yaml device tree binding,
which restricts allowed properties. As a result, including it causes a
devicetree schema validation failure during dtbs_check.
Since there is only a single power domain specified for lpuart4, the kernel
PM core handles it automatically without needing it to be explicitly named.
> + dmas = <&edma2 20 0 FSL_EDMA_RX>, <&edma2 21 0 0>;
> + dma-names = "rx","tx";
> + status = "disabled";
> + };
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260706-qm_dts-v1-0-14117a48fbdb@nxp.com?part=1
next prev parent reply other threads:[~2026-07-06 22:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-06 21:52 [PATCH 0/4] arm64: dts: imx8qm: collect some small update and fixes Frank.Li
2026-07-06 21:52 ` [PATCH 1/4] arm64: dts: imx8qm-ss-dma: add lpuart4 node Frank.Li
2026-07-06 22:00 ` sashiko-bot [this message]
2026-07-06 21:52 ` [PATCH 2/4] arm64: dts: imx8qm-ss-audio: add spdif1 node Frank.Li
2026-07-06 21:52 ` [PATCH 3/4] arm64: dts: imx8qm-ss-lsio: add lsio mu6,8,8b Frank.Li
2026-07-06 22:04 ` sashiko-bot
2026-07-06 21:52 ` [PATCH 4/4] arm64: dts: imx8-ss-audio: Fix LPCG clock indices for ASRC0 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=20260706220051.C19FA1F000E9@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=Frank.Li@kernel.org \
--cc=Frank.Li@oss.nxp.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 \
/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