From: Andrew Lunn <andrew@lunn.ch>
To: David Jander <david@protonic.nl>
Cc: Russell King - ARM Linux admin <linux@armlinux.org.uk>,
Florian Fainelli <f.fainelli@gmail.com>,
Oleksij Rempel <o.rempel@pengutronix.de>,
netdev@vger.kernel.org, Sascha Hauer <s.hauer@pengutronix.de>,
linux-kernel@vger.kernel.org, Fabio Estevam <festevam@gmail.com>,
linux-imx@nxp.com, kernel@pengutronix.de,
Shawn Guo <shawnguo@kernel.org>,
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 14:54:33 +0200 [thread overview]
Message-ID: <20200331125433.GA24486@lunn.ch> (raw)
In-Reply-To: <20200331104459.6857474e@erd988>
> - 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)
> - Enable TXC delay. To clarify, the RGMII specification version 1 specified
> that the RXC and TXC traces should be routed long enough to introduce a
> certain delay to the clock signal, or the delay should be introduced via
> other means. In a later version of the spec, a provision was given for MAC
> or PHY devices to generate this delay internally. The i.MX6 MAC interface
> is unable to generate the required delay internally, so it has to be taken
> care of either by the board layout, or by the PHY device. This is the
> crucial point: The amount of delay set by the PHY delay register depends on
> the board layout. It should NEVER be hard-coded in SoC setup code. The
> correct way is to specify it in the DT. Needless to say that this too,
> isn't i.MX6-specific.
Correct:
# RX and TX delays are added by the MAC when required
- rgmii
# RGMII with internal RX and TX delays provided by the PHY,
# the MAC should not add the RX or TX delays in this case
- rgmii-id
# RGMII with internal RX delay provided by the PHY, the MAC
# should not add an RX delay in this case
- rgmii-rxid
# RGMII with internal TX delay provided by the PHY, the MAC
# should not add an TX delay in this case
- rgmii-txid
The needed properties exist.
I think part of the issue is that there are iMX6 board which are not
device tree?
Andrew
next prev parent reply other threads:[~2020-03-31 12:54 UTC|newest]
Thread overview: 24+ 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 15:08 ` Andrew Lunn
2020-03-30 5:26 ` Oleksij Rempel
2020-03-30 17:33 ` Florian Fainelli
2020-03-30 17:41 ` Russell King - ARM Linux admin
2020-03-31 7:47 ` Marc Kleine-Budde
2020-03-31 7:54 ` Russell King - ARM Linux admin
2020-03-31 8:00 ` Marc Kleine-Budde
2020-03-31 8:19 ` Russell King - ARM Linux admin
2020-04-01 6:33 ` Oleksij Rempel
2020-04-01 17:10 ` Florian Fainelli
2020-03-31 8:06 ` Philippe Schenker
2020-03-31 8:44 ` David Jander
2020-03-31 9:36 ` Russell King - ARM Linux admin
2020-03-31 15:41 ` David Jander
2020-03-31 15:53 ` Russell King - ARM Linux admin
2020-03-31 12:54 ` Andrew Lunn [this message]
2020-03-31 15:15 ` Russell King - ARM Linux admin
2020-03-31 15:40 ` Vladimir Oltean
2020-03-31 17:03 ` Russell King - ARM Linux admin
2020-03-31 17:16 ` Oleksij Rempel
2020-03-31 17:46 ` Russell King - ARM Linux admin
2020-03-31 13:45 ` Oleksij Rempel
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=20200331125433.GA24486@lunn.ch \
--to=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: 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).