mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Vinod Koul <vkoul@kernel.org>
To: tglx@kernel.org, John Madieu <john.madieu.xa@bp.renesas.com>
Cc: Frank.Li@kernel.org, claudiu.beznea.uj@bp.renesas.com,
	 biju.das.jz@bp.renesas.com, geert+renesas@glider.be,
	 cosmin-gabriel.tanislav.xa@renesas.com,
	dmaengine@vger.kernel.org,  linux-kernel@vger.kernel.org,
	john.madieu@gmail.com
Subject: Re: [PATCH v4 0/2] Add DMA ACK signal routing for RZ/V2H family
Date: Mon, 08 Jun 2026 17:43:13 +0530	[thread overview]
Message-ID: <178092079307.96550.9925462090761726451.b4-ty@kernel.org> (raw)
In-Reply-To: <20260525110750.4020112-1-john.madieu.xa@bp.renesas.com>


On Mon, 25 May 2026 11:07:48 +0000, John Madieu wrote:
> Some peripherals on RZ/V2H, RZ/V2N, and RZ/G3E SoCs require explicit
> DMA ACK signal routing through the ICU for level-based DMA handshaking.
> 
> Rather than encoding the ACK signal number as a second DMA specifier
> cell, derive it in-driver from the MID/RID request number using
> arithmetic formulas based on ICU Table 4.6-28 (3 linear peripheral
> groups). It must also be noted that DMA ack register is located in
> the ICU block
> 
> [...]

Applied, thanks!

[1/2] irqchip/renesas-rzv2h: Add DMA ACK signal routing support
      commit: 5d596b9139f59ce412f41283baadaf809936eaf4
[2/2] dma: sh: rz-dmac: Add DMA ACK signal routing support
      commit: c0a207898fca8cbb4fad0da1e950d477b6afbf64

Best regards,
-- 
~Vinod



      parent reply	other threads:[~2026-06-08 12:13 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-25 11:07 John Madieu
2026-05-25 11:07 ` [PATCH v4 1/2] irqchip/renesas-rzv2h: Add DMA ACK signal routing support John Madieu
2026-05-25 11:07 ` [PATCH v4 2/2] dma: sh: rz-dmac: " John Madieu
2026-06-08 12:13 ` 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=178092079307.96550.9925462090761726451.b4-ty@kernel.org \
    --to=vkoul@kernel.org \
    --cc=Frank.Li@kernel.org \
    --cc=biju.das.jz@bp.renesas.com \
    --cc=claudiu.beznea.uj@bp.renesas.com \
    --cc=cosmin-gabriel.tanislav.xa@renesas.com \
    --cc=dmaengine@vger.kernel.org \
    --cc=geert+renesas@glider.be \
    --cc=john.madieu.xa@bp.renesas.com \
    --cc=john.madieu@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tglx@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

all inboxes | Powered by JetHome®