From: Troy Mitchell <troymitchell988@gmail.com>
To: "Troy Mitchell" <troy.mitchell@linux.spacemit.com>,
"Vinod Koul" <vkoul@kernel.org>, "Frank Li" <Frank.Li@kernel.org>,
"Rob Herring" <robh@kernel.org>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
"Conor Dooley" <conor+dt@kernel.org>,
"Yixun Lan" <dlan@kernel.org>,
"Guodong Xu" <guodong@riscstar.com>,
"Michael Turquette" <mturquette@baylibre.com>,
"Stephen Boyd" <sboyd@kernel.org>,
"Paul Walmsley" <pjw@kernel.org>,
"Palmer Dabbelt" <palmer@dabbelt.com>,
"Albert Ou" <aou@eecs.berkeley.edu>,
"Alexandre Ghiti" <alex@ghiti.fr>
Cc: <dmaengine@vger.kernel.org>, <devicetree@vger.kernel.org>,
<linux-riscv@lists.infradead.org>, <spacemit@lists.linux.dev>,
<linux-kernel@vger.kernel.org>, <linux-clk@vger.kernel.org>,
"Brian Masney" <bmasney@redhat.com>
Subject: Re: [PATCH v3 0/5] dmaengine: Add Peripheral DMA support for SpacemiT K3 SoC
Date: Fri, 24 Apr 2026 21:58:27 +0800 [thread overview]
Message-ID: <DI1FSG6ITXK3.GG7XHRD4JSGC@linux.spacemit.com> (raw)
In-Reply-To: <20260424-k3-pdma-v3-0-efdf2e414a08@linux.spacemit.com>
Apologies, I just realized the version number is incorrect.
This patchset should be v4.
- Troy
On Fri Apr 24, 2026 at 4:20 PM CST, Troy Mitchell wrote:
> Hi all,
>
> This patch series introduces Peripheral DMA (PDMA) support for the
> SpacemiT K3 SoC, leveraging the existing mmp_pdma driver.
>
> The K3 PDMA IP is largely based on the design found in the previous
> SpacemiT K1 SoC, but introduces a few key architectural differences:
> 1. It features a variable extended DRCMR base address for DMA request
> numbers (>= 64) depending on the hardware implementation.
> 2. Unlike the K1 SoC, where some DMA masters had memory addressing
> limitations (requiring a dedicated dma-bus), the K3 DMA masters
> have full memory addressing capabilities.
>
> The series is structured as follows:
> - Patch 1: Introduce the necessary dt-bindings: K3 compatible string.
> - Patch 2-3: Refactor the mmp_pdma driver to support variable extended
> DRCMR bases, and add the specific implementation/ops for the K3 SoC.
> - Patch 4: Fixes a critical clock issue where the DDR bus clock
> (top_dclk) could be gated by CCF, which would cause DMA engines to
> hang and lead to system instability.
> - Patch 5: Finally, instantiates the PDMA controller node in the
> SpacemiT K3 device tree.
>
> ---
> Changes in v4:
> - patch 4/5:
> - add Brian's RB tag
> - patch 1/5:
> - update commit message
> Link to v3: https://lore.kernel.org/all/20260331-k3-pdma-v3-0-a4e60dd8b4b3@linux.spacemit.com/
>
> Changes in v3:
> - Removed the dt-bindings patches related to the DMA number.
> - patch 1/5:
> - update commit message
> - patch 2-5: nothing
> - Link to v2: https://lore.kernel.org/r/20260326-k3-pdma-v2-0-ca94ca7bb595@linux.spacemit.com
>
> Changes in v2:
> - patch 1-6 are added in this version
> - patch 7/7
> - update commit message
> - using k3 compatible string
> - Link to v1: https://lore.kernel.org/all/20260317-k3-pdma-v1-1-f39d3e97b53a@linux.spacemit.com/
>
> ---
> Guodong Xu (3):
> dt-bindings: dmaengine: Add SpacemiT K3 DMA compatible string
> dmaengine: mmp_pdma: support variable extended DRCMR base
> dmaengine: mmp_pdma: add Spacemit K3 support
>
> Troy Mitchell (2):
> clk: spacemit: k3: mark top_dclk as CLK_IS_CRITICAL
> riscv: dts: spacemit: Add PDMA controller node for K3 SoC
>
> .../devicetree/bindings/dma/spacemit,k1-pdma.yaml | 4 ++-
> arch/riscv/boot/dts/spacemit/k3.dtsi | 11 +++++++
> drivers/clk/spacemit/ccu-k3.c | 2 +-
> drivers/dma/mmp_pdma.c | 37 ++++++++++++++++++++--
> 4 files changed, 49 insertions(+), 5 deletions(-)
> ---
> base-commit: 02f90981a67f3b9ee7d6684e7503a4fed7aade0c
> change-id: 20260317-k3-pdma-7c1734431436
>
> Best regards,
> --
> Troy Mitchell <troy.mitchell@linux.spacemit.com>
next prev parent reply other threads:[~2026-04-24 13:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-24 8:20 [PATCH v3 0/5] dmaengine: Add Peripheral DMA support for SpacemiT K3 SoC Troy Mitchell
2026-04-24 8:20 ` [PATCH v3 1/5] dt-bindings: dmaengine: Add SpacemiT K3 DMA compatible string Troy Mitchell
2026-04-24 17:03 ` Conor Dooley
2026-04-24 8:20 ` [PATCH v3 2/5] dmaengine: mmp_pdma: support variable extended DRCMR base Troy Mitchell
2026-04-24 8:20 ` [PATCH v3 3/5] dmaengine: mmp_pdma: add Spacemit K3 support Troy Mitchell
2026-04-24 8:20 ` [PATCH v3 4/5] clk: spacemit: k3: mark top_dclk as CLK_IS_CRITICAL Troy Mitchell
2026-04-24 8:20 ` [PATCH v3 5/5] riscv: dts: spacemit: Add PDMA controller node for K3 SoC Troy Mitchell
2026-04-24 13:58 ` Troy Mitchell [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-03-31 8:27 [PATCH v3 0/5] dmaengine: Add Peripheral DMA support for SpacemiT " Troy Mitchell
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=DI1FSG6ITXK3.GG7XHRD4JSGC@linux.spacemit.com \
--to=troymitchell988@gmail.com \
--cc=Frank.Li@kernel.org \
--cc=alex@ghiti.fr \
--cc=aou@eecs.berkeley.edu \
--cc=bmasney@redhat.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dlan@kernel.org \
--cc=dmaengine@vger.kernel.org \
--cc=guodong@riscstar.com \
--cc=krzk+dt@kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=mturquette@baylibre.com \
--cc=palmer@dabbelt.com \
--cc=pjw@kernel.org \
--cc=robh@kernel.org \
--cc=sboyd@kernel.org \
--cc=spacemit@lists.linux.dev \
--cc=troy.mitchell@linux.spacemit.com \
--cc=vkoul@kernel.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