[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <d37a3f46-e92e-4ac0-aee0-b9f3638a3b93@lunn.ch>
Date: Thu, 22 Jun 2023 17:43:34 +0200
From: Andrew Lunn <andrew@...n.ch>
To: "Russell King (Oracle)" <linux@...linux.org.uk>
Cc: Florian Fainelli <f.fainelli@...il.com>,
netdev <netdev@...r.kernel.org>,
Heiner Kallweit <hkallweit1@...il.com>,
Oleksij Rempel <linux@...pel-privat.de>
Subject: Re: [PATCH v4 net-next 7/9] net: phy: Add phy_support_eee()
indicating MAC support EEE
> > > + * Efficient Ethernet. This should be called before phy_start() in
> > > + * order that EEE is negotiated when the link comes up as part of
> > > + * phy_start(). EEE is enabled by default when the hardware supports
> > > + * it.
> > > + */
> > > +void phy_support_eee(struct phy_device *phydev)
> > > +{
> > > + linkmode_copy(phydev->advertising_eee, phydev->supported_eee);
> > > + phydev->eee_cfg.tx_lpi_enabled = true;
> > > + phydev->eee_cfg.eee_enabled = true;
> > > +}
> > > +EXPORT_SYMBOL(phy_support_eee);
> >
> > A bit worried that naming this function might be confusing driver authors
> > that this is a function that reports whether EEE is supported, though I am
> > not able to come up with better names.
>
> Possibly phy_enable_eee_support() ?
As i said in the commit message, i followed what we do for pause:
void phy_support_sym_pause(struct phy_device *phydev);
void phy_support_asym_pause(struct phy_device *phydev);
but phy_enable_eee_support() is less ambiguous.
Andrew
Powered by blists - more mailing lists