linux-kernel - Re: [PATCH 2/2] ARM: dts: NSP: MX6X: correct LED function types

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: <20220225004726.1106616-1-f.fainelli@gmail.com>
Date:   Thu, 24 Feb 2022 16:47:26 -0800
From:   Florian Fainelli <f.fainelli@...il.com>
To:     bcm-kernel-feedback-list@...adcom.com,
        Matthew Hagan <mnhagan88@...il.com>
Cc:     Rob Herring <robh+dt@...nel.org>, Ray Jui <rjui@...adcom.com>,
        Scott Branden <sbranden@...adcom.com>,
        devicetree@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
        linux-kernel@...r.kernel.org
Subject: Re: [PATCH 2/2] ARM: dts: NSP: MX6X: correct LED function types

On Wed, 23 Feb 2022 23:50:40 +0000, Matthew Hagan <mnhagan88@...il.com> wrote:
> Currently, the amber LED will remain always on. This is due to a
> misinterpretation of the LED sub-node properties, where-by "default-state"
> was used to indicate the initial state when powering on the device. When in
> use, however, this resulted in the amber LED always being on. Instead change
> this to only indicate a fault state.
> 
> Assign LED_FUNCTION_POWER to the green PWM LED.
> 
> These changes bring the MX64/65 in line with the MR32's devicetree.
> 
> Signed-off-by: Matthew Hagan <mnhagan88@...il.com>
> ---

Applied to https://github.com/Broadcom/stblinux/commits/devicetree/next, thanks!
--
Florian