devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Leonidas P. Papadakos" <papadakospan@gmail.com>
To: Peter Geis <pgwipeout@gmail.com>
Cc: Rob Herring <robh+dt@kernel.org>,
	Heiko Stuebner <heiko@sntech.de>,
	Jose Abreu <jose.abreu@synopsys.com>,
	Robin Murphy <robin.murphy@arm.com>,
	devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	linux-rockchip@lists.infradead.org
Subject: Re: [PATCH] arm64: dts: rockchip: set TX PBL for rk3328-roc-cc gmac
Date: Mon, 22 Apr 2019 09:40:22 +0300	[thread overview]
Message-ID: <1555915222.1262.0@gmail.com> (raw)
In-Reply-To: <8865b046-fb3a-4071-335c-66abb344d7f4@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1028 bytes --]



Στις Κυρ, 21 Απρ, 2019 at 7:00 ΜΜ, ο/η Peter Geis 
<pgwipeout@gmail.com> έγραψε:
> Thanks for sharing that thread, it's nice to finally have an answer 
> to why we have these issues.
> I've tested this on *my* Firefly rk3328-roc-cc, and while this patch 
> succeeds in preventing the tx lockup, iperf3 drops to a delightful 
> 15mbps.
> 
> It would seem we have significant differences between manufacturing 
> runs of the various boards.
> The auto adjustment feature that was discussed in that thread is 
> probably the only thing that will solve this for all boards.
> Until then I don't think we are going to get a solution that works 
> for all.

Indeed that feature would be optimal. Just to confirm, you have 
replaced force_thresh_dma_mode with this txpbl thing, right?
That is the only ethernet modification I have in the dts, done though 
u-boot. That is on linux 5.1

> fdt rm /ethernet@ff540000 snps,force_thresh_dma_mode
> fdt set /ethernet@ff540000 snps,txpbl <0x4>


[-- Attachment #2: Type: text/html, Size: 1559 bytes --]

  reply	other threads:[~2019-04-22  6:40 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-17 21:01 [PATCH] arm64: dts: rockchip: set TX PBL for rk3328-roc-cc gmac Leonidas P. Papadakos
     [not found] ` <20190417210059.26262-1-papadakospan-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2019-04-21 16:00   ` Peter Geis
2019-04-22  6:40     ` Leonidas P. Papadakos [this message]
     [not found]     ` <8865b046-fb3a-4071-335c-66abb344d7f4-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2019-04-22  6:43       ` Leonidas P. Papadakos
     [not found]         ` <1555915435.1262.1-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2019-04-22 11:57           ` Peter Geis
     [not found]             ` <9a5c62b4-ea75-de4f-9b71-ffa42cb8eaac-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2019-04-22 13:13               ` Leonidas P. Papadakos
     [not found]                 ` <1555938803.1241.1-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2019-05-23  0:00                   ` Peter Geis
     [not found]                     ` <8ded737d-1fd5-3609-ca2e-cfeba63b2d95-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2019-06-14  9:26                       ` Heiko Stuebner
2019-06-15 12:27                         ` Peter Geis

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=1555915222.1262.0@gmail.com \
    --to=papadakospan@gmail.com \
    --cc=devicetree@vger.kernel.org \
    --cc=heiko@sntech.de \
    --cc=jose.abreu@synopsys.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-rockchip@lists.infradead.org \
    --cc=pgwipeout@gmail.com \
    --cc=robh+dt@kernel.org \
    --cc=robin.murphy@arm.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;
as well as URLs for NNTP newsgroup(s).