From: Andrew Lunn <andrew@lunn.ch>
To: Antoine Tenart <antoine.tenart@bootlin.com>
Cc: davem@davemloft.net, f.fainelli@gmail.com, hkallweit1@gmail.com,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
foss@0leil.net
Subject: Re: [PATCH net-next v2 3/3] net: phy: mscc: RGMII skew delay configuration
Date: Fri, 28 Feb 2020 17:29:42 +0100 [thread overview]
Message-ID: <20200228162942.GF29979@lunn.ch> (raw)
In-Reply-To: <20200228155702.2062570-4-antoine.tenart@bootlin.com>
> +static void vsc8584_rgmii_set_skews(struct phy_device *phydev)
> +{
> + u32 skew_rx, skew_tx;
> + struct device *dev = &phydev->mdio.dev;
> +
> + /* We first set the Rx and Tx skews to their default value in h/w
> + * (0.2 ns).
> + */
> + skew_rx = VSC8584_RGMII_SKEW_0_2;
> + skew_tx = VSC8584_RGMII_SKEW_0_2;
> +
> + /* Based on the interface mode, we then retrieve (if available) Rx
> + * and/or Tx skews from the device tree. We do not fail if the
> + * properties do not exist, the default skew configuration is a valid
> + * one.
> + */
> + if (phydev->interface == PHY_INTERFACE_MODE_RGMII_ID ||
> + phydev->interface == PHY_INTERFACE_MODE_RGMII_RXID)
> + of_property_read_u32(dev->of_node, "vsc8584,rgmii-skew-rx",
> + &skew_rx);
> + if (phydev->interface == PHY_INTERFACE_MODE_RGMII_ID ||
> + phydev->interface == PHY_INTERFACE_MODE_RGMII_TXID)
> + of_property_read_u32(dev->of_node, "vsc8584,rgmii-skew-tx",
> + &skew_tx);
Hi Antoine
That is not the correct meaning of PHY_INTERFACE_MODE_RGMII_ID etc.
PHY_INTERFACE_MODE_RGMII_ID means add a 2ns delay on both RX and TX.
PHY_INTERFACE_MODE_RGMII_RXID means add a 2ns delay on the RX.
PHY_INTERFACE_MODE_RGMII means 0 delay, with the assumption that
either the MAC is adding the delay, or the PCB is designed with extra
copper tracks to add the delay.
You only need "vsc8584,rgmii-skew-rx" when 2ns is not correct for you
board, and you need more fine grain control.
What is not clearly defined, is how you combine
PHY_INTERFACE_MODE_RGMII* with DT properties. I guess i would enforce
that phydev->interface is PHY_INTERFACE_MODE_RGMII and then the delays
in DT are absolute values.
There is also some discussion about what should go in DT. #defines
like you have, or time in pS, and the driver converts to register
values. I generally push towards pS.
Andrew
next prev parent reply other threads:[~2020-02-28 16:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-28 15:56 [PATCH net-next v2 0/3] net: phy: mscc: add support for RGMII MAC mode Antoine Tenart
2020-02-28 15:57 ` [PATCH net-next v2 1/3] " Antoine Tenart
2020-02-28 16:14 ` Andrew Lunn
2020-02-28 15:57 ` [PATCH net-next v2 2/3] dt-bindings: net: phy: mscc: document rgmii skew properties Antoine Tenart
2020-02-28 15:57 ` [PATCH net-next v2 3/3] net: phy: mscc: RGMII skew delay configuration Antoine Tenart
2020-02-28 16:29 ` Andrew Lunn [this message]
2020-02-28 16:48 ` Antoine Tenart
2020-02-28 17:26 ` Andrew Lunn
2020-02-28 21:15 ` Antoine Tenart
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=20200228162942.GF29979@lunn.ch \
--to=andrew@lunn.ch \
--cc=antoine.tenart@bootlin.com \
--cc=davem@davemloft.net \
--cc=f.fainelli@gmail.com \
--cc=foss@0leil.net \
--cc=hkallweit1@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.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).