mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Gerhard Engleder <gerhard@engleder-embedded.com>
To: Horatiu Vultur <horatiu.vultur@microchip.com>
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
	andrew@lunn.ch, hkallweit1@gmail.com, linux@armlinux.org.uk,
	davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
	pabeni@redhat.com, richardcochran@gmail.com
Subject: Re: [PATCH net-next] net: phy: micrel: Add support for non PTP SKUs for lan8814
Date: Fri, 17 Oct 2025 23:15:21 +0200	[thread overview]
Message-ID: <79f403f0-84ed-43fe-b093-d7ce122d41fd@engleder-embedded.com> (raw)
In-Reply-To: <20251017074730.3057012-1-horatiu.vultur@microchip.com>

On 17.10.25 09:47, Horatiu Vultur wrote:
> The lan8814 has 4 different SKUs and for 2 of these SKUs the PTP is
> disabled. All these SKUs have the same value in the register 2 and 3
> meaning we can't differentiate them based on device id therefore check

Did you miss to start a new sentence?

> the SKU register and based on this allow or not to create a PTP device.
> 
> Signed-off-by: Horatiu Vultur <horatiu.vultur@microchip.com>
> ---
>   drivers/net/phy/micrel.c | 38 ++++++++++++++++++++++++++++++++++++++
>   1 file changed, 38 insertions(+)
> 
> diff --git a/drivers/net/phy/micrel.c b/drivers/net/phy/micrel.c
> index 79ce3eb6752b6..16855bf8c3916 100644
> --- a/drivers/net/phy/micrel.c
> +++ b/drivers/net/phy/micrel.c
> @@ -101,6 +101,8 @@
>   #define LAN8814_CABLE_DIAG_VCT_DATA_MASK	GENMASK(7, 0)
>   #define LAN8814_PAIR_BIT_SHIFT			12
>   
> +#define LAN8814_SKUS				0xB
> +
>   #define LAN8814_WIRE_PAIR_MASK			0xF
>   
>   /* Lan8814 general Interrupt control/status reg in GPHY specific block. */
> @@ -367,6 +369,9 @@
>   
>   #define LAN8842_REV_8832			0x8832
>   
> +#define LAN8814_REV_LAN8814			0x8814
> +#define LAN8814_REV_LAN8818			0x8818
> +
>   struct kszphy_hw_stat {
>   	const char *string;
>   	u8 reg;
> @@ -449,6 +454,7 @@ struct kszphy_priv {
>   	bool rmii_ref_clk_sel;
>   	bool rmii_ref_clk_sel_val;
>   	bool clk_enable;
> +	bool is_ptp_available;
>   	u64 stats[ARRAY_SIZE(kszphy_hw_stats)];
>   	struct kszphy_phy_stats phy_stats;
>   };
> @@ -4130,6 +4136,17 @@ static int lan8804_config_intr(struct phy_device *phydev)
>   	return 0;
>   }
>   
> +/* Check if the PHY has 1588 support. There are multiple skus of the PHY and
> + * some of them support PTP while others don't support it. This function will
> + * return true is the sku supports it, otherwise will return false.
> + */

Hasn't net also switched to the common kernel multiline comment style
starting with an empty line?

> +static bool lan8814_has_ptp(struct phy_device *phydev)
> +{
> +	struct kszphy_priv *priv = phydev->priv;
> +
> +	return priv->is_ptp_available;
> +}
> +
>   static irqreturn_t lan8814_handle_interrupt(struct phy_device *phydev)
>   {
>   	int ret = IRQ_NONE;
> @@ -4146,6 +4163,9 @@ static irqreturn_t lan8814_handle_interrupt(struct phy_device *phydev)
>   		ret = IRQ_HANDLED;
>   	}
>   
> +	if (!lan8814_has_ptp(phydev))
> +		return ret;
> +
>   	while (true) {
>   		irq_status = lanphy_read_page_reg(phydev, LAN8814_PAGE_PORT_REGS,
>   						  PTP_TSU_INT_STS);
> @@ -4207,6 +4227,9 @@ static void lan8814_ptp_init(struct phy_device *phydev)
>   	    !IS_ENABLED(CONFIG_NETWORK_PHY_TIMESTAMPING))
>   		return;
>   
> +	if (!lan8814_has_ptp(phydev))
> +		return;
> +
>   	lanphy_write_page_reg(phydev, LAN8814_PAGE_PORT_REGS,
>   			      TSU_HARD_RESET, TSU_HARD_RESET_);
>   
> @@ -4336,6 +4359,9 @@ static int __lan8814_ptp_probe_once(struct phy_device *phydev, char *pin_name,
>   
>   static int lan8814_ptp_probe_once(struct phy_device *phydev)
>   {
> +	if (!lan8814_has_ptp(phydev))
> +		return 0;
> +
>   	return __lan8814_ptp_probe_once(phydev, "lan8814_ptp_pin",
>   					LAN8814_PTP_GPIO_NUM);
>   }
> @@ -4450,6 +4476,18 @@ static int lan8814_probe(struct phy_device *phydev)
>   	devm_phy_package_join(&phydev->mdio.dev, phydev,
>   			      addr, sizeof(struct lan8814_shared_priv));
>   
> +	/* There are lan8814 SKUs that don't support PTP. Make sure that for
> +	 * those skus no PTP device is created. Here we check if the SKU
> +	 * supports PTP.
> +	 */

Check comment style.

> +	err = lanphy_read_page_reg(phydev, LAN8814_PAGE_COMMON_REGS,
> +				   LAN8814_SKUS);
> +	if (err < 0)
> +		return err;
> +
> +	priv->is_ptp_available = err == LAN8814_REV_LAN8814 ||
> +				 err == LAN8814_REV_LAN8818;
> +
>   	if (phy_package_init_once(phydev)) {
>   		err = lan8814_release_coma_mode(phydev);
>   		if (err)


  reply	other threads:[~2025-10-17 21:31 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-17  7:47 Horatiu Vultur
2025-10-17 21:15 ` Gerhard Engleder [this message]
2025-10-20  6:39   ` Horatiu Vultur
2025-10-20 18:11     ` Gerhard Engleder
2025-10-21  6:51       ` Horatiu Vultur
2025-10-21  9:03       ` Russell King (Oracle)
2025-10-21 23:14       ` Jakub Kicinski
2025-10-22  4:12         ` Gerhard Engleder

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=79f403f0-84ed-43fe-b093-d7ce122d41fd@engleder-embedded.com \
    --to=gerhard@engleder-embedded.com \
    --cc=andrew@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=hkallweit1@gmail.com \
    --cc=horatiu.vultur@microchip.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 \
    --cc=richardcochran@gmail.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

all inboxes | Powered by JetHome®