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]
Message-ID: <20211014102918.GA21116@duo.ucw.cz>
Date:   Thu, 14 Oct 2021 12:29:18 +0200
From:   Pavel Machek <pavel@....cz>
To:     Marek BehĂșn <kabel@...nel.org>
Cc:     devicetree@...r.kernel.org, linux-leds@...r.kernel.org,
        Andrew Lunn <andrew@...n.ch>, robh+dt@...nel.org,
        Jacek Anaszewski <jacek.anaszewski@...il.com>,
        netdev@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 2/3] dt-bindings: leds: Add `excludes` property

Hi!

> Some RJ-45 connectors have LEDs wired in the following way:
> 
>          LED1
>       +--|>|--+
>       |       |
>   A---+--|<|--+---B
>          LED2
> 
> With + on A and - on B, LED1 is ON and LED2 is OFF. Inverting the
> polarity turns LED1 OFF and LED2 ON.
> 
> So these LEDs exclude each other.
> 
> Add new `excludes` property to the LED binding. The property is a
> phandle-array to all the other LEDs that are excluded by this LED.

I don't think this belongs to the LED binding.

This is controller limitation, and the driver handling the controller
needs to know about it... so it does not need to learn that from the
LED binding.

Best regards,
								Pavel
-- 
http://www.livejournal.com/~pavelmachek

Download attachment "signature.asc" of type "application/pgp-signature" (196 bytes)

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ