linux-kernel - Re: [PATCH v13 RESEND 3/4] docs: ABI: Document LP5812 LED sysfs interfaces

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] [day] [month] [year] [list]

Message-Id: <20250819162945.231085-1-trannamatk@gmail.com>
Date: Tue, 19 Aug 2025 23:29:45 +0700
From: Nam Tran <trannamatk@...il.com>
To: rdunlap@...radead.org
Cc: lee@...nel.org,
	pavel@...nel.org,
	gregkh@...uxfoundation.org,
	christophe.jaillet@...adoo.fr,
	krzk+dt@...nel.org,
	robh@...nel.org,
	conor+dt@...nel.org,
	corbet@....net,
	linux-leds@...r.kernel.org,
	linux-kernel@...r.kernel.org,
	devicetree@...r.kernel.org,
	linux-doc@...r.kernel.org
Subject: Re: [PATCH v13 RESEND 3/4] docs: ABI: Document LP5812 LED sysfs interfaces

On Sun, 17 Aug 2025, Randy Dunlap wrote:

> > +What:		/sys/class/leds/led_<id>/lod_lsd
> > +Date:		July 2025
> > +KernelVersion:	6.17
> > +Contact:	Nam Tran <trannamatk@...il.com>
> > +Description:
> > +		0 0 mean no lod and lsd fault detected, 1 1 mean lod and lsd fault detected (RO)
> 
> At first the "0 0" and "1 1" confused me (thought it was a typo),
> but I think what you are showing here is a sysfs file with 2 values, right?
> That used to be discouraged (or even nacked), although I don't know the
> current policy on that.

The lod_lsd sysfs file currently reports two values: the first value is the LOD
(LED open detection) fault status, the first value is the LOD (LED open detection)
fault status.

I followed this approach to keep the two related fault bits in a single file, but
I'm open to splitting them into separate sysfs entries if that is preferred.

Best regards,
Nam Tran