From: Claudiu Beznea <claudiu.beznea@tuxon.dev>
To: Biju Das <biju.das.jz@bp.renesas.com>,
"vkoul@kernel.org" <vkoul@kernel.org>,
Prabhakar Mahadev Lad <prabhakar.mahadev-lad.rj@bp.renesas.com>,
"lgirdwood@gmail.com" <lgirdwood@gmail.com>,
"broonie@kernel.org" <broonie@kernel.org>,
"perex@perex.cz" <perex@perex.cz>,
"tiwai@suse.com" <tiwai@suse.com>,
"p.zabel@pengutronix.de" <p.zabel@pengutronix.de>,
"geert+renesas@glider.be" <geert+renesas@glider.be>,
Fabrizio Castro <fabrizio.castro.jz@renesas.com>
Cc: "dmaengine@vger.kernel.org" <dmaengine@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-sound@vger.kernel.org" <linux-sound@vger.kernel.org>,
"linux-renesas-soc@vger.kernel.org"
<linux-renesas-soc@vger.kernel.org>,
Claudiu Beznea <claudiu.beznea.uj@bp.renesas.com>
Subject: Re: [PATCH 5/7] dmaengine: sh: rz-dmac: Add suspend to RAM support
Date: Thu, 5 Feb 2026 15:00:13 +0200 [thread overview]
Message-ID: <7f0305f6-ae2d-4069-b53a-d2a81e75d164@tuxon.dev> (raw)
In-Reply-To: <TY3PR01MB11346C8AD27554E40EC5746E38693A@TY3PR01MB11346.jpnprd01.prod.outlook.com>
Hi, Biju,
On 1/26/26 17:28, Biju Das wrote:
> Hi All,
>
>> -----Original Message-----
>> From: Biju Das
>> Sent: 26 January 2026 13:12
>> Subject: RE: [PATCH 5/7] dmaengine: sh: rz-dmac: Add suspend to RAM support
>>
[ ... ]
>>
>> For s2idle issue on RZ/G3L is DMA device is in asserted state, not forwarding any IRQ to cpu for
>> wakeup.
>>
>> For S2RAM issue on RZ/G3L is during suspend hardware turns DMAACLK off/ Asserted state. Clock framwork
>> is not turning On DMAACLK as it critical clk.
>>
>> Can you please check your TF-A for the second case? First case, RZ/G3S may ok for reset assert state,
>> it can forward IRQs to CPU.
>
> Just to summarize, currently there are 2 differences identified between RZ/G3S and RZ/G3L:
>
> SoC differences for s2idle:
>
> RZ/G3S: Can wake the system if the DMA device is in the assert state
>
> RZ/G3L: Cannot wake the system if the DMA device is in the assert state.
>
>
> TF-A differences for s2ram:
>
> RZ/G3S: TF_A turns on DMA_ACLK during boot/resume.
>
> RZ/G3L: TF_A does not handle DMA_ACLK during boot/resume.
I'm seeing at [1] you are addressing these differences in the clock/reset
drivers. With that, are you still considering this patch is breaking your system?
Thank you,
Claudiu
[1] https://lore.kernel.org/all/20260130143456.256813-1-biju.das.jz@bp.renesas.com
next prev parent reply other threads:[~2026-02-05 13:00 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-26 10:31 [PATCH 0/7] Renesas: dmaengine and ASoC fixes Claudiu
2026-01-26 10:31 ` [PATCH 1/7] dmaengine: sh: rz-dmac: Add enable status bit Claudiu
2026-01-26 10:31 ` [PATCH 2/7] dmaengine: sh: rz-dmac: Add pause " Claudiu
2026-01-26 10:31 ` [PATCH 3/7] dmaengine: sh: rz-dmac: Drop the update of CHCTRL_SETEN in channel->chctrl APIs Claudiu
2026-01-26 10:31 ` [PATCH 4/7] dmaengine: sh: rz-dmac: Add cyclic DMA support Claudiu
2026-01-26 10:31 ` [PATCH 5/7] dmaengine: sh: rz-dmac: Add suspend to RAM support Claudiu
2026-01-26 11:03 ` Biju Das
2026-01-26 12:04 ` Claudiu Beznea
2026-01-26 12:10 ` Biju Das
2026-01-26 12:39 ` Claudiu Beznea
2026-01-26 12:51 ` Biju Das
2026-01-26 13:06 ` Biju Das
2026-01-26 13:07 ` Claudiu Beznea
2026-01-26 13:12 ` Biju Das
2026-01-26 15:28 ` Biju Das
2026-02-05 13:00 ` Claudiu Beznea [this message]
2026-02-05 13:30 ` Biju Das
2026-02-05 13:33 ` Geert Uytterhoeven
2026-02-05 14:06 ` Biju Das
2026-02-05 17:20 ` Claudiu Beznea
2026-02-05 17:41 ` Biju Das
2026-02-06 7:25 ` Biju Das
2026-02-06 9:58 ` Claudiu Beznea
2026-02-06 10:08 ` Biju Das
2026-03-12 10:07 ` Biju Das
2026-03-12 12:26 ` Tommaso Merciai
2026-03-16 14:02 ` claudiu beznea
2026-01-26 10:31 ` [PATCH 6/7] ASoC: renesas: rz-ssi: Use generic PCM dmaengine APIs Claudiu
2026-01-26 14:26 ` Geert Uytterhoeven
2026-01-26 14:46 ` Claudiu Beznea
2026-01-26 10:31 ` [PATCH 7/7] dmaengine: sh: rz-dmac: Set the Link End (LE) bit on the last descriptor Claudiu
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=7f0305f6-ae2d-4069-b53a-d2a81e75d164@tuxon.dev \
--to=claudiu.beznea@tuxon.dev \
--cc=biju.das.jz@bp.renesas.com \
--cc=broonie@kernel.org \
--cc=claudiu.beznea.uj@bp.renesas.com \
--cc=dmaengine@vger.kernel.org \
--cc=fabrizio.castro.jz@renesas.com \
--cc=geert+renesas@glider.be \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=p.zabel@pengutronix.de \
--cc=perex@perex.cz \
--cc=prabhakar.mahadev-lad.rj@bp.renesas.com \
--cc=tiwai@suse.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