Devicetree
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Zakariya Hadrami" <zkh@mailbox.org>
Cc: robh@kernel.org, conor+dt@kernel.org, devicetree@vger.kernel.org,
	linux-watchdog@vger.kernel.org
Subject: Re: [PATCH v3 4/4] ARM: dts: mediatek: Add basic support for Amazon ford board
Date: Tue, 08 Sep 2026 22:07:30 +0000	[thread overview]
Message-ID: <20260908220731.0CF1E1F00A3A@smtp.kernel.org> (raw)
In-Reply-To: <20260908-mt8127-amazon-ford-basic-v3-4-fc46bf1b6cb2@mailbox.org>

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] Device Tree Compiler (DTC) warnings due to using a unit address without a 'reg' property in the simple-framebuffer node.
--

commit 03486b0d7f26e5bd328d2d2b8f2a803bdf72c6b4
Author: Zakariya Hadrami <zkh@mailbox.org>

ARM: dts: mediatek: Add basic support for Amazon ford board

This tablet uses a MediaTek MT8127 system-on-chip with 1GB of RAM.
It can currently boot into initramfs with a working UART and
Simple Framebuffer using already initialized panel by the bootloader.

> diff --git a/arch/arm/boot/dts/mediatek/mt8127-amazon-ford.dts b/arch/arm/boot/dts/mediatek/mt8127-amazon-ford.dts
> new file mode 100644
> index 0000000000000..21bdab0e43f88
> --- /dev/null
> +++ b/arch/arm/boot/dts/mediatek/mt8127-amazon-ford.dts

[ ... ]

> +	chosen {
> +		stdout-path = "serial0:921600n8";
> +
> +		framebuffer0: framebuffer@b7a00000 {

[Severity: Low]
Will this node name cause Device Tree Compiler warnings during make dtbs?

Since the node is named with a unit address (@b7a00000) but only uses a
memory-region property without a corresponding reg property, it seems this
would trigger a unit_address_vs_reg warning.

Additionally, it might trigger an avoid_default_addr_size warning because
its parent (chosen) lacks #address-cells and #size-cells.

Would it be better to omit the unit address here?

> +			compatible = "simple-framebuffer";
> +			memory-region = <&framebuffer_reserved>;
> +			width = <1024>;
> +			height = <600>;
> +			stride = <(1024 * 2)>;
> +			format = "r5g6b5";
> +		};
> +	};

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260908-mt8127-amazon-ford-basic-v3-0-fc46bf1b6cb2@mailbox.org?part=4

  reply	other threads:[~2026-09-08 22:07 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-08 21:59 [PATCH v3 0/4] ARM: Basic support for Amazon ford tablet (MT8127) Zakariya Hadrami via B4 Relay
2026-09-08 21:59 ` [PATCH v3 1/4] dt-bindings: watchdog: mediatek: Add MT8127 Zakariya Hadrami via B4 Relay
2026-09-08 21:59 ` [PATCH v3 2/4] dt-bindings: arm: mediatek: Add MT8127 Amazon ford Zakariya Hadrami via B4 Relay
2026-09-08 21:59 ` [PATCH v3 3/4] ARM: dts: mediatek: mt8127: Add watchdog support Zakariya Hadrami via B4 Relay
2026-09-08 21:59 ` [PATCH v3 4/4] ARM: dts: mediatek: Add basic support for Amazon ford board Zakariya Hadrami via B4 Relay
2026-09-08 22:07   ` sashiko-bot [this message]
2026-09-09 19:54     ` Zakariya Hadrami

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=20260908220731.0CF1E1F00A3A@smtp.kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-watchdog@vger.kernel.org \
    --cc=robh@kernel.org \
    --cc=sashiko-reviews@lists.linux.dev \
    --cc=zkh@mailbox.org \
    /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