linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Abhijeet V <abhijeetviswa@gmail.com>
To: Corentin Chary <corentin.chary@gmail.com>,
	Hans de Goede <hdegoede@redhat.com>,
	Mark Gross <markgross@kernel.org>
Cc: acpi4asus-user@lists.sourceforge.net,
	platform-driver-x86@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: [PATCH 0/2] asus-wmi: Keyboard rgb led multicolor support
Date: Sat, 12 Feb 2022 01:31:20 +0530	[thread overview]
Message-ID: <20220211200122.9821-1-abhijeetviswa@gmail.com> (raw)

Hi

This patch series adds support for rgb keyboards on certain ASUS laptops
by utilizing the multicolor led device class. Much of the wmi
interacting code was obtained from the faustus kernel module:
https://github.com/hackbnw/faustus

The driver is hardcoded to use only the static mode provided by the
platform. There are other modes that are supported like strobe, and
rainbow and also variable speeds. However, I'm not sure how to integrate
that into the led classdev. Support for them could be added in a
separate patch later.

This is my first contribution (other than reporting a regression to
asus-wmi recently). I've tried my best to stick to the kernel's code
standards. I apologize if I've missed any obviously glaring issues.

Thanks
Abhijeet



             reply	other threads:[~2022-02-11 20:01 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-11 20:01 Abhijeet V [this message]
2022-02-11 20:01 ` [PATCH 1/2] asus-wmi: Use led multicolor class for keyboard backlight Abhijeet V
2022-02-12 19:08   ` kernel test robot
2022-02-13  6:20     ` Abhijeet Viswa
2022-02-16  9:58   ` Pavel Machek
2022-02-11 20:01 ` [PATCH 2/2] asus-wmi: Add support for keyboard rgb backlights Abhijeet V
2022-02-17 16:17   ` Hans de Goede

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=20220211200122.9821-1-abhijeetviswa@gmail.com \
    --to=abhijeetviswa@gmail.com \
    --cc=acpi4asus-user@lists.sourceforge.net \
    --cc=corentin.chary@gmail.com \
    --cc=hdegoede@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=markgross@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;
as well as URLs for NNTP newsgroup(s).