From: Joao Pinto <Joao.Pinto@synopsys.com>
To: David Miller <davem@davemloft.net>, <clabbe.montjoie@gmail.com>
Cc: <treding@nvidia.com>, <arnd@arndb.de>, <peppe.cavallaro@st.com>,
<alexandre.torgue@st.com>, <Joao.Pinto@synopsys.com>,
<netdev@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] [net-next] stmmac: use netif_set_real_num_{rx,tx}_queues
Date: Fri, 31 Mar 2017 11:14:10 +0100 [thread overview]
Message-ID: <d262f8c8-28f4-d6f5-3c01-4bca114667dd@synopsys.com> (raw)
In-Reply-To: <20170330.104832.599422532945133952.davem@davemloft.net>
Às 6:48 PM de 3/30/2017, David Miller escreveu:
> From: Thierry Reding <treding@nvidia.com>
> Date: Thu, 30 Mar 2017 16:34:36 +0200
>
>> On Thu, Mar 30, 2017 at 09:45:36AM +0200, Corentin Labbe wrote:
>>> On Tue, Mar 28, 2017 at 06:01:05PM -0700, David Miller wrote:
>>>> From: Arnd Bergmann <arnd@arndb.de>
>>>> Date: Tue, 28 Mar 2017 11:48:21 +0200
>>>>
>>>>> A driver must not access the two fields directly but should instead use
>>>>> the helper functions to set the values and keep a consistent internal
>>>>> state:
>>>>>
>>>>> ethernet/stmicro/stmmac/stmmac_main.c: In function 'stmmac_dvr_probe':
>>>>> ethernet/stmicro/stmmac/stmmac_main.c:4083:8: error: 'struct net_device' has no member named 'real_num_rx_queues'; did you mean 'real_num_tx_queues'?
>>>>>
>>>>> Fixes: a8f5102af2a7 ("net: stmmac: TX and RX queue priority configuration")
>>>>> Signed-off-by: Arnd Bergmann <arnd@arndb.de>
>>>>
>>>> Applied.
>>>
>>> This break my revert patch. (since it patch ("net: stmmac: enable multiple buffers").
>>> Since dwmac-sunxi is still broken, what can I do ? send two revert patch ? or adapt the reverting patch.
>>
>> Have you tried if the kcalloc() patch I sent on Tuesday fixes things the
>> issues introduced by the multiple buffers patch? Niklas reported that it
>> restores functionality on his setup.
>
> I think he said yesterday that he did indeed test all of your patches and it
> did not fix things for him.
>
> http://marc.info/?l=linux-kernel&m=149076922813085&w=2
>
> I am going to revert the enable multiple buffers commit, and I would ask that
> all involved parties work together in the background to resolve all of this.
>
> Thank you.
>
@David: Agreed.
@Corentin: Please check if the DMA Engine is well configured and if the dma
rx/tx has started. This is done by dumping the DMA Registers.
Please also check the MAC related registers and dump them in order to have a
clear picture if the IP is being well configured.
This is critial to analise what's hapenning in your setup.
Joao
next prev parent reply other threads:[~2017-03-31 10:16 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-28 9:48 Arnd Bergmann
2017-03-29 1:01 ` David Miller
2017-03-30 7:45 ` Corentin Labbe
2017-03-30 14:34 ` Thierry Reding
2017-03-30 16:35 ` Niklas Cassel
2017-03-30 16:42 ` Joao Pinto
2017-04-03 13:07 ` Giuseppe CAVALLARO
2017-04-03 13:12 ` Joao Pinto
2017-04-04 6:15 ` Giuseppe CAVALLARO
2017-03-30 17:48 ` David Miller
2017-03-31 10:14 ` Joao Pinto [this message]
2017-03-31 10:43 ` Joao Pinto
2017-03-31 16:57 ` David Miller
2017-03-31 16:58 ` Joao Pinto
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=d262f8c8-28f4-d6f5-3c01-4bca114667dd@synopsys.com \
--to=joao.pinto@synopsys.com \
--cc=alexandre.torgue@st.com \
--cc=arnd@arndb.de \
--cc=clabbe.montjoie@gmail.com \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=peppe.cavallaro@st.com \
--cc=treding@nvidia.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®