[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20240324181201.87882-1-mustafa.eskieksi@gmail.com>
Date: Sun, 24 Mar 2024 21:12:00 +0300
From: mustafa <mustafa.eskieksi@...il.com>
To: hdegoede@...hat.com,
ilpo.jarvinen@...ux.intel.com,
jdelvare@...e.com,
linux@...ck-us.net,
pavel@....cz,
lee@...nel.org,
mustafa.eskieksi@...il.com,
linux-kernel@...r.kernel.org,
platform-driver-x86@...r.kernel.org,
linux-hwmon@...r.kernel.org,
linux-leds@...r.kernel.org
Subject: [PATCH v5 0/1] platform/x86: Add wmi driver for Casper Excalibur laptops
From: Mustafa Ekşi <mustafa.eskieksi@...il.com>
Hi,
I want to note that moving mutex_init to the bottom of the function
crashes the driver when mutex_lock is called. I didn't investigate it
further but I wanted to say that since Ai Chao also did it like that.
Driver sets all leds to white on start. Before that, when a led's
brightness is changed, that led's color gets set to white but others
keep their old colors which creates a bad user experience (at least for
me). Please inform me if this is a bad approach.
Also, this driver still lacks support for changing modes and I seek
advise for that.
Mustafa Ekşi (1):
platform/x86: Add wmi driver for Casper Excalibur laptops
MAINTAINERS | 6 +
drivers/platform/x86/Kconfig | 14 +
drivers/platform/x86/Makefile | 1 +
drivers/platform/x86/casper-wmi.c | 641 ++++++++++++++++++++++++++++++
4 files changed, 662 insertions(+)
create mode 100644 drivers/platform/x86/casper-wmi.c
--
2.44.0
Powered by blists - more mailing lists