On 25/01/19 20:27, Heiner Kallweit wrote:
/cut
Thanks for the link. According to the description SmartEEE works
only if
both link partners support it (hence are Atheros PHY's). I would assume
that this usually isn't the case, shouldn't the feature be an opt-in
therefore?
I'm not convinced about that - I've been using AtherOS SmartEEE with
i.MX6 for quite some time (I have patches which allow me to read out
the stats via ethtool, and configure it - they're specific to the
FEC driver though.) SmartEEE works just like EEE for me, and I
notice no problems.
I have i.MX6 boards connected to Netgear GS116 and similar switches,
and also Marvell DSA switches on other platforms.
This is why I said above about "more detail". Then maybe folk would
know what to look for to see whether there is a problem.
OK, then the description of the referenced patch isn't fully correct
and SmartEEE and EEE are partially compatible, and the problem is
just that we don't know exactly to which extent.
Reading from the datasheet at [0] it seems that SmartEEE is compatible
with EEE but it's something different.
With SmartEEE the PHY can actually enter LPI state even if this is not
supported by the link partner since the LPI pattern is generated inside
the PHY itself, so auto-implementing a sort of EEE.
So AFAICT EEE and SmartEEE are two different things requiring two
different properties in the DTS if we want to have the possibility to
disable it.
Cheers,
[0]
https://media.digikey.com/pdf/Data%20Sheets/CSR%20PDFs/AR8031_DS_(Atheros)_Rev1.0_Aug2011.pdf
--
Carlo Caione
