Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S965401AbcCJJOJ (ORCPT ); Thu, 10 Mar 2016 04:14:09 -0500 Received: from mx08-00178001.pphosted.com ([91.207.212.93]:32480 "EHLO mx07-00178001.pphosted.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S934335AbcCJJNt (ORCPT ); Thu, 10 Mar 2016 04:13:49 -0500 Message-ID: <56E13AAB.2080900@st.com> Date: Thu, 10 Mar 2016 10:13:15 +0100 From: Giuseppe CAVALLARO User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0 MIME-Version: 1.0 To: Dinh Nguyen CC: Tomeu Vizoso , =?UTF-8?B?QW5kcmVhcyBGw6RyYmVy?= , Fabrice GASNIER , "devicetree@vger.kernel.org" , =?UTF-8?B?SGVpa28gU3TDvGJuZXI=?= , , "open list:ARM/Rockchip SoC..." , LAKML , Gabriel Fernandez , Alexandre TORGUE , =?UTF-8?B?RnJhbmsgU2Now6RmZXI=?= , LKML Subject: Re: [PATCH v3 0/8] arm64: rockchip: Initial GeekBox enablement References: <1457294038-14243-1-git-send-email-afaerber@suse.de> <56DD7172.4000707@suse.de> <2714888.1DdqvJZ8cb@diego> <56DD7593.5060003@suse.de> <56DD8176.2080603@st.com> <56DD8FBE.9010200@suse.de> <56DD99A4.5030004@st.com> <56DDA26C.3050301@suse.de> <56DDA3D5.3090209@st.com> <56DDB749.1020808@suse.de> <56DE7E1D.5070508@st.com> <56DFE55B.2090806@st.com> <56DFE64B.8060606@st.com> <56DFF253.9050208@st.com> <56DFFA9E.7060602@st.com> <56E033C8.40506@st.com> <56E038CE.606@st.com> In-Reply-To: Content-Type: text/plain; charset="UTF-8"; format=flowed Content-Transfer-Encoding: 7bit X-Originating-IP: [10.52.139.40] X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:,, definitions=2016-03-10_06:,, signatures=0 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1628 Lines: 43 On 3/9/2016 5:31 PM, Dinh Nguyen wrote: > On Wed, Mar 9, 2016 at 8:53 AM, Giuseppe CAVALLARO > 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