Devicetree
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "AngeloGioacchino Del Regno" <angelogioacchino.delregno@collabora.com>
Cc: robh@kernel.org, devicetree@vger.kernel.org, conor+dt@kernel.org
Subject: Re: [PATCH v2 2/7] arm64: dts: mediatek: mt8173: Add and use UART AP_DMA controller
Date: Tue, 07 Jul 2026 16:16:20 +0000	[thread overview]
Message-ID: <20260707161620.CB8AC1F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260707154841.198870-3-angelogioacchino.delregno@collabora.com>

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [High] The newly added `apdma` node uses a `reg` base address that overlaps exactly with the DMA channel already assigned to `i2c4` (`0x11000300`), leading to guaranteed probe failures for one of the devices.
--

--- Patch [2]: [PATCH v2 2/7] arm64: dts: mediatek: mt8173: Add and use UART AP_DMA controller ---
commit 02e7bfa1531235c71580128c63236a6715a1e297
Author: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>

arm64: dts: mediatek: mt8173: Add and use UART AP_DMA controller

This commit adds the UART AP_DMA controller to the MT8173 device tree and
assigns its DMA channels to the four UART controllers. This is intended to
increase data TX/RX efficiency for the UARTs.

> diff --git a/arch/arm64/boot/dts/mediatek/mt8173.dtsi b/arch/arm64/boot/dts/mediatek/mt8173.dtsi
> index 78c2ccd5be132..7297225f61c99 100644
> --- a/arch/arm64/boot/dts/mediatek/mt8173.dtsi
> +++ b/arch/arm64/boot/dts/mediatek/mt8173.dtsi
> @@ -673,6 +673,25 @@ gic: interrupt-controller@10221000 {
>  				(GIC_CPU_MASK_SIMPLE(4) | IRQ_TYPE_LEVEL_HIGH)>;
>  		};
>  
> +		apdma: dma-controller@11000300 {
> +			compatible = "mediatek,mt8173-uart-dma", "mediatek,mt6577-uart-dma";
> +			reg = <0 0x11000300 0 0x80>, <0 0x11000380 0 0x80>,

[Severity: High]
Does this node's first reg region conflict with the DMA region already
assigned to the i2c4 controller?

Looking at the existing i2c4 node later in the same file:

		i2c4: i2c@11011000 {
			compatible = "mediatek,mt8173-i2c";
			reg = <0 0x11011000 0 0x70>,
			      <0 0x11000300 0 0x80>;

Since both devices claim 0x11000300 and apdma is not marked as disabled,
would request_mem_region() return -EBUSY and fail to probe one of the
devices? This could break i2c4-attached devices like trackpads on
mt8173-elm boards.

> +			      <0 0x11000400 0 0x80>, <0 0x11000480 0 0x80>,
> +			      <0 0x11000500 0 0x80>, <0 0x11000580 0 0x80>,
> +			      <0 0x11000600 0 0x80>, <0 0x11000680 0 0x80>;

[ ... ]

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260707154841.198870-1-angelogioacchino.delregno@collabora.com?part=2

  reply	other threads:[~2026-07-07 16:16 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-07 15:48 [PATCH v2 0/7] dts: Add and use UART AP_DMA controller on MTK SoCs AngeloGioacchino Del Regno
2026-07-07 15:48 ` [PATCH v2 1/7] arm64: dts: mediatek: mt6795: Remove deprecated UART DMA property AngeloGioacchino Del Regno
2026-07-07 15:48 ` [PATCH v2 2/7] arm64: dts: mediatek: mt8173: Add and use UART AP_DMA controller AngeloGioacchino Del Regno
2026-07-07 16:16   ` sashiko-bot [this message]
2026-07-07 15:48 ` [PATCH v2 3/7] arm64: dts: mediatek: mt8183: " AngeloGioacchino Del Regno
2026-07-07 15:48 ` [PATCH v2 4/7] arm64: dts: mediatek: mt8186: " AngeloGioacchino Del Regno
2026-07-07 16:37   ` sashiko-bot
2026-07-07 15:48 ` [PATCH v2 5/7] arm64: dts: mediatek: mt8188: " AngeloGioacchino Del Regno
2026-07-07 15:48 ` [PATCH v2 6/7] arm64: dts: mediatek: mt8192: " AngeloGioacchino Del Regno
2026-07-07 15:48 ` [PATCH v2 7/7] arm64: dts: mediatek: mt8195: " AngeloGioacchino Del Regno
2026-07-07 16:54   ` sashiko-bot

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=20260707161620.CB8AC1F000E9@smtp.kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=angelogioacchino.delregno@collabora.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox