From: Andrew Lunn <andrew@lunn.ch>
To: chalianis1@gmail.com
Cc: 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 17:14:20 +0200 [thread overview]
Message-ID: <33f056e7-6bf4-47be-aa8b-95640bf2151c@lunn.ch> (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.
Reading this description, it sounds like the fibre interrupt it not
cascaded into the micr? There are two completely different sets of
registers.
So i seems like you should be reading this register in
dp83869_handle_interrupt() same as the MICR.
Andrew
---
pw-bot: cr
next prev parent reply other threads:[~2025-07-26 15:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-26 0:10 chalianis1
2025-07-26 0:14 ` Jakub Kicinski
2025-07-26 15:14 ` Andrew Lunn [this message]
2025-07-26 20:05 ` Simon Horman
-- 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=33f056e7-6bf4-47be-aa8b-95640bf2151c@lunn.ch \
--to=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
all inboxes | Powered by JetHome®