netdev - Re: [PATCH RFC ???net???] net: phy: realtek: fix wake-on-lan support

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID:
 <DU2PR01MB8701360F4AAB1FB50A98368E9624A@DU2PR01MB8701.eurprd01.prod.exchangelabs.com>
Date: Wed, 30 Jul 2025 15:03:42 +0000
From: Daniel Braunwarth <Daniel.Braunwarth@...a.com>
To: Andrew Lunn <andrew@...n.ch>, Gatien CHEVALLIER
	<gatien.chevallier@...s.st.com>
CC: "Russell King (Oracle)" <rmk+kernel@...linux.org.uk>, Heiner Kallweit
	<hkallweit1@...il.com>, "David S. Miller" <davem@...emloft.net>, Eric Dumazet
	<edumazet@...gle.com>, Florian Fainelli <florian.fainelli@...adcom.com>,
	Jakub Kicinski <kuba@...nel.org>, Jon Hunter <jonathanh@...dia.com>,
	"netdev@...r.kernel.org" <netdev@...r.kernel.org>, Paolo Abeni
	<pabeni@...hat.com>, Thierry Reding <treding@...dia.com>
Subject: Re: [PATCH RFC ???net???] net: phy: realtek: fix wake-on-lan support

>> IMHO, I think 3) may optionally declare another interrupt as well
>> for WoL events.
>
> The 3) i've seen is a Marvell based NAS box. It is a long time
> ago. But as far as i remember, the SoC had no idea why it woke up, it
> could not ask the PMIC why the power was turned on. So there was no
> ability to invoke an interrupt handler.
>
> I've also seen X86/BIOS platforms which are similar. The BIOS swallows
> the interrupt, it never gets delivered to Linux once it is
> running. And the BIOS itself might poke PHY registers.

That's like our hardware looks like.

We have a TI J784S4 SoC which has an integrated 9 port switch. One internal, and 8 external ports.

It's similar to the device tree in arch/arm64/boot/dts/ti/k3-j784s4-evm-quad-port-eth-exp1.dtso.

The PHYs are directly connected to the PMIC of our board.
We don't have any clue **why** the PMIC wakes the board.
Could be a WoL event or somebody pressed the power button of our robot controller.


Regards
Daniel

Internal