From: <Arun.Ramadoss@microchip.com>
To: <andrew@lunn.ch>, <linux@armlinux.org.uk>, <hkallweit1@gmail.com>,
<wojciech.drewek@intel.com>, <davem@davemloft.net>,
<kuba@kernel.org>, <pabeni@redhat.com>, <edumazet@google.com>,
<Horatiu.Vultur@microchip.com>
Cc: <netdev@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<UNGLinuxDriver@microchip.com>
Subject: Re: [PATCH net-next v3 2/2] net: phy: micrel: lan8814 cable improvement errata
Date: Mon, 4 Mar 2024 14:08:07 +0000 [thread overview]
Message-ID: <869fb04a63de027c486b660e44ca4cb87212f478.camel@microchip.com> (raw)
In-Reply-To: <20240304091548.1386022-3-horatiu.vultur@microchip.com>
On Mon, 2024-03-04 at 10:15 +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.
>
> Reviewed-by: Wojciech Drewek <wojciech.drewek@intel.com>
> Signed-off-by: Horatiu Vultur <horatiu.vultur@microchip.com>
Acked-by: Arun Ramadoss <arun.ramadoss@microchip.com>
next prev parent reply other threads:[~2024-03-04 14:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-04 9:15 [PATCH net-next v3 0/2] net: phy: micrel: lan8814 erratas Horatiu Vultur
2024-03-04 9:15 ` [PATCH net-next v3 1/2] net: phy: micrel: lan8814 led errata Horatiu Vultur
2024-03-04 13:24 ` Andrew Lunn
2024-03-04 9:15 ` [PATCH net-next v3 2/2] net: phy: micrel: lan8814 cable improvement errata Horatiu Vultur
2024-03-04 13:25 ` Andrew Lunn
2024-03-04 14:08 ` Arun.Ramadoss [this message]
2024-03-05 19:20 ` [PATCH net-next v3 0/2] net: phy: micrel: lan8814 erratas patchwork-bot+netdevbpf
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=869fb04a63de027c486b660e44ca4cb87212f478.camel@microchip.com \
--to=arun.ramadoss@microchip.com \
--cc=Horatiu.Vultur@microchip.com \
--cc=UNGLinuxDriver@microchip.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hkallweit1@gmail.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 \
--cc=wojciech.drewek@intel.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®