mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jakub Kicinski <kuba@kernel.org>
To: Rosen Penev <rosenp@gmail.com>
Cc: netdev@vger.kernel.org, Andrew Lunn <andrew@lunn.ch>,
	Heiner Kallweit <hkallweit1@gmail.com>,
	Russell King <linux@armlinux.org.uk>,
	"David S. Miller" <davem@davemloft.net>,
	Eric Dumazet <edumazet@google.com>,
	Paolo Abeni <pabeni@redhat.com>,
	Michael Stapelberg <michael@stapelberg.de>,
	linux-kernel@vger.kernel.org (open list)
Subject: Re: [PATCHv2 net] net: phy: marvell: undo WoL setup when Wake-on-LAN is disabled
Date: Sat, 19 Sep 2026 15:41:33 -0700	[thread overview]
Message-ID: <20260919154133.3fd41455@kernel.org> (raw)
In-Reply-To: <20260914212409.74539-1-rosenp@gmail.com>

On Mon, 14 Sep 2026 14:24:09 -0700 Rosen Penev wrote:
> Fully disabling Wake-on-LAN on the 88E1318S/88E1510 used to leave
> the WoL interrupt enable bit (CSIER.WOL_EIE) set and LED[2]
> configured as the INTn pin. A magic packet arriving after "wol d"
> would still assert INTn, and a later "wol g" re-enabled WoL from a
> dirty register state.
> 
> Fully disabling WoL clears CSIER.WOL_EIE on the copper page. The
> LED[2]/INTn pin mux is disposed of only when this driver forced it to
> the INTn function: the INTn enable and polarity bits read at arming
> time are saved, and restored once all WoL options are cleared, so PHYs
> serving the MAC interrupt, strap configs, or marvell,reg-init values
> are never touched. The FORCE_INT bit is not set while disposing of the
> pin: it holds the interrupt line asserted and turns the shared PHY
> interrupt into a "nobody cared" IRQ storm when the PHY interrupt is in
> use.

Oof, this is pretty hard to read. The paragraph is pretty much 2
run-on sentences.

Please add info about how the issue was discovered and how it was
tested. If you don't have HW back to net-next without Fixes it goes.
The AI is pretty bad at judging severity, I need to find time to tune
the Fixes suggestions further :/
-- 
pw-bot: cr

  parent reply	other threads:[~2026-09-19 22:41 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-14 21:24 Rosen Penev
2026-09-17 21:24 ` netdev-bot+sashiko
2026-09-19 22:41 ` Jakub Kicinski [this message]
2026-09-20  1:05   ` Rosen Penev

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=20260919154133.3fd41455@kernel.org \
    --to=kuba@kernel.org \
    --cc=andrew@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=hkallweit1@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@armlinux.org.uk \
    --cc=michael@stapelberg.de \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=rosenp@gmail.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®