netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: <Arun.Ramadoss@microchip.com>
To: <olteanv@gmail.com>, <UNGLinuxDriver@microchip.com>,
	<vivien.didelot@gmail.com>, <andrew@lunn.ch>,
	<f.fainelli@gmail.com>, <kuba@kernel.org>, <wei.fang@nxp.com>,
	<edumazet@google.com>, <pabeni@redhat.com>,
	<o.rempel@pengutronix.de>, <Woojung.Huh@microchip.com>,
	<davem@davemloft.net>, <hkallweit1@gmail.com>
Cc: <linux-kernel@vger.kernel.org>, <netdev@vger.kernel.org>,
	<intel-wired-lan@lists.osuosl.org>, <kernel@pengutronix.de>
Subject: Re: [PATCH net-next v5 02/23] net: phy: add genphy_c45_read_eee_abilities() function
Date: Mon, 6 Feb 2023 14:46:19 +0000	[thread overview]
Message-ID: <af4fa39e31a6275a07c577cb3d7fa5f114bdda05.camel@microchip.com> (raw)
In-Reply-To: <20230206135050.3237952-3-o.rempel@pengutronix.de>

Hi Oleksij,

On Mon, 2023-02-06 at 14:50 +0100, Oleksij Rempel wrote:
> EXTERNAL EMAIL: Do not click links or open attachments unless you
> know the content is safe
> 
> Add generic function for EEE abilities defined by IEEE 802.3
> specification. For now following registers are supported:
> - IEEE 802.3-2018 45.2.3.10 EEE control and capability 1 (Register
> 3.20)
> - IEEE 802.3cg-2019 45.2.1.186b 10BASE-T1L PMA status register
>   (Register 1.2295)
> 
> Since I was not able to find any flag signaling support of these
> registers, we should detect link mode abilities first and then based
> on
> these abilities doing EEE link modes detection.
> 
> Results of EEE ability detection will be stored into new variable
> phydev->supported_eee.
> 
> Signed-off-by: Oleksij Rempel <o.rempel@pengutronix.de>
> ---
>  drivers/net/phy/phy-c45.c    | 70
> ++++++++++++++++++++++++++++++++++++
>  drivers/net/phy/phy_device.c | 16 +++++++++
>  include/linux/mdio.h         | 26 ++++++++++++++
>  include/linux/phy.h          |  5 +++
>  4 files changed, 117 insertions(+)
> 
> diff --git a/drivers/net/phy/phy-c45.c b/drivers/net/phy/phy-c45.c
> index 9f9565a4819d..3ae642d3ae14 100644
> --- a/drivers/net/phy/phy-c45.c
> +++ b/drivers/net/phy/phy-c45.c
> @@ -661,6 +661,76 @@ int genphy_c45_read_mdix(struct phy_device
> *phydev)
>  }
>  EXPORT_SYMBOL_GPL(genphy_c45_read_mdix);
> 
> +/**
> + * genphy_c45_read_eee_cap1 - read supported EEE link modes from
> register 3.20
> + * @phydev: target phy_device struct
> + */
> +static int genphy_c45_read_eee_cap1(struct phy_device *phydev)
> +{
> +       int val;
> +
> +       /* IEEE 802.3-2018 45.2.3.10 EEE control and capability 1
> +        * (Register 3.20)
> +        */
> +       val = phy_read_mmd(phydev, MDIO_MMD_PCS, MDIO_PCS_EEE_ABLE);
> +       if (val < 0)
> +               return val;
> +
> +       /* The 802.3 2018 standard says the top 2 bits are reserved
> and should
> +        * read as 0. Also, it seems unlikely anybody will build a
> PHY which
> +        * supports 100GBASE-R deep sleep all the way down to
> 100BASE-TX EEE.
> +        * If MDIO_PCS_EEE_ABLE is 0xffff assume EEE is not
> supported.
> +        */
> +       if (val == GENMASK(15, 0))

nit: Magic number can be replaced by macro.

> +               return 0;
> +
> +       mii_eee_cap1_mod_linkmode_t(phydev->supported_eee, val);
> +
> +       /* Some buggy devices indicate EEE link modes in
> MDIO_PCS_EEE_ABLE
> +        * which they don't support as indicated by BMSR, ESTATUS
> etc.
> +        */
> +       linkmode_and(phydev->supported_eee, phydev->supported_eee,
> +                    phydev->supported);
> +
> +       return 0;
> +}
> +
> +
> 

  reply	other threads:[~2023-02-06 14:46 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-06 13:50 [PATCH net-next v5 00/23] net: add EEE support for KSZ9477 and AR8035 with i.MX6 Oleksij Rempel
2023-02-06 13:50 ` [PATCH net-next v5 01/23] net: dsa: microchip: enable EEE support Oleksij Rempel
2023-02-07  0:44   ` Andrew Lunn
2023-02-06 13:50 ` [PATCH net-next v5 02/23] net: phy: add genphy_c45_read_eee_abilities() function Oleksij Rempel
2023-02-06 14:46   ` Arun.Ramadoss [this message]
2023-02-07  0:44   ` Andrew Lunn
2023-02-08  5:19   ` Jakub Kicinski
2023-02-06 13:50 ` [PATCH net-next v5 03/23] net: phy: micrel: add ksz9477_get_features() Oleksij Rempel
2023-02-07  0:45   ` Andrew Lunn
2023-02-06 13:50 ` [PATCH net-next v5 04/23] net: phy: export phy_check_valid() function Oleksij Rempel
2023-02-06 13:50 ` [PATCH net-next v5 05/23] net: phy: add genphy_c45_ethtool_get/set_eee() support Oleksij Rempel
2023-02-06 14:54   ` Arun.Ramadoss
2023-02-06 13:50 ` [PATCH net-next v5 06/23] net: phy: c22: migrate to genphy_c45_write_eee_adv() Oleksij Rempel
2023-02-07  0:52   ` Andrew Lunn
2023-02-06 13:50 ` [PATCH net-next v5 07/23] net: phy: c45: " Oleksij Rempel
2023-02-07  0:52   ` Andrew Lunn
2023-02-06 13:50 ` [PATCH net-next v5 08/23] net: phy: migrate phy_init_eee() to genphy_c45_eee_is_active() Oleksij Rempel
2023-02-07  0:54   ` Andrew Lunn
2023-02-06 13:50 ` [PATCH net-next v5 09/23] net: phy: start using genphy_c45_ethtool_get/set_eee() Oleksij Rempel
2023-02-07  1:05   ` Andrew Lunn
2023-02-06 13:50 ` [PATCH net-next v5 10/23] net: phy: add driver specific get/set_eee support Oleksij Rempel
2023-02-06 13:50 ` [PATCH net-next v5 11/23] net: phy: at803x: implement ethtool access to SmartEEE functionality Oleksij Rempel
2023-02-06 13:50 ` [PATCH net-next v5 12/23] net: phy: at803x: ar8035: fix EEE support for half duplex links Oleksij Rempel
2023-02-06 13:50 ` [PATCH net-next v5 13/23] net: phy: add PHY specifica flag to signal SmartEEE support Oleksij Rempel
2023-02-06 13:50 ` [PATCH net-next v5 14/23] net: phy: at803x: add PHY_SMART_EEE flag to AR8035 Oleksij Rempel
2023-02-06 13:50 ` [PATCH net-next v5 15/23] net: phy: add phy_has_smarteee() helper Oleksij Rempel
2023-02-08  5:20   ` Jakub Kicinski
2023-02-06 13:50 ` [PATCH net-next v5 16/23] net: fec: add support for PHYs with SmartEEE support Oleksij Rempel
2023-02-06 13:50 ` [PATCH net-next v5 17/23] e1000e: replace EEE ethtool helpers to linkmode variants Oleksij Rempel
2023-02-06 13:50 ` [PATCH net-next v5 18/23] igb: " Oleksij Rempel
2023-02-06 13:50 ` [PATCH net-next v5 19/23] igc: " Oleksij Rempel
2023-02-06 13:50 ` [PATCH net-next v5 20/23] tg3: " Oleksij Rempel
2023-02-06 13:50 ` [PATCH net-next v5 21/23] r8152: " Oleksij Rempel
2023-02-06 13:50 ` [PATCH net-next v5 22/23] net: usb: ax88179_178a: " Oleksij Rempel
2023-02-06 13:50 ` [PATCH net-next v5 23/23] net: mdio: drop EEE ethtool helpers in favor " Oleksij Rempel
2023-02-08  5:25 ` [PATCH net-next v5 00/23] net: add EEE support for KSZ9477 and AR8035 with i.MX6 Jakub Kicinski
2023-02-08  8:30   ` Oleksij Rempel

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=af4fa39e31a6275a07c577cb3d7fa5f114bdda05.camel@microchip.com \
    --to=arun.ramadoss@microchip.com \
    --cc=UNGLinuxDriver@microchip.com \
    --cc=Woojung.Huh@microchip.com \
    --cc=andrew@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=f.fainelli@gmail.com \
    --cc=hkallweit1@gmail.com \
    --cc=intel-wired-lan@lists.osuosl.org \
    --cc=kernel@pengutronix.de \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=o.rempel@pengutronix.de \
    --cc=olteanv@gmail.com \
    --cc=pabeni@redhat.com \
    --cc=vivien.didelot@gmail.com \
    --cc=wei.fang@nxp.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 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).