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: Mon, 7 Mar 2016 16:09:24 +0100 [thread overview]
Message-ID: <56DD99A4.5030004@st.com> (raw)
In-Reply-To: <56DD8FBE.9010200@suse.de>
Hi Andreas
On 3/7/2016 3:27 PM, Andreas F?rber wrote:
> Hello Giuseppe,
>
> Am 07.03.2016 um 14:26 schrieb Giuseppe CAVALLARO:
>> On 3/7/2016 1:35 PM, Andreas F?rber wrote:
>>> Am 07.03.2016 um 13:24 schrieb Heiko St?bner:
>>>> Am Montag, 7. M?rz 2016, 13:17:54 schrieb Andreas F?rber:
>>>>> Am 06.03.2016 um 20:53 schrieb Andreas F?rber:
>>>>>> On next-20160304 the GMAC seems to have regressed, it no longer
>>>>>> finds the
>>>>>> PHY:
>>>>>>
>>>>>> libphy: PHY stmmac-0:ffffffff not found
>>
>> snps,phy-addr is not correct. Can you check it?
>
> It was never set:
>
> https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/tree/arch/arm64/boot/dts/rockchip/rk3368.dtsi#n436
>
> https://github.com/afaerber/linux/blob/96c5b5fd395fee5713755e93e677fb011cb9ddc0/arch/arm64/boot/dts/rockchip/rk3368-geekbox.dts#L114
>
>> In the stmmac_mdio if this is not passed as parameter the bus should
>> be scanned and the first IDs found should select the right address.
>> I suppose in your box there is a real transceiver, so maybe the patch
>> from Gabriel is not actually necessary.
>
> On the GeekBox module there's an RTL8211E phy.
>
> Indeed, reverting Gabriel's commit fixes the observed error messages:
>
> rk_gmac-dwmac ff290000.ethernet eth0: Link is Up - 1Gbps/Full - flow
> control rx/tx
so this means that the phy is found and the link auto-negotiated.
Gabriel, it sounds that the patch solved a regression you found on
a configuration where the MAC dialogs with a switch but it breaks the
setup with use a std transceiver.
> http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/drivers/net/ethernet/stmicro?id=88f8b1bb41c6208f81b6a480244533ded7b59493
>
> However, I am unable to ping any hosts on the network now.
hmm, this could be another problem. I wonder if you can
check which recent patch is introducing the problem on ARM64.
For example if this depends on Oct_2015 update.
If you share some logs to me I can take a look at them.
Then we can try to check if the problem in on rx or tx path.
I also ask you yo check the axi settings.
Let me know
Regards
peppe
>
> Regards,
> Andreas
>
>>>>>> eth0: Could not attach to PHY
>>>>>> stmmac_open: Cannot attach to PHY (error: -19)
>>>>>
>>>>> Still with us in next-20160307. CC'ing stmmac maintainers.
>>
>> peppe
>>
>>>>
>>>> do you remember from what revision you rebased away from, when it was
>>>> still
>>>> working (as a known-good state)?
>>>
>>> Hm, next-20160111 possibly... leaving all the 5 days and 4 days ago
>>> changes as candidates ("stmmac: share reset function between dwmac100
>>> and dwmac1000" .. "stmmac: Fix 'eth0: No PHY found' regression").
>
next prev parent reply other threads:[~2016-03-07 15:09 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 [this message]
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
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=56DD99A4.5030004@st.com \
--to=peppe.cavallaro@st$(echo .)com \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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