Devicetree
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Varadarajan Narayanan" <varadarajan.narayanan@oss.qualcomm.com>
Cc: devicetree@vger.kernel.org, conor+dt@kernel.org, robh@kernel.org
Subject: Re: [PATCH v5 3/3] arm64: dts: qcom: ipq5210: Introduce RDP504 NAND variant DT file
Date: Mon, 07 Sep 2026 07:32:51 +0000	[thread overview]
Message-ID: <20260907073251.C108E1F00A3A@smtp.kernel.org> (raw)
In-Reply-To: <20260907-08-dts-v5-3-584e5ab50b40@oss.qualcomm.com>

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] Ambiguous root compatible string for the NAND variant prevents proper board identification.
--

commit 054f8927949f274ca03510708d77e6e740a88b02
Author: Varadarajan Narayanan <varadarajan.narayanan@oss.qualcomm.com>

arm64: dts: qcom: ipq5210: Introduce RDP504 NAND variant DT file

Add DT file for the NAND variant and include it in the Makefile.

[ ... ]

> diff --git a/arch/arm64/boot/dts/qcom/ipq5210-rdp504-nand.dts b/arch/arm64/boot/dts/qcom/ipq5210-rdp504-nand.dts
> new file mode 100644
> index 0000000000000..1145fcf0a3025
> --- /dev/null
> +++ b/arch/arm64/boot/dts/qcom/ipq5210-rdp504-nand.dts
> @@ -0,0 +1,17 @@
> +// SPDX-License-Identifier: BSD-3-Clause
> +/*
> + * Copyright (c) Qualcomm Technologies, Inc. and/or its subsidiaries.
> + */
> +
> +/dts-v1/;
> +
> +#include "ipq5210-rdp504-common.dtsi"
> +
> +/ {
> +	model = "Qualcomm Technologies, Inc. IPQ5210 RDP504 (NAND)";
> +	compatible = "qcom,ipq5210-rdp504", "qcom,ipq5210";

[Severity: Medium]
Will this compatible string prevent bootloaders from selecting the correct DTB
from a multi-DTB image?

Bootloaders that rely on the root compatible string to select the correct
Device Tree Blob (DTB) from a multi-DTB image (such as a FIT image) cannot
deterministically distinguish between this newly added NAND variant and the
existing eMMC variant, because both define the exact same compatible string
("qcom,ipq5210-rdp504").

Since the board must be physically reworked to change from eMMC to NAND,
loading the wrong DTB could lead to pin conflicts and an inability to access
the storage medium.

Should the NAND variant declare a distinct, unique compatible string, such as
"qcom,ipq5210-rdp504-nand"?

> +};
> +
> +&qpic_nand {
> +	status = "okay";
> +};

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260907-08-dts-v5-0-584e5ab50b40@oss.qualcomm.com?part=3

      reply	other threads:[~2026-09-07  7:32 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-07  7:24 [PATCH v5 0/3] Enable mutliple peripherals in IPQ5210 Varadarajan Narayanan
2026-09-07  7:24 ` [PATCH v5 1/3] arm64: dts: qcom: ipq5210: Add nodes for multiple peripherals Varadarajan Narayanan
2026-09-07  7:39   ` sashiko-bot
2026-09-07  7:24 ` [PATCH v5 2/3] arm64: dts: qcom: ipq5210: Introduce RDP504 common DT file Varadarajan Narayanan
2026-09-07  7:24 ` [PATCH v5 3/3] arm64: dts: qcom: ipq5210: Introduce RDP504 NAND variant " Varadarajan Narayanan
2026-09-07  7:32   ` sashiko-bot [this message]

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=20260907073251.C108E1F00A3A@smtp.kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=robh@kernel.org \
    --cc=sashiko-reviews@lists.linux.dev \
    --cc=varadarajan.narayanan@oss.qualcomm.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