Thread (98 messages) 98 messages, 7 authors, 2024-11-07

RE: [PATCH 00/16] Add initial USB support for the Renesas RZ/G3S SoC

From: Biju Das <biju.das.jz@bp.renesas.com>
Date: 2024-09-03 11:07:10
Also in: linux-clk, linux-devicetree, linux-phy, linux-pm, linux-renesas-soc, linux-usb, lkml

Hi Claudiu,
-----Original Message-----
From: claudiu beznea <claudiu.beznea@tuxon.dev>
Sent: Tuesday, September 3, 2024 12:00 PM
Subject: Re: [PATCH 00/16] Add initial USB support for the Renesas RZ/G3S SoC



On 03.09.2024 13:31, Biju Das wrote:
quoted
quoted
quoted
During boot clr USB PWR READY signal in TF-A.
STR case, suspend set USB PWR READY signal in TF-A.
STR case, resume clr USB PWR READY signal in TF-A.
As I said previously, it can be done in different ways. My point was
to let Linux set what it needs for all it's devices to work. I think the way to go forward is a
maintainer decision.
quoted
I agree, there can be n number of solution for a problem.

Since you modelled system state signal (USB PWRRDY) as reset control
signal, it is reset/DT maintainer's decision to say the final word whether this signal fits in reset
system framework or not?

I was thinking:
1/ Geert would be the best to say if he considers it OK to handle this
   in Linux
I agree Geert is the right person for taking SYSTEM decisions,
since the signal is used only during state transitions
(Table 41.6.4 AWO to ALL_ON and 41.6.3 ALL_ON to AWO)

2/ if OK, then we should get approval from Ulf and Philipp on the power
   domain or reset approaches
Ok.

Cheers,
Biju
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help