[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ed20f083-90e1-406c-bcda-f9fc92807278@lunn.ch>
Date: Tue, 6 Aug 2024 00:56:18 +0200
From: Andrew Lunn <andrew@...n.ch>
To: Lee Jones <lee@...nel.org>
Cc: Marek Vasut <marex@...x.de>, devicetree@...r.kernel.org,
Conor Dooley <conor+dt@...nel.org>,
Jacek Anaszewski <jacek.anaszewski@...il.com>,
Krzysztof Kozlowski <krzk+dt@...nel.org>,
Pavel Machek <pavel@....cz>, Rob Herring <robh@...nel.org>,
linux-leds@...r.kernel.org, netdev@...r.kernel.org
Subject: Re: [PATCH v2] dt-bindings: leds: Document "netdev" trigger
> > We could do, but we have to keep netdev around for backwards
> > compatibility. There are DT blobs using it which we cannot break.
>
> Oh, this 'just' a documentation patch? 'netdev' is already in use?
>
A few examples:
intel/ixp/intel-ixp42x-iomega-nas100d.dts: linux,default-trigger = "netdev";
intel/ixp/intel-ixp42x-dlink-dsm-g600.dts: linux,default-trigger = "netdev";
nxp/imx/imx53-m53menlo.dts: linux,default-trigger = "netdev";
rockchip/rk3128-xpi-3128.dts: * linux,default-trigger = "netdev";
ti/omap/am5729-beagleboneai.dts: linux,default-trigger = "netdev";
ti/omap/am335x-netcan-plus-1xx.dts: linux,default-trigger = "netdev";
Andrew
Powered by blists - more mailing lists