All of lore.kernel.org
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Ben Grisdale" <bengris32@protonmail.ch>
Cc: devicetree@vger.kernel.org, linux-serial@vger.kernel.org,
	robh@kernel.org, conor+dt@kernel.org
Subject: Re: [PATCH v2 6/6] arm64: dts: mediatek: Add Amazon Echo Dot (2016)
Date: Thu, 05 Nov 2026 14:38:41 +0000	[thread overview]
Message-ID: <sashiko-outbox-199255@kernel.org> (raw)
In-Reply-To: <20261105-arm64-initial-support-for-mediatek-mt8163-soc-v2-6-e68d7d428f99@protonmail.ch>

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] arm64: dts: mediatek: unmatched mediatek,mt8163-wdt compatible in mt8163.dtsi
--

commit 1dcf4259a2a7c0a8d0a32ef9d20a66f3c078542e
Author: Ben Grisdale <bengris32@protonmail.ch>

arm64: dts: mediatek: Add Amazon Echo Dot (2016)

This commit adds a device tree for the Amazon Echo Dot (2nd generation, 2016),
codenamed "biscuit", based on the MediaTek MT8163 SoC, and enables building
mt8163-amazon-biscuit.dtb.

> diff --git a/arch/arm64/boot/dts/mediatek/mt8163-amazon-biscuit.dts b/arch/arm64/boot/dts/mediatek/mt8163-amazon-biscuit.dts
> new file mode 100644
> index 0000000000000..5fb5d59e4ed25
> --- /dev/null
> +++ b/arch/arm64/boot/dts/mediatek/mt8163-amazon-biscuit.dts
> @@ -0,0 +1,68 @@
> +// SPDX-License-Identifier: GPL-2.0-only OR MIT
> +/*
> + * Copyright (c) 2026 Ben Grisdale <bengris32@protonmail.ch>
> + */
> +
> +/dts-v1/;
> +#include "mt8163.dtsi"

[Severity: Medium]
Building mt8163-amazon-biscuit.dtb includes arch/arm64/boot/dts/mediatek/mt8163.dtsi,
which defines watchdog@10007000 without a fallback compatible:

arch/arm64/boot/dts/mediatek/mt8163.dtsi:
		watchdog: watchdog@10007000 {
			compatible = "mediatek,mt8163-wdt";
			reg = <0 0x10007000 0 0x1000>;
			interrupts = <GIC_SPI 128 IRQ_TYPE_EDGE_FALLING>;
			#reset-cells = <1>;
		};

However, mediatek,mt8163-wdt is not documented in
Documentation/devicetree/bindings/watchdog/mediatek,mtk-wdt.yaml, nor is it
present in mtk_wdt_dt_ids[] in drivers/watchdog/mtk_wdt.c:

drivers/watchdog/mtk_wdt.c:
static const struct of_device_id mtk_wdt_dt_ids[] = {
	{ .compatible = "mediatek,mt2712-wdt", .data = &mt2712_data },
	{ .compatible = "mediatek,mt6589-wdt", .data = &mt6589_data },
	...

Will this cause dtbs_check to fail on mt8163-amazon-biscuit.dtb and prevent
the MediaTek watchdog and TOPRGU reset controller driver from binding to
watchdog@10007000 at runtime? Should watchdog@10007000 in mt8163.dtsi include
a fallback compatible such as "mediatek,mt6589-wdt" (along with the binding
update), or should mediatek,mt8163-wdt be added to the binding and driver?

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20261105-arm64-initial-support-for-mediatek-mt8163-soc-v2-0-e68d7d428f99@protonmail.ch?part=6

      reply	other threads:[~2026-11-05 14:38 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-05 14:28 [PATCH v2 0/6] arm64: Initial support for MediaTek MT8163 SoC Ben Grisdale
2026-11-05 14:28 ` Ben Grisdale via B4 Relay
2026-11-05 14:28 ` [PATCH v2 1/6] dt-bindings: arm: mediatek: Add MT8163 Amazon Echo Dot (2016) Ben Grisdale
2026-11-05 14:28   ` Ben Grisdale via B4 Relay
2026-11-05 14:31   ` sashiko-bot
2026-11-05 14:28 ` [PATCH v2 2/6] dt-bindings: interrupt-controller: mediatek,mt6577-sysirq: Add MT8163 Ben Grisdale
2026-11-05 14:28   ` Ben Grisdale via B4 Relay
2026-11-05 14:30   ` sashiko-bot
2026-11-05 14:28 ` [PATCH v2 3/6] dt-bindings: timer: mediatek,timer: " Ben Grisdale
2026-11-05 14:28   ` Ben Grisdale via B4 Relay
2026-11-05 14:31   ` sashiko-bot
2026-11-05 14:28 ` [PATCH v2 4/6] dt-bindings: serial: mediatek,uart: " Ben Grisdale
2026-11-05 14:28   ` Ben Grisdale via B4 Relay
2026-11-05 14:31   ` sashiko-bot
2026-11-05 14:28 ` [PATCH v2 5/6] arm64: dts: mediatek: Add basic support for MT8163 SoC Ben Grisdale
2026-11-05 14:28   ` Ben Grisdale via B4 Relay
2026-11-05 14:43   ` sashiko-bot
2026-11-05 14:28 ` [PATCH v2 6/6] arm64: dts: mediatek: Add Amazon Echo Dot (2016) Ben Grisdale
2026-11-05 14:28   ` Ben Grisdale via B4 Relay
2026-11-05 14:38   ` 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=sashiko-outbox-199255@kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=bengris32@protonmail.ch \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-serial@vger.kernel.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.