public inbox for netdev@vger.kernel.org
 help / color / mirror / Atom feed
From: Vladimir Oltean <olteanv@gmail.com>
To: David Epping <david.epping@missinglinkelectronics.com>
Cc: Andrew Lunn <andrew@lunn.ch>,
	Heiner Kallweit <hkallweit1@gmail.com>,
	Russell King <linux@armlinux.org.uk>,
	"David S . Miller" <davem@davemloft.net>,
	Eric Dumazet <edumazet@google.com>,
	Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
	UNGLinuxDriver@microchip.com
Subject: Re: [PATCH net 3/3] net: phy: mscc: enable VSC8501/2 RGMII RX clock
Date: Sun, 21 May 2023 16:43:56 +0300	[thread overview]
Message-ID: <20230521134356.ar3itavhdypnvasc@skbuf> (raw)
In-Reply-To: <20230520160603.32458-4-david.epping@missinglinkelectronics.com>

On Sat, May 20, 2023 at 06:06:03PM +0200, David Epping wrote:
> +/* For VSC8501 and VSC8502 the RGMII RX clock output is disabled by default. */
> +static int vsc85xx_rgmii_enable_rx_clk(struct phy_device *phydev,
> +				       u32 rgmii_cntl)
> +{
> +	int rc, phy_id;
> +
> +	phy_id = phydev->drv->phy_id & phydev->drv->phy_id_mask;
> +	if (PHY_ID_VSC8501 != phy_id && PHY_ID_VSC8502 != phy_id)
> +		return 0;

Not only bit 11 is reserved for VSC8530, but it's also read-only, so it
should not matter what is written there.

Since vsc85xx_rgmii_enable_rx_clk() and vsc85xx_rgmii_set_skews() write
to the same register, would it not make sense to combine the two into a
single phy_modify_paged() call, and to zeroize bit 11 as part of that?

The other caller of vsc85xx_rgmii_set_skews(), VSC8572, unfortunately
does not document bit 11 at all - it doesn't say if it's read-only or not.
We could conditionally include the VSC8502_RGMII_RX_CLK_DISABLE bit in the
"mask" argument of phy_modify_paged() based on rgmii_cntl == VSC8502_RGMII_CNTL,
such as to exclude VSC8572.

What do you think?

  parent reply	other threads:[~2023-05-21 13:44 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-20 16:06 [PATCH net 0/3] net: phy: mscc: support VSC8501 David Epping
2023-05-20 16:06 ` [PATCH net 1/3] net: phy: mscc: add VSC8502 to MODULE_DEVICE_TABLE David Epping
2023-05-21 12:28   ` Vladimir Oltean
2023-05-20 16:06 ` [PATCH net 2/3] net: phy: mscc: add support for VSC8501 David Epping
2023-05-21 12:28   ` Vladimir Oltean
2023-05-20 16:06 ` [PATCH net 3/3] net: phy: mscc: enable VSC8501/2 RGMII RX clock David Epping
2023-05-21 12:35   ` Vladimir Oltean
2023-05-21 13:12     ` Vladimir Oltean
2023-05-21 16:08       ` David Epping
2023-05-21 13:43   ` Vladimir Oltean [this message]
2023-05-21 16:16     ` David Epping
2023-05-22  9:49       ` Vladimir Oltean
2023-05-22  9:54         ` Vladimir Oltean
2023-05-22  9:58       ` Vladimir Oltean
2023-05-22 14:00         ` David Epping
2023-05-22 14:42           ` Andrew Lunn
2023-05-22 15:11           ` Vladimir Oltean
2023-05-22 15:22             ` David Epping
2023-05-22 15:42               ` Vladimir Oltean
2023-05-21 17:59   ` Russell King (Oracle)
2023-05-22 13:48     ` David Epping
2023-05-21 13:33 ` [PATCH net 0/3] net: phy: mscc: support VSC8501 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=20230521134356.ar3itavhdypnvasc@skbuf \
    --to=olteanv@gmail.com \
    --cc=UNGLinuxDriver@microchip.com \
    --cc=andrew@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=david.epping@missinglinkelectronics.com \
    --cc=edumazet@google.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=pabeni@redhat.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