mirror of
https://github.com/openwrt/openwrt.git
synced 2024-12-22 23:12:32 +00:00
95ebd609ae
Changelog: https://cdn.kernel.org/pub/linux/kernel/v5.x/ChangeLog-5.15.139
Removed upstreamed:
x86/patches-5.15/120-hwrng-geode-fix-accessing-registers.patch[3]
All other patches automatically rebased.
3. https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=v5.15.139&id=a5c83c8043d70b9a28d1bd78a2dbbab340f43889
Build system: x86_64
Build-tested: ramips/tplink_archer-a6-v3
Run-tested: ramips/tplink_archer-a6-v3
Signed-off-by: John Audia <therealgraysky@proton.me>
[Refresh on top of OpenWrt 23.05]
Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
(cherry picked from commit df167450a5)
32 lines
1.2 KiB
Diff
32 lines
1.2 KiB
Diff
From 349cbe949b9622cc05b148ecfa6268cbbae35b45 Mon Sep 17 00:00:00 2001
|
|
From: =?UTF-8?q?Marek=20Beh=C3=BAn?= <kabel@kernel.org>
|
|
Date: Mon, 4 Jul 2022 12:59:55 +0200
|
|
Subject: [PATCH] leds: turris-omnia: change max brightness from 255 to 1
|
|
MIME-Version: 1.0
|
|
Content-Type: text/plain; charset=UTF-8
|
|
Content-Transfer-Encoding: 8bit
|
|
|
|
Using binary brightness makes more sense for this controller, because
|
|
internally in the MCU it works that way: the LED has a color, and a
|
|
state whether it is ON or OFF.
|
|
|
|
The resulting brightness computation with led_mc_calc_color_components()
|
|
will now always result in either (0, 0, 0) or the multi_intensity value.
|
|
|
|
Signed-off-by: Marek Behún <kabel@kernel.org>
|
|
---
|
|
drivers/leds/leds-turris-omnia.c | 2 +-
|
|
1 file changed, 1 insertion(+), 1 deletion(-)
|
|
|
|
--- a/drivers/leds/leds-turris-omnia.c
|
|
+++ b/drivers/leds/leds-turris-omnia.c
|
|
@@ -177,7 +177,7 @@ static int omnia_led_register(struct i2c
|
|
init_data.fwnode = &np->fwnode;
|
|
|
|
cdev = &led->mc_cdev.led_cdev;
|
|
- cdev->max_brightness = 255;
|
|
+ cdev->max_brightness = 1;
|
|
cdev->brightness_set_blocking = omnia_led_brightness_set_blocking;
|
|
cdev->trigger_type = &omnia_hw_trigger_type;
|
|
cdev->default_trigger = omnia_hw_trigger.name;
|