From: Wolfram Sang <wsa+renesas@sang-engineering.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: linux-renesas-soc@vger.kernel.org,
Biju Das <biju.das.jz@bp.renesas.com>,
Conor Dooley <conor+dt@kernel.org>,
devicetree@vger.kernel.org, dmaengine@vger.kernel.org,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Magnus Damm <magnus.damm@gmail.com>,
Philipp Zabel <p.zabel@pengutronix.de>,
Rob Herring <robh@kernel.org>, Vinod Koul <vkoul@kernel.org>,
Linux MMC List <linux-mmc@vger.kernel.org>
Subject: Re: [PATCH v2 0/3] dmaengine: sh: rz-dmac: add r7s72100 support
Date: Fri, 15 Nov 2024 18:08:49 +0100 [thread overview]
Message-ID: <ZzeAIQe1zdoNYkyO@ninjato> (raw)
In-Reply-To: <CAMuHMdW5PhRT0B+ua=MyTeTZF+BOFEzQ8XyWtBGOiU+YKbathg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 459 bytes --]
> I am not sure if the SDHI driver or the RZ-DMAC driver (or virt-dma)
> should be fixed, as the documentation[1] states:
>
> Note that callbacks will always be invoked from the DMA
> engines tasklet, never from interrupt context.
Back then, I had the impression that we can rework the SDHI SYSDMAC part
to not use a completion like the internal DMAC version does. But it has
been a while and I got completely side-tracked meanwhile.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2024-11-15 17:08 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-01 12:43 [PATCH v2 0/3] dmaengine: sh: rz-dmac: add r7s72100 support Wolfram Sang
2024-10-01 12:43 ` [PATCH v2 2/3] dt-bindings: dma: rz-dmac: Document RZ/A1H SoC Wolfram Sang
2024-10-02 6:19 ` Krzysztof Kozlowski
2024-10-02 6:37 ` Wolfram Sang
2024-10-04 14:46 ` Geert Uytterhoeven
2024-10-04 19:57 ` Wolfram Sang
2024-10-07 7:30 ` Geert Uytterhoeven
2024-10-07 7:34 ` Geert Uytterhoeven
2024-11-15 14:47 ` [PATCH v2 0/3] dmaengine: sh: rz-dmac: add r7s72100 support Geert Uytterhoeven
2024-11-15 17:08 ` 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=ZzeAIQe1zdoNYkyO@ninjato \
--to=wsa+renesas@sang-engineering.com \
--cc=biju.das.jz@bp.renesas.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmaengine@vger.kernel.org \
--cc=geert@linux-m68k.org \
--cc=krzk+dt@kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=p.zabel@pengutronix.de \
--cc=robh@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;
as well as URLs for NNTP newsgroup(s).