linux-kernel - Re: [PATCH 2/2] reset: rzg2l-usbphy-ctrl: Add suspend/resume support

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <575b271790b267ac4cbbb190b26341656e2c7e0c.camel@pengutronix.de>
Date: Fri, 07 Nov 2025 14:50:19 +0100
From: Philipp Zabel <p.zabel@...gutronix.de>
To: Claudiu <claudiu.beznea@...on.dev>
Cc: linux-renesas-soc@...r.kernel.org, linux-kernel@...r.kernel.org, Claudiu
 Beznea <claudiu.beznea.uj@...renesas.com>
Subject: Re: [PATCH 2/2] reset: rzg2l-usbphy-ctrl: Add suspend/resume support

On Do, 2025-11-06 at 16:33 +0200, Claudiu wrote:
> From: Claudiu Beznea <claudiu.beznea.uj@...renesas.com>
> 
> The RZ/G2L USBPHY control driver is also used on the RZ/G3S SoC.
> The RZ/G3S SoC supports a power-saving mode in which power to most USB
> components (including the USBPHY control block) is turned off. Because of
> this, the USBPHY control block needs to be reconfigured when returning
> from power-saving mode.
> 
> Add suspend/resume support to handle runtime suspend/resume of the device,
> assert/deassert the reset signal, and reinitialize the USBPHY control
> block.
> 
> Signed-off-by: Claudiu Beznea <claudiu.beznea.uj@...renesas.com>
> ---
>  drivers/reset/reset-rzg2l-usbphy-ctrl.c | 94 +++++++++++++++++++++----
>  1 file changed, 79 insertions(+), 15 deletions(-)
> 
> diff --git a/drivers/reset/reset-rzg2l-usbphy-ctrl.c b/drivers/reset/reset-rzg2l-usbphy-ctrl.c
> index 9ce0c1f5d465..8ba65839f6e4 100644
> --- a/drivers/reset/reset-rzg2l-usbphy-ctrl.c
> +++ b/drivers/reset/reset-rzg2l-usbphy-ctrl.c
[...]
> @@ -266,10 +273,67 @@ static void rzg2l_usbphy_ctrl_remove(struct platform_device *pdev)
>  	reset_control_assert(priv->rstc);
>  }
>  
> +static int rzg2l_usbphy_ctrl_suspend(struct device *dev)
> +{
> +	struct rzg2l_usbphy_ctrl_priv *priv = dev_get_drvdata(dev);
> +	int ret;
> +
> +	pm_runtime_put(dev);

Should this be pm_runtime_put_sync(dev)?

> +
> +	ret = reset_control_assert(priv->rstc);
> +	if (ret)
> +		goto rpm_resume;
> +
> +	ret = rzg2l_usbphy_ctrl_set_pwrrdy(priv->pwrrdy, false);

This sets PWRRDY=1, and needs to be set after MSTOP=1,CLK_ON=0,
according to 58128aa88867 ("reset: rzg2l-usbphy-ctrl: Add support for
USB PWRRDY"). I assume MSTOP/CLK_ON refer to the PHY clock in that
description, so the pm_runtime_put() above is required to have taken
effect here.



regards
Philipp