linux-kernel - Re: [PATCH v2 4/4] ARM: dts: marvell: Indicate USB activity on x530

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]

Date: Wed, 28 Feb 2024 01:11:27 +0000
From: Chris Packham <Chris.Packham@...iedtelesis.co.nz>
To: Andy Shevchenko <andy.shevchenko@...il.com>
CC: "andy@...nel.org" <andy@...nel.org>, "geert@...ux-m68k.org"
	<geert@...ux-m68k.org>, "robh+dt@...nel.org" <robh+dt@...nel.org>,
	"krzysztof.kozlowski+dt@...aro.org" <krzysztof.kozlowski+dt@...aro.org>,
	"conor+dt@...nel.org" <conor+dt@...nel.org>, "andrew@...n.ch"
	<andrew@...n.ch>, "gregory.clement@...tlin.com"
	<gregory.clement@...tlin.com>, "sebastian.hesselbarth@...il.com"
	<sebastian.hesselbarth@...il.com>, "ojeda@...nel.org" <ojeda@...nel.org>,
	"tzimmermann@...e.de" <tzimmermann@...e.de>, "javierm@...hat.com"
	<javierm@...hat.com>, "robin@...tonic.nl" <robin@...tonic.nl>,
	"lee@...nel.org" <lee@...nel.org>, "pavel@....cz" <pavel@....cz>,
	"devicetree@...r.kernel.org" <devicetree@...r.kernel.org>,
	"linux-leds@...r.kernel.org" <linux-leds@...r.kernel.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"linux-arm-kernel@...ts.infradead.org" <linux-arm-kernel@...ts.infradead.org>
Subject: Re: [PATCH v2 4/4] ARM: dts: marvell: Indicate USB activity on x530


On 28/02/24 13:09, Andy Shevchenko wrote:
> On Tue, Feb 27, 2024 at 11:22 PM Chris Packham
> <chris.packham@...iedtelesis.co.nz> wrote:
>> Use the dot on the 7 segment LED block to indicate USB access on the
>> x530.
> Not sure if it's a good idea. I have some plans for the compressed
> format, i.e. use DP for dots (or compatible pieces) so we may print up
> to double characters with that (e.g., '6.4.5.3.' as a single string on
> a 4-digit display).
>
> That said, I would like to defer this for a while.
>
In our case this is how we've matched up other devices which have a 3 
LED tower for "power", "fault" and "usb" with devices which have a 
7-segment LED instead. I just wanted to reflect reality in the upstream dts.

It also answers the question "what about the DP LED"?