From: Carlo Caione <ccaione@baylibre.com>
To: Russell King - ARM Linux admin <linux@armlinux.org.uk>,
Heiner Kallweit <hkallweit1@gmail.com>
Cc: mark.rutland@arm.com, andrew@lunn.ch, f.fainelli@gmail.com,
devicetree@vger.kernel.org, s.hauer@pengutronix.de,
robh+dt@kernel.org, abailon@baylibre.com, kernel@pengutronix.de,
fabio.estevam@nxp.com, shawnguo@kernel.org, aisheng.dong@nxp.com,
linux-arm-kernel@lists.infradead.org, linux-imx@nxp.com
Subject: Re: [PATCH 0/3] at803x: Add quirk to disable SmartEEE
Date: Wed, 30 Jan 2019 10:16:39 +0000 [thread overview]
Message-ID: <5b7fa0ee-eea9-d92f-5cdf-6c1b83a61c89@baylibre.com> (raw)
In-Reply-To: <20190128190401.zzus6m6fjxpyf36d@e5254000004ec.dyn.armlinux.org.uk>
On 28/01/2019 19:04, Russell King - ARM Linux admin wrote:
Hi Russell,
> There is no "advertisement of SmartEEE" - it's just EEE. That is
> because as far as the link partner is concerned, SmartEEE is just
> EEE.
>
> Carlio posted a link to one of the datasheets for the family. In
> there, it describes the EEE capability register, which describes
> what is supported, and the EEE wake error counter register.
>
> It also describes the EEE advertisement and link parter advertisement
> registers.
>
> All these registers correspond to the 802.3 section 45 defined MMD
> and address offsets found in Clause 45 compliant PHYs, and these
> registers control not only EEE but also SmartEEE.
>
> Please stop thinking that SmartEEE is different on the link partner
> side from EEE - as far as the link partner is concerned, there is
> no difference. The difference is all to do with the MAC side of
> the local PHY.
Thank you for clarifying how the SmartEEE is really working.
Now, the problem is that the MMD registers controlling the EEE (7.3c and
7.3d, touched by the "eee-broken-*" property) are not the same as the
ones for the SmartEEE (3.805b, 3.805c, 3.805d). So, is it worth to add a
new DT property to deal also with the cases where we want to selectively
disable the SmartEEE?
Thanks,
--
Carlo Caione
next prev parent reply other threads:[~2019-01-30 10:16 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-25 12:55 [PATCH 0/3] at803x: Add quirk to disable SmartEEE Carlo Caione
2019-01-25 12:55 ` [PATCH 1/3] net: phy: at803x: Introduce " Carlo Caione
2019-01-25 12:55 ` [PATCH 2/3] dt-bindings: net: at803x: Document at803x, smarteee-disabled property Carlo Caione
2019-01-25 18:42 ` [PATCH 2/3] dt-bindings: net: at803x: Document at803x,smarteee-disabled property Florian Fainelli
2019-01-25 12:55 ` [PATCH 3/3] arm64: dts: imx8mq-evk: Disable SmartEEE Carlo Caione
2019-01-25 13:06 ` [PATCH 0/3] at803x: Add quirk to disable SmartEEE Russell King - ARM Linux admin
2019-01-25 18:15 ` Heiner Kallweit
2019-01-25 18:48 ` Carlo Caione
2019-01-25 19:07 ` Heiner Kallweit
2019-01-25 19:19 ` Russell King - ARM Linux admin
2019-01-25 19:27 ` Heiner Kallweit
2019-01-28 10:46 ` Carlo Caione
2019-01-28 15:57 ` Russell King - ARM Linux admin
2019-01-28 18:23 ` Heiner Kallweit
2019-01-28 19:04 ` Russell King - ARM Linux admin
2019-01-30 10:16 ` Carlo Caione [this message]
2019-01-30 10:47 ` Russell King - ARM Linux admin
2019-04-12 0:25 ` Vladimir Oltean
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=5b7fa0ee-eea9-d92f-5cdf-6c1b83a61c89@baylibre.com \
--to=ccaione@baylibre.com \
--cc=abailon@baylibre.com \
--cc=aisheng.dong@nxp.com \
--cc=andrew@lunn.ch \
--cc=devicetree@vger.kernel.org \
--cc=f.fainelli@gmail.com \
--cc=fabio.estevam@nxp.com \
--cc=hkallweit1@gmail.com \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=linux@armlinux.org.uk \
--cc=mark.rutland@arm.com \
--cc=robh+dt@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@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