[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <80bea3ec2ec86d2e75002f849da174f50e0b846b.camel@microchip.com>
Date: Fri, 1 Mar 2024 03:27:32 +0000
From: <Arun.Ramadoss@...rochip.com>
To: <andrew@...n.ch>, <linux@...linux.org.uk>, <hkallweit1@...il.com>,
<wojciech.drewek@...el.com>, <davem@...emloft.net>, <kuba@...nel.org>,
<pabeni@...hat.com>, <edumazet@...gle.com>, <Horatiu.Vultur@...rochip.com>
CC: <netdev@...r.kernel.org>, <linux-kernel@...r.kernel.org>,
<UNGLinuxDriver@...rochip.com>
Subject: Re: [PATCH net-next v2 2/2] net: phy: micrel: lan8814 cable
improvement errata
Hi Horatiu,
On Thu, 2024-02-29 at 20:52 +0100, Horatiu Vultur wrote:
> When the length of the cable is more than 100m and the lan8814 is
> configured to run in 1000Base-T Slave then the register of the device
> needs to be optimized.
>
> Workaround this by setting the measure time to a value of 0xb. This
> value can be set regardless of the configuration.
>
> This issue is described in 'LAN8814 Silicon Errata and Data Sheet
> Clarification' and according to that, this will not be corrected in a
> future silicon revision.
>
> Signed-off-by: Horatiu Vultur <horatiu.vultur@...rochip.com>
> ---
> drivers/net/phy/micrel.c | 19 +++++++++++++++++++
> 1 file changed, 19 insertions(+)
>
> diff --git a/drivers/net/phy/micrel.c b/drivers/net/phy/micrel.c
> index 88cc03982bb78..788fdd54fd22d 100644
> --- a/drivers/net/phy/micrel.c
> +++ b/drivers/net/phy/micrel.c
> @@ -117,6 +117,10 @@
> #define LAN8814_EEE_STATE 0x38
> #define LAN8814_EEE_STATE_MASK2P5P BIT(10)
>
> +#define LAN8814_PD_CONTROLS 0x9d
> +#define LAN8814_PD_CONTROLS_PD_MEAS_TIME_MASK_ GENMASK(3, 0)
> +#define LAN8814_PD_CONTROLS_PD_MEAS_TIME_VAL_ 0xb
nitpick: TIME_VAL macro is very generic if it can end with specific
like TIME_VAL_100M or something similar will gives more readability.
> +
>
Powered by blists - more mailing lists