From: sashiko-bot@kernel.org
To: "Adrian Ng Ho Yin" <adrian.ho.yin.ng@altera.com>
Cc: devicetree@vger.kernel.org, krzk+dt@kernel.org, robh@kernel.org,
conor+dt@kernel.org
Subject: Re: [PATCH 2/2] arm64: dts: agilex5: add support for debug daughter card
Date: Fri, 08 May 2026 20:42:37 +0000 [thread overview]
Message-ID: <20260508204237.ADF26C2BCB0@smtp.kernel.org> (raw)
In-Reply-To: <a42751b4c7eb9b4d58f2ef1db3591ff68385a562.1778237639.git.adrian.ho.yin.ng@altera.com>
Thank you for your contribution! Sashiko AI review found 2 potential issue(s) to consider:
- [Low] Abuse of the 'rohm,dh2228fv' compatible string to force the 'spidev' driver to bind.
- [Low] Including a '.dts' file directly instead of using a '.dtsi' include file.
--
commit 3916af69e58bdb9bf4d736172238dd0b03e9465b
Author: Adrian Ng Ho Yin <adrian.ho.yin.ng@altera.com>
arm64: dts: agilex5: add support for debug daughter card
This commit adds a new device tree for the Agilex 5 SoCDK when fitted with
the debug daughter card. It disables several peripherals such as gpio0 and
gmac2 while enabling gmac0 and spi0 for debugging purposes.
> diff --git a/arch/arm64/boot/dts/intel/socfpga_agilex5_socdk_debug.dts b/arch/arm64/boot/dts/intel/socfpga_agilex5_socdk_debug.dts
> new file mode 100644
> index 0000000000000..3981a9e876b0a
> --- /dev/null
> +++ b/arch/arm64/boot/dts/intel/socfpga_agilex5_socdk_debug.dts
> @@ -0,0 +1,50 @@
> +// SPDX-License-Identifier: GPL-2.0
> +/*
> + * Copyright (C) 2026, Altera Corporation
> + */
> +#include "socfpga_agilex5_socdk.dts"
This isn't a bug, but does this include a final board .dts file instead of a
shared .dtsi include?
Standard Device Tree conventions typically involve refactoring shared
configurations into a common .dtsi file, as .dts files are meant to be the
final top-level compilation unit for a board.
[ ... ]
> +&spi0 {
> + status = "okay";
> + spidev@0 {
> + compatible = "rohm,dh2228fv";
Is there actually a Rohm DH2228FV hardware device present on this debug
daughter card?
The commit message indicates this exposes the SPI interface for debugging.
Does this code use the 'rohm,dh2228fv' compatible string solely to force the
Linux spidev driver to bind?
The Device Tree is meant for describing hardware, and using fake hardware
compatible strings to instantiate userspace interfaces bypasses the kernel
warnings against using a bare 'spidev' compatible string.
> + reg = <0>;
> + spi-max-frequency = <10000000>;
> + };
> +};
--
Sashiko AI review · https://sashiko.dev/#/patchset/cover.1778237639.git.adrian.ho.yin.ng@altera.com?part=2
next prev parent reply other threads:[~2026-05-08 20:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-08 10:57 [PATCH 0/2] arm64: dts: agilex5: add support for debug daughter card Adrian Ng Ho Yin
2026-05-08 10:57 ` [PATCH 1/2] dt-bindings: altera: add compatible for agilex5 socdk " Adrian Ng Ho Yin
2026-05-08 15:01 ` Conor Dooley
2026-05-08 10:57 ` [PATCH 2/2] arm64: dts: agilex5: add support for " Adrian Ng Ho Yin
2026-05-08 20:42 ` sashiko-bot [this message]
2026-05-09 12:05 ` [PATCH 0/2] " Dinh Nguyen
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=20260508204237.ADF26C2BCB0@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=adrian.ho.yin.ng@altera.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=robh@kernel.org \
--cc=sashiko@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