[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <7c79b1f8-a5b6-46b7-99fc-a0ac1bec5694@lunn.ch>
Date: Mon, 25 Mar 2024 14:04:11 +0100
From: Andrew Lunn <andrew@...n.ch>
To: Kory Maincent <kory.maincent@...tlin.com>
Cc: Elad Nachman <enachman@...vell.com>,
Taras Chornyi <taras.chornyi@...ision.eu>,
"davem@...emloft.net" <davem@...emloft.net>,
"edumazet@...gle.com" <edumazet@...gle.com>,
"kuba@...nel.org" <kuba@...nel.org>,
"pabeni@...hat.com" <pabeni@...hat.com>,
"thomas.petazzoni@...tlin.com" <thomas.petazzoni@...tlin.com>,
"miquel.raynal@...tlin.com" <miquel.raynal@...tlin.com>,
"przemyslaw.kitszel@...el.com" <przemyslaw.kitszel@...el.com>,
"dkirjanov@...e.de" <dkirjanov@...e.de>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [EXTERNAL] Re: [PATCH v2 0/5] Fix prestera driver fail to probe
twice
> Prestera is indeed not directly involved in PoE. I wrote a hack to be able to
> get the PoE ports control, for testing my PoE patch series.
>
> The aim in the future will be to add RJ45 port abstraction.
> The Prestera will get the port abstraction which will get the PoE ports control.
> The prestera driver then might receive an EPROBE_DEFER from it.
O.K, so EPRODE_DEFER has to work in a meaningful way. I'm not sure we
can call a 30 second delay meaningful.
And it is not just PoE. phylink_create() can return EPROBE_DEFER, and
there are probably others.
Andrew
Powered by blists - more mailing lists