From: Simon Horman <horms@kernel.org>
To: chalianis1@gmail.com
Cc: andrew@lunn.ch, hkallweit1@gmail.com, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, linux@armlinux.org.uk,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
stable@vger.kernel.org
Subject: Re: [PATCH net] phy: dp83869: fix interrupts issue when using with an optical fiber sfp. to correctly clear the interrupts both status registers must be read.
Date: Sat, 26 Jul 2025 21:05:38 +0100 [thread overview]
Message-ID: <20250726200538.GO1367887@horms.kernel.org> (raw)
In-Reply-To: <20250726001034.28885-1-chalianis1@gmail.com>
On Fri, Jul 25, 2025 at 08:10:34PM -0400, chalianis1@gmail.com wrote:
> From: Anis Chali <chalianis1@gmail.com>
>
> from datasheet of dp83869hm
> 7.3.6 Interrupt
> The DP83869HM can be configured to generate an interrupt when changes of internal status occur. The interrupt
> allows a MAC to act upon the status in the PHY without polling the PHY registers. The interrupt source can be
> selected through the interrupt registers, MICR (12h) and FIBER_INT_EN (C18h). The interrupt status can be
> read from ISR (13h) and FIBER_INT_STTS (C19h) registers. Some interrupts are enabled by default and can
> be disabled through register access. Both the interrupt status registers must be read in order to clear pending
> interrupts. Until the pending interrupts are cleared, new interrupts may not be routed to the interrupt pin.
>
> Fixes: 01db923e8377 ("net: phy: dp83869: Add TI dp83869 phy")
>
> Cc: stable@vger.kernel.org
> Signed-off-by: Anis Chali <chalianis1@gmail.com>
> ---
> drivers/net/phy/dp83869.c | 7 +++++++
> 1 file changed, 7 insertions(+)
>
> diff --git a/drivers/net/phy/dp83869.c b/drivers/net/phy/dp83869.c
> index a62cd838a9ea..1e8c20f387b8 100644
> --- a/drivers/net/phy/dp83869.c
> +++ b/drivers/net/phy/dp83869.c
> @@ -41,6 +41,7 @@
> #define DP83869_IO_MUX_CFG 0x0170
> #define DP83869_OP_MODE 0x01df
> #define DP83869_FX_CTRL 0x0c00
> +#define DP83869_FX_INT_STS 0x0c19
>
> #define DP83869_SW_RESET BIT(15)
> #define DP83869_SW_RESTART BIT(14)
> @@ -195,6 +196,12 @@ static int dp83869_ack_interrupt(struct phy_device *phydev)
> if (err < 0)
> return err;
>
> + if (linkmode_test_bit(ETHTOOL_LINK_MODE_FIBRE_BIT, phydev->supported)) {
> + err = phy_read_mmd(phydev, DP83869_DEVADDR, DP83869_FX_INT_STS);
> + if (err < 0)
> + return err;
Hi Anis,
Its invisible, of course, but the line above has trailing whitespace.
Flagged by checkpatch.
> + }
> +
> return 0;
> }
>
> --
> 2.49.0
>
>
next prev parent reply other threads:[~2025-07-26 20:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-26 0:10 [PATCH net] phy: dp83869: fix interrupts issue when using with an optical fiber sfp. to correctly clear the interrupts both status registers must be read chalianis1
2025-07-26 0:14 ` Jakub Kicinski
2025-07-26 15:14 ` Andrew Lunn
2025-07-26 20:05 ` Simon Horman [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-07-26 0:09 chalianis1
2025-05-19 14:47 chalianis1
2025-05-19 15:01 ` Andrew Lunn
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=20250726200538.GO1367887@horms.kernel.org \
--to=horms@kernel.org \
--cc=andrew@lunn.ch \
--cc=chalianis1@gmail.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 \
--cc=stable@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