From: Yixun Lan <dlan@kernel.org>
To: Zhengyu He <hezhy472013@gmail.com>
Cc: Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Paul Walmsley <pjw@kernel.org>,
Palmer Dabbelt <palmer@dabbelt.com>,
Albert Ou <aou@eecs.berkeley.edu>,
Alexandre Ghiti <alex@ghiti.fr>, Mark Brown <broonie@kernel.org>,
Alex Elder <elder@kernel.org>,
devicetree@vger.kernel.org, linux-riscv@lists.infradead.org,
spacemit@lists.linux.dev, linux-kernel@vger.kernel.org,
linux-spi@vger.kernel.org, wefu@redhat.com,
liyeshan <yeshan.li@spacemit.com>,
Guodong Xu <docular.xu@gmail.com>
Subject: Re: [PATCH 1/4] riscv: dts: spacemit: add K3 PDMA request numbers
Date: Sat, 25 Jul 2026 13:15:55 +0000 [thread overview]
Message-ID: <20260725131555-GKF77545@kernel.org> (raw)
In-Reply-To: <20260717-k3-com260-spi-v7-2-rc2-b4-preview-20260716-v1-1-969a1b0f783f@gmail.com>
Hi Zhengyu,
On 07:45 Fri 17 Jul , Zhengyu He wrote:
> From: liyeshan <yeshan.li@spacemit.com>
>
> Add a local DTS header that gives symbolic names to the SpacemiT K3
> PDMA request lines of the non-secure peripherals. Device trees can use
> these K3_PDMA_* macros instead of hard-coded request numbers when wiring
> a peripheral "dmas" property.
>
> Signed-off-by: liyeshan <yeshan.li@spacemit.com>
> Signed-off-by: Guodong Xu <docular.xu@gmail.com>
> Signed-off-by: Zhengyu He <hezhy472013@gmail.com>
Reviewed-by: Yixun Lan <dlan@kernel.org>
> ---
> arch/riscv/boot/dts/spacemit/k3-pdma.h | 83 ++++++++++++++++++++++++++++++++++
> 1 file changed, 83 insertions(+)
>
> diff --git a/arch/riscv/boot/dts/spacemit/k3-pdma.h b/arch/riscv/boot/dts/spacemit/k3-pdma.h
> new file mode 100644
> index 000000000000..a5b723ad616a
> --- /dev/null
> +++ b/arch/riscv/boot/dts/spacemit/k3-pdma.h
> @@ -0,0 +1,83 @@
> +/* SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) */
> +/*
> + * DMA request number (DRQ) definitions for non-secure peripherals of
> + * the SpacemiT K3 PDMA.
> + *
> + * Copyright (c) 2025 SpacemiT
> + * Copyright (c) 2026 Guodong Xu <docular.xu@gmail.com>
> + */
> +
> +#ifndef _DTS_SPACEMIT_K3_PDMA_H
> +#define _DTS_SPACEMIT_K3_PDMA_H
> +
> +/* UART DMA request numbers */
> +#define K3_PDMA_UART0_TX 3
> +#define K3_PDMA_UART0_RX 4
> +#define K3_PDMA_UART2_TX 5
> +#define K3_PDMA_UART2_RX 6
> +#define K3_PDMA_UART3_TX 7
> +#define K3_PDMA_UART3_RX 8
> +#define K3_PDMA_UART4_TX 9
> +#define K3_PDMA_UART4_RX 10
> +#define K3_PDMA_UART5_TX 25
> +#define K3_PDMA_UART5_RX 26
> +#define K3_PDMA_UART6_TX 27
> +#define K3_PDMA_UART6_RX 28
> +#define K3_PDMA_UART7_TX 29
> +#define K3_PDMA_UART7_RX 30
> +#define K3_PDMA_UART8_TX 31
> +#define K3_PDMA_UART8_RX 32
> +#define K3_PDMA_UART9_TX 33
> +#define K3_PDMA_UART9_RX 34
> +#define K3_PDMA_UART10_TX 53
> +#define K3_PDMA_UART10_RX 54
> +
> +/* I2C DMA request numbers */
> +#define K3_PDMA_I2C0_TX 11
> +#define K3_PDMA_I2C0_RX 12
> +#define K3_PDMA_I2C1_TX 13
> +#define K3_PDMA_I2C1_RX 14
> +#define K3_PDMA_I2C2_TX 15
> +#define K3_PDMA_I2C2_RX 16
> +#define K3_PDMA_I2C4_TX 17
> +#define K3_PDMA_I2C4_RX 18
> +#define K3_PDMA_I2C5_TX 35
> +#define K3_PDMA_I2C5_RX 36
> +#define K3_PDMA_I2C6_TX 37
> +#define K3_PDMA_I2C6_RX 38
> +#define K3_PDMA_I2C8_TX 41
> +#define K3_PDMA_I2C8_RX 42
> +
> +/* SSP/SPI DMA request numbers */
> +#define K3_PDMA_SSP3_TX 19
> +#define K3_PDMA_SSP3_RX 20
> +#define K3_PDMA_SSPA0_TX 21
> +#define K3_PDMA_SSPA0_RX 22
> +#define K3_PDMA_SSPA1_TX 23
> +#define K3_PDMA_SSPA1_RX 24
> +#define K3_PDMA_SSPA2_TX 56
> +#define K3_PDMA_SSPA2_RX 57
> +#define K3_PDMA_SSPA3_TX 58
> +#define K3_PDMA_SSPA3_RX 59
> +#define K3_PDMA_SSPA4_TX 60
> +#define K3_PDMA_SSPA4_RX 61
> +#define K3_PDMA_SSPA5_TX 62
> +#define K3_PDMA_SSPA5_RX 63
> +
> +/* CAN DMA request numbers */
> +#define K3_PDMA_CAN0_RX 43
> +#define K3_PDMA_CAN1_RX 44
> +#define K3_PDMA_CAN2_RX 51
> +#define K3_PDMA_CAN3_RX 52
> +
> +/* SSP0/1 DMA request numbers */
> +#define K3_PDMA_SSP0_TX 64
> +#define K3_PDMA_SSP0_RX 65
> +#define K3_PDMA_SSP1_TX 66
> +#define K3_PDMA_SSP1_RX 67
> +
> +/* QSPI DMA request numbers */
> +#define K3_PDMA_QSPI_RX 84
> +#define K3_PDMA_QSPI_TX 85
> +
> +#endif /* _DTS_SPACEMIT_K3_PDMA_H */
>
> --
> 2.53.0
>
--
Yixun Lan (dlan)
next prev parent reply other threads:[~2026-07-25 13:15 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-17 14:45 [PATCH 0/4] spi: spacemit: support K3 SPI controllers Zhengyu He
2026-07-17 14:45 ` [PATCH 1/4] riscv: dts: spacemit: add K3 PDMA request numbers Zhengyu He
2026-07-25 13:15 ` Yixun Lan [this message]
2026-07-17 14:45 ` [PATCH 2/4] spi: dt-bindings: spacemit: add K3 SPI compatible Zhengyu He
2026-07-17 14:45 ` [PATCH 3/4] riscv: dts: spacemit: add SPI controllers for K3 Zhengyu He
2026-07-25 13:15 ` Yixun Lan
2026-07-17 14:45 ` [PATCH 4/4] riscv: dts: spacemit: enable SPI0 on K3 CoM260-IFX Zhengyu He
2026-07-17 14:51 ` sashiko-bot
2026-07-25 13:13 ` Yixun Lan
2026-07-21 21:41 ` (subset) [PATCH 0/4] spi: spacemit: support K3 SPI controllers Mark Brown
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=20260725131555-GKF77545@kernel.org \
--to=dlan@kernel.org \
--cc=alex@ghiti.fr \
--cc=aou@eecs.berkeley.edu \
--cc=broonie@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=docular.xu@gmail.com \
--cc=elder@kernel.org \
--cc=hezhy472013@gmail.com \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=linux-spi@vger.kernel.org \
--cc=palmer@dabbelt.com \
--cc=pjw@kernel.org \
--cc=robh@kernel.org \
--cc=spacemit@lists.linux.dev \
--cc=wefu@redhat.com \
--cc=yeshan.li@spacemit.com \
/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