[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <63c3efa6-94a2-40c7-b47d-876ff330d261@lunn.ch>
Date: Sat, 11 May 2024 19:19:07 +0200
From: Andrew Lunn <andrew@...n.ch>
To: "Russell King (Oracle)" <linux@...linux.org.uk>
Cc: Jitendra Vegiraju <jitendra.vegiraju@...adcom.com>,
netdev@...r.kernel.org, davem@...emloft.net, edumazet@...gle.com,
kuba@...nel.org, pabeni@...hat.com,
bcm-kernel-feedback-list@...adcom.com, alexandre.torgue@...s.st.com,
joabreu@...opsys.com, mcoquelin.stm32@...il.com,
richardcochran@...il.com, linux-kernel@...r.kernel.org,
linux-stm32@...md-mailman.stormreply.com,
linux-arm-kernel@...ts.infradead.org
Subject: Re: [PATCH v2, net-next, 2/2] net: stmmac: PCI driver for BCM8958X
SoC
On Sat, May 11, 2024 at 06:12:38PM +0100, Russell King (Oracle) wrote:
> On Sat, May 11, 2024 at 06:16:52PM +0200, Andrew Lunn wrote:
> > > + /* This device interface is directly attached to the switch chip on
> > > + * the SoC. Since no MDIO is present, register fixed_phy.
> > > + */
> > > + brcm_priv->phy_dev =
> > > + fixed_phy_register(PHY_POLL,
> > > + &dwxgmac_brcm_fixed_phy_status, NULL);
> > > + if (IS_ERR(brcm_priv->phy_dev)) {
> > > + dev_err(&pdev->dev, "%s\tNo PHY/fixed_PHY found\n", __func__);
> > > + return -ENODEV;
> > > + }
> > > + phy_attached_info(brcm_priv->phy_dev);
> >
> > What switch is it? Will there be patches to extend SF2?
>
> ... and why is this legacy fixed_phy even necessary when stmmac uses
> phylink which supports fixed links, including with custom fixed status?
It might be because it is a PCI device, and they are trying to avoid
DT? Maybe because they have not figured out how to add DT properties
to a PCI device. It is possible.
Andrew
Powered by blists - more mailing lists