linux-kernel - Re: (subset) [PATCH] leds: leds-lp55xx: use correct address for memory programming

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: <175681646443.2328142.16671286354720773270.b4-ty@kernel.org>
Date: Tue, 02 Sep 2025 13:34:24 +0100
From: Lee Jones <lee@...nel.org>
To: Lee Jones <lee@...nel.org>, Pavel Machek <pavel@...nel.org>, 
 Christian Marangi <ansuelsmth@...il.com>, 
 Andrei Lalaev <andrei.lalaev@...on-paar.com>
Cc: linux-leds@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: (subset) [PATCH] leds: leds-lp55xx: use correct address for
 memory programming

On Wed, 20 Aug 2025 10:47:12 +0200, Andrei Lalaev wrote:
> Memory programming doesn't work for devices without page support.
> For example, LP5562 has 3 engines but doesn't support pages,
> the start address is changed depending on engine number.
> According to datasheet [1], the PROG MEM register addresses for each
> engine are as follows:
> 
>   Engine 1: 0x10
>   Engine 2: 0x30
>   Engine 3: 0x50
> 
> [...]

Applied, thanks!

[1/1] leds: leds-lp55xx: use correct address for memory programming
      commit: d6058316d16ee0d1861c0550051b2492efb54b79

--
Lee Jones [李琼斯]