public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: E Shattow <e@freeshell.de>
To: u-boot@lists.denx.de
Cc: E Shattow <e@freeshell.de>,
	Minda Chen <minda.chen@starfivetech.com>,
	Tom Rini <trini@konsulko.com>,
	Leo Yu-Chi Liang <ycliang@andestech.com>,
	Heinrich Schuchardt <xypron.glpk@gmx.de>,
	Chanho Park <chanho61.park@samsung.com>,
	"E. Shattow" <lucent@gmail.com>,
	Lukasz Tekieli <tekieli.lukasz@gmail.com>,
	Lukas Funke <lukas.funke@weidmueller.com>,
	Aurelien Jarno <aurelien@aurel32.net>,
	H Bell <dmoo_dv@protonmail.com>
Subject: [PATCH] riscv64: dts: starfive: Star64 ethernet0 phy delay values sync with upstream Linux
Date: Sat, 26 Oct 2024 04:35:28 -0700	[thread overview]
Message-ID: <20241026113537.10347-2-e@freeshell.de> (raw)

Fix bad delay values copied from vendor board support package of Star64, improves
performance and reliability of bottom network port.

Fixes: 7ebf7e77c0616ef0d2f58cc1684c230f656bd3d6
Signed-off-by: E Shattow <e@freeshell.de>
---
 board/starfive/visionfive2/spl.c | 4 +---
 1 file changed, 1 insertion(+), 3 deletions(-)

diff --git a/board/starfive/visionfive2/spl.c b/board/starfive/visionfive2/spl.c
index f55c6b5d34..eb545e9365 100644
--- a/board/starfive/visionfive2/spl.c
+++ b/board/starfive/visionfive2/spl.c
@@ -103,9 +103,7 @@ static const struct starfive_vf2_pro star64_pine64[] = {
 	{"/soc/ethernet@16030000/mdio/ethernet-phy@0",
 		"motorcomm,rx-data-drv-microamp", "2910"},
 	{"/soc/ethernet@16030000/mdio/ethernet-phy@0",
-		"rx-internal-delay-ps", "1900"},
-	{"/soc/ethernet@16030000/mdio/ethernet-phy@0",
-		"tx-internal-delay-ps", "1500"},
+		"rx-internal-delay-ps", "1500"},
 
 	{"/soc/ethernet@16040000/mdio/ethernet-phy@1",
 		"motorcomm,tx-clk-adj-enabled", NULL},
-- 
2.45.2


             reply	other threads:[~2024-10-26 12:54 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-26 11:35 E Shattow [this message]
2024-10-28  7:58 ` [PATCH] riscv64: dts: starfive: Star64 ethernet0 phy delay values sync with upstream Linux Leo Liang

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=20241026113537.10347-2-e@freeshell.de \
    --to=e@freeshell.de \
    --cc=aurelien@aurel32.net \
    --cc=chanho61.park@samsung.com \
    --cc=dmoo_dv@protonmail.com \
    --cc=lucent@gmail.com \
    --cc=lukas.funke@weidmueller.com \
    --cc=minda.chen@starfivetech.com \
    --cc=tekieli.lukasz@gmail.com \
    --cc=trini@konsulko.com \
    --cc=u-boot@lists.denx.de \
    --cc=xypron.glpk@gmx.de \
    --cc=ycliang@andestech.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