From: Hans de Goede <hdegoede@redhat.com>
To: leo60228 <leo@60228.dev>,
platform-driver-x86@vger.kernel.org,
Jafar Akhondali <jafar.akhoondali@gmail.com>
Subject: Re: [PATCH] platform/x86: add support for Acer Predator LEDs
Date: Wed, 16 Jun 2021 18:00:26 +0200 [thread overview]
Message-ID: <2731fa44-7727-df4a-9214-91a5311ef3cc@redhat.com> (raw)
In-Reply-To: <20210615221931.18148-1-leo@60228.dev>
Hi,
On 6/16/21 12:19 AM, leo60228 wrote:
> The Acer Predator Helios 500's keyboard has four zones of RGB LEDs.
>
> This driver allows them to be controlled from Linux.
>
> Signed-off-by: leo60228 <leo@60228.dev>
We only accept contributions under real-names, so you need to
use your real first + lastname here.
Also the GUID you are using:
#define ACER_LED_METHOD_GUID "7A4DDFE7-5B5D-40B4-8595-4408E0CC7F56"
Is the same one as used by another recent patch for adding
keyboard LED zones support for Acer laptops:
https://lore.kernel.org/platform-driver-x86/CAMW3L+24ZGowtpURUbjoCoA+eZMF0wDae1izxS+HM2uz1L9Rig@mail.gmail.com/
I've added Jafar to the Cc here.
So it looks like we have 2 people working on the same driver,
please coordinate between the 2 of you to submit a single driver.
FWIW I do believe that this submission, which adds this as a new
driver for the new UUID, rather then adding extra code to acer-wmi.c
is the better approach. Jafar's version does have the benefit of
also adding support for some of the special effect modes, but
there is still a discussion ongoing on how the userspace API should
look for those, so starting with a clean driver like this, which does
not support the effects might be best for now.
<snip>
I've not done anything close to a full review, but one thing stood
out on a quick scan of the driver:
> +static int __init acer_led_init(void)
> +{
> + return wmi_driver_register(&acer_led_driver);
> +}
> +late_initcall(acer_led_init);
> +
> +static void __exit acer_led_exit(void)
> +{
> + wmi_driver_unregister(&acer_led_driver);
> +}
> +module_exit(acer_led_exit);
All these lines can be replaced by a single:
module_wmi_driver(acer_led_driver);
statement.
Regards,
Hans
next prev parent reply other threads:[~2021-06-16 16:01 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-15 22:19 [PATCH] platform/x86: add support for Acer Predator LEDs leo60228
2021-06-15 23:24 ` Barnabás Pőcze
[not found] ` <CAPRrO0xZunTfYYSOg-Gvk18FMHPufAURZ=fWjQN1bmP=RuuzGA@mail.gmail.com>
2021-06-16 0:21 ` Barnabás Pőcze
2021-06-16 0:24 ` leo60228
2021-06-16 0:51 ` [PATCH v2] " leo60228
2021-06-16 15:43 ` Enrico Weigelt, metux IT consult
2021-06-16 15:56 ` leo60228
2021-06-16 17:20 ` Enrico Weigelt, metux IT consult
2021-06-16 17:50 ` Hans de Goede
2021-06-21 19:23 ` Enrico Weigelt, metux IT consult
2021-06-21 19:43 ` Hans de Goede
2021-06-22 10:19 ` input devices vs. keyboard backlights [WAS: [PATCH v2] platform/x86: add support for Acer Predator LEDs] Enrico Weigelt, metux IT consult
2021-06-22 10:46 ` Hans de Goede
2021-06-16 15:41 ` [PATCH] platform/x86: add support for Acer Predator LEDs Enrico Weigelt, metux IT consult
2021-06-16 16:06 ` leo60228
2021-06-16 17:22 ` Enrico Weigelt, metux IT consult
2021-06-16 16:00 ` Hans de Goede [this message]
2021-06-16 16:16 ` leo60228
2021-06-16 16:39 ` Hans de Goede
2021-06-16 17:01 ` leo60228
2021-06-16 17:13 ` Jafar Akhondali
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=2731fa44-7727-df4a-9214-91a5311ef3cc@redhat.com \
--to=hdegoede@redhat.com \
--cc=jafar.akhoondali@gmail.com \
--cc=leo@60228.dev \
--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