public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: <Parthiban.Veerasooran@microchip.com>
To: <Divya.Koppera@microchip.com>
Cc: <Arun.Ramadoss@microchip.com>, <UNGLinuxDriver@microchip.com>,
	<andrew@lunn.ch>, <hkallweit1@gmail.com>, <linux@armlinux.org.uk>,
	<davem@davemloft.net>, <edumazet@google.com>, <kuba@kernel.org>,
	<pabeni@redhat.com>, <netdev@vger.kernel.org>,
	<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH net-next] net: phy: microchip_t1: Interrupt support for lan887x
Date: Tue, 1 Oct 2024 11:58:11 +0000	[thread overview]
Message-ID: <e585b195-3213-46d2-807c-5906d5332502@microchip.com> (raw)
In-Reply-To: <20240930153423.16893-1-divya.koppera@microchip.com>

Hi,

On 30/09/24 9:04 pm, Divya Koppera wrote:
> Add support for link up and link down interrupts in lan887x.
> 
> Signed-off-by: Divya Koppera <divya.koppera@microchip.com>
> ---
>   drivers/net/phy/microchip_t1.c | 63 ++++++++++++++++++++++++++++++++++
>   1 file changed, 63 insertions(+)
> 
> diff --git a/drivers/net/phy/microchip_t1.c b/drivers/net/phy/microchip_t1.c
> index a5ef8fe50704..383050a5b0ed 100644
> --- a/drivers/net/phy/microchip_t1.c
> +++ b/drivers/net/phy/microchip_t1.c
> @@ -226,6 +226,18 @@
>   #define MICROCHIP_CABLE_MAX_TIME_DIFF	\
>   	(MICROCHIP_CABLE_MIN_TIME_DIFF + MICROCHIP_CABLE_TIME_MARGIN)
>   
> +#define LAN887X_INT_STS				0xf000
> +#define LAN887X_INT_MSK				0xf001
> +#define LAN887X_INT_MSK_T1_PHY_INT_MSK		BIT(2)
> +#define LAN887X_INT_MSK_LINK_UP_MSK		BIT(1)
> +#define LAN887X_INT_MSK_LINK_DOWN_MSK		BIT(0)
> +
> +#define LAN887X_MX_CHIP_TOP_LINK_MSK	(LAN887X_INT_MSK_LINK_UP_MSK |\
> +					 LAN887X_INT_MSK_LINK_DOWN_MSK)
> +
> +#define LAN887X_MX_CHIP_TOP_ALL_MSK	(LAN887X_INT_MSK_T1_PHY_INT_MSK |\
> +					 LAN887X_MX_CHIP_TOP_LINK_MSK)
> +
>   #define DRIVER_AUTHOR	"Nisar Sayed <nisar.sayed@microchip.com>"
>   #define DRIVER_DESC	"Microchip LAN87XX/LAN937x/LAN887x T1 PHY driver"
>   
> @@ -1474,6 +1486,7 @@ static void lan887x_get_strings(struct phy_device *phydev, u8 *data)
>   		ethtool_puts(&data, lan887x_hw_stats[i].string);
>   }
>   
> +static int lan887x_config_intr(struct phy_device *phydev);
>   static int lan887x_cd_reset(struct phy_device *phydev,
>   			    enum cable_diag_state cd_done)
>   {
> @@ -1504,6 +1517,10 @@ static int lan887x_cd_reset(struct phy_device *phydev,
>   		if (rc < 0)
>   			return rc;
>   
> +		rc = lan887x_config_intr(phydev);
> +		if (rc < 0)
> +			return rc;
> +
>   		rc = lan887x_phy_reconfig(phydev);
>   		if (rc < 0)
>   			return rc;
> @@ -1830,6 +1847,50 @@ static int lan887x_cable_test_get_status(struct phy_device *phydev,
>   	return lan887x_cable_test_report(phydev);
>   }
>   
> +static int lan887x_config_intr(struct phy_device *phydev)
> +{
> +	int ret;
> +
> +	if (phydev->interrupts == PHY_INTERRUPT_ENABLED) {
> +		/* Clear the interrupt status before enabling interrupts */
> +		ret = phy_read_mmd(phydev, MDIO_MMD_VEND1, LAN887X_INT_STS);
> +		if (ret < 0)
> +			return ret;
> +
> +		/* Unmask for enabling interrupt */
> +		ret = phy_write_mmd(phydev, MDIO_MMD_VEND1, LAN887X_INT_MSK,
> +				    (u16)~LAN887X_MX_CHIP_TOP_ALL_MSK);
> +	} else {
> +		ret = phy_write_mmd(phydev, MDIO_MMD_VEND1, LAN887X_INT_MSK,
> +				    GENMASK(15, 0));
> +		if (ret < 0)
> +			return ret;
> +
> +		ret = phy_read_mmd(phydev, MDIO_MMD_VEND1, LAN887X_INT_STS);
> +	}
> +
> +	return ret < 0 ? ret : 0;
> +}
> +
> +static irqreturn_t lan887x_handle_interrupt(struct phy_device *phydev)
> +{
> +	int ret = IRQ_NONE;
I think you can remove 'ret' by simply returning IRQ_HANDLED and 
IRQ_NONE directly to save one line.

Best regards,
Parthiban V
> +	int irq_status;
> +
> +	irq_status = phy_read_mmd(phydev, MDIO_MMD_VEND1, LAN887X_INT_STS);
> +	if (irq_status < 0) {
> +		phy_error(phydev);
> +		return IRQ_NONE;
> +	}
> +
> +	if (irq_status & LAN887X_MX_CHIP_TOP_LINK_MSK) {
> +		phy_trigger_machine(phydev);
> +		ret = IRQ_HANDLED;
> +	}
> +
> +	return ret;
> +}
> +
>   static struct phy_driver microchip_t1_phy_driver[] = {
>   	{
>   		PHY_ID_MATCH_MODEL(PHY_ID_LAN87XX),
> @@ -1881,6 +1942,8 @@ static struct phy_driver microchip_t1_phy_driver[] = {
>   		.read_status	= genphy_c45_read_status,
>   		.cable_test_start = lan887x_cable_test_start,
>   		.cable_test_get_status = lan887x_cable_test_get_status,
> +		.config_intr    = lan887x_config_intr,
> +		.handle_interrupt = lan887x_handle_interrupt,
>   	}
>   };
>   


  parent reply	other threads:[~2024-10-01 11:58 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-30 15:34 [PATCH net-next] net: phy: microchip_t1: Interrupt support for lan887x Divya Koppera
2024-09-30 16:18 ` Kalesh Anakkur Purayil
2024-10-01  5:38   ` Divya.Koppera
2024-09-30 16:44 ` Andrew Lunn
2024-10-01  5:37   ` Divya.Koppera
2024-10-01 11:58 ` Parthiban.Veerasooran [this message]
2024-10-01 14:04   ` Divya.Koppera

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=e585b195-3213-46d2-807c-5906d5332502@microchip.com \
    --to=parthiban.veerasooran@microchip.com \
    --cc=Arun.Ramadoss@microchip.com \
    --cc=Divya.Koppera@microchip.com \
    --cc=UNGLinuxDriver@microchip.com \
    --cc=andrew@lunn.ch \
    --cc=davem@davemloft.net \
    --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