mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Nuno Sá" <noname.nuno@gmail.com>
To: Ken Sloat <ken.s@variscite.com>
Cc: Michael Hennerich <michael.hennerich@analog.com>,
	Andrew Lunn <andrew@lunn.ch>,
	Heiner Kallweit <hkallweit1@gmail.com>,
	Russell King <linux@armlinux.org.uk>,
	"David S. Miller" <davem@davemloft.net>,
	Jakub Kicinski <kuba@kernel.org>,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1] net: phy: adin: Add flags to disable enhanced link detection
Date: Tue, 28 Feb 2023 16:09:44 +0100	[thread overview]
Message-ID: <f5920799e6b0b6b5321ca38eb3b28024dc1be81f.camel@gmail.com> (raw)
In-Reply-To: <20230228144056.2246114-1-ken.s@variscite.com>

Hi,

Thanks for the patch! Some comments from my side...

On Tue, 2023-02-28 at 09:40 -0500, Ken Sloat wrote:
> Enhanced link detection is an ADI PHY feature that allows for earlier
> detection of link down if certain signal conditions are met. This
> feature is for the most part enabled by default on the PHY. This is
> not suitable for all applications and breaks the IEEE standard as
> explained in the ADI datasheet.
> 
> To fix this, add override flags to disable enhanced link detection
> for 1000BASE-T and 100BASE-TX respectively by clearing any related
> feature enable bits.
> 
> This new feature was tested on an ADIN1300 but according to the
> datasheet applies equally for 100BASE-TX on the ADIN1200.
> 
> Signed-off-by: Ken Sloat <ken.s@variscite.com>
> ---
>  drivers/net/phy/adin.c | 38 ++++++++++++++++++++++++++++++++++++++
>  1 file changed, 38 insertions(+)
> 
> diff --git a/drivers/net/phy/adin.c b/drivers/net/phy/adin.c
> index da65215d19bb..8809f3e036a4 100644
> --- a/drivers/net/phy/adin.c
> +++ b/drivers/net/phy/adin.c
> @@ -69,6 +69,15 @@
>  #define ADIN1300_EEE_CAP_REG                   0x8000
>  #define ADIN1300_EEE_ADV_REG                   0x8001
>  #define ADIN1300_EEE_LPABLE_REG                        0x8002
> +#define ADIN1300_FLD_EN_REG                            0x8E27
> +#define   ADIN1300_FLD_PCS_ERR_100_EN                  BIT(7)
> +#define   ADIN1300_FLD_PCS_ERR_1000_EN                 BIT(6)
> +#define   ADIN1300_FLD_SLCR_OUT_STUCK_100_EN   BIT(5)
> +#define   ADIN1300_FLD_SLCR_OUT_STUCK_1000_EN  BIT(4)
> +#define   ADIN1300_FLD_SLCR_IN_ZDET_100_EN             BIT(3)
> +#define   ADIN1300_FLD_SLCR_IN_ZDET_1000_EN            BIT(2)
> +#define   ADIN1300_FLD_SLCR_IN_INVLD_100_EN            BIT(1)
> +#define   ADIN1300_FLD_SLCR_IN_INVLD_1000_EN   BIT(0)
>  #define ADIN1300_CLOCK_STOP_REG                        0x9400
>  #define ADIN1300_LPI_WAKE_ERR_CNT_REG          0xa000
>  
> @@ -508,6 +517,31 @@ static int adin_config_clk_out(struct phy_device
> *phydev)
>                               ADIN1300_GE_CLK_CFG_MASK, sel);
>  }
>  
> +static int adin_config_fld_en(struct phy_device *phydev)
> +{
> +       struct device *dev = &phydev->mdio.dev;
> +       int reg;
> +
> +       reg = phy_read_mmd(phydev, MDIO_MMD_VEND1,
> ADIN1300_FLD_EN_REG);
> +       if (reg < 0)
> +               return reg;
> +
> +       if (device_property_read_bool(dev, "adi,disable-fld-1000base-
> t"))

"adi,disable-fld-1000base-tx"?

> +               reg &= ~(ADIN1300_FLD_PCS_ERR_1000_EN |
> +                                ADIN1300_FLD_SLCR_OUT_STUCK_1000_EN
> |
> +                                ADIN1300_FLD_SLCR_IN_ZDET_1000_EN |
> +                                ADIN1300_FLD_SLCR_IN_INVLD_1000_EN);
> +
> +       if (device_property_read_bool(dev, "adi,disable-fld-100base-
> tx"))
> +               reg &= ~(ADIN1300_FLD_PCS_ERR_100_EN |
> +                                ADIN1300_FLD_SLCR_OUT_STUCK_100_EN |
> +                                ADIN1300_FLD_SLCR_IN_ZDET_100_EN |
> +                                ADIN1300_FLD_SLCR_IN_INVLD_100_EN);
> +
> +       return phy_write_mmd(phydev, MDIO_MMD_VEND1,
> +                            ADIN1300_FLD_EN_REG, reg);

nit: You could use phy_clear_bits_mmd() to simplify the function a bit.


You also need to add these new properties to:

Documentation/devicetree/bindings/net/adi,adin.yaml


- Nuno Sá


  parent reply	other threads:[~2023-02-28 15:07 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-28 14:40 Ken Sloat
2023-02-28 14:53 ` Andrew Lunn
2023-02-28 15:13   ` Ken Sloat
2023-02-28 15:19     ` Andrew Lunn
2023-02-28 15:28       ` Ken Sloat
2023-02-28 15:35         ` Andrew Lunn
2023-03-01  3:31       ` Jakub Kicinski
2023-03-01 13:02         ` Andrew Lunn
2023-03-01 14:08           ` Ken Sloat
2023-02-28 15:09 ` Nuno Sá [this message]
2023-02-28 15:18   ` Ken Sloat
2023-02-28 18:49 ` [PATCH v2 1/2] net: phy: adin: Add flags to allow disabling of fast link down Ken Sloat
2023-02-28 18:49   ` [PATCH v2 2/2] dt-bindings: net: adin: Document bindings for fast link down disable Ken Sloat
2023-03-02  8:59     ` Krzysztof Kozlowski
2023-03-07 18:19       ` Ken Sloat
2023-03-08 10:19         ` Krzysztof Kozlowski
2023-03-01  7:33   ` [PATCH v2 1/2] net: phy: adin: Add flags to allow disabling of fast link down Nuno Sá
2023-03-01 12:32     ` Ken Sloat

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=f5920799e6b0b6b5321ca38eb3b28024dc1be81f.camel@gmail.com \
    --to=noname.nuno@gmail.com \
    --cc=andrew@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=hkallweit1@gmail.com \
    --cc=ken.s@variscite.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@armlinux.org.uk \
    --cc=michael.hennerich@analog.com \
    --cc=netdev@vger.kernel.org \
    /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

all inboxes | Powered by JetHome®