From: Claudiu Beznea <claudiu.beznea@tuxon.dev>
To: Pavel Machek <pavel@denx.de>
Cc: Biju Das <biju.das.jz@bp.renesas.com>,
"nobuhiro1.iwamatsu@toshiba.co.jp"
<nobuhiro1.iwamatsu@toshiba.co.jp>,
"cip-dev@lists.cip-project.org" <cip-dev@lists.cip-project.org>
Subject: Re: [cip-dev] [PATCH 5.10.y-cip 00/22] RZ/{G2L, G2LC, G2UL, G3S, Five, V2L}: Backport MSTOP support
Date: Mon, 24 Nov 2025 15:21:07 +0200 [thread overview]
Message-ID: <33863cee-c6ab-4b3d-9bcf-82ef2c8b597c@tuxon.dev> (raw)
In-Reply-To: <aSQvAIPPOVe7dAuF@duo.ucw.cz>
Hi, Pavel,
On 11/24/25 12:10, Pavel Machek wrote:
> Hi!
>
>>>>>> I'm going to send a PoC patch for the media drivers used by the
>>>>>> RZ/{G2L, G2LC, G2UL, V2L} SoCs in reply to this thread. Please let me
>>>>>> know how do you consider this approach.
>>>>>
>>>>> I'll take a look, but if mainline is happy, likely I'll be happy, too.
>>>>
>>>> In mainline the problem is already fixed by patches 01-11 from this series.
>>>> The PoC patch that I sent is intended for CIP kernels only, and, along with it, all the other drivers
>>>> used by the RZ/{G2L, G2LC, G2UL, G3S, Five, V2L} SoCs will have to be patched with something similar.
>>>
>>>
>>> What to do with Mali driver used in RZ/{G2L, G2LC, V2L} ? Mali driver is used by other vendors as well.
>>> Maybe special handling??
>>
>> DT nodes for the Mali IP on RZ/{G2L, G2LC, V2L} have Renesas compatibles.
>> Taking into account these compatibles, the code could be adjusted to be
>> executed only for the Renesas SoCs.
>
> Ok, so we have two solutions:
>
> 1) one requires small changes to unrelated drivers in the tree
>
> 2) one that is only touching Renesas code, but is not mainline, an is
> not going mainline
>
> Neither is good. I don't believe there's another possibility?
I don't know another one at the moment, too.
>
> I'd still like to know how much power this saves, and if we really
> need to have this in 5.10.
I'll ask internal HW team about it and. In parallel, I'll try on my side to
check the exposed board rails to see if there is any diff in terms of power
consumption w/ and w/o this feature.
>
> It looks to me like 1) is less bad, and we may have to live with it,
> but I'd like to get confirmation from other stakeholders at this
> point.I t may be best discussed at thursday's IRC meeting. (Do you
> want to join? :-) ).
I'll be there.
Thank you,
Claudiu
next prev parent reply other threads:[~2025-11-24 13:21 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-06 8:11 [PATCH 5.10.y-cip 00/22] RZ/{G2L, G2LC, G2UL, G3S, Five, V2L}: Backport MSTOP support Claudiu
2025-11-06 8:11 ` [PATCH 5.10.y-cip 01/22] PM: domains: Add flags to specify power on attach/detach Claudiu
2025-11-06 8:11 ` [PATCH 5.10.y-cip 02/22] of: Add of_machine_compatible_match() Claudiu
2025-11-06 8:11 ` [PATCH 5.10.y-cip 03/22] PM: domains: Add helper to check for PM domain detach on unbind cleanup Claudiu
2025-11-06 8:12 ` [PATCH 5.10.y-cip 04/22] PM: domains: Detach on device_unbind_cleanup() Claudiu
2025-11-06 8:12 ` [PATCH 5.10.y-cip 05/22] driver core: platform: Drop dev_pm_domain_detach() call Claudiu
2025-11-06 8:12 ` [PATCH 5.10.y-cip 06/22] mmc: sdio: " Claudiu
2025-11-06 8:12 ` [PATCH 5.10.y-cip 07/22] spi: " Claudiu
2025-11-06 8:12 ` [PATCH 5.10.y-cip 08/22] rpmsg: core: " Claudiu
2025-11-06 8:12 ` [PATCH 5.10.y-cip 09/22] soundwire: bus: " Claudiu
2025-11-06 8:12 ` [PATCH 5.10.y-cip 10/22] serdev: " Claudiu
2025-11-06 8:12 ` [PATCH 5.10.y-cip 11/22] i2c: core: " Claudiu
2025-11-06 8:12 ` [PATCH 5.10.y-cip 12/22] clk: renesas: rzg2l: Extend power domain support Claudiu
2025-11-06 8:12 ` [PATCH 5.10.y-cip 13/22] clk: renesas: rzg2l: Postpone updating priv->clks[] Claudiu
2025-11-06 8:12 ` [PATCH 5.10.y-cip 14/22] clk: renesas: rzg2l: Move pointers after hw member Claudiu
2025-11-06 8:12 ` [PATCH 5.10.y-cip 15/22] clk: renesas: rzg2l: Add macro to loop through module clocks Claudiu
2025-11-06 8:12 ` [PATCH 5.10.y-cip 16/22] clk: renesas: rzg2l: Add support for MSTOP in clock enable/disable API Claudiu
2025-11-06 8:12 ` [PATCH 5.10.y-cip 17/22] clk: renesas: r9a08g045: Drop power domain instantiation Claudiu
2025-11-06 8:12 ` [PATCH 5.10.y-cip 18/22] clk: renesas: r9a08g045: Add MSTOP for coupled clocks as well Claudiu
2025-11-06 8:12 ` [PATCH 5.10.y-cip 19/22] clk: renesas: r9a08g045: Add MSTOP for GPIO Claudiu
2025-11-06 8:12 ` [PATCH 5.10.y-cip 20/22] clk: renesas: r9a07g044: Add MSTOP for RZ/G2L Claudiu
2025-11-06 8:12 ` [PATCH 5.10.y-cip 21/22] clk: renesas: r9a07g043: Add MSTOP for RZ/G2UL Claudiu
2025-11-06 8:12 ` [PATCH 5.10.y-cip 22/22] clk: renesas: r9a07g04[34]: Use tabs instead of spaces Claudiu
2025-11-06 19:23 ` [PATCH 5.10.y-cip 00/22] RZ/{G2L, G2LC, G2UL, G3S, Five, V2L}: Backport MSTOP support Pavel Machek
2025-11-07 10:06 ` Claudiu Beznea
[not found] ` <1875B18477989308.416970@lists.cip-project.org>
2025-11-11 8:47 ` [cip-dev] " Claudiu Beznea
2025-11-21 12:47 ` Claudiu Beznea
2025-11-21 12:50 ` [PATCH] drm: renesas: Open/close devres_group on probe/remove Claudiu
2025-11-21 13:43 ` [cip-dev] [PATCH 5.10.y-cip 00/22] RZ/{G2L, G2LC, G2UL, G3S, Five, V2L}: Backport MSTOP support Pavel Machek
2025-11-21 13:55 ` Claudiu Beznea
2025-11-23 9:15 ` Biju Das
2025-11-24 8:03 ` Claudiu Beznea
2025-11-24 10:10 ` Pavel Machek
2025-11-24 13:21 ` Claudiu Beznea [this message]
2025-11-28 12:02 ` Pavel Machek
2025-11-28 14:54 ` Claudiu Beznea
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=33863cee-c6ab-4b3d-9bcf-82ef2c8b597c@tuxon.dev \
--to=claudiu.beznea@tuxon.dev \
--cc=biju.das.jz@bp.renesas.com \
--cc=cip-dev@lists.cip-project.org \
--cc=nobuhiro1.iwamatsu@toshiba.co.jp \
--cc=pavel@denx.de \
/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