From: Lee Jones <lee@kernel.org>
To: linux-leds@vger.kernel.org, Liang Haowen <nbg2974@gmail.com>
Cc: lee@kernel.org, pavel@kernel.org, mkp@kernel.org,
linux-scsi@vger.kernel.org, platform-driver-x86@vger.kernel.org,
linux-kernel@vger.kernel.org, denis.benato@linux.dev,
W_Armin@gmx.de, hansg@kernel.org, ilpo.jarvinen@linux.intel.com,
scardracs@disroot.org
Subject: Re: (subset) [RFC v10 1/1] leds: asus-aura-scsi: Add ASUS Aura RGB LED driver for ROG NVMe enclosures
Date: Wed, 28 Oct 2026 12:34:12 +0000 [thread overview]
Message-ID: <179319085271.3664457.8130606663267466619.b4-ty@b4> (raw)
In-Reply-To: <20261015140051.1159817-2-nbg2974@gmail.com>
On Thu, 15 Oct 2026 22:00:51 +0800, Liang Haowen wrote:
> ASUS ROG external NVMe enclosures (ROG STRIX Arion, USB 0b05:1932) are
> plain USB mass-storage devices with no HID interface: the Aura LEDs
> hang off an ENE controller driven by vendor SCSI commands on the same
> LUN as the disk. The enclosure has 4 independently addressable LEDs,
> verified on hardware.
>
> Register a scsi_device_handler matched by INQUIRY (vendor "ROG",
> model "ESD-S1C"); it does not claim the sdev (sd keeps owning the
> disk) and exposes each LED as a multicolor LED class device,
> /sys/class/leds/asus-arion-0-0-0-0::led-0 through led-3. The
> H:C:T:L part of the sdev name keeps the names unique when more than
> one enclosure is connected, with its colons flattened to dashes. The
> color section stays empty, since multicolor LEDs enumerate their
> palette via multi_intensity, and the four identical zones use the
> function name with a "-N" ordinal, as the naming section in
> Documentation/leds/leds-class.rst asks for.
>
> [...]
Applied, thanks!
[1/1] leds: asus-aura-scsi: Add ASUS Aura RGB LED driver for ROG NVMe enclosures
commit: e3ea86f2c378b5ba6355712f09566eec44eb16bf
--
Lee Jones [李琼斯]
next prev parent reply other threads:[~2026-10-28 12:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20261015140051.1159817-1-nbg2974@gmail.com>
2026-10-15 14:00 ` Liang Haowen
2026-10-15 14:58 ` Liang Haowen
2026-10-28 12:34 ` Lee Jones [this message]
2026-10-28 12:52 ` (subset) " Liang Haowen
2026-10-30 10:26 ` Lee Jones
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=179319085271.3664457.8130606663267466619.b4-ty@b4 \
--to=lee@kernel.org \
--cc=W_Armin@gmx.de \
--cc=denis.benato@linux.dev \
--cc=hansg@kernel.org \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=mkp@kernel.org \
--cc=nbg2974@gmail.com \
--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®