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: <176795584369.1637221.16089079913533797869.b4-ty@kernel.org>
Date: Fri, 09 Jan 2026 10:50:43 +0000
From: Lee Jones <lee@...nel.org>
To: Lee Jones <lee@...nel.org>, Pavel Machek <pavel@...nel.org>, 
 Linus Walleij <linus.walleij@...aro.org>, 
 Daniel Thompson <daniel.thompson@...aro.org>, 
 Duje Mihanović <dujemihanovic32@...il.com>
Cc: Karel Balej <balejk@...fyz.cz>, David Wronek <david@...nlining.org>, 
 phone-devel@...r.kernel.org, ~postmarketos/upstreaming@...ts.sr.ht, 
 linux-leds@...r.kernel.org, linux-kernel@...r.kernel.org, 
 Duje Mihanović <duje@...emihanovic.xyz>
Subject: Re: (subset) [PATCH v2] leds: expresswire: Fix chip state breakage

On Wed, 17 Dec 2025 19:14:23 +0100, Duje Mihanović wrote:
> It is possible to put the KTD2801 chip in an unknown/undefined state by
> changing the brightness very rapidly (for example, with a brightness
> slider). When this happens, the brightness is stuck on max and cannot be
> changed until the chip is power cycled.
> 
> Fix this by disabling interrupts while talking to the chip. While at it,
> make expresswire_power_off() use fsleep() and also unexport some
> functions meant to be internal.
> 
> [...]

Applied, thanks!

[1/1] leds: expresswire: Fix chip state breakage
      commit: 25da3f049fb36f6e88e4c4334040b5b0bf9355b7

--
Lee Jones [李琼斯]


Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ