From: Frank Li <Frank.li@nxp.com>
To: John Madieu <john.madieu.xa@bp.renesas.com>
Cc: Vinod Koul <vkoul@kernel.org>, Frank Li <Frank.Li@kernel.org>,
Thomas Gleixner <tglx@kernel.org>,
Geert Uytterhoeven <geert+renesas@glider.be>,
Fabrizio Castro <fabrizio.castro.jz@renesas.com>,
Claudiu Beznea <claudiu.beznea@tuxon.dev>,
Biju Das <biju.das.jz@bp.renesas.com>,
Lad Prabhakar <prabhakar.mahadev-lad.rj@bp.renesas.com>,
Cosmin Tanislav <cosmin-gabriel.tanislav.xa@renesas.com>,
john.madieu@gmail.com, linux-renesas-soc@vger.kernel.org,
dmaengine@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCh v3 2/2] dma: sh: rz-dmac: Add DMA ACK signal routing support
Date: Thu, 7 May 2026 14:49:11 -0400 [thread overview]
Message-ID: <afzep7hF8uj-jRhc@lizhi-Precision-Tower-5810> (raw)
In-Reply-To: <20260402162212.12016-3-john.madieu.xa@bp.renesas.com>
On Thu, Apr 02, 2026 at 06:22:12PM +0200, John Madieu wrote:
> Some peripherals on RZ/G3E SoCs (SSIU, SPDIF, SCU/SRC, DVC, PFC)
> require explicit ACK signal routing through the ICU for level-based DMA
> handshaking.
>
> Rather than extending the DT binding with an optional second #dma-cells
> (which would require all DMA consumers to supply two cells even when ACK
> routing is not needed), derive the ACK signal number directly from the
> MID/RID request number using the linear mapping defined in RZ/G3E hardware
> manual Table 4.6-28:
>
> PFC external DMA pins (DREQ0..DREQ4):
> req_no 0x000-0x004 -> ACK No. 84-88
>
> SSIU BUSIFs (ssip00..ssip93):
> req_no 0x161-0x198 -> ACK No. 28-83
>
> SPDIF (CH0..CH2) + SCU SRC (sr0..sr9) + DVC (cmd0..cmd1):
> req_no 0x199-0x1b4 -> ACK No. 0-27
>
> ACK routing is programmed when a channel is prepared for transfer and
> cleared when the channel is released or the transfer times out, following
> the same pattern as MID/RID request routing.
>
> Signed-off-by: John Madieu <john.madieu.xa@bp.renesas.com>
> ---
>
> Changes:
>
> v3: No changes
>
> v2:
> - Drop DMA ACK second cell from DT specifier
> - Derive ACK signal number in-driver from MID/RID using arithmetic formulas
> per ICU Table 4.6-28 (3 linear peripheral groups)
>
> drivers/dma/sh/rz-dmac.c | 72 ++++++++++++++++++++++++++++++++++++++++
> 1 file changed, 72 insertions(+)
>
> static void rz_dmac_prepare_desc_for_memcpy(struct rz_dmac_chan *channel)
> {
> struct dma_chan *chan = &channel->vc.chan;
> @@ -431,6 +489,7 @@ static void rz_dmac_prepare_descs_for_slave_sg(struct rz_dmac_chan *channel)
> channel->lmdesc.tail = lmdesc;
>
> rz_dmac_set_dma_req_no(dmac, channel->index, channel->mid_rid);
> + rz_dmac_set_dma_ack_no(dmac, channel->index, channel->dmac_ack);
I am not familar with your hardware, why ACK folllow req immediately?
suppose ACK happen after transfer done.
If ACK need after req, why not add ack handle in rz_dmac_set_dma_req_no()
directly.
Frank
> --
> 2.25.1
>
prev parent reply other threads:[~2026-05-07 18:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-02 16:22 [PATCh v3 0/2] Add DMA ACK signal routing for RZ/V2H family John Madieu
2026-04-02 16:22 ` [PATCh v3 1/2] irqchip/renesas-rzv2h: Add DMA ACK signal routing support John Madieu
2026-04-29 7:23 ` Thomas Gleixner
2026-04-02 16:22 ` [PATCh v3 2/2] dma: sh: rz-dmac: " John Madieu
2026-05-07 18:49 ` Frank Li [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=afzep7hF8uj-jRhc@lizhi-Precision-Tower-5810 \
--to=frank.li@nxp.com \
--cc=Frank.Li@kernel.org \
--cc=biju.das.jz@bp.renesas.com \
--cc=claudiu.beznea@tuxon.dev \
--cc=cosmin-gabriel.tanislav.xa@renesas.com \
--cc=dmaengine@vger.kernel.org \
--cc=fabrizio.castro.jz@renesas.com \
--cc=geert+renesas@glider.be \
--cc=john.madieu.xa@bp.renesas.com \
--cc=john.madieu@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=prabhakar.mahadev-lad.rj@bp.renesas.com \
--cc=tglx@kernel.org \
--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