From: Heiko Stuebner <heiko@sntech.de>
To: devicetree@vger.kernel.org, shironeko <shironeko@tesaguri.club>
Cc: conor+dt@kernel.org, krzysztof.kozlowski+dt@linaro.org,
robh+dt@kernel.org, shironeko <shironeko@tesaguri.club>
Subject: Re: [PATCH] arm64: dts: rockchip: add missing tx/rx-fifo-depth
Date: Thu, 16 Nov 2023 21:12:51 +0100 [thread overview]
Message-ID: <10369814.nUPlyArG6x@phil> (raw)
In-Reply-To: <20231115210417.144134-1-shironeko@tesaguri.club>
Hi,
Am Mittwoch, 15. November 2023, 22:04:17 CET schrieb shironeko:
just if you need to resend, the patch subject could please
mention both the gmac and rk3328 :-)
> Without fifo depths attempting to change the MTU will fail. These values
> are from the RK3328 Technical Reference Manual, briefly tested with Rock64.
>
> Signed-off-by: shironeko <shironeko@tesaguri.club>
> ---
> arch/arm64/boot/dts/rockchip/rk3328.dtsi | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/arch/arm64/boot/dts/rockchip/rk3328.dtsi b/arch/arm64/boot/dts/rockchip/rk3328.dtsi
> index e729e7a22b23..1573250ac24e 100644
> --- a/arch/arm64/boot/dts/rockchip/rk3328.dtsi
> +++ b/arch/arm64/boot/dts/rockchip/rk3328.dtsi
> @@ -916,6 +916,8 @@ gmac2io: ethernet@ff540000 {
> resets = <&cru SRST_GMAC2IO_A>;
> reset-names = "stmmaceth";
> rockchip,grf = <&grf>;
> + tx-fifo-depth = <2048>;
> + rx-fifo-depth = <4096>;
> snps,txpbl = <0x4>;
> status = "disabled";
> };
>
hmm, what about the other gmac-interface (gmac2phy).
Does the TRM provide depth information for that too?
Thanks
Heiko
next prev parent reply other threads:[~2023-11-16 20:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-15 21:04 [PATCH] arm64: dts: rockchip: add missing tx/rx-fifo-depth shironeko
2023-11-16 20:12 ` Heiko Stuebner [this message]
2023-11-16 21:46 ` shironeko
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=10369814.nUPlyArG6x@phil \
--to=heiko@sntech.de \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=robh+dt@kernel.org \
--cc=shironeko@tesaguri.club \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.