From: Kurt Borja <kuurtb@gmail.com>
To: "Hans de Goede" <hdegoede@redhat.com>,
"Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>,
"Armin Wolf" <W_Armin@gmx.de>
Cc: Gabriel Marcano <gabemarcano@yahoo.com>,
platform-driver-x86@vger.kernel.org,
Dell.Client.Kernel@dell.com, linux-kernel@vger.kernel.org,
Kurt Borja <kuurtb@gmail.com>
Subject: [PATCH 0/2] platform/x86: alienware-wmi-wmax: Add support for GPIO methods
Date: Wed, 23 Apr 2025 04:49:44 -0300 [thread overview]
Message-ID: <20250423-awcc-gpio-v1-0-160a11bc3f9a@gmail.com> (raw)
Hi all,
I found a great blog post [1], which described the reverse engineering
process of the GPIO control methods present on this device.
In summary, these methods expose some debugging capabilities of the RGB
lighting controller present on Dell gaming laptops. See [Patch 2] for
more info.
Exposing these methods to DebugFS is useful for developers exploring
this RGB controllers (myself included).
Thanks for your feedback!
[1] https://gabriel.marcanobrady.family/blog/2024/12/16/dell-g5-5505-se-acpi-or-figuring-out-how-to-reset-the-rgb-controller/
Signed-off-by: Kurt Borja <kuurtb@gmail.com>
---
Kurt Borja (2):
platform/x86: alienware-wmi-wmax: Expose GPIO debug methods
Documentation: wmi: alienware-wmi: Add GPIO control documentation
Documentation/wmi/devices/alienware-wmi.rst | 85 +++++++++++++++++-
drivers/platform/x86/dell/alienware-wmi-wmax.c | 116 ++++++++++++++++++++++++-
2 files changed, 196 insertions(+), 5 deletions(-)
---
base-commit: 981527828c301644bc4014faa9c523e8a5e32a32
change-id: 20250413-awcc-gpio-24b1f5c546d2
Best regards,
--
~ Kurt
next reply other threads:[~2025-04-23 7:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-23 7:49 Kurt Borja [this message]
2025-04-23 7:49 ` [PATCH 1/2] platform/x86: alienware-wmi-wmax: Expose GPIO debug methods Kurt Borja
2025-04-27 1:07 ` Armin Wolf
2025-04-27 6:21 ` Kurt Borja
2025-04-23 7:49 ` [PATCH 2/2] Documentation: wmi: alienware-wmi: Add GPIO control documentation Kurt Borja
2025-04-27 1:01 ` Armin Wolf
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20250423-awcc-gpio-v1-0-160a11bc3f9a@gmail.com \
--to=kuurtb@gmail.com \
--cc=Dell.Client.Kernel@dell.com \
--cc=W_Armin@gmx.de \
--cc=gabemarcano@yahoo.com \
--cc=hdegoede@redhat.com \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=platform-driver-x86@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®