public inbox for linux-arm-kernel@lists.infradead.org 
 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, 31 Mar 2016 09:53:26 +0200	[thread overview]
Message-ID: <56FCD776.2090206@st.com> (raw)
In-Reply-To: <CADhT+wdXXp322vmgFmWTUiiRZTsCWeJSSdU=BMEEbSyb_bnrUw@mail.gmail.com>

On 3/30/2016 6:44 PM, Dinh Nguyen wrote:
> On Tue, Mar 15, 2016 at 7:36 AM, Giuseppe CAVALLARO
> <peppe.cavallaro@st•com> wrote:
>> Hello Tomeu
>>
>> On 3/15/2016 8:23 AM, Tomeu Vizoso wrote:
>>>
>>> Thanks.
>>>
>>> Btw, I have rebased on top of 4.5 this morning and I have noticed that
>>> 88f8b1bb41c6 ("stmmac: Fix 'eth0: No PHY found' regression") got in
>>> there, so I guess we have now a bunch of boards with broken network on
>>> that release:(
>>
>>
>>
>> This is the status on my side: I am testing on an HW that has the
>> Enhanced descriptors and all works fine.
>>
>> On this HW, if I force the driver to use the normal descriptor
>> layout, I meet problems but using both net.git and net-next.
>> So I suspect I cannot ply with this HW forcing the normal descriptors.
>> But! That is helping me to check if, on net-next, the stmmac is
>> actually  programming fine the normal desc case.
>> I have just found another fix so I kindly ask you to apply the temp
>> patch  attached and let me know.
>> In details, I have noticed that the OWN bit was not set in the right
>> TDES0.
>>
>> I also ask you to give me a log of the kernel where the stmmac was
>> running fine. I would like to see which configuration it is selected
>> at runtime by the driver on your box.
>>  From your previous logs (where the stmmac failed), it seems that
>> the  problem is on normal desc but, to be honest, this is the first
>> case I see a 3.50a with HW capability register and w/o Enhanced
>> descriptors.
>>
>
> Are you still working on a fix for:
>
> [    1.196110] libphy: PHY stmmac-0:ffffffff not found
> [    1.200972] eth0: Could not attach to PHY
> [    1.204991] stmmac_open: Cannot attach to PHY (error: -19)
>
> I see the error still there as of linux-next 20160330.

this could be because the fixes have been not applied on net-next
I will check and resend all asap

peppe

>
> Dinh
>

  reply	other threads:[~2016-03-31  7:53 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
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 [this message]
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=56FCD776.2090206@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