From: Vladimir Oltean <olteanv@gmail.com> To: Russell King - ARM Linux admin <linux@armlinux.org.uk> Cc: Andrew Lunn <andrew@lunn.ch>, David Jander <david@protonic.nl>, Florian Fainelli <f.fainelli@gmail.com>, Oleksij Rempel <o.rempel@pengutronix.de>, netdev <netdev@vger.kernel.org>, Sascha Hauer <s.hauer@pengutronix.de>, lkml <linux-kernel@vger.kernel.org>, Fabio Estevam <festevam@gmail.com>, dl-linux-imx <linux-imx@nxp.com>, kernel@pengutronix.de, Shawn Guo <shawnguo@kernel.org>, "moderated list:ARM/Mediatek SoC support" <linux-arm-kernel@lists.infradead.org>, Heiner Kallweit <hkallweit1@gmail.com> Subject: Re: [PATCH v2] ARM: imx: allow to disable board specific PHY fixups Date: Tue, 31 Mar 2020 18:40:13 +0300 [thread overview] Message-ID: <CA+h21hriL_8gGE8iqShuR0h3m2si=MLTuKk12Btx3=XB1RM++g@mail.gmail.com> (raw) In-Reply-To: <20200331151503.GO25745@shell.armlinux.org.uk> Hi Russell, On Tue, 31 Mar 2020 at 18:15, Russell King - ARM Linux admin <linux@armlinux.org.uk> wrote: > > On Tue, Mar 31, 2020 at 02:54:33PM +0200, Andrew Lunn wrote: > > > - Disable the SmartEEE feature of the phy. The comment in the code implies > > > that for some reason it doesn't work, but the reason itself is not given. > > > Anyway, disabling SmartEEE should IMHO opinion be controlled by a DT > > > setting. There is no reason to believe this problem is specific to the > > > i.MX6. Besides, it is a feature of the phy, so it seems logical to expose > > > that via the DT. Once that is done, it has no place here. > > > > The device tree properties are defined: > > > > bindings/net/ethernet-phy.yaml: eee-broken-100tx: > > bindings/net/ethernet-phy.yaml: eee-broken-1000t: > > bindings/net/ethernet-phy.yaml: eee-broken-10gt: > > bindings/net/ethernet-phy.yaml: eee-broken-1000kx: > > bindings/net/ethernet-phy.yaml: eee-broken-10gkx4: > > bindings/net/ethernet-phy.yaml: eee-broken-10gkr: > > > > And there is a helper: > > > > void of_set_phy_eee_broken(struct phy_device *phydev) > > Disabling the advertisement may solve it, but that is not known. > What the quirk is doing is disabling the SmartEEE feature only > (which is where the PHY handles the EEE so-called "transparently" > to the MAC). > > It's all very well waving arms years later and saying we don't > like code that was merged, but unless someone can prove that an > alternative way is better and doesn't regress anything, there > won't be a way forward. > For what it's worth, your position on these device tree bindings for broken EEE seems to have changed from the one that you expressed in this thread: https://www.spinics.net/lists/arm-kernel/msg703453.html To quote from that: > > 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. > > [...] > > > > Otherwise, using the existing "eee-broken-*" properties to disable the > > link modes where EEE fails would be the correct way forward, and should > > be used in preference to disabling SmartEEE. > > > > However, no one has mentioned what the problem that is trying to be > > addressed. Is it data corruption? Is it that the link fails? Is it > > lost packets? Is it that the MAC supports EEE? I think there needs to > > be some better understanding of the problem at hand before trying to > > address it. Regards, -Vladimir
WARNING: multiple messages have this Message-ID (diff)
From: Vladimir Oltean <olteanv@gmail.com> To: Russell King - ARM Linux admin <linux@armlinux.org.uk> Cc: Andrew Lunn <andrew@lunn.ch>, Florian Fainelli <f.fainelli@gmail.com>, netdev <netdev@vger.kernel.org>, Sascha Hauer <s.hauer@pengutronix.de>, lkml <linux-kernel@vger.kernel.org>, Oleksij Rempel <o.rempel@pengutronix.de>, dl-linux-imx <linux-imx@nxp.com>, kernel@pengutronix.de, David Jander <david@protonic.nl>, Shawn Guo <shawnguo@kernel.org>, Fabio Estevam <festevam@gmail.com>, "moderated list:ARM/Mediatek SoC support" <linux-arm-kernel@lists.infradead.org>, Heiner Kallweit <hkallweit1@gmail.com> Subject: Re: [PATCH v2] ARM: imx: allow to disable board specific PHY fixups Date: Tue, 31 Mar 2020 18:40:13 +0300 [thread overview] Message-ID: <CA+h21hriL_8gGE8iqShuR0h3m2si=MLTuKk12Btx3=XB1RM++g@mail.gmail.com> (raw) In-Reply-To: <20200331151503.GO25745@shell.armlinux.org.uk> Hi Russell, On Tue, 31 Mar 2020 at 18:15, Russell King - ARM Linux admin <linux@armlinux.org.uk> wrote: > > On Tue, Mar 31, 2020 at 02:54:33PM +0200, Andrew Lunn wrote: > > > - Disable the SmartEEE feature of the phy. The comment in the code implies > > > that for some reason it doesn't work, but the reason itself is not given. > > > Anyway, disabling SmartEEE should IMHO opinion be controlled by a DT > > > setting. There is no reason to believe this problem is specific to the > > > i.MX6. Besides, it is a feature of the phy, so it seems logical to expose > > > that via the DT. Once that is done, it has no place here. > > > > The device tree properties are defined: > > > > bindings/net/ethernet-phy.yaml: eee-broken-100tx: > > bindings/net/ethernet-phy.yaml: eee-broken-1000t: > > bindings/net/ethernet-phy.yaml: eee-broken-10gt: > > bindings/net/ethernet-phy.yaml: eee-broken-1000kx: > > bindings/net/ethernet-phy.yaml: eee-broken-10gkx4: > > bindings/net/ethernet-phy.yaml: eee-broken-10gkr: > > > > And there is a helper: > > > > void of_set_phy_eee_broken(struct phy_device *phydev) > > Disabling the advertisement may solve it, but that is not known. > What the quirk is doing is disabling the SmartEEE feature only > (which is where the PHY handles the EEE so-called "transparently" > to the MAC). > > It's all very well waving arms years later and saying we don't > like code that was merged, but unless someone can prove that an > alternative way is better and doesn't regress anything, there > won't be a way forward. > For what it's worth, your position on these device tree bindings for broken EEE seems to have changed from the one that you expressed in this thread: https://www.spinics.net/lists/arm-kernel/msg703453.html To quote from that: > > 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. > > [...] > > > > Otherwise, using the existing "eee-broken-*" properties to disable the > > link modes where EEE fails would be the correct way forward, and should > > be used in preference to disabling SmartEEE. > > > > However, no one has mentioned what the problem that is trying to be > > addressed. Is it data corruption? Is it that the link fails? Is it > > lost packets? Is it that the MAC supports EEE? I think there needs to > > be some better understanding of the problem at hand before trying to > > address it. Regards, -Vladimir _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2020-03-31 15:40 UTC|newest] Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-03-29 11:04 [PATCH v2] ARM: imx: allow to disable board specific PHY fixups Oleksij Rempel 2020-03-29 11:04 ` Oleksij Rempel 2020-03-29 15:08 ` Andrew Lunn 2020-03-29 15:08 ` Andrew Lunn 2020-03-30 5:26 ` Oleksij Rempel 2020-03-30 5:26 ` Oleksij Rempel 2020-03-30 17:33 ` Florian Fainelli 2020-03-30 17:33 ` Florian Fainelli 2020-03-30 17:41 ` Russell King - ARM Linux admin 2020-03-30 17:41 ` Russell King - ARM Linux admin 2020-03-31 7:47 ` Marc Kleine-Budde 2020-03-31 7:47 ` Marc Kleine-Budde 2020-03-31 7:54 ` Russell King - ARM Linux admin 2020-03-31 7:54 ` Russell King - ARM Linux admin 2020-03-31 8:00 ` Marc Kleine-Budde 2020-03-31 8:00 ` Marc Kleine-Budde 2020-03-31 8:19 ` Russell King - ARM Linux admin 2020-03-31 8:19 ` Russell King - ARM Linux admin 2020-04-01 6:33 ` Oleksij Rempel 2020-04-01 6:33 ` Oleksij Rempel 2020-04-01 17:10 ` Florian Fainelli 2020-04-01 17:10 ` Florian Fainelli 2020-03-31 8:06 ` Philippe Schenker 2020-03-31 8:06 ` Philippe Schenker 2020-03-31 8:44 ` David Jander 2020-03-31 8:44 ` David Jander 2020-03-31 9:36 ` Russell King - ARM Linux admin 2020-03-31 9:36 ` Russell King - ARM Linux admin 2020-03-31 15:41 ` David Jander 2020-03-31 15:41 ` David Jander 2020-03-31 15:53 ` Russell King - ARM Linux admin 2020-03-31 15:53 ` Russell King - ARM Linux admin 2020-03-31 12:54 ` Andrew Lunn 2020-03-31 12:54 ` Andrew Lunn 2020-03-31 15:15 ` Russell King - ARM Linux admin 2020-03-31 15:15 ` Russell King - ARM Linux admin 2020-03-31 15:40 ` Vladimir Oltean [this message] 2020-03-31 15:40 ` Vladimir Oltean 2020-03-31 17:03 ` Russell King - ARM Linux admin 2020-03-31 17:03 ` Russell King - ARM Linux admin 2020-03-31 17:16 ` Oleksij Rempel 2020-03-31 17:16 ` Oleksij Rempel 2020-03-31 17:46 ` Russell King - ARM Linux admin 2020-03-31 17:46 ` Russell King - ARM Linux admin 2020-03-31 13:45 ` Oleksij Rempel 2020-03-31 13:45 ` Oleksij Rempel 2020-03-31 14:08 ` Russell King - ARM Linux admin 2020-03-31 14:08 ` Russell King - ARM Linux admin
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='CA+h21hriL_8gGE8iqShuR0h3m2si=MLTuKk12Btx3=XB1RM++g@mail.gmail.com' \ --to=olteanv@gmail.com \ --cc=andrew@lunn.ch \ --cc=david@protonic.nl \ --cc=f.fainelli@gmail.com \ --cc=festevam@gmail.com \ --cc=hkallweit1@gmail.com \ --cc=kernel@pengutronix.de \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=linux-imx@nxp.com \ --cc=linux-kernel@vger.kernel.org \ --cc=linux@armlinux.org.uk \ --cc=netdev@vger.kernel.org \ --cc=o.rempel@pengutronix.de \ --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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.