public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Giuseppe CAVALLARO <peppe.cavallaro@st.com>
To: "Tomeu Vizoso" <tomeu@tomeuvizoso.net>,
	"Dinh Nguyen" <dinh.linux@gmail.com>,
	"Andreas Färber" <afaerber@suse.de>
Cc: "Fabrice GASNIER" <fabrice.gasnier@st.com>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	"Heiko Stübner" <heiko@sntech.de>,
	netdev@vger.kernel.org,
	"open list:ARM/Rockchip SoC..."
	<linux-rockchip@lists.infradead.org>,
	LAKML <linux-arm-kernel@lists.infradead.org>,
	"Gabriel Fernandez" <gabriel.fernandez@linaro.org>,
	"Alexandre TORGUE" <alexandre.torgue@st.com>,
	"Frank Schäfer" <fschaefer.oss@googlemail.com>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v3 0/8] arm64: rockchip: Initial GeekBox enablement
Date: Wed, 9 Mar 2016 15:53:02 +0100	[thread overview]
Message-ID: <56E038CE.606@st.com> (raw)
In-Reply-To: <56E033C8.40506@st.com>

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.

  Andreas: you are also using 3.50 with normal desc but I have not
           clear if just reverting 0e80bdc9a72d  commit the
           network is ok or you see timeout issues.

In the meantime I am trying to find a box where try normal setup
and I can confirm that enhanced descriptors are ok on my side

Regards
Peppe




On 3/9/2016 3:31 PM, Giuseppe CAVALLARO wrote:
> Hi Tomeu
>
> On 3/9/2016 11:53 AM, Tomeu Vizoso wrote:
>> On 9 March 2016 at 11:27, Giuseppe CAVALLARO <peppe.cavallaro@st.com>
>> wrote:
>>> Hello Tomeu, Andreas,
>>>
>>> On 3/9/2016 10:52 AM, Giuseppe CAVALLARO wrote:
>>>>>
>>>>> * today's linux-next: probe failed
>>>>>
>>>>> * today's linux-next + revert of 88f8b1bb41c6 stmmac: Fix 'eth0: No
>>>>> PHY found' regression: probe succeeded but no network at all
>>>>>
>>>>> * today's linux-next + revert of 88f8b1bb41c6 (stmmac: Fix 'eth0: No
>>>>> PHY found' regression) + revert of 0e80bdc9a72d (stmmac: first frame
>>>>> prep at the end of xmit routine): probe succeeded, dhcp succeeds and
>>>>> nfsroot works for a few seconds before timing out
>>>>
>>>>
>>>> ok, I was looking at this problem now that seems to related
>>>> the "stmmac: first frame prep at the end of xmit routine"
>>>> that, at first glance, is breaking the gmac 3.50 with normal
>>>> descriptor.
>>>
>>>
>>> I have no Hw where to test this use case. So, I wonder if may I ask
>>> you to
>>> test some patch.
>>>
>>> This first patch adds a missing barrier to the normal routine that
>>> inits the
>>> descriptor. Barrier was needed to well manage the OWN
>>> descriptor and it was not added in case of normal desc case after
>>> the xmit rework.
>>>
>>> Then I will check the algo behind the new xmit and in case of problems,
>>> if you agree, we will decide to revert it because it aimed to add an
>>> optimization.
>>>
>>> Let me know if you agree.
>>
>> I'm not sure what you would like to be tested, but just in case, I
>> have just tried your patch on top of these commits and the result is
>> the "transmit queue 0 timed out" error during boot:
>>
>> 6542b30d0a67 Revert "stmmac: first frame prep at the end of xmit routine"
>> eb5274cbc0f7 Revert "stmmac: do not poll phy handler when attach a
>> switch"
>> e88e625a68d9 Revert "stmmac: fix phy init when attached to a phy"
>> ef5dd3777876 stmmac: fix MDIO settings
>> 77634ba1f25c Revert "stmmac: Fix 'eth0: No PHY found' regression"
>> 7811b4ffc312 Add linux-next specific files for 20160309
>
> I missed that the issue is not only related the
>    "stmmac: first frame prep at the end of xmit routine"
> I have to try to test on 3.50 with normal descriptor.
> When using enhanced descriptors all works fine on my
> side.
>
> I keep you informed.
>
> peppe
>
>
>> Regards,
>>
>> Tomeu
>>
>>> Regards
>>> Peppe
>>
>>
>
>
>

  reply	other threads:[~2016-03-09 14:53 UTC|newest]

Thread overview: 29+ 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 1/8] Documentation: devicetree: Add vendor prefix for GeekBuying.com Andreas Färber
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 4/8] Documentation: devicetree: Clean up gpio-keys example Andreas Färber
2016-03-07 18:05   ` Heiko Stübner
2016-03-07 18:27     ` 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
     [not found] ` <56DD7172.4000707@suse.de>
     [not found]   ` <2714888.1DdqvJZ8cb@diego>
     [not found]     ` <56DD7593.5060003@suse.de>
     [not found]       ` <56DD8176.2080603@st.com>
     [not found]         ` <56DD8FBE.9010200@suse.de>
     [not found]           ` <56DD99A4.5030004@st.com>
     [not found]             ` <56DDA26C.3050301@suse.de>
     [not found]               ` <56DDA3D5.3090209@st.com>
     [not found]                 ` <56DDB749.1020808@suse.de>
     [not found]                   ` <CADhT+wfO8x4En78g5ixnnwbpaeXJGDo+Q1sOABYsbXzNZy0CPw@mail.gmail.com>
     [not found]                     ` <56DE7E1D.5070508@st.com>
     [not found]                       ` <CADhT+weKf+F98uxCQhRa2RfMm8+4p=rrNZc-Vf=w_HPycXto=A@mail.gmail.com>
     [not found]                         ` <CAAObsKD9HoEbtV_JMz_R=bcrQseDmhncRAWP9k8djksL-LMQqw@mail.gmail.com>
     [not found]                           ` <56DFE55B.2090806@st.com>
     [not found]                             ` <56DFE64B.8060606@st.com>
     [not found]                               ` <CAAObsKBr9SXg1-wr9O-ypR8JozdGpeAwfDLMeUKi8ozxkKyTXg@mail.gmail.com>
     [not found]                                 ` <56DFF253.9050208@st.com>
2016-03-09 10:27                                   ` [PATCH v3 0/8] arm64: rockchip: Initial GeekBox enablement Giuseppe CAVALLARO
2016-03-09 10:53                                     ` Tomeu Vizoso
2016-03-09 14:31                                       ` Giuseppe CAVALLARO
2016-03-09 14:53                                         ` Giuseppe CAVALLARO [this message]
2016-03-09 16:31                                           ` Dinh Nguyen
2016-03-10  9:13                                             ` Giuseppe CAVALLARO
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

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=56E038CE.606@st.com \
    --to=peppe.cavallaro@st.com \
    --cc=afaerber@suse.de \
    --cc=alexandre.torgue@st.com \
    --cc=devicetree@vger.kernel.org \
    --cc=dinh.linux@gmail.com \
    --cc=fabrice.gasnier@st.com \
    --cc=fschaefer.oss@googlemail.com \
    --cc=gabriel.fernandez@linaro.org \
    --cc=heiko@sntech.de \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rockchip@lists.infradead.org \
    --cc=netdev@vger.kernel.org \
    --cc=tomeu@tomeuvizoso.net \
    /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