mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Joao Pinto <Joao.Pinto@synopsys.com>
To: Giuseppe CAVALLARO <peppe.cavallaro@st.com>,
	Corentin Labbe <clabbe.montjoie@gmail.com>,
	<alexandre.torgue@st.com>
Cc: <netdev@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
	Joao Pinto <Joao.Pinto@synopsys.com>
Subject: Re: linux-next-20170320 break stmmac on dwmac-sunxi
Date: Tue, 21 Mar 2017 14:49:36 +0000	[thread overview]
Message-ID: <3b6997f7-b1b9-a9f5-40b2-dcc7810820c6@synopsys.com> (raw)
In-Reply-To: <4184996f-08c7-b884-98f5-a9b4abf9e0ba@st.com>

Hi Peppe,

Às 2:39 PM de 3/21/2017, Giuseppe CAVALLARO escreveu:
> Hello Corentin
> 
> yes, bisect process is really good approach to me. Pls give us more details.
> Recently the multi DMA channel logic has been added so it could be that
> something is needed to allow your platform to manage the new code.
> Or we introduced some regression. If I have some other idea, I ping you.
> 
> Peppe
> 
> On 3/20/2017 8:54 PM, Corentin Labbe wrote:
>> Hello
>>
>> Just pushed next-20170320 to my boards and stmmac stop working on both intree
>> dwmac-sunxi and my dev dwmac-sun8i.
>> It seems that interrupts never fire, and transmit queue timeout.
>> I will try to bisect this problem but perhaps other people could try to
>> reproduce it.
>>
>> Regards
>> Corentin Labbe
>>
> 

Corentin spotted 2 bugs (dma_op_mode was only being set for core versions >=
4.00 and rx/tx default nº of queues was being set in a place that would not be
accessible if no multiqueue config is added to the DT). Thierry will send a set
of patches to improve soon.

Thanks,
Joao

      reply	other threads:[~2017-03-21 14:49 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-20 19:54 Corentin Labbe
2017-03-21  9:23 ` Giuseppe CAVALLARO
2017-03-21 14:39 ` Giuseppe CAVALLARO
2017-03-21 14:49   ` Joao Pinto [this message]

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=3b6997f7-b1b9-a9f5-40b2-dcc7810820c6@synopsys.com \
    --to=joao.pinto@synopsys.com \
    --cc=alexandre.torgue@st.com \
    --cc=clabbe.montjoie@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=peppe.cavallaro@st.com \
    /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

all inboxes | Powered by JetHome®