From: Cristian Mazzotta <cmmazzo@icloud.com>
To: wse@tuxedocomputers.com
Cc: tgu@tuxedocomputers.com, jikos@kernel.org, bentiss@kernel.org,
hansg@kernel.org, linux-input@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-leds@vger.kernel.org,
Cristian Mazzotta <cmmazzo@icloud.com>
Subject: Re: [PATCH v4] HID: generic: add LampArray support via hid-lamparray helper
Date: Thu, 27 Aug 2026 13:47:15 -0500 [thread overview]
Message-ID: <20260827184715.136843-1-cmmazzo@icloud.com> (raw)
In-Reply-To: <8c05e11f-6e63-420a-996b-5d1986743ce7@tuxedocomputers.com>
Am 25.03.26 um 11:35 schrieb Werner Sembach:
> as Tim went on to other endeavors, I'm taking over this patch. I have
> yet to test it myself, but i was already in the feedback loop while he
> was writing it, so I'm not unfamiliar with the code.
Hi Werner,
I recently got a new laptop (Acer Predator PT14-52T) with absolutely zero
support for any RGB outside of Windows 11; while studying the behavior of
the Windows driver, I found out about LampArray devices and so I ended up
landing here.
This laptop has 2 LampArray devices: a USB attached keyboard (05AF:767A)
and an I2C ENE controller (0CF2:5130) for 3 zones in total. The original
motivation was power draw during s2idle; the lights would stay on and
constantly draw power. I measured 12.35W drop to 2.84W when I
blanked the lights and measured with a simple usb power meter, so I've
been working off of Tim's code for the past little bit.
Getting full support required touching most of the driver:
- Multi-zone support with individual zone states instead of a single
monolithic zone taking every device.
- lamparray_read_lamp_count() used hid_hw_request(), which is
asynchronous, so the value was read before the transfer completed.
Switched to hid_hw_raw_request()
- lamparray_parse_update_report() would bind to the last HID_LAIP_LAMP_COUNT
(usage 0x0003) parsed rather than the first, so LampCount ended up
being on the wrong field. This has been fixed by binding the first match.
- Added suspend and resume hooks, including an autonomous mode refresh
on S4 that my laptop needed
- use_leds_uapi=0 now leaves the LED class devs registered, but ignores
all writes rather than unregistering them.
- Also added ABI documentation since it was missing previously
About half of the driver changed, so I don't think it would be easily
reviewable as a delta from v4.
Would you prefer that I post it as a v5 with Tim's patch as a base, or
should I just send you the changes that you can add to your own version?
I don't want to duplicate work if you already have a v5 in progress.
I have hardware in front of me so I can test whatever is useful.
Thank you,
Cristian Mazzotta
next prev parent reply other threads:[~2026-08-27 18:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-23 8:39 Tim Guttzeit
2026-03-25 10:21 ` Werner Sembach
2026-03-25 10:35 ` Werner Sembach
2026-08-27 18:47 ` Cristian Mazzotta [this message]
2026-08-27 22:13 ` Werner Sembach
2026-08-28 14:45 ` Cristian Mazzotta
2026-09-03 9:31 ` Aaron Erhardt
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=20260827184715.136843-1-cmmazzo@icloud.com \
--to=cmmazzo@icloud.com \
--cc=bentiss@kernel.org \
--cc=hansg@kernel.org \
--cc=jikos@kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=tgu@tuxedocomputers.com \
--cc=wse@tuxedocomputers.com \
/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®