From: "Russell King (Oracle)" <linux@armlinux.org.uk>
To: Arun Ramadoss <arun.ramadoss@microchip.com>
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
Andrew Lunn <andrew@lunn.ch>,
Heiner Kallweit <hkallweit1@gmail.com>,
Jakub Kicinski <kuba@kernel.org>,
"David S . Miller" <davem@davemloft.net>
Subject: Re: [RFC PATCH net-next 4/4] net: phy: added master-slave config and cable diagnostics for Lan937x
Date: Mon, 28 Feb 2022 14:12:41 +0000 [thread overview]
Message-ID: <YhzYWXf30zcedsH1@shell.armlinux.org.uk> (raw)
In-Reply-To: <20220228140510.20883-5-arun.ramadoss@microchip.com>
On Mon, Feb 28, 2022 at 07:35:10PM +0530, Arun Ramadoss wrote:
> To configure the Lan937x T1 phy as master or slave using the ethtool -s
> <dev> master-slave <forced-master/forced-slave>, the config_aneg and
> read status functions are added. And for the cable-diagnostics, used the
> lan87xx routines.
>
> Signed-off-by: Prasanna Vengateshan <prasanna.vengateshan@microchip.com>
> Signed-off-by: Arun Ramadoss <arun.ramadoss@microchip.com>
> ---
> drivers/net/phy/microchip_t1.c | 75 ++++++++++++++++++++++++++++++++++
> 1 file changed, 75 insertions(+)
>
> diff --git a/drivers/net/phy/microchip_t1.c b/drivers/net/phy/microchip_t1.c
> index 634a1423182a..3a0d4c4fab0a 100644
> --- a/drivers/net/phy/microchip_t1.c
> +++ b/drivers/net/phy/microchip_t1.c
> @@ -81,6 +81,9 @@
> #define T1_REG_BANK_SEL 8
> #define T1_REG_ADDR_MASK 0xFF
>
> +#define T1_MODE_STAT_REG 0x11
> +#define T1_LINK_UP_MSK BIT(0)
> +
> #define DRIVER_AUTHOR "Nisar Sayed <nisar.sayed@microchip.com>"
> #define DRIVER_DESC "Microchip LAN87XX/LAN937x T1 PHY driver"
>
> @@ -435,6 +438,11 @@ static int lan_phy_config_init(struct phy_device *phydev)
> if (rc < 0)
> phydev_err(phydev, "failed to initialize phy\n");
>
> + phydev->duplex = DUPLEX_FULL;
> + phydev->speed = SPEED_100;
> + phydev->pause = 0;
> + phydev->asym_pause = 0;
Shouldn't this be done in lan937x_read_status()?
Have you tested this patch with various invocations of ethtool -s ?
E.g. autoneg on, autoneg off at various forced speeds, both suitable
for the PHY and unsuitable? Are all these sensibly handled?
Thanks.
--
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
FTTP is here! 40Mbps down 10Mbps up. Decent connectivity at last!
next prev parent reply other threads:[~2022-02-28 14:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-28 14:05 [RFC PATCH net-next 0/4] Add support for LAN937x T1 Phy Arun Ramadoss
2022-02-28 14:05 ` [RFC PATCH net-next 1/4] net: phy: used the genphy_soft_reset for phy reset in Lan87xx Arun Ramadoss
2022-03-02 3:19 ` Andrew Lunn
2022-03-02 10:04 ` Arun.Ramadoss
2022-02-28 14:05 ` [RFC PATCH net-next 2/4] net: phy: updated the initialization routine for LAN87xx Arun Ramadoss
2022-02-28 14:05 ` [RFC PATCH net-next 3/4] net: phy: added the LAN937x phy support Arun Ramadoss
2022-03-02 3:22 ` Andrew Lunn
2022-03-02 9:57 ` Arun.Ramadoss
2022-02-28 14:05 ` [RFC PATCH net-next 4/4] net: phy: added master-slave config and cable diagnostics for Lan937x Arun Ramadoss
2022-02-28 14:12 ` Russell King (Oracle) [this message]
2022-03-01 16:59 ` Arun.Ramadoss
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=YhzYWXf30zcedsH1@shell.armlinux.org.uk \
--to=linux@armlinux.org.uk \
--cc=andrew@lunn.ch \
--cc=arun.ramadoss@microchip.com \
--cc=davem@davemloft.net \
--cc=hkallweit1@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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 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.