From: Charles Perry <charles.perry@microchip.com>
To: Andrew Lunn <andrew@lunn.ch>
Cc: "Russell King (Oracle)" <linux@armlinux.org.uk>,
Charles Perry <charles.perry@microchip.com>,
<netdev@vger.kernel.org>,
Maxime Chevallier <maxime.chevallier@bootlin.com>,
Heiner Kallweit <hkallweit1@gmail.com>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH net-next v3 2/2] net: mdio: add a driver for PIC64-HPSC/HX MDIO controller
Date: Tue, 31 Mar 2026 07:43:28 -0700 [thread overview]
Message-ID: <acvdkBF4ZjZaCHwd@bby-cbu-swbuild03.eng.microchip.com> (raw)
In-Reply-To: <88d652b9-ed4f-4bf4-b0ab-8703c15ce58b@lunn.ch>
On Tue, Mar 31, 2026 at 04:20:55PM +0200, Andrew Lunn wrote:
> On Tue, Mar 31, 2026 at 03:05:28PM +0100, Russell King (Oracle) wrote:
> > On Tue, Mar 31, 2026 at 06:42:02AM -0700, Charles Perry wrote:
> > > I don't know if there's any value in waiting for write completion here as
> > > write completion doesn't mean that the effects of the write are available
> > > right now. I also didn't run into any issues in my testing. Let me know if
> > > you know of a use case where this wouldn't work.
> > >
> > > I can add a wait for transaction completion if that's expected by phylib.
> >
> > Consider a PHY using a shared interrupt line, and the interrupt being
> > disabled in at the PHY before being torn down... wouldn't we want the
> > write to the register which enables interrupts to complete before we
> > unregister the interrupt handler for the particular PHY?
> >
> > I do notice that other MDIO drivers don't wait. Some PHY drivers don't
> > access the PHY after the write to disable interrupts either. So, maybe
> > phy_free_interrupt() should read-back from the PHY before calling
> > free_irq() to guarantee that the write has completed?
> >
> > Andrew?
>
> The general pattern is to not wait on write.
Ok, then it's status quo for this.
I'll send a v4 later this week for the other return issue.
Thanks,
Charles
next prev parent reply other threads:[~2026-03-31 14:43 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-31 12:38 [PATCH net-next v3 0/2] Add support for PIC64-HPSC/HX MDIO controller Charles Perry
2026-03-31 12:38 ` [PATCH net-next v3 1/2] dt-bindings: net: document Microchip " Charles Perry
2026-03-31 12:38 ` [PATCH net-next v3 2/2] net: mdio: add a driver for " Charles Perry
2026-03-31 12:51 ` Andrew Lunn
2026-03-31 12:57 ` Russell King (Oracle)
2026-03-31 13:42 ` Charles Perry
2026-03-31 14:05 ` Russell King (Oracle)
2026-03-31 14:20 ` Andrew Lunn
2026-03-31 14:43 ` Charles Perry [this message]
2026-03-31 14:57 ` Russell King (Oracle)
2026-03-31 23:43 ` 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=acvdkBF4ZjZaCHwd@bby-cbu-swbuild03.eng.microchip.com \
--to=charles.perry@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=maxime.chevallier@bootlin.com \
--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