From: Vinod Koul <vkoul@kernel.org>
To: Inochi Amaoto <inochiama@gmail.com>
Cc: Eugeniy Paltsev <Eugeniy.Paltsev@synopsys.com>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Chen Wang <unicorn_wang@outlook.com>,
Paul Walmsley <pjw@kernel.org>,
Palmer Dabbelt <palmer@dabbelt.com>,
Albert Ou <aou@eecs.berkeley.edu>,
Alexandre Ghiti <alex@ghiti.fr>,
Alexander Sverdlin <alexander.sverdlin@gmail.com>,
Longbin Li <looong.bin@gmail.com>, Ze Huang <huangze@whut.edu.cn>,
dmaengine@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, sophgo@lists.linux.dev,
linux-riscv@lists.infradead.org, Yixun Lan <dlan@kernel.org>
Subject: Re: (subset) [PATCH v3 0/3] riscv: sophgo: allow DMA multiplexer set channel number for DMA controller
Date: Thu, 26 Feb 2026 12:35:50 +0530 [thread overview]
Message-ID: <aZ_wziVgEPGOSAd3@vaman> (raw)
In-Reply-To: <aZ9z0gV8ZrfpL2JG@inochi.infowork>
On 26-02-26, 06:13, Inochi Amaoto wrote:
> On Wed, Feb 25, 2026 at 04:54:13PM +0530, Vinod Koul wrote:
> >
> > On Tue, 20 Jan 2026 09:37:02 +0800, Inochi Amaoto wrote:
> > > As the DMA controller on Sophgo CV1800 series SoC only has 8 channels,
> > > the SoC provides a dma multiplexer to reuse the DMA channel. However,
> > > the dma multiplexer also controlls the DMA interrupt multiplexer, which
> > > means that the dma multiplexer needs to know the channel number.
> > >
> > > Change the DMA phandle args parsing logic so it can use handshake
> > > number as channel number if necessary.
> > >
> > > [...]
> >
> > Applied, thanks!
> >
> > [1/3] dt-bindings: dma: snps,dw-axi-dmac: Add CV1800B compatible
> > commit: 5eda5f42d2fee87127b568206a9fcc07a2f6eab6
> > [2/3] dmaengine: dw-axi-dmac: Add support for CV1800B DMA
> > commit: 02a380ea7ed2d737a42693d7957ec8c33a92d9fd
> >
> > Best regards,
> > --
> > ~Vinod
> >
> >
>
> Hi, Vinod
>
> I guess you applied the version 4, but replied to the version 3?
Nope, I had already picked 3. so reply went on that.
--
~Vinod
prev parent reply other threads:[~2026-02-26 7:05 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-20 1:37 [PATCH v3 0/3] riscv: sophgo: allow DMA multiplexer set channel number for DMA controller Inochi Amaoto
2026-01-20 1:37 ` [PATCH v3 1/3] dt-bindings: dma: snps,dw-axi-dmac: Add CV1800B compatible Inochi Amaoto
2026-01-20 19:56 ` Conor Dooley
2026-02-25 10:30 ` Vinod Koul
2026-02-25 10:43 ` Inochi Amaoto
2026-01-20 1:37 ` [PATCH v3 2/3] dmaengine: dw-axi-dmac: Add support for CV1800B DMA Inochi Amaoto
2026-01-29 22:36 ` Frank Li
2026-01-20 1:37 ` [PATCH v3 3/3] riscv: dts: sophgo: cv180x: Allow the DMA multiplexer to set channel number for DMA controller Inochi Amaoto
2026-02-25 11:24 ` (subset) [PATCH v3 0/3] riscv: sophgo: allow DMA multiplexer " Vinod Koul
2026-02-25 22:13 ` Inochi Amaoto
2026-02-26 7:05 ` Vinod Koul [this message]
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=aZ_wziVgEPGOSAd3@vaman \
--to=vkoul@kernel.org \
--cc=Eugeniy.Paltsev@synopsys.com \
--cc=alex@ghiti.fr \
--cc=alexander.sverdlin@gmail.com \
--cc=aou@eecs.berkeley.edu \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dlan@kernel.org \
--cc=dmaengine@vger.kernel.org \
--cc=huangze@whut.edu.cn \
--cc=inochiama@gmail.com \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=looong.bin@gmail.com \
--cc=palmer@dabbelt.com \
--cc=pjw@kernel.org \
--cc=robh@kernel.org \
--cc=sophgo@lists.linux.dev \
--cc=unicorn_wang@outlook.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