devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Vladimir Oltean <olteanv@gmail.com>
To: Prasanna Vengateshan <prasanna.vengateshan@microchip.com>
Cc: andrew@lunn.ch, netdev@vger.kernel.org, robh+dt@kernel.org,
	UNGLinuxDriver@microchip.com, woojung.huh@microchip.com,
	hkallweit1@gmail.com, linux@armlinux.org.uk, davem@davemloft.net,
	kuba@kernel.org, linux-kernel@vger.kernel.org,
	vivien.didelot@gmail.com, f.fainelli@gmail.com,
	devicetree@vger.kernel.org
Subject: Re: [PATCH v8 net-next 06/10] net: dsa: microchip: add support for phylink management
Date: Mon, 7 Feb 2022 19:27:13 +0200	[thread overview]
Message-ID: <20220207172713.efts4o7b7xor37uu@skbuf> (raw)
In-Reply-To: <20220207172204.589190-7-prasanna.vengateshan@microchip.com>

On Mon, Feb 07, 2022 at 10:52:00PM +0530, Prasanna Vengateshan wrote:
> +static void lan937x_apply_rgmii_delay(struct ksz_device *dev, int port,
> +				      phy_interface_t interface, u8 val)
> +{
> +	struct ksz_port *p = &dev->ports[port];
> +
> +	/* Clear Ingress & Egress internal delay enabled bits */
> +	val &= ~(PORT_RGMII_ID_EG_ENABLE | PORT_RGMII_ID_IG_ENABLE);
> +
> +	if (interface == PHY_INTERFACE_MODE_RGMII_TXID ||
> +	    interface == PHY_INTERFACE_MODE_RGMII_ID) {
> +		/* if the delay is 0, let us not enable DLL */
> +		if (p->rgmii_tx_val) {
> +			lan937x_update_rgmii_tx_rx_delay(dev, port, true);
> +			dev_info(dev->dev, "Applied rgmii tx delay for the port %d\n",
> +				 port);
> +			val |= PORT_RGMII_ID_EG_ENABLE;
> +		}
> +	}
> +
> +	if (interface == PHY_INTERFACE_MODE_RGMII_RXID ||
> +	    interface == PHY_INTERFACE_MODE_RGMII_ID) {
> +		/* if the delay is 0, let us not enable DLL */
> +		if (p->rgmii_rx_val) {
> +			lan937x_update_rgmii_tx_rx_delay(dev, port, false);
> +			dev_info(dev->dev, "Applied rgmii rx delay for the port %d\n",
> +				 port);
> +			val |= PORT_RGMII_ID_IG_ENABLE;
> +		}
> +	}
> +
> +	/* Enable RGMII internal delays */
> +	lan937x_pwrite8(dev, port, REG_PORT_XMII_CTRL_1, val);
> +}
> +
> +void lan937x_mac_config(struct ksz_device *dev, int port,
> +			phy_interface_t interface)
> +{
> +	u8 data8;
> +
> +	lan937x_pread8(dev, port, REG_PORT_XMII_CTRL_1, &data8);
> +
> +	/* clear MII selection & set it based on interface later */
> +	data8 &= ~PORT_MII_SEL_M;
> +
> +	/* configure MAC based on interface */
> +	switch (interface) {
> +	case PHY_INTERFACE_MODE_MII:
> +		lan937x_config_gbit(dev, false, &data8);
> +		data8 |= PORT_MII_SEL;
> +		break;
> +	case PHY_INTERFACE_MODE_RMII:
> +		lan937x_config_gbit(dev, false, &data8);
> +		data8 |= PORT_RMII_SEL;
> +		break;
> +	case PHY_INTERFACE_MODE_RGMII:
> +		lan937x_config_gbit(dev, true, &data8);
> +		data8 |= PORT_RGMII_SEL;
> +		break;
> +	case PHY_INTERFACE_MODE_RGMII_ID:
> +	case PHY_INTERFACE_MODE_RGMII_TXID:
> +	case PHY_INTERFACE_MODE_RGMII_RXID:
> +		lan937x_config_gbit(dev, true, &data8);
> +		data8 |= PORT_RGMII_SEL;
> +
> +		/* Apply rgmii internal delay for the mac */
> +		lan937x_apply_rgmii_delay(dev, port, interface, data8);

I think the agreement from previous discussions was to apply RGMII delay
_exclusively_ based on the 'rx-internal-delay-ps' and 'tx-internal-delay-ps'
properties, at least for new drivers with no legacy. You are omitting to
apply delays in phy-mode = "rgmii", which contradicts that agreement.
I think you should treat all 4 RGMII cases the same, and remove the
interface checks from lan937x_apply_rgmii_delay.

> +
> +		/* rgmii delay configuration is already applied above,
> +		 * hence return from here as no changes required
> +		 */
> +		return;
> +	default:
> +		dev_err(dev->dev, "Unsupported interface '%s' for port %d\n",
> +			phy_modes(interface), port);
> +		return;
> +	}
> +
> +	/* Write the updated value */
> +	lan937x_pwrite8(dev, port, REG_PORT_XMII_CTRL_1, data8);
> +}

  reply	other threads:[~2022-02-07 17:34 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-07 17:21 [PATCH v8 net-next 00/10] net: dsa: microchip: DSA driver support for LAN937x switch Prasanna Vengateshan
2022-02-07 17:21 ` [PATCH v8 net-next 01/10] dt-bindings: net: dsa: dt bindings for microchip lan937x Prasanna Vengateshan
2022-02-08  2:53   ` Florian Fainelli
2022-02-09 11:58     ` Prasanna Vengateshan
2022-02-12  3:56       ` Florian Fainelli
2022-02-18 16:38         ` Prasanna Vengateshan
2022-02-22 19:47           ` Florian Fainelli
2022-03-02 11:41         ` Prasanna Vengateshan
2022-03-10 17:27           ` Prasanna Vengateshan
2022-02-07 17:21 ` [PATCH v8 net-next 02/10] net: dsa: move mib->cnt_ptr reset code to ksz_common.c Prasanna Vengateshan
2022-02-08  2:53   ` Florian Fainelli
2022-02-07 17:21 ` [PATCH v8 net-next 03/10] net: phy: Add support for LAN937x T1 phy driver Prasanna Vengateshan
2022-02-08 13:09   ` Andrew Lunn
2022-02-09 11:27     ` Prasanna Vengateshan
2022-02-07 17:21 ` [PATCH v8 net-next 04/10] net: dsa: tag_ksz: add tag handling for Microchip LAN937x Prasanna Vengateshan
2022-02-08  2:54   ` Florian Fainelli
2022-02-07 17:21 ` [PATCH v8 net-next 05/10] net: dsa: microchip: add DSA support for microchip lan937x Prasanna Vengateshan
2022-02-07 17:28   ` Vladimir Oltean
2022-02-07 17:22 ` [PATCH v8 net-next 06/10] net: dsa: microchip: add support for phylink management Prasanna Vengateshan
2022-02-07 17:27   ` Vladimir Oltean [this message]
2022-02-09 11:01     ` Prasanna Vengateshan
2022-02-07 17:22 ` [PATCH v8 net-next 07/10] net: dsa: microchip: add support for ethtool port counters Prasanna Vengateshan
2022-02-08  3:03   ` Florian Fainelli
2022-02-07 17:22 ` [PATCH v8 net-next 08/10] net: dsa: microchip: add support for port mirror operations Prasanna Vengateshan
2022-02-08  2:58   ` Florian Fainelli
2022-02-07 17:22 ` [PATCH v8 net-next 09/10] net: dsa: microchip: add support for fdb and mdb management Prasanna Vengateshan
2022-02-08  3:02   ` Florian Fainelli
2022-02-07 17:22 ` [PATCH v8 net-next 10/10] net: dsa: microchip: add support for vlan operations Prasanna Vengateshan
2022-02-08  2:59   ` Florian Fainelli

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=20220207172713.efts4o7b7xor37uu@skbuf \
    --to=olteanv@gmail.com \
    --cc=UNGLinuxDriver@microchip.com \
    --cc=andrew@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=devicetree@vger.kernel.org \
    --cc=f.fainelli@gmail.com \
    --cc=hkallweit1@gmail.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@armlinux.org.uk \
    --cc=netdev@vger.kernel.org \
    --cc=prasanna.vengateshan@microchip.com \
    --cc=robh+dt@kernel.org \
    --cc=vivien.didelot@gmail.com \
    --cc=woojung.huh@microchip.com \
    /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).