[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <32df3424-a9c3-c69c-2b45-731647f27e01@baylibre.com>
Date: Wed, 22 May 2019 16:02:22 +0200
From: Neil Armstrong <narmstrong@...libre.com>
To: Jose Abreu <Jose.Abreu@...opsys.com>,
Simon Huelck <simonmail@....de>,
Sebastian Gottschall <s.gottschall@...media-net.de>,
Jerome Brunet <jbrunet@...libre.com>,
Martin Blumenstingl <martin.blumenstingl@...glemail.com>
Cc: "linux-amlogic@...ts.infradead.org"
<linux-amlogic@...ts.infradead.org>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
"alexandre.torgue@...com" <alexandre.torgue@...com>,
Emiliano Ingrassia <ingrassia@...genesys.com>,
"Gpeppe.cavallaro@...com" <Gpeppe.cavallaro@...com>
Subject: Re: stmmac / meson8b-dwmac
Hi Jose,
On 13/05/2019 11:07, Jose Abreu wrote:
> From: Simon Huelck <simonmail@....de>
> Date: Sat, May 11, 2019 at 15:53:34
>
>> ethtool -S gave me some counts for mmc_rx_fifo_overflow, which i didnt
>> recognize before.
>
> Flow Control can prevent this to happen. Please check if your DT FIFO
> bindings are >= 4096.
Actually our DT node minimalist :
ethmac: ethernet@...10000 {
compatible = "amlogic,meson-gxbb-dwmac", "snps,dwmac-3.710", "snps,dwmac";
reg = <0x0 0xc9410000 0x0 0x10000
0x0 0xc8834540 0x0 0x4>;
interrupts = <GIC_SPI 8 IRQ_TYPE_LEVEL_HIGH>;
interrupt-names = "macirq";
};
(I removed pinctrl, clocks and reset)
The dwmac bindings are quite complex, and we aren't sure how to describe correctly the HW.
Could you point us on the right direction ?
Thanks,
Neil
>
>> Do we have new ideas / new direction to dig for ?
>
> GIT Bisect is the best direction to follow.
>
> Thanks,
> Jose Miguel Abreu
> _______________________________________________
> linux-amlogic mailing list
> linux-amlogic@...ts.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-amlogic
>
Powered by blists - more mailing lists