mirror of https://lore.kernel.org/linux-amlogic/
 help / color / mirror / Atom feed
From: peppe.cavallaro@st.com (Giuseppe CAVALLARO)
To: linus-amlogic@lists.infradead.org
Subject: stmmac/RTL8211F/Meson GXBB: TX throughput problems
Date: Mon, 14 Nov 2016 08:47:22 +0100	[thread overview]
Message-ID: <68696e92-d056-5f29-9e71-72066f0c7673@st.com> (raw)
In-Reply-To: <CAFBinCDq0neyidQBO13F4Yz-GZPorGyRQ2t5Vb-PL0Ls582+4Q@mail.gmail.com>

Hello Martin

On 11/7/2016 6:37 PM, Martin Blumenstingl wrote:
> Hi Peppe,
>
> On Mon, Nov 7, 2016 at 11:59 AM, Giuseppe CAVALLARO
> <peppe.cavallaro@st.com> wrote:
>> In the meantime, I will read again the thread just to see if
>> there is something I am missing.
> if you are re-reading this thread: please note that there are two
> devices in discussion here!

many thx for the sum :-)

> Both are using the Amlogic S905 (GXBB) SoC and both are experiencing
> the same issue (Gbit TX issues, RX with Gbit speeds and RX/TX with
> 100Mbit speed are NOT affected):
> - Odroid-C2 (used by Jerome and Andr? Roth)
> - Tronsmart Vega S95 Meta (my device)
>
> The (Gbit TX) problem seems to be gone on the Odroid-C2 with Jerome's
> patch which disables EEE in drivers/net/phy/realtek.c (at least in his
> tests, I don't have that device so I can't verify).
> The same problem still appears on my Tronsmart Vega S95 Meta even with
> the patched PHY driver.

just an doubt, maybe useful, in the past, on GiGa setup I saw similar
problems and it was due to retiming so maybe 2ns could be necessary
(or better granularity via PAD logic if available).

Regards
Peppe

> Unfortunately I don't have a second device to rule out that my
> Tronsmart Vega S95 Meta could be broken (not unlikely, I get DDR
> errors from time to time in u-boot). Maybe Andreas Faerber can test
> ethernet with and without Jerome's patch on one of his Tronsmart
> devices.
>
>
> Regards,
> Martin
>

  reply	other threads:[~2016-11-14  7:47 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-11 20:39 Martin Blumenstingl
2016-09-12 16:37 ` Alexandre Torgue
2016-09-12 21:26   ` Martin Blumenstingl
2016-09-17 21:23     ` André Roth
2016-09-26  6:17       ` Giuseppe CAVALLARO
2016-10-01 15:58         ` Martin Blumenstingl
2016-11-03 16:36           ` Jerome Brunet
2016-11-05 12:20             ` Martin Blumenstingl
2016-11-13 19:20             ` André Roth
     [not found] ` <216F2694-1C1D-44DA-AC15-57ED15C24BBE@bluematt.me>
2016-09-12 21:29   ` Martin Blumenstingl
2016-09-14 15:30 ` Giuseppe CAVALLARO
2016-09-18 20:42   ` André Roth
2016-09-19  5:38     ` Giuseppe CAVALLARO
2016-10-01 20:15   ` Martin Blumenstingl
2016-10-01 20:40     ` Martin Blumenstingl
2016-10-31 10:25     ` André Roth
2016-11-03 16:57       ` Jerome Brunet
2016-11-07 10:59         ` Giuseppe CAVALLARO
2016-11-07 17:37           ` Martin Blumenstingl
2016-11-14  7:47             ` Giuseppe CAVALLARO [this message]
2016-11-14 11:02               ` Jerome Brunet
2016-11-14 15:00             ` Andreas Färber
2016-11-15 11:27               ` Jerome Brunet
2016-11-13 19:13         ` André Roth
2016-11-14 10:49           ` Jerome Brunet
2016-11-17 18:44             ` André Roth
2016-11-17 21:47               ` Jerome Brunet
2016-10-01 20:26   ` Martin Blumenstingl

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=68696e92-d056-5f29-9e71-72066f0c7673@st.com \
    --to=peppe.cavallaro@st.com \
    --cc=linus-amlogic@lists.infradead.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

all inboxes | Powered by JetHome®