From: Christoph Stoidner <C.Stoidner@phytec.de>
To: Shawn Guo <shawnguo@kernel.org>, Sascha Hauer <s.hauer@pengutronix.de>
Cc: Stefan Wahren <wahrenst@gmx.net>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
Fabio Estevam <festevam@gmail.com>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"imx@lists.linux.dev" <imx@lists.linux.dev>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"upstream@lists.phytec.de" <upstream@lists.phytec.de>,
Andrew Lunn <andrew@lunn.ch>
Subject: Re: [Upstream] Re: [PATCH v3] arm64: dts: freescale: imx93-phycore-som: Delay the phy reset by a gpio
Date: Thu, 7 Aug 2025 12:53:09 +0000 [thread overview]
Message-ID: <39243f47f601253ebf6e7ef30475f70ec2a932a4.camel@phytec.de> (raw)
In-Reply-To: <ad5e7450c5cf3a2f9a5d3c23f7219eb08be31062.camel@phytec.de>
Hello Shawn,
sorry for bothering.
Can you tell me if there's anything missing or wrong with this patch,
or if there's anything else I can do so that it becomes applied?
Thanks and regards,
Christoph
On Fr, 2025-07-18 at 17:33 +0000, Christoph Stoidner wrote:
> 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
> >
> _______________________________________________
> upstream mailing list -- upstream@lists.phytec.de
> To unsubscribe send an email to upstream-leave@lists.phytec.de
next prev parent reply other threads:[~2025-08-07 12:53 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-24 11:23 [PATCH v3] arm64: dts: freescale: imx93-phycore-som: Delay the phy reset by a gpio Christoph Stoidner
2025-05-24 17:44 ` Andrew Lunn
2025-05-24 21:37 ` AW: " Christoph Stoidner
2025-05-26 6:44 ` Stefan Wahren
2025-05-26 9:09 ` Christoph Stoidner
2025-05-26 9:24 ` Stefan Wahren
2025-05-26 10:04 ` Christoph Stoidner
2025-05-26 12:14 ` Stefan Wahren
2025-05-28 18:30 ` Christoph Stoidner
2025-05-28 19:29 ` Andrew Lunn
2025-05-30 13:40 ` Christoph Stoidner
2025-06-02 2:09 ` Andrew Lunn
2025-06-02 11:46 ` Christoph Stoidner
2025-06-02 12:26 ` Andrew Lunn
2025-07-08 8:35 ` [Upstream] " Primoz Fiser
2025-07-18 17:33 ` Christoph Stoidner
2025-07-18 17:47 ` Andrew Lunn
2025-08-07 12:53 ` Christoph Stoidner [this message]
2025-08-20 2:36 ` Shawn Guo
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=39243f47f601253ebf6e7ef30475f70ec2a932a4.camel@phytec.de \
--to=c.stoidner@phytec.de \
--cc=andrew@lunn.ch \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=imx@lists.linux.dev \
--cc=kernel@pengutronix.de \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@kernel.org \
--cc=upstream@lists.phytec.de \
--cc=wahrenst@gmx.net \
/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;
as well as URLs for NNTP newsgroup(s).