From: Joao Pinto <Joao.Pinto@synopsys.com>
To: Heiner Kallweit <hkallweit1@gmail.com>,
Joao Pinto <Joao.Pinto@synopsys.com>
Cc: <clabbe.montjoie@gmail.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
Corentin Labbe <clabbe.montjoie@gmail.com>
Subject: Re: linux-next-20170320 breaks stmmac on meson (Amlogic S905GXBB)
Date: Tue, 21 Mar 2017 10:13:08 +0000 [thread overview]
Message-ID: <88d2fa04-a9db-dbab-2c4f-03310ef7d540@synopsys.com> (raw)
In-Reply-To: <690d5153-7725-83e6-208a-6cb4cac3cd93@gmail.com>
Hi Heiner and Corentin,
Às 9:58 PM de 3/20/2017, Heiner Kallweit escreveu:
> As reported by Corentin Labbe before:
> stmmac in the latest next kernel is broken also on meson8b.
>
> The following commit seems to create the trouble:
> 6deee2221e11 "net: stmmac: prepare dma op mode config for multiple queues"
>
> I also get queue timeout errors.
>From what you are describing it seems that the tx op mode is not being
configured by some reason and so it is not enabled.
Please check if this path is being executed:
stmmac_mtl_configuration >> stmmac_dma_operation_mode >> priv->hw->dma->dma_tx_mode
It must iterate by all the available channels / queues, that should be =1 since
I assume you have a single queue:
if (priv->synopsys_id >= DWMAC_CORE_4_00) {
for (chan = 0; chan < rx_channels_count; chan++)
priv->hw->dma->dma_rx_mode(priv->ioaddr, rxmode, chan,
rxfifosz);
for (chan = 0; chan < tx_channels_count; chan++)
priv->hw->dma->dma_tx_mode(priv->ioaddr, txmode, chan);
Could you please check if RX and TX op mode are being programmed?
The rx and tx queue counters are initialized in stmmac_mtl_setup() function
(stmmac_platform.c). If they are not declared in DT they assume the default
value of 1.
>
> Rgds, Heiner
>
Thanks.
next prev parent reply other threads:[~2017-03-21 10:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-20 21:58 linux-next-20170320 breaks stmmac on meson (Amlogic S905GXBB) Heiner Kallweit
2017-03-21 10:13 ` Joao Pinto [this message]
2017-03-21 14:07 ` Corentin Labbe
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=88d2fa04-a9db-dbab-2c4f-03310ef7d540@synopsys.com \
--to=joao.pinto@synopsys.com \
--cc=clabbe.montjoie@gmail.com \
--cc=hkallweit1@gmail.com \
--cc=netdev@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).