From: Conor Dooley <conor@kernel.org>
To: Henry Bell <dmoo_dv@protonmail.com>, E Shattow <e@freeshell.de>
Cc: conor@kernel.org, Conor Dooley <conor.dooley@microchip.com>,
Emil Renner Berthing <kernel@esmil.dk>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Paul Walmsley <paul.walmsley@sifive.com>,
Palmer Dabbelt <palmer@dabbelt.com>,
Albert Ou <aou@eecs.berkeley.edu>,
devicetree@vger.kernel.org, linux-riscv@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] riscv: dts: starfive: Update ethernet phy0 delay parameter values for Star64
Date: Wed, 23 Oct 2024 11:30:03 +0100 [thread overview]
Message-ID: <20241023-guts-versus-1a2bcfdfbec2@spud> (raw)
In-Reply-To: <20241022061004.62812-1-e@freeshell.de>
From: Conor Dooley <conor.dooley@microchip.com>
On Mon, 21 Oct 2024 23:09:51 -0700, E Shattow wrote:
> Improve function of Star64 bottom network port phy0 with updated delay values.
> Initial upstream patches supporting Star64 use the same vendor board support
> package parameters known to result in an unreliable bottom network port.
>
> Success acquiring DHCP lease and no dropped packets to ping LAN address:
> rx 900: tx 1500 1650 1800 1950
> rx 750: tx 1650 1800 1950
> rx 600: tx 1800 1950
> rx 1050: tx 1650 1800 1950
> rx 1200: tx 1500 1650 1800 1950
> rx 1350: tx 1500 1650 1800 1950
> rx 1500: tx 1500 1650 1800 1950
> rx 1650: tx 1500 1650 1800 1950
> rx 1800: tx 1500 1650 1800 1950
> rx 1900: tx 1950
> rx 1950: tx 1950
>
> [...]
Applied to riscv-soc-fixes, thanks!
[1/1] riscv: dts: starfive: Update ethernet phy0 delay parameter values for Star64
https://git.kernel.org/conor/c/825bb69228c8
Thanks,
Conor.
prev parent reply other threads:[~2024-10-23 10:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-22 6:09 [PATCH] riscv: dts: starfive: Update ethernet phy0 delay parameter values for Star64 E Shattow
2024-10-22 16:41 ` Conor Dooley
2024-10-23 1:12 ` E Shattow
2024-10-22 17:39 ` Emil Renner Berthing
2024-10-23 10:30 ` Conor Dooley [this message]
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=20241023-guts-versus-1a2bcfdfbec2@spud \
--to=conor@kernel.org \
--cc=aou@eecs.berkeley.edu \
--cc=conor+dt@kernel.org \
--cc=conor.dooley@microchip.com \
--cc=devicetree@vger.kernel.org \
--cc=dmoo_dv@protonmail.com \
--cc=e@freeshell.de \
--cc=kernel@esmil.dk \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=robh@kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).