From: Horatiu Vultur <horatiu.vultur@microchip.com>
To: ChunHao Lin <hau@realtek.com>
Cc: <hkallweit1@gmail.com>, <netdev@vger.kernel.org>, <nic_swsd@realtek.com>
Subject: Re: [PATCH net] r8169: fix rtl8168h rx crc error
Date: Wed, 22 Mar 2023 09:21:04 +0100 [thread overview]
Message-ID: <20230322082104.y6pz7ewu3ojd3esh@soft-dev3-1> (raw)
In-Reply-To: <20230322064550.2378-1-hau@realtek.com>
The 03/22/2023 14:45, ChunHao Lin wrote:
>
> When link speed is 10 Mbps and temperature is under -20°C, rtl8168h may
> have rx crc error. Disable phy 10 Mbps pll off to fix this issue.
Don't forget to add the fixes tag.
Another comment that I usually get is to replace hardcoded values with
defines, but on the other side I can see that this file already has
plently of hardcoded values.
Reviewed-by: Horatiu Vultur <horatiu.vultur@microchip.com>
>
> Signed-off-by: ChunHao Lin <hau@realtek.com>
> ---
> drivers/net/ethernet/realtek/r8169_phy_config.c | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/drivers/net/ethernet/realtek/r8169_phy_config.c b/drivers/net/ethernet/realtek/r8169_phy_config.c
> index 930496cd34ed..b50f16786c24 100644
> --- a/drivers/net/ethernet/realtek/r8169_phy_config.c
> +++ b/drivers/net/ethernet/realtek/r8169_phy_config.c
> @@ -826,6 +826,9 @@ static void rtl8168h_2_hw_phy_config(struct rtl8169_private *tp,
> /* disable phy pfm mode */
> phy_modify_paged(phydev, 0x0a44, 0x11, BIT(7), 0);
>
> + /* disable 10m pll off */
> + phy_modify_paged(phydev, 0x0a43, 0x10, BIT(0), 0);
> +
> rtl8168g_disable_aldps(phydev);
> rtl8168g_config_eee_phy(phydev);
> }
> --
> 2.37.2
>
--
/Horatiu
next prev parent reply other threads:[~2023-03-22 8:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-22 6:45 [PATCH net] r8169: fix rtl8168h rx crc error ChunHao Lin
2023-03-22 8:21 ` Horatiu Vultur [this message]
2023-03-22 12:13 ` Hau
2023-03-22 19:59 ` Jakub Kicinski
2023-03-23 13:57 ` Hau
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=20230322082104.y6pz7ewu3ojd3esh@soft-dev3-1 \
--to=horatiu.vultur@microchip.com \
--cc=hau@realtek.com \
--cc=hkallweit1@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=nic_swsd@realtek.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