From: <Arun.Ramadoss@microchip.com>
To: <andrew@lunn.ch>, <olteanv@gmail.com>, <davem@davemloft.net>,
<Woojung.Huh@microchip.com>, <pabeni@redhat.com>,
<o.rempel@pengutronix.de>, <edumazet@google.com>,
<f.fainelli@gmail.com>, <kuba@kernel.org>
Cc: <kernel@pengutronix.de>, <linux-kernel@vger.kernel.org>,
<netdev@vger.kernel.org>, <UNGLinuxDriver@microchip.com>
Subject: Re: [RFC net-next v2 3/3] net: dsa: microchip: implement PHY loopback configuration for KSZ8794 and KSZ8873
Date: Tue, 9 Jan 2024 14:33:47 +0000 [thread overview]
Message-ID: <5adfec6cbd3ba5fa7c36474d9f395839a2b5b590.camel@microchip.com> (raw)
In-Reply-To: <20240109095753.1872010-4-o.rempel@pengutronix.de>
On Tue, 2024-01-09 at 10:57 +0100, Oleksij Rempel wrote:
> EXTERNAL EMAIL: Do not click links or open attachments unless you
> know the content is safe
>
> Correct the PHY loopback bit handling in the ksz8_w_phy_bmcr and
> ksz8_r_phy_bmcr functions for KSZ8794 and KSZ8873 variants in the
> ksz8795
> driver. Previously, the code erroneously used Bit 7 of port register
> 0xD
> for both chip variants, which is actually for LED configuration. This
> update ensures the correct registers and bits are used for the PHY
> loopback feature:
>
> - For KSZ8794: Use 0xF / Bit 7.
> - For KSZ8873: Use 0xD / Bit 0.
>
> The lack of loopback support was seen on KSZ8873 system by using
> "ethtool -t lanX". After this patch, the ethtool selftest will work,
> but only if port is not part of a bridge.
>
> Signed-off-by: Oleksij Rempel <o.rempel@pengutronix.de>
> ---
> drivers/net/dsa/microchip/ksz8795.c | 36 ++++++++++++++++++++---
> --
> drivers/net/dsa/microchip/ksz8795_reg.h | 1 +
> 2 files changed, 30 insertions(+), 7 deletions(-)
>
> diff --git a/drivers/net/dsa/microchip/ksz8795.c
> b/drivers/net/dsa/microchip/ksz8795.c
> index 51e0194453df..1d8377640a3d 100644
> --- a/drivers/net/dsa/microchip/ksz8795.c
> +++ b/drivers/net/dsa/microchip/ksz8795.c
> @@ -731,16 +731,25 @@ static int ksz8_r_phy_bmcr(struct ksz_device
> *dev, u16 port, u16 *val)
> if (ret)
> return ret;
>
> - if (restart & PORT_PHY_LOOPBACK)
> - *val |= BMCR_LOOPBACK;
> -
> if (ctrl & PORT_FORCE_100_MBIT)
> *val |= BMCR_SPEED100;
>
> if (ksz_is_ksz88x3(dev)) {
> + if (restart & KSZ8873_PORT_PHY_LOOPBACK)
> + *val |= BMCR_LOOPBACK;
> +
> if ((ctrl & PORT_AUTO_NEG_ENABLE))
> *val |= BMCR_ANENABLE;
> } else {
> + u8 stat3;
> +
> + ret = ksz_pread8(dev, port, REG_PORT_STATUS_3,
> &stat3);
> + if (ret)
> + return ret;
> +
> + if (stat3 & PORT_PHY_LOOPBACK)
> + *val |= BMCR_LOOPBACK;
> +
> if (!(ctrl & PORT_AUTO_NEG_DISABLE))
> *val |= BMCR_ANENABLE;
> }
> @@ -1001,8 +1010,7 @@ static int ksz8_w_phy_bmcr(struct ksz_device
> *dev, u16 port, u16 val)
>
> restart = 0;
> restart_mask = PORT_LED_OFF | PORT_TX_DISABLE |
> PORT_AUTO_NEG_RESTART |
> - PORT_POWER_DOWN | PORT_AUTO_MDIX_DISABLE |
> PORT_FORCE_MDIX |
> - PORT_PHY_LOOPBACK;
> + PORT_POWER_DOWN | PORT_AUTO_MDIX_DISABLE |
> PORT_FORCE_MDIX;
>
> if (val & KSZ886X_BMCR_DISABLE_LED)
> restart |= PORT_LED_OFF;
> @@ -1022,8 +1030,22 @@ static int ksz8_w_phy_bmcr(struct ksz_device
> *dev, u16 port, u16 val)
> if (val & KSZ886X_BMCR_FORCE_MDI)
> restart |= PORT_FORCE_MDIX;
>
> - if (val & BMCR_LOOPBACK)
> - restart |= PORT_PHY_LOOPBACK;
> + if (ksz_is_ksz88x3(dev)) {
> + restart_mask |= KSZ8873_PORT_PHY_LOOPBACK;
> +
> + if (val & BMCR_LOOPBACK)
> + restart |= KSZ8873_PORT_PHY_LOOPBACK;
> + } else {
> + u8 stat3 = 0;
> +
> + if (val & BMCR_LOOPBACK)
> + stat3 |= PORT_PHY_LOOPBACK;
> +
> + ret = ksz_prmw8(dev, port, REG_PORT_STATUS_3,
> PORT_PHY_LOOPBACK,
> + stat3);
> + if (ret)
> + return ret;
nitpick: As it is independent thing, it will be good to have wrapper
function for writing and reading phy loopback in stat3 register.
> + }
>
> return ksz_prmw8(dev, port, regs[P_NEG_RESTART_CTRL],
> restart_mask,
> restart);
> diff --git a/drivers/net/dsa/microchip/ksz8795_reg.h
> b/drivers/net/dsa/microchip/ksz8795_reg.h
> index beca974e0171..7c9341ef73b0 100644
> --- a/drivers/net/dsa/microchip/ksz8795_reg.h
> +++ b/drivers/net/dsa/microchip/ksz8795_reg.h
> @@ -265,6 +265,7 @@
> #define PORT_AUTO_MDIX_DISABLE BIT(2)
> #define PORT_FORCE_MDIX BIT(1)
> #define PORT_MAC_LOOPBACK BIT(0)
> +#define KSZ8873_PORT_PHY_LOOPBACK BIT(0)
>
> #define REG_PORT_1_STATUS_2 0x1E
> #define REG_PORT_2_STATUS_2 0x2E
> --
> 2.39.2
>
prev parent reply other threads:[~2024-01-09 14:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-09 9:57 [RFC net-next v2 0/3] net: dsa: microchip: implement PHY loopback Oleksij Rempel
2024-01-09 9:57 ` [RFC net-next v2 1/3] net: dsa: microchip: ksz8: move BMCR specific code to separate function Oleksij Rempel
2024-01-09 14:29 ` Arun.Ramadoss
2024-01-09 9:57 ` [RFC net-next v2 2/3] net: dsa: microchip: Remove redundant optimization in ksz8_w_phy_bmcr Oleksij Rempel
2024-01-09 14:30 ` Arun.Ramadoss
2024-01-09 9:57 ` [RFC net-next v2 3/3] net: dsa: microchip: implement PHY loopback configuration for KSZ8794 and KSZ8873 Oleksij Rempel
2024-01-09 14:33 ` Arun.Ramadoss [this message]
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=5adfec6cbd3ba5fa7c36474d9f395839a2b5b590.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=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 \
/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®