[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <fe22ae64-2a09-45ce-8dbf-a4683745e21c@lunn.ch>
Date: Tue, 16 Dec 2025 08:09:29 +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 2/6] net: phy: add support to set default
rules
On Mon, Dec 15, 2025 at 08:57:01PM +0800, Jijie Shao wrote:
> The node of led need add new property: rules,
> and rules can be set as:
> BIT(TRIGGER_NETDEV_LINK) | BIT(TRIGGER_NETDEV_RX)
Please could you expand this description. It is not clear to my why it
is needed. OF systems have not needed it so far. What is special about
your hardware?
Also, it looks like you are expanding the DT binding, so you need to
update the binding .yaml file.
Andrew
Powered by blists - more mailing lists