From: "Andreas Färber" <afaerber@suse.de>
To: Giuseppe CAVALLARO <peppe.cavallaro@st.com>
Cc: netdev@vger.kernel.org, gabriel.fernandez@linaro.org,
fschaefer.oss@googlemail.com, dinh.linux@gmail.com,
davem@davemloft.net, preid@electromag.com.au,
Tomeu Vizoso <tomeu@tomeuvizoso.net>
Subject: Re: [PATCHv3 (net.git) 2/2] stmmac: fix MDIO settings
Date: Wed, 16 Mar 2016 10:47:27 +0100 [thread overview]
Message-ID: <56E92BAF.3020001@suse.de> (raw)
In-Reply-To: <56E82FF3.5010402@st.com>
Hi Peppe,
Am 15.03.2016 um 16:53 schrieb Giuseppe CAVALLARO:
> On 3/15/2016 1:54 AM, Andreas Färber wrote:
>> The connectivity issue still remains. Kernel log snippet:
>>
>> [ +0.001117] rk_gmac-dwmac ff290000.ethernet: Looking up phy-supply
>> from device tree
>> [ +0.000028] rk808 0-001b: Looking up vcc12-supply from device tree
>> [ +0.000014] vcc_lan: supplied by vcc_io
>> [ +0.000101] rk_gmac-dwmac ff290000.ethernet: clock input or output?
>> (input).
>> [ +0.000009] rk_gmac-dwmac ff290000.ethernet: TX delay(0x30).
>> [ +0.000008] rk_gmac-dwmac ff290000.ethernet: RX delay(0x10).
>> [ +0.000014] rk_gmac-dwmac ff290000.ethernet: init for RGMII
>> [ +0.000104] rk_gmac-dwmac ff290000.ethernet: clock input from PHY
>> [ +0.005063] rk_gmac-dwmac ff290000.ethernet: no reset control found
>> [ +0.000007] stmmac - user ID: 0x10, Synopsys ID: 0x35
>> [ +0.000002] Ring mode enabled
>> [ +0.000006] DMA HW capability register supported
>> [ +0.000000] Normal descriptors
>
> ^^^^^^^^^^^^^^^^^^
>
>> [ +0.000003] RX Checksum Offload Engine supported (type 2)
>> [ +0.000002] TX Checksum insertion supported
>> [ +0.000002] Wake-Up On Lan supported
>> [ +0.000053] Enable RX Mitigation via HW Watchdog Timer
>> [ +0.000771] of_get_named_gpiod_flags: can't parse 'snps,reset-gpio'
>> property of node '/ethernet@ff290000[0]'
>> [ +0.004250] libphy: stmmac: probed
>> [ +0.000009] eth0: PHY ID 001cc915 at 0 IRQ POLL (stmmac-0:00) active
>> [ +0.000005] eth0: PHY ID 001cc915 at 1 IRQ POLL (stmmac-0:01)
>>
>> As before, reverting "stmmac: first frame prep at the end of xmit
>> routine" fixes it. My test cases are `ping 192.168.1.1` and `zypper up`.
>
> so on your side, this revert fixes the issue and you do not see any
> tx watchdog as Tomeu's raised.
Confirmed, the system ran stable over night. I don't use NFS on that
system myself, having GMAC working only since v2.
> I have fixed some problems on top of
> "stmmac: first frame prep at the end of xmit ..." please
> see patch attached for net-next.
>
> Indeed, the normal tx descriptors are well filled w/o
> "stmmac: first frame prep at the end of xmit ..."
>
> I wonder if you could try the attachment in order to understand if we
> have to actually revert the patch (I ask you to not revert the
> patch "stmmac: first frame...").
Works great on top of next-20160314 with i2c plus this series, please
add my Tested-by. Thanks a lot for investigating!
Cheers,
Andreas
--
SUSE Linux GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Felix Imendörffer, Jane Smithard, Graham Norton; HRB 21284 (AG Nürnberg)
next prev parent reply other threads:[~2016-03-16 9:47 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-11 13:33 [PATCHv3 (net.git) 0/2] stmmac: MDIO fixes Giuseppe Cavallaro
2016-03-11 13:33 ` [PATCH v3(linux-sti-3.10)(net.git) 1/2] Revert "stmmac: Fix 'eth0: No PHY found' regression" Giuseppe Cavallaro
2016-03-11 13:33 ` [PATCHv3 (net.git) 2/2] stmmac: fix MDIO settings Giuseppe Cavallaro
2016-03-11 15:14 ` Phil Reid
2016-03-11 15:32 ` Giuseppe CAVALLARO
2016-03-14 0:50 ` Phil Reid
2016-03-12 10:50 ` Frank Schäfer
2016-03-14 9:14 ` Gabriel Fernandez
2016-03-14 9:28 ` Giuseppe CAVALLARO
2016-03-15 0:54 ` Andreas Färber
2016-03-15 15:53 ` Giuseppe CAVALLARO
2016-03-16 9:47 ` Andreas Färber [this message]
2016-03-16 10:18 ` 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=56E92BAF.3020001@suse.de \
--to=afaerber@suse.de \
--cc=davem@davemloft.net \
--cc=dinh.linux@gmail.com \
--cc=fschaefer.oss@googlemail.com \
--cc=gabriel.fernandez@linaro.org \
--cc=netdev@vger.kernel.org \
--cc=peppe.cavallaro@st.com \
--cc=preid@electromag.com.au \
--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;
as well as URLs for NNTP newsgroup(s).