[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <3b1d35d7-ed62-4351-9e94-28e614d7f763@lunn.ch>
Date: Mon, 27 Oct 2025 01:16:12 +0100
From: Andrew Lunn <andrew@...n.ch>
To: Sven Eckelmann <se@...onwunderlich.de>
Cc: Heiner Kallweit <hkallweit1@...il.com>,
Russell King <linux@...linux.org.uk>,
"David S. Miller" <davem@...emloft.net>,
Eric Dumazet <edumazet@...gle.com>,
Jakub Kicinski <kuba@...nel.org>, Paolo Abeni <pabeni@...hat.com>,
netdev@...r.kernel.org, linux-kernel@...r.kernel.org,
sw@...onwunderlich.de, Issam Hamdi <ih@...onwunderlich.de>
Subject: Re: [PATCH] net: phy: realtek: Add RTL8224 cable testing support
> +#define RTL8224_SRAM_RTCT_FAULT_BUSY BIT(0)
> +#define RTL8224_SRAM_RTCT_FAULT_OPEN BIT(3)
> +#define RTL8224_SRAM_RTCT_FAULT_SAME_SHORT BIT(4)
> +#define RTL8224_SRAM_RTCT_FAULT_OK BIT(5)
> +#define RTL8224_SRAM_RTCT_FAULT_DONE BIT(6)
> +#define RTL8224_SRAM_RTCT_FAULT_CROSS_SHORT BIT(7)
It is unusual these are bits. Does the datasheet say what happens if
the cable is both same short and cross short?
> +static int rtl8224_cable_test_result_trans(u32 result)
> +{
> + if (result & RTL8224_SRAM_RTCT_FAULT_SAME_SHORT)
> + return ETHTOOL_A_CABLE_RESULT_CODE_SAME_SHORT;
> +
> + if (result & RTL8224_SRAM_RTCT_FAULT_BUSY)
> + return ETHTOOL_A_CABLE_RESULT_CODE_UNSPEC;
> +
> + if (result & RTL8224_SRAM_RTCT_FAULT_CROSS_SHORT)
> + return ETHTOOL_A_CABLE_RESULT_CODE_CROSS_SHORT;
I don't remember seeing a PHY able to report both same short and cross
short at the same time. Maybe there has been, but there is no code for
it. We could add such a code.
Andrew
Powered by blists - more mailing lists