Re: [Upstream] Re: [PATCH v3] arm64: dts: freescale: imx93-phycore-som: Delay the phy reset by a gpio

[Christoph Stoidner <C.Stoidner@phytec.de>]

On Di, 2025-07-08 at 10:35 +0200, Primoz Fiser wrote:
> Hi all,
> 
> is there something holding up this patch?

I dont see any blocker.
@Maintainers: If there is any missing/blocking point, could you
please comment.

Thanks,
Christoph

> 
> BR,
> Primoz
> 
> On 2. 06. 25 14:26, Andrew Lunn wrote:
> > > > I agree it is long enough, but i'm also surprised how slow the
> > > > kernel
> > > > was. Are you using a fixed IP address, or dhcp?
> > > 
> > > I use a fixed IP address.
> > > 
> > > But isn't the bringup of ethernet+phy interface one of the last
> > > things
> > > that happens during the kernel boot-up?
> > 
> > Mounting the rootfs is somewhat towards the end of the core
> > kernel. But if you have an initramfs, there can be modules loaded
> > both
> > before and afterwards, and once the rootfs has been mounted, yet
> > more
> > modules can be loaded.
> > 
> > > However, what timing would you expect?
> > 
> > I've seen interfaces configured up from deep within
> > register_netdev(). I don't remember the exact configuration, but i
> > thought it was NFS root. It might be in combination with initramfs.
> > If
> > you have the Ethernet driver as a module in the initramfs, and are
> > using the "rootwait" option, it could be that you are already past
> > the
> > point it would first mount the rootfs, and with every new device
> > popping into existence it is trying to see if the just created
> > device
> > allows it to do the mount. At that point, register_netdev() is
> > going
> > to trigger actions.
> > 
> >  Andrew
> > _______________________________________________
> > upstream mailing list -- upstream@lists.phytec.de
> > To unsubscribe send an email to upstream-leave@lists.phytec.de
>