public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
To: Denis Benato <denis.benato@linux.dev>
Cc: LKML <linux-kernel@vger.kernel.org>,
	platform-driver-x86@vger.kernel.org,
	 Hans de Goede <hansg@kernel.org>,
	"Luke D . Jones" <luke@ljones.dev>,
	 Mateusz Schyboll <dragonn@op.pl>,
	Denis Benato <benato.denis96@gmail.com>
Subject: Re: [PATCH v4 0/3] platform/x86: asus-wmi: move keyboard control firmware attributes
Date: Tue, 13 Jan 2026 16:02:30 +0200 (EET)	[thread overview]
Message-ID: <992b2843-4afa-ede1-d276-8ccaa61b1fee@linux.intel.com> (raw)
In-Reply-To: <88609e7c-3348-440e-adc0-eed9dc4d452c@linux.dev>

On Mon, 12 Jan 2026, Denis Benato wrote:
> On 1/3/26 00:43, Denis Benato wrote:
> >
> > I was recently reading through the asusctl issue tracker and I found
> > out that some users have been having troubles with the keyboard RGB control
> > that was working before since the creation of asus-armoury and subequent
> > deprecation of old sysfs attributes.
> >
> > This patch series aims to re-introduce those attributes in asus-armoury
> > so that userspace tools can still control keyboard RGB lighting
> > without having to rely on deprecated asus-wmi attributes.
> >
> > In addition to that, since disabling OOBE is essential for controlling
> > LEDs on some models and it was incorrectly tied to deprecated attributes,
> > this patch series also fixes sending OOBE at probe time.
> >
> > Link: https://gitlab.com/asus-linux/asusctl/-/issues/619
> >
> > Regards,
> > Denis
> Hi Ilpo,
> 
> I see no comments on this revision, did I sent it at wrong time?
> Should I resend some other time?
> 
> Sorry for the question but I don't know if something went wrong,
> and if so what exactly.

Hi,

Nothing is wrong, I've just had to spend time on finally processing 
some larger next series which were even older than yours. And we're only 1 
week past a holiday period which tend to add to delay.

Patchwork keeps track of pdx86 patches:

https://patchwork.kernel.org/project/platform-driver-x86/list/

If your patch is listed there, there's no need to ping as I'll get it it 
eventually (and it won't get forgotten).

There's no "wrong time" to send a patch to pdx86, only that when the 
merge window is open, I might do processing of any patches during that 
time. But unlike some other subsystems, we don't disallow sending patches 
during merge window or any other time.

-- 
 i.

> > Changelog:
> > - v1
> >   - Initial submission
> > - v2
> >   - asus-armoury: drivers should be silent on success
> >   - asus-armoury: make better use of __free annotation
> > - v3
> >   - asus-wmi: use GENMASK for flags
> >   - asus-armoury: fix error handling in keyboard attribute creation
> >   - asus-armoury: fix logic bug in error path
> >   - asus-armoury: use proper defines for keyboard state flags
> > - v4
> >   - asus-armoury: reorder variable declarations
> >   - asus-armoury: add bitfields.h include for BIT and FIELD_PREP
> >   - asus-armoury: reorganize armoury_kbd_state() for clarity
> >
> > Denis Benato (3):
> >   platform/x86: asus-wmi: explicitly mark more code with
> >     CONFIG_ASUS_WMI_DEPRECATED_ATTRS
> >   platform/x86: asus-wmi: fix sending OOBE at probe
> >   platform/x86: asus-armoury: add keyboard control firmware attributes
> >
> >  drivers/platform/x86/asus-armoury.c        | 253 +++++++++++++++++++++
> >  drivers/platform/x86/asus-wmi.c            |  13 +-
> >  include/linux/platform_data/x86/asus-wmi.h |  18 ++
> >  3 files changed, 283 insertions(+), 1 deletion(-)



  reply	other threads:[~2026-01-13 14:02 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-02 23:43 [PATCH v4 0/3] platform/x86: asus-wmi: move keyboard control firmware attributes Denis Benato
2026-01-02 23:43 ` [PATCH v4 1/3] platform/x86: asus-wmi: explicitly mark more code with CONFIG_ASUS_WMI_DEPRECATED_ATTRS Denis Benato
2026-01-02 23:43 ` [PATCH v4 2/3] platform/x86: asus-wmi: fix sending OOBE at probe Denis Benato
2026-01-02 23:43 ` [PATCH v4 3/3] platform/x86: asus-armoury: add keyboard control firmware attributes Denis Benato
2026-01-12 20:49 ` [PATCH v4 0/3] platform/x86: asus-wmi: move " Denis Benato
2026-01-13 14:02   ` Ilpo Järvinen [this message]
2026-01-13 21:53     ` Denis Benato
2026-01-14  9:04       ` Ilpo Järvinen
2026-01-16 18:10         ` Denis Benato
2026-01-26  1:36 ` Denis Benato
2026-01-26 12:56   ` Ilpo Järvinen

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=992b2843-4afa-ede1-d276-8ccaa61b1fee@linux.intel.com \
    --to=ilpo.jarvinen@linux.intel.com \
    --cc=benato.denis96@gmail.com \
    --cc=denis.benato@linux.dev \
    --cc=dragonn@op.pl \
    --cc=hansg@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luke@ljones.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