From: Philipp Zabel <p.zabel@pengutronix.de>
To: Tommaso Merciai <tommaso.merciai.xr@bp.renesas.com>,
tomm.merciai@gmail.com, prabhakar.mahadev-lad.rj@bp.renesas.com
Cc: linux-renesas-soc@vger.kernel.org, biju.das.jz@bp.renesas.com,
"Peter Rosin" <peda@lysator.liu.se>,
"Fabrizio Castro" <fabrizio.castro.jz@renesas.com>,
"Alvin Šipraga" <alvin.sipraga@analog.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] reset: rzv2h-usb2phy: Add suspend/resume support
Date: Tue, 03 Nov 2026 12:05:57 +0100 [thread overview]
Message-ID: <9e0d2e4a1f551d2e016975b146b8303508a7a1fe.camel@pengutronix.de> (raw)
In-Reply-To: <da95bad94c99855b960b3566c07671f8c15d5dea.1791389435.git.tommaso.merciai.xr@bp.renesas.com>
On Do, 2026-10-08 at 09:44 +0200, Tommaso Merciai wrote:
> The RZ/V2H(P) USB2PHY reset driver is also used on the RZ/G3E SoC,
> where deep sleep turns off power to the USB2PHY block.
> Part of the initialization sequence written at probe time is cleared,
> leaving the PHY unprepared to receive assert and deassert requests.
>
> Add suspend/resume support to assert the reset on suspend, and to
> deassert it and rewrite the initialization sequence on resume.
>
> Signed-off-by: Tommaso Merciai <tommaso.merciai.xr@bp.renesas.com>
Reviewed-by: Philipp Zabel <p.zabel@pengutronix.de>
Can I apply this independently from patch 2?
regards
Philipp
next prev parent reply other threads:[~2026-11-03 11:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-08 7:44 [PATCH 0/2] Restore RZ/V2H(P) USB2PHY reset and VBENCTL mux state on resume Tommaso Merciai
2026-10-08 7:44 ` [PATCH 1/2] reset: rzv2h-usb2phy: Add suspend/resume support Tommaso Merciai
2026-11-03 11:05 ` Philipp Zabel [this message]
2026-11-03 12:06 ` Tommaso Merciai
2026-10-08 7:44 ` [PATCH 2/2] mux: rzv2h-vbenctl: Add suspend and resume support Tommaso Merciai
2026-11-03 15:12 ` Alvin Šipraga
2026-11-02 14:35 ` [PATCH 0/2] Restore RZ/V2H(P) USB2PHY reset and VBENCTL mux state on resume Tommaso Merciai
2026-11-03 12:37 ` Philipp Zabel
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=9e0d2e4a1f551d2e016975b146b8303508a7a1fe.camel@pengutronix.de \
--to=p.zabel@pengutronix.de \
--cc=alvin.sipraga@analog.com \
--cc=biju.das.jz@bp.renesas.com \
--cc=fabrizio.castro.jz@renesas.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=peda@lysator.liu.se \
--cc=prabhakar.mahadev-lad.rj@bp.renesas.com \
--cc=tomm.merciai@gmail.com \
--cc=tommaso.merciai.xr@bp.renesas.com \
/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
all inboxes | Powered by JetHome®