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>,
Geert Uytterhoeven <geert+renesas@glider.be>,
Magnus Damm <magnus.damm@gmail.com>,
dmaengine@vger.kernel.org
Subject: Re: [PATCH 2/4] dmaengine: sh: rcar-dmac: SMMU doesn't need IPMMU workaround
Date: Sun, 6 Sep 2026 23:47:37 +0200 [thread overview]
Message-ID: <ap3fdT-0J3TUalMQ@shikoro> (raw)
In-Reply-To: <CAMuHMdXj14sZXrcPhNA7HZ8+nB9FYypcOhNEYpkhYj7YZsMQhg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1633 bytes --]
> > struct rcar_dmac_of_data {
> > u32 chan_offset_base;
> > u32 chan_offset_stride;
> > + unsigned int has_ipmmu:1;
>
> broken_ipmmu_microTLB_0?
Yes, that's a better name.
> > @@ -2000,11 +2003,13 @@ static void rcar_dmac_shutdown(struct platform_device *pdev)
> > static const struct rcar_dmac_of_data rcar_dmac_data = {
> > .chan_offset_base = 0x8000,
> > .chan_offset_stride = 0x80,
> > + .has_ipmmu = 1,
>
> The issue this fixes was seen on R-Car H2 and M2-W.
> R-Car H3 ES1.0 already existed at that time, so R-Car Gen3 might be
> affected or not.
Yes...
>
> > };
> >
> > static const struct rcar_dmac_of_data rcar_gen4_dmac_data = {
> > .chan_offset_base = 0x0,
> > .chan_offset_stride = 0x1000,
> > + .has_ipmmu = 1,
>
> Let's hope this issue was fixed in R-Car Gen4. Perhaps someone can
> verify this using the test Laurent shared[1] a long time ago?
... I also envisioned future updates once we find out if Gen3/4 are
affected. But for now, enabling Gen5 has priority and this is what this
series does. Rest can be done incrementally.
> > static const struct of_device_id rcar_dmac_of_ids[] = {
>
> [1] https://lore.kernel.org/1422137953-30156-1-git-send-email-laurent.pinchart+renesas@ideasonboard.com
Ah, I didn't find this one. The commit/branch still exists today :)
https://git.linuxtv.org/pinchartl/media.git/commit/?h=dma/iommu/debug&id=86db1ee12532f8de2bca02c0bab77ad7619ef7f2
Unsurprisingly, cherry-picking it (10 years old) to v7.3-rc1 is a mess.
I suggest to postpone this...
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2026-09-06 21:47 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 [this message]
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
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=ap3fdT-0J3TUalMQ@shikoro \
--to=wsa+renesas@sang-engineering.com \
--cc=Frank.Li@kernel.org \
--cc=dmaengine@vger.kernel.org \
--cc=geert+renesas@glider.be \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.