linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: peppe.cavallaro@st.com (Giuseppe CAVALLARO)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 0/8] arm64: rockchip: Initial GeekBox enablement
Date: Thu, 10 Mar 2016 10:13:15 +0100	[thread overview]
Message-ID: <56E13AAB.2080900@st.com> (raw)
In-Reply-To: <CADhT+wcMpzA_Coj8Z5OQZsc3bF3a7yOmsbazQMPtcdUWkJSuCA@mail.gmail.com>

On 3/9/2016 5:31 PM, Dinh Nguyen wrote:
> On Wed, Mar 9, 2016 at 8:53 AM, Giuseppe CAVALLARO
> <peppe.cavallaro@st.com> wrote:
>> Hi Tomeu, Dinh, Andreas
>>
>> I need a sum and help from you to go ahead on the
>> tx timeout.
>>
>> The "stmmac: MDIO fixes" seems to be the candidate to
>> fix the phy connection and I will send the V2 asap (Andreas' comment).
>>
>> So, supposing the probe is ok and phy is connected,
>> I need your input ...
>>
>>   Tomeu: after revering the 0e80bdc9a72d (stmmac: first frame
>>          prep at the end of xmit routine) the network is
>>          not stable and there is a timeout after a while.
>>          The box has 3.50 with normal desc settings.
>>
>>   Dinh: the network is ok, I wonder if you can share a boot
>>         log just to understand if the normal or enhanced
>>         descriptors are used.
>>
>
> Here it is:
...
> [    0.850523] stmmac - user ID: 0x10, Synopsys ID: 0x37
> [    0.855570]  Ring mode enabled
> [    0.858611]  DMA HW capability register supported
> [    0.863128]  Enhanced/Alternate descriptors
> [    0.867482]  Enabled extended descriptors
> [    0.871482]  RX Checksum Offload Engine supported (type 2)
> [    0.876948]  TX Checksum insertion supported
> [    0.881204]  Enable RX Mitigation via HW Watchdog Timer
> [    0.886863] socfpga-dwmac ff702000.ethernet eth0: No MDIO subnode found
> [    0.899090] libphy: stmmac: probed
> [    0.902484] eth0: PHY ID 00221611 at 4 IRQ POLL (stmmac-0:04) active

Thx Dinh, so you are using the Enhanced/Alternate descriptors
I am debugging on my side on a setup with normal descriptors, I let you
know

peppe

  reply	other threads:[~2016-03-10  9:13 UTC|newest]

Thread overview: 47+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1457294038-14243-1-git-send-email-afaerber@suse.de>
2016-03-06 19:53 ` [PATCH v3 2/8] Documentation: devicetree: rockchip: Document GeekBox Andreas Färber
2016-03-06 19:53 ` [PATCH v3 3/8] arm64: dts: rockchip: Add GeekBox config Andreas Färber
2016-03-06 19:53 ` [PATCH v3 5/8] arm64: dts: rockchip: Clean up gpio-keys nodes Andreas Färber
2016-03-06 19:53 ` [PATCH v3 6/8] arm64: dts: rockchip: Add power key to GeekBox Andreas Färber
2016-03-10 23:04   ` Julien Chauveau
2016-03-16 10:58     ` Andreas Färber
2016-03-16 13:52       ` Andreas Färber
2016-03-10 23:09   ` Julien Chauveau
2016-03-06 19:53 ` [PATCH v3 7/8] Documentation: devicetree: rockchip: Document Landingship Andreas Färber
2016-03-17 14:46   ` Rob Herring
2016-03-06 19:53 ` [PATCH v3 8/8] arm64: dts: rockchip: Add Landingship config Andreas Färber
2016-03-07 12:17 ` [PATCH v3 0/8] arm64: rockchip: Initial GeekBox enablement Andreas Färber
2016-03-07 12:24   ` Heiko Stübner
2016-03-07 12:35     ` Andreas Färber
2016-03-07 13:26       ` Giuseppe CAVALLARO
2016-03-07 14:27         ` Andreas Färber
2016-03-07 15:09           ` Giuseppe CAVALLARO
2016-03-07 15:46             ` Andreas Färber
2016-03-07 15:52               ` Giuseppe CAVALLARO
2016-03-07 17:15                 ` Andreas Färber
2016-03-07 23:22                   ` Dinh Nguyen
2016-03-08  7:24                     ` Giuseppe CAVALLARO
2016-03-08 15:45                       ` Dinh Nguyen
2016-03-09  7:24                         ` Giuseppe CAVALLARO
2016-03-09  8:35                         ` Tomeu Vizoso
2016-03-09  8:56                           ` Giuseppe CAVALLARO
2016-03-09  9:00                             ` Giuseppe CAVALLARO
2016-03-09  9:42                               ` Tomeu Vizoso
2016-03-09  9:52                                 ` Giuseppe CAVALLARO
2016-03-09 10:27                                   ` Giuseppe CAVALLARO
2016-03-09 10:53                                     ` Tomeu Vizoso
2016-03-09 14:31                                       ` Giuseppe CAVALLARO
2016-03-09 14:53                                         ` Giuseppe CAVALLARO
2016-03-09 16:31                                           ` Dinh Nguyen
2016-03-10  9:13                                             ` Giuseppe CAVALLARO [this message]
2016-03-10 16:47                                               ` Dinh Nguyen
2016-03-11  9:09                                                 ` Giuseppe CAVALLARO
2016-03-14 11:43                                                   ` Tomeu Vizoso
2016-03-14 16:20                                                     ` Giuseppe CAVALLARO
2016-03-15  7:23                                                       ` Tomeu Vizoso
2016-03-15 12:36                                                         ` Giuseppe CAVALLARO
2016-03-30 16:44                                                           ` Dinh Nguyen
2016-03-31  7:53                                                             ` Giuseppe CAVALLARO
2016-03-08 10:03                     ` Gabriel Fernandez
2016-03-08 10:24                       ` Giuseppe CAVALLARO
2016-03-08 10:33                         ` Gabriel Fernandez
2016-03-11 12:12   ` Michael Trimarchi

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=56E13AAB.2080900@st.com \
    --to=peppe.cavallaro@st.com \
    --cc=linux-arm-kernel@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;
as well as URLs for NNTP newsgroup(s).