linux-kernel - Re: [PATCH] led/led-class: Handle LEDs with the same name

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: <CAPybu_1g5=pJwDTUWV_pP58fCuUm-vWU_O9h-Qah7G_wSPyjbA@mail.gmail.com>
Date:	Fri, 20 Feb 2015 00:22:46 +0100
From:	Ricardo Ribalda Delgado <ricardo.ribalda@...il.com>
To:	Josh Cartwright <joshc@...com>
Cc:	Bryan Wu <cooloney@...il.com>, Rob Herring <robh+dt@...nel.org>,
	Richard Purdie <rpurdie@...ys.net>,
	Linux LED Subsystem <linux-leds@...r.kernel.org>,
	lkml <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] led/led-class: Handle LEDs with the same name

Helo Josh

On Fri, Feb 20, 2015 at 12:15 AM, Josh Cartwright <joshc@...com> wrote:
>
> Is this solvable by adding support for led properties in an aliases { }
> node?  I suppose that would mean you'd need to also overlay a selection
> of which LED is "red", but I don't know if that is a problem.

I think there are two concens here. One is to provide an unique name
when a led is register and the other is to locate the led.

This patch is just mend for providing unique names, so the led
subsystem can play nicer with overlays.

The other might be solved with an sysfs symbolic link.... I need to
check it out, but it is a different issue.

>
>   Josh



-- 
Ricardo Ribalda
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/