From: Yixun Lan <dlan@gentoo.org>
To: Vivian Wang <wangruikang@iscas.ac.cn>
Cc: Guodong Xu <guodong@riscstar.com>, Ze Huang <huangze@whut.edu.cn>,
Alex Elder <elder@riscstar.com>,
spacemit@lists.linux.dev, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Paul Walmsley <paul.walmsley@sifive.com>,
Palmer Dabbelt <palmer@dabbelt.com>,
Albert Ou <aou@eecs.berkeley.edu>,
Alexandre Ghiti <alex@ghiti.fr>, Vivian Wang <uwu@dram.page>,
devicetree@vger.kernel.org, linux-riscv@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/3] riscv: dts: spacemit: Add DMA translation buses for K1
Date: Wed, 9 Jul 2025 06:40:09 +0000 [thread overview]
Message-ID: <20250709064009-GYB487904@gentoo> (raw)
In-Reply-To: <20250623-k1-dma-buses-rfc-wip-v1-0-c0144082061f@iscas.ac.cn>
On 18:04 Mon 23 Jun , Vivian Wang wrote:
> The SpacemiT K1 has various static translations of DMA accesses. This
> series adds all the DMA translation bus nodes and also moves existing
> nodes as necessary.
>
> According to SpacemiT DT maintainer Yixun Lan [1], it's preferable from
> a SoC DT maintainer's perspective to have this done at once instead of
> spreading these changes into various driver series. Once this is merged,
> life will be easier for future users of the buses.
>
> This series contains no bindings changes.
>
> Patch 3 moves the eMMC node added in [1].
>
> These patches can also be pulled from:
>
> https://github.com/dramforever/linux/tree/k1/dma-ranges/v1
>
> [1]: https://lore.kernel.org/r/20250623070147-GYA193822@gentoo
> [2]: https://lore.kernel.org/r/20250523-22-k1-sdhci-v1-1-6e0adddf7494@gentoo.org
>
Hi Krzysztof,
Just want to clarify, I believe you previous concern about the
"children of simple-bus are supposed to have unit addresses" [3] isn't
really an issue any more.. but, please let me know if I'm wrong..
Hi Vivian,
We'd like to push this series for v6.17, so I've queued it at
k1/dt-for-next branch of SpacemiT SoC tree [4] for now, FYI.
Link: https://lore.kernel.org/all/2dc8ab35-4f58-49d3-8e8b-3e463fa592ae@kernel.org/ [3]
Link: https://github.com/spacemit-com/linux/tree/k1/dt-for-next [4]
Thanks all
--
Yixun Lan (dlan)
next prev parent reply other threads:[~2025-07-09 6:40 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-23 10:04 [PATCH 0/3] riscv: dts: spacemit: Add DMA translation buses for K1 Vivian Wang
2025-06-23 10:04 ` [PATCH 1/3] " Vivian Wang
2025-06-26 7:54 ` Guodong Xu
2025-06-23 10:04 ` [PATCH 2/3] riscv: dts: spacemit: Move UARTs under dma-bus " Vivian Wang
2025-06-24 12:21 ` Guodong Xu
2025-06-24 12:51 ` Vivian Wang
2025-06-25 3:21 ` Vivian Wang
2025-06-26 7:58 ` Guodong Xu
2025-06-23 10:04 ` [PATCH 3/3] riscv: dts: spacemit: Move eMMC under storage-bus " Vivian Wang
2025-07-09 6:40 ` Yixun Lan [this message]
2025-07-09 7:17 ` [PATCH 0/3] riscv: dts: spacemit: Add DMA translation buses " Vivian Wang
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=20250709064009-GYB487904@gentoo \
--to=dlan@gentoo.org \
--cc=alex@ghiti.fr \
--cc=aou@eecs.berkeley.edu \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=elder@riscstar.com \
--cc=guodong@riscstar.com \
--cc=huangze@whut.edu.cn \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=robh@kernel.org \
--cc=spacemit@lists.linux.dev \
--cc=uwu@dram.page \
--cc=wangruikang@iscas.ac.cn \
/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