netdev - Re: [PATCH RFC net-next 3/6] net: hibmcge: create a software node for phy

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: <b23a63c0-110c-49ab-8189-670717f243a3@lunn.ch>
Date: Thu, 8 Jan 2026 14:59:37 +0100
From: Andrew Lunn <andrew@...n.ch>
To: Jijie Shao <shaojijie@...wei.com>
Cc: davem@...emloft.net, edumazet@...gle.com, kuba@...nel.org,
	pabeni@...hat.com, andrew+netdev@...n.ch, horms@...nel.org,
	Frank.Sae@...or-comm.com, hkallweit1@...il.com,
	linux@...linux.org.uk, shenjian15@...wei.com,
	liuyonglong@...wei.com, chenhao418@...wei.com,
	jonathan.cameron@...wei.com, salil.mehta@...wei.com,
	shiyongbang@...wei.com, netdev@...r.kernel.org,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH RFC net-next 3/6] net: hibmcge: create a software node
 for phy_led

> I did some research, and it seems that our board uses ACPI,
> so it might not be possible to use this method.
> 
> If we rely on ACPI, we would need to ask the BIOS team to add ACPI entries.
> I need to communicate with the customer's BIOS team, which may not be easy.

If you are going the ACPI route, please take a look at:

Documentation/firmware-guide/acpi/dsd/phy.rst

The basic structure of how to list PHYs is defined here.

And you also want to look at:

Documentation/firmware-guide/acpi/dsd/leds.rst

Since you are describing LEDs on a PHY. You will probably need to
extend phy.rst to reference leds.rst.

      Andrew