From: Wojciech Drewek <wojciech.drewek@intel.com>
To: Horatiu Vultur <horatiu.vultur@microchip.com>, <andrew@lunn.ch>,
<hkallweit1@gmail.com>, <linux@armlinux.org.uk>,
<davem@davemloft.net>, <edumazet@google.com>, <kuba@kernel.org>,
<pabeni@redhat.com>
Cc: <netdev@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<UNGLinuxDriver@microchip.com>
Subject: Re: [PATCH net-next 2/2] net: phy: micrel: lan8814 cable improvement errata
Date: Wed, 28 Feb 2024 11:03:51 +0100 [thread overview]
Message-ID: <62ee2e75-72d5-43bf-a37f-948692a0e551@intel.com> (raw)
In-Reply-To: <20240228062813.1007138-3-horatiu.vultur@microchip.com>
On 28.02.2024 07:28, 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@microchip.com>
> ---
> drivers/net/phy/micrel.c | 10 ++++++++++
> 1 file changed, 10 insertions(+)
>
> diff --git a/drivers/net/phy/micrel.c b/drivers/net/phy/micrel.c
> index 5a0cc89eaebdd..1e3b0436e161e 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
> +
> /* Represents 1ppm adjustment in 2^32 format with
> * each nsec contains 4 clock cycles.
> * The value is calculated as following: (1/1000000)/((2^-32)/4)
> @@ -3302,6 +3306,12 @@ static void lan8814_errata_fixes(struct phy_device *phydev)
> val = lanphy_read_page_reg(phydev, 2, LAN8814_EEE_STATE);
> val &= ~LAN8814_EEE_STATE_MASK2P5P;
> lanphy_write_page_reg(phydev, 2, LAN8814_EEE_STATE, val);
> +
> + /* Improve cable reach beyond 100m */
> + val = lanphy_read_page_reg(phydev, 1, LAN8814_PD_CONTROLS);
> + val &= ~LAN8814_PD_CONTROLS_PD_MEAS_TIME_MASK_;
> + val |= LAN8814_PD_CONTROLS_PD_MEAS_TIME_VAL_;
> + lanphy_write_page_reg(phydev, 1, LAN8814_PD_CONTROLS, val);
Ok, now I see that the second fix is also in lan8814_errata_fixes.
I'd suggest to split both fixes to separate functions and name them
in more descriptive way.
> }
>
> static int lan8814_probe(struct phy_device *phydev)
next prev parent reply other threads:[~2024-02-28 10:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-28 6:28 [PATCH net-next 0/2] net: phy: micrel: lan8814 erratas Horatiu Vultur
2024-02-28 6:28 ` [PATCH net-next 1/2] net: phy: micrel: lan8814 led errata Horatiu Vultur
2024-02-28 9:58 ` Wojciech Drewek
2024-02-28 6:28 ` [PATCH net-next 2/2] net: phy: micrel: lan8814 cable improvement errata Horatiu Vultur
2024-02-28 10:03 ` Wojciech Drewek [this message]
2024-02-28 14:02 ` Horatiu Vultur
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=62ee2e75-72d5-43bf-a37f-948692a0e551@intel.com \
--to=wojciech.drewek@intel.com \
--cc=UNGLinuxDriver@microchip.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hkallweit1@gmail.com \
--cc=horatiu.vultur@microchip.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=netdev@vger.kernel.org \
--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®