From: Wolfram Sang <wsa+renesas@sang-engineering.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: linux-renesas-soc@vger.kernel.org, Vinod Koul <vkoul@kernel.org>,
Frank Li <Frank.Li@kernel.org>,
Magnus Damm <magnus.damm@gmail.com>,
dmaengine@vger.kernel.org
Subject: Re: [PATCH 4/4] dmaengine: sh: rcar-dmac: Add support for R-Car Gen5 SoCs
Date: Sun, 6 Sep 2026 23:48:35 +0200 [thread overview]
Message-ID: <ap3fs0Ay25nRxCzF@shikoro> (raw)
In-Reply-To: <CAMuHMdWAL+B7RchaV+PMDT7XbQvXz1WZ82B0EZXcH8VLBEbL+w@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 302 bytes --]
> > + .compatible = "renesas,rcar-gen5-dmac",
> > + .data = &rcar_gen5_dmac_data,
>
> I expect this can just point to rcar_gen4_dmac_data, once we have
> confirmed the IPMMU issue does not impact R-Car Gen4.
I'd be more than happy if this is the case somewhen.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2026-09-06 21:48 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-25 14:15 [PATCH 0/4] dmaengine: sh: rcar-dmac: add R-Car Gen5 X5H support Wolfram Sang
2026-08-25 14:15 ` [PATCH 1/4] dmaengine: sh: rcar-dmac: fix style in struct initialization Wolfram Sang
2026-08-25 15:35 ` Frank Li
2026-09-04 12:29 ` Geert Uytterhoeven
2026-08-25 14:15 ` [PATCH 2/4] dmaengine: sh: rcar-dmac: SMMU doesn't need IPMMU workaround Wolfram Sang
2026-08-25 15:37 ` Frank Li
2026-09-04 12:44 ` Geert Uytterhoeven
2026-09-06 21:47 ` Wolfram Sang
2026-08-25 14:15 ` [PATCH 3/4] dt-bindings: renesas,rcar-dmac: Add support for R-Car X5H SoC Wolfram Sang
2026-08-28 10:12 ` Krzysztof Kozlowski
2026-09-04 12:59 ` Geert Uytterhoeven
2026-08-25 14:15 ` [PATCH 4/4] dmaengine: sh: rcar-dmac: Add support for R-Car Gen5 SoCs Wolfram Sang
2026-08-25 15:40 ` Frank Li
2026-08-26 8:17 ` Wolfram Sang
2026-09-04 13:01 ` Geert Uytterhoeven
2026-09-06 21:48 ` Wolfram Sang [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=ap3fs0Ay25nRxCzF@shikoro \
--to=wsa+renesas@sang-engineering.com \
--cc=Frank.Li@kernel.org \
--cc=dmaengine@vger.kernel.org \
--cc=geert@linux-m68k.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--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