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,
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: Mon, 19 May 2025 17:01:11 +0200 [thread overview]
Message-ID: <97d0e167-ef11-4cbf-a473-fb823d7b727a@lunn.ch> (raw)
In-Reply-To: <20250519144701.92264-1-chalianis1@gmail.com>
On Mon, May 19, 2025 at 10:47:01AM -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: interrupts issue when using with an optical fiber sfp.
The subject is now correct, but the Fixes: tag is supposed to be a git
hash for when the problem was introduced:
https://docs.kernel.org/process/submitting-patches.html#describe-your-changes
Andrew
---
pw-bot: cr
next prev parent reply other threads:[~2025-05-19 15:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-19 14:47 chalianis1
2025-05-19 15:01 ` Andrew Lunn [this message]
2025-07-26 0:09 chalianis1
2025-07-26 0:10 chalianis1
2025-07-26 0:14 ` Jakub Kicinski
2025-07-26 15:14 ` Andrew Lunn
2025-07-26 20:05 ` Simon Horman
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=97d0e167-ef11-4cbf-a473-fb823d7b727a@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 \
--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
all inboxes | Powered by JetHome®