From: "Russell King (Oracle)" <linux@armlinux.org.uk>
To: Raju Lakkaraju <Raju.Lakkaraju@microchip.com>
Cc: netdev@vger.kernel.org, davem@davemloft.net, kuba@kernel.org,
andrew@lunn.ch, horms@kernel.org, hkallweit1@gmail.com,
richardcochran@gmail.com, rdunlap@infradead.org,
bryan.whitehead@microchip.com, edumazet@google.com,
pabeni@redhat.com, linux-kernel@vger.kernel.org,
UNGLinuxDriver@microchip.com
Subject: Re: [PATCH net-next V2 3/4] net: lan743x: Migrate phylib to phylink
Date: Tue, 30 Jul 2024 12:29:28 +0100 [thread overview]
Message-ID: <ZqjOmOzNLE0+oYP2@shell.armlinux.org.uk> (raw)
In-Reply-To: <ZqjE9A8laPxYP1ta@HYD-DK-UNGSW21.microchip.com>
On Tue, Jul 30, 2024 at 04:18:20PM +0530, Raju Lakkaraju wrote:
> Ok.
> After change, i ran the checkpatch script. it's giving follwoing warning
> i.e.
> "CHECK: Comparison to NULL could be written "dn""
>
> Is it OK ?
Assuming its referring to:
return dn != NULL;
in a function that returns a bool, I find that utterly perverse, and I
suggest in this case ignoring checkpatch.
> > > +static int lan743x_phylink_connect(struct lan743x_adapter *adapter)
> > > +{
> > > + struct device_node *dn = adapter->pdev->dev.of_node;
> > > + struct net_device *dev = adapter->netdev;
> > > + struct fixed_phy_status fphy_status = {
> > > + .link = 1,
> > > + .speed = SPEED_1000,
> > > + .duplex = DUPLEX_FULL,
> > > + };
> > > + struct phy_device *phydev;
> > > + int ret;
> > > +
> > > + if (dn)
> > > + ret = phylink_of_phy_connect(adapter->phylink, dn, 0);
> > > +
> > > + if (!dn || (ret && !lan743x_phy_handle_exists(dn))) {
> > > + phydev = phy_find_first(adapter->mdiobus);
> > > + if (!phydev) {
> > > + if (((adapter->csr.id_rev & ID_REV_ID_MASK_) ==
> > > + ID_REV_ID_LAN7431_) || adapter->is_pci11x1x) {
> > > + phydev = fixed_phy_register(PHY_POLL,
> > > + &fphy_status,
> > > + NULL);
> > > + if (IS_ERR(phydev)) {
> > > + netdev_err(dev, "No PHY/fixed_PHY found\n");
> > > + return PTR_ERR(phydev);
> > > + }
> >
> > Eww. Given that phylink has its own internal fixed-PHY support, can we
> > not find some way to avoid the legacy fixed-PHY usage here?
>
> Yes. I agree with you. This is very much valid suggestion.
> Andrew also gave same suggestion.
>
> Currently we don't have Device Tree support for LAN743X driver.
> For SFP support, I create the software-node an passing the paramters there.
>
> I don't have fixed-PHY hardware setup currently.
> I would like to take this as action item to fix it after SFP support commits.
Note that SFP shouldn't be using a fixed-phy at all.
--
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
FTTP is here! 80Mbps down 10Mbps up. Decent connectivity at last!
next prev parent reply other threads:[~2024-07-30 11:29 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-16 11:33 [PATCH net-next V2 0/4] Add support to PHYLINK for LAN743x/PCI11x1x chips Raju Lakkaraju
2024-07-16 11:33 ` [PATCH net-next V2 1/4] net: lan743x: Create separate PCS power reset function Raju Lakkaraju
2024-07-18 3:30 ` Andrew Lunn
2024-07-16 11:33 ` [PATCH net-next V2 2/4] net: lan743x: Create separate Link Speed Duplex state function Raju Lakkaraju
2024-07-18 3:33 ` Andrew Lunn
2024-07-16 11:33 ` [PATCH net-next V2 3/4] net: lan743x: Migrate phylib to phylink Raju Lakkaraju
2024-07-18 3:43 ` Andrew Lunn
2024-07-25 9:34 ` Raju Lakkaraju
2024-07-29 9:16 ` Russell King (Oracle)
2024-07-30 10:48 ` Raju Lakkaraju
2024-07-30 11:29 ` Russell King (Oracle) [this message]
2024-07-16 11:33 ` [PATCH net-next V2 4/4] net: lan743x: Add support to ethtool phylink get and set settings Raju Lakkaraju
2024-07-16 13:17 ` [PATCH net-next V2 0/4] Add support to PHYLINK for LAN743x/PCI11x1x chips Paolo Abeni
2024-07-16 13:37 ` Jiri Pirko
2024-07-18 3:27 ` Andrew Lunn
2024-07-18 5:08 ` Raju Lakkaraju
2024-07-18 15:09 ` Andrew Lunn
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=ZqjOmOzNLE0+oYP2@shell.armlinux.org.uk \
--to=linux@armlinux.org.uk \
--cc=Raju.Lakkaraju@microchip.com \
--cc=UNGLinuxDriver@microchip.com \
--cc=andrew@lunn.ch \
--cc=bryan.whitehead@microchip.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hkallweit1@gmail.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=rdunlap@infradead.org \
--cc=richardcochran@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.