From: Igor Velkov <iav@iav.lv>
To: Andrew Lunn <andrew@lunn.ch>
Cc: Maxime Chevallier <maxime.chevallier@bootlin.com>,
Andrew Lunn <andrew+netdev@lunn.ch>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Russell King <linux@armlinux.org.uk>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next] net: stmmac: mask the MAC interrupt while resume resets the MAC
Date: Sun, 04 Oct 2026 21:28:27 +0300 [thread overview]
Message-ID: <20261004212827.irq-shut-reply@iav.lv> (raw)
In-Reply-To: <17175b15-877c-4cbe-aca8-7c8d44eb667e@lunn.ch>
On Sun, Oct 04, 2026 at 04:42:23PM +0200, Andrew Lunn wrote:
> Is probe written this way? Does the needed code already exists, its
> just not used on resume when it should be?
Open is, by ordering: __stmmac_open() calls stmmac_hw_setup(), which
does the reset, and only then stmmac_request_irq(). stmmac_release()
frees the line again. MTU change, the ethtool ring and channel changes
and the reset subtask all go through release and open, so they get the
same ordering.
Resume is the only other caller of stmmac_hw_setup(), and the only one
that resets with the handler installed: nothing in suspend frees or
disables the line. The PM core disables it for the noirq phase only;
dpm_resume_noirq() enables it again before stmmac_resume() runs.
So there is no helper to reuse, only that ordering. The patch gives
resume the same with disable_irq()/enable_irq() instead of
free_irq()/request_irq().
--
Igor Velkov
next prev parent reply other threads:[~2026-10-04 18:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-30 19:28 Igor Velkov via B4 Relay
2026-10-01 12:40 ` Andrew Lunn
2026-10-02 4:36 ` Igor Velkov
2026-10-04 14:42 ` Andrew Lunn
2026-10-04 18:28 ` Igor Velkov [this message]
2026-10-04 20:13 ` netdev-bot+sashiko
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=20261004212827.irq-shut-reply@iav.lv \
--to=iav@iav.lv \
--cc=andrew+netdev@lunn.ch \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.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
all inboxes | Powered by JetHome®