From: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
To: Hans de Goede <hdegoede@redhat.com>, Armin Wolf <W_Armin@gmx.de>,
Kurt Borja <kuurtb@gmail.com>
Cc: Gabriel Marcano <gabemarcano@yahoo.com>,
platform-driver-x86@vger.kernel.org,
Dell.Client.Kernel@dell.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 0/2] platform/x86: alienware-wmi-wmax: Add support for GPIO methods
Date: Wed, 07 May 2025 13:36:56 +0300 [thread overview]
Message-ID: <174661421671.2744.17735064647207719106.b4-ty@linux.intel.com> (raw)
In-Reply-To: <20250505-awcc-gpio-v4-0-edda44c3a0dc@gmail.com>
On Mon, 05 May 2025 15:43:30 -0300, Kurt Borja wrote:
> 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.
>
> [...]
Thank you for your contribution, it has been applied to my local
review-ilpo-next branch. Note it will show up in the public
platform-drivers-x86/review-ilpo-next branch only once I've pushed my
local branch there, which might take a while.
The list of commits applied:
[1/2] platform/x86: alienware-wmi-wmax: Expose GPIO debug methods
commit: 8e27c47983c516a4d9e85199c0904e2da4c447df
[2/2] Documentation: wmi: alienware-wmi: Add GPIO control documentation
commit: c959bee66489a41555bd2be43a93da8be16b4acd
--
i.
prev parent reply other threads:[~2025-05-07 10:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-05 18:43 Kurt Borja via B4 Relay
2025-05-05 18:43 ` [PATCH v4 1/2] platform/x86: alienware-wmi-wmax: Expose GPIO debug methods Kurt Borja via B4 Relay
2025-05-05 18:43 ` [PATCH v4 2/2] Documentation: wmi: alienware-wmi: Add GPIO control documentation Kurt Borja via B4 Relay
2025-05-07 10:36 ` Ilpo Järvinen [this message]
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=174661421671.2744.17735064647207719106.b4-ty@linux.intel.com \
--to=ilpo.jarvinen@linux.intel.com \
--cc=Dell.Client.Kernel@dell.com \
--cc=W_Armin@gmx.de \
--cc=gabemarcano@yahoo.com \
--cc=hdegoede@redhat.com \
--cc=kuurtb@gmail.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®