Devicetree
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Enzo Adriano via B4 Relay"
	<devnull+enzo.adriano.code.gmail.com@kernel.org>
Cc: robh@kernel.org, devicetree@vger.kernel.org, conor+dt@kernel.org,
	linux-sunxi@lists.linux.dev
Subject: Re: [PATCH 3/4] arm64: dts: allwinner: add Allwinner A733 SoC
Date: Sat, 13 Jun 2026 11:50:18 +0000	[thread overview]
Message-ID: <20260613115018.D3A111F00A3F@smtp.kernel.org> (raw)
In-Reply-To: <20260613-a733-dts-v1-public-ready-v1-3-7787c94681db@gmail.com>

Thank you for your contribution! Sashiko AI review found 2 potential issue(s) to consider:
- [Low] The patch references missing header files for CCU clock and reset bindings, which will cause a build failure.
- [Low] New compatible strings for the CCU and pinctrl are used without being documented in the YAML schemas.
--

commit 08b3c222d5fc2b42b4c8ea3dd602ebcc113d5545
Author: Enzo Adriano <enzo.adriano.code@gmail.com>

arm64: dts: allwinner: add Allwinner A733 SoC

Add the initial A733 SoC description with CPUs, timers, interrupt
controller, clocks, pinctrl, UART0, and MMC0.

Keep peripherals disabled by default. Board DTS files can enable only the
devices that are proven on their hardware.

> diff --git a/arch/arm64/boot/dts/allwinner/sun60i-a733.dtsi b/arch/arm64/boot/dts/allwinner/sun60i-a733.dtsi
> new file mode 100644
> --- /dev/null
> +++ b/arch/arm64/boot/dts/allwinner/sun60i-a733.dtsi
> @@ -0,0 +1,198 @@
> +// SPDX-License-Identifier: (GPL-2.0-only OR MIT)
> +
> +#include <dt-bindings/interrupt-controller/arm-gic.h>
> +#include <dt-bindings/clock/sun60i-a733-ccu.h>
> +#include <dt-bindings/reset/sun60i-a733-ccu.h>

[Severity: Low]
Are these header files introduced in a different patch? Compiling this device
tree will fail at the preprocessor stage because these headers are missing
from the baseline tree and aren't added in this patch.

[ ... ]

> +		pio: pinctrl@2000000 {
> +			compatible = "allwinner,sun60i-a733-pinctrl";

[Severity: Low]
Are these new compatible strings documented in the dt-binding YAML schemas?
Adding new compatibles without their corresponding binding documentation will
trigger make dtbs_check warnings.

> +			reg = <0x02000000 0x600>;

[ ... ]

> +		ccu: clock-controller@2002000 {
> +			compatible = "allwinner,sun60i-a733-ccu";

[Severity: Low]
Will this compatible string also need to be added to the YAML schemas to
avoid validation warnings?

> +			reg = <0x02002000 0x2000>;

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260613-a733-dts-v1-public-ready-v1-0-7787c94681db@gmail.com?part=3

  reply	other threads:[~2026-06-13 11:50 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-13  9:42 [PATCH 0/4] arm64: dts: allwinner: add A733/Cubie A7S DTS support Enzo Adriano via B4 Relay
2026-06-13  9:42 ` [PATCH 1/4] dt-bindings: arm: sunxi: add Radxa Cubie A7S Enzo Adriano via B4 Relay
2026-06-13  9:42 ` [PATCH 2/4] dt-bindings: mmc: add Allwinner A733 compatible Enzo Adriano via B4 Relay
2026-06-13  9:42 ` [PATCH 3/4] arm64: dts: allwinner: add Allwinner A733 SoC Enzo Adriano via B4 Relay
2026-06-13 11:50   ` sashiko-bot [this message]
2026-06-13  9:42 ` [PATCH 4/4] arm64: dts: allwinner: add Radxa Cubie A7S Enzo Adriano via B4 Relay
2026-06-13  9:50   ` sashiko-bot
2026-06-13 11:37   ` Jernej Škrabec
2026-06-13 13:29     ` Enzo

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=20260613115018.D3A111F00A3F@smtp.kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=devnull+enzo.adriano.code.gmail.com@kernel.org \
    --cc=linux-sunxi@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