Re: [PATCH] phy: renesas: rcar-gen3-usb2: Avoid long delay in atomic context

[Claudiu Beznea]

Hi, David,

On 5/15/26 12:47, David Laight wrote:
> On Thu, 14 May 2026 23:18:44 +0200
> Pavel Machek <pavel@xxxxxxxxxxxx> wrote:
>
> > Hi!
> >
> > > From: Claudiu Beznea <claudiu.beznea.uj@xxxxxxxxxxxxxx>
> > >
> > > The OTG PHY initialization sequence needs to wait for 20 ms at a specific
> > > step, as described in commit 72c0339c115b ("phy: renesas:
> > > rcar-gen3-usb2: follow the hardware manual procedure").
> > >
> > > Commit 55a387ebb921 ("phy: renesas: rcar-gen3-usb2: Lock around hardware
> > > registers and driver data") tried to address various problems in the
> > > rcar-gen3-usb2 driver and converted the mutex protecting HW register
> > > accesses to a spin lock, leaving, however, a long delay in the critical
> > > section protected by the spin lock. This may become a problem,
> > > especially on RT kernels.
> > >
> > > To address this, release the spin lock before sleeping for 20 ms as
> > > required by the HW manual and reacquire it afterwards. To avoid other
> > > threads entering the critical section and configuring the HW while the
> > > software is waiting for the OTG initialization to complete, introduce the
> > > otg_initializing variable alongside the otg_init_done completion. Any
> > > other thread trying to configure the HW while the OTG PHY initialization
> > > is in progress waits for the completion instead of immediately returning
> > > errors to PHY users. The IRQs were also disabled while waiting for the OTG
> > > PHY initialization to complete, as the interrupt handler may also apply HW
> > > settings.
> >
> > Just... there has to be a better way.
> >
> > > +++ b/drivers/phy/renesas/phy-rcar-gen3-usb2.c
> > > +static int rcar_gen3_phy_wait_otg_init(struct rcar_gen3_chan *channel,
> > > +				       unsigned long *flags)
> > > +{
> > > +	unsigned long timeout = msecs_to_jiffies(25);
> > > +	unsigned long ret = 1;
> > > +
> > > +	lockdep_assert_held(&channel->lock);
> > > +
> > > +	/*
> > > +	 * The OTG can be initialized only once and needs to release the lock
> > > +	 * and wait for 20 ms due to hardware constraints. Wait for the OTG PHY
> > > +	 * initialization to complete if another PHY executes configuration
> > > +	 * code while the OTG PHY is waiting. This avoids returning failures to
> > > +	 * PHY users.
> > > +	 */
> > > +	if (READ_ONCE(channel->otg_initializing)) {
> > > +		spin_unlock_irqrestore(&channel->lock, *flags);
> >
> > This is not nice, passing flags between functions like this is a red flag.
>
> It would be better to just inline the code.

I can do that, I tried to avoid it.

> And I'd guess you need to redo the initial tests after re-acquiring the lock?

Could you please let me know what do you mean by "initial tests"

> Or even need to do a state change/reference count before releasing the
> lock to stop other threads 'doing anything nasty'.

I'm not sure I understand this. I'll explain how the patch works:

The HW provides a single OTG PHY. As the HW has a single OTG PHY and the start 
of the OTG PHY initialization is done under spinlock, at any moment, a single 
thread could set the otg_initializing. That would be the thread configuring the 
OTG PHY. And once the OTG PHY was set there is no way it will run again (due to 
rphy->initialized). Unless the struct phy_ops::exit() is called for the OTG PHY.

With the solution in this patch, once a thread sets the otg_initializing, all 
the other threads that will want to set HW registers should wait due to the 
completion mechanism.

If there is any thread that executes wait_for_completion() while:
- otg_initializing is set and
- the OTG configuration thread released the spin lock to execute the fsleep()
if the wait_for_completion times out, the PHY code returns error to the caller 
so the thread calling into the PHY driver will not continue into the PHY driver.

If instead there is no timeout, the waiting thread will have to re-acquire the 
spin lock before executing any HW settings.

If there is no timeout, the code that setup the OTG PHY have already been 
running rphy->initialized = true for the OTG PHY, under spinlock, and no other 
thread will enter the above OTG initialization section:

	/* Initialize otg part (only if we initialize a PHY with IRQs). */
	if (rphy->int_enable_bits && channel->is_otg_channel &&
	    !rcar_gen3_is_any_otg_rphy_initialized(channel)) {
		rcar_gen3_init_otg_phase0(channel);
		disable_irq_nosync(channel->irq);
		reinit_completion(&channel->otg_init_done);
		WRITE_ONCE(channel->otg_initializing, true);
		spin_unlock_irqrestore(&channel->lock, flags);

		fsleep(20000);

		spin_lock_irqsave(&channel->lock, flags);
		WRITE_ONCE(channel->otg_initializing, false);
		complete_all(&channel->otg_init_done);
		enable_irq(channel->irq);
		rcar_gen3_init_otg_phase1(channel);
	}

Thank you,
Claudiu