From: Liang Haowen <nbg2974@gmail.com>
To: linux-leds@vger.kernel.org
Cc: Lee Jones <lee@kernel.org>, Pavel Machek <pavel@kernel.org>,
"Martin K . Petersen" <mkp@kernel.org>,
linux-scsi@vger.kernel.org, platform-driver-x86@vger.kernel.org,
linux-kernel@vger.kernel.org,
Denis Benato <denis.benato@linux.dev>,
Armin Wolf <W_Armin@gmx.de>, Hans de Goede <hansg@kernel.org>,
Ilpo Jarvinen <ilpo.jarvinen@linux.intel.com>,
Marco Scardovi <scardracs@disroot.org>
Subject: [RFC v9 0/1] leds: asus-aura-scsi: Add ASUS Aura RGB LED driver for ROG NVMe enclosures
Date: Fri, 25 Sep 2026 21:40:09 +0800 [thread overview]
Message-ID: <20260925134010.2815025-1-nbg2974@gmail.com> (raw)
Hello,
v9, as its own thread, addressing Ilpo's line review of v8 and the
one real sashiko item. This time the full pass over the code was
done.
Changes since v8:
- The DMA staging buffer is cacheline-aligned now, so an
invalidation on non-coherent architectures cannot clobber the
rest of struct asus_aura (the sashiko High).
- One pass over the code for includes, per Ilpo's comment: the
explicit set is array_size.h, blk-mq.h, blk_types.h, blkdev.h,
build_bug.h, byteorder/generic.h, cache.h, compiler.h,
compiler_attributes.h, container_of.h, dev_printk.h, err.h,
jiffies.h, the led headers, module.h, slab.h, sprintf.h,
spinlock.h, string.h, workqueue.h and the scsi ones; unused ones
(bits.h, kernel.h) dropped.
- ENE_OPCODE and ENE_TIMEOUT are defines again, the timeout value
stays 5 s (Ilpo).
- The container_of() declarations are single lines (Lee's v6
comment, Ilpo's reminder), and every loop over the LED array
uses ARRAY_SIZE() (Ilpo).
- The MODE/APPLY writes pass named locals with sizeof() instead of
compound literals (Ilpo).
- The driver now applies without saving. The controller flash only
changes on an explicit save command, which this driver never
sends: the LED class interface is runtime state and does not
promise persistence across power cycles, and a save on every
update would wear the flash. This drops the flash-wear caveat
from the previous versions.
Everything else is unchanged from v8: the multicolor LED
interface, the SCSI device handler attachment, the protocol
handling and the remaining caveats. On the interface direction:
the LED side will move onto Marco's Dynamic Lighting class
(OpenGamingCollective/linux-unstable#17) once that settles; he has
removed his draft SCSI driver from the series and says the SCSI
part will be added by its maintainer, so the two efforts are
aligned on the same split.
v9 was verified on hardware again, including a visual check of the
per-LED colours: the four LEDs, sequential updates, unplug under
load (zero splats, zero leaked nodes, clean rmmod).
Liang Haowen (1):
leds: asus-aura-scsi: Add ASUS Aura RGB LED driver for ROG NVMe
enclosures
--
2.55.0
Liang Haowen (1):
leds: asus-aura-scsi: Add ASUS Aura RGB LED driver for ROG NVMe
enclosures
--
2.55.0
next reply other threads:[~2026-09-25 13:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-25 13:40 Liang Haowen [this message]
2026-09-25 13:40 ` [RFC v9 1/1] " Liang Haowen
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=20260925134010.2815025-1-nbg2974@gmail.com \
--to=nbg2974@gmail.com \
--cc=W_Armin@gmx.de \
--cc=denis.benato@linux.dev \
--cc=hansg@kernel.org \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=lee@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=mkp@kernel.org \
--cc=pavel@kernel.org \
--cc=platform-driver-x86@vger.kernel.org \
--cc=scardracs@disroot.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®