From: sashiko-bot@kernel.org
To: "AngeloGioacchino Del Regno" <angelogioacchino.delregno@collabora.com>
Cc: conor+dt@kernel.org, devicetree@vger.kernel.org, robh@kernel.org
Subject: Re: [PATCH 5/7] arm64: dts: mediatek: mt8188: Add and use UART AP_DMA controller
Date: Wed, 01 Jul 2026 12:57:21 +0000 [thread overview]
Message-ID: <20260701125721.734DA1F00A3A@smtp.kernel.org> (raw)
In-Reply-To: <20260701121929.19374-6-angelogioacchino.delregno@collabora.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] The apdma device node is placed out of order based on its unit-address.
--
commit abad4b5e77dac5657d316ab360e0ca880d69701b
Author: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>
arm64: dts: mediatek: mt8188: Add and use UART AP_DMA controller
This commit adds the UART DMA controller (AP_DMA) to the MT8188 SoC.
It also assigns the respective DMA channels to the four UART controllers
to improve data transmission and reception efficiency.
> diff --git a/arch/arm64/boot/dts/mediatek/mt8188.dtsi b/arch/arm64/boot/dts/mediatek/mt8188.dtsi
> index 75133794cec38..8f01d95e6d7d9 100644
> --- a/arch/arm64/boot/dts/mediatek/mt8188.dtsi
> +++ b/arch/arm64/boot/dts/mediatek/mt8188.dtsi
> @@ -1338,6 +1338,31 @@ systimer: timer@10017000 {
> clocks = <&clk13m>;
> };
>
> + apdma: dma-controller@10220880 {
[Severity: Low]
This isn't a bug, but should this node be placed further down in the file
to maintain ascending unit-address order?
The unit-address 10220880 is placed here after timer@10017000 but before
pwrap@10024000 (shown below), which breaks the numerical sorting convention
for Device Tree nodes.
> + compatible = "mediatek,mt8188-uart-dma", "mediatek,mt6835-uart-dma";
[ ... ]
> + #dma-cells = <1>;
> + dma-requests = <12>;
> + };
> +
> pwrap: pwrap@10024000 {
> compatible = "mediatek,mt8188-pwrap", "mediatek,mt8195-pwrap", "syscon";
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260701121929.19374-1-angelogioacchino.delregno@collabora.com?part=5
next prev parent reply other threads:[~2026-07-01 12:57 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-01 12:19 [PATCH 0/7] dts: Add and use UART AP_DMA controller on MTK SoCs AngeloGioacchino Del Regno
2026-07-01 12:19 ` [PATCH 1/7] arm64: dts: mediatek: mt6795: Remove deprecated UART DMA property AngeloGioacchino Del Regno
2026-07-01 12:19 ` [PATCH 2/7] arm64: dts: mediatek: mt8173: Add and use UART AP_DMA controller AngeloGioacchino Del Regno
2026-07-01 12:35 ` sashiko-bot
2026-07-01 12:19 ` [PATCH 3/7] arm64: dts: mediatek: mt8183: " AngeloGioacchino Del Regno
2026-07-01 12:19 ` [PATCH 4/7] arm64: dts: mediatek: mt8186: " AngeloGioacchino Del Regno
2026-07-01 12:49 ` sashiko-bot
2026-07-01 12:19 ` [PATCH 5/7] arm64: dts: mediatek: mt8188: " AngeloGioacchino Del Regno
2026-07-01 12:57 ` sashiko-bot [this message]
2026-07-01 12:19 ` [PATCH 6/7] arm64: dts: mediatek: mt8192: " AngeloGioacchino Del Regno
2026-07-01 12:19 ` [PATCH 7/7] arm64: dts: mediatek: mt8195: " AngeloGioacchino Del Regno
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=20260701125721.734DA1F00A3A@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 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.