From: Andrew Lunn <andrew@lunn.ch>
To: chalianis1@gmail.com
Cc: hkallweit1@gmail.com, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, linux@armlinux.org.uk,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] net: phy: dp83869: fix interrupts issue, not correctly handled when operate with an optical fiber sfp.
Date: Mon, 19 May 2025 14:42:38 +0200 [thread overview]
Message-ID: <b62d0d20-6ba2-46ff-b581-7fea1e810300@lunn.ch> (raw)
In-Reply-To: <20250519022417.338302-1-chalianis1@gmail.com>
On Sun, May 18, 2025 at 10:24:17PM -0400, chalianis1@gmail.com wrote:
> From: Anis Chali <chalianis1@gmail.com>
>
> to correctly clear the interrupts both status registers must be read.
>
> from datasheet: http://ti.com/lit/ds/symlink/dp83869hm.pdf
> 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.
>
> Signed-off-by: Anis Chali <chalianis1@gmail.com>
This seems like something for stable?
https://www.kernel.org/doc/html/latest/process/stable-kernel-rules.html
Please include a Fixes: tag.
Please base this patch on the net tree:
https://www.kernel.org/doc/html/latest/process/maintainer-netdev.html
> ---
> 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..98d773175462 100644
> --- a/drivers/net/phy/dp83869.c
> +++ b/drivers/net/phy/dp83869.c
> @@ -25,6 +25,7 @@
> #define DP83869_CFG2 0x14
> #define DP83869_CTRL 0x1f
> #define DP83869_CFG4 0x1e
> +#define DP83869_FX_INT_STS 0xc19
It appears that this is an Extended register, so it belong after
DP83869_FX_CTRL?
Andrew
---
pw-bot: cr
prev parent reply other threads:[~2025-05-19 12:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-19 2:24 chalianis1
2025-05-19 12:42 ` Andrew Lunn [this message]
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=b62d0d20-6ba2-46ff-b581-7fea1e810300@lunn.ch \
--to=andrew@lunn.ch \
--cc=chalianis1@gmail.com \
--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
all inboxes | Powered by JetHome®