Re: [PATCH RFC 0/2] Keyboard lighting for the Lenovo Legion Pro 7 Gen 10
From: Rong Zhang
Date: Wed Nov 11 2026 - 12:53:34 EST
Hi Ciro,
On Wed, 2026-11-11 at 14:27 -0300, Ciro Pedrini wrote:
> Hey Rong,
>
> On Wed, 2026-11-11 at 20:10 +0800, Rong Zhang wrote:
> > What if (four permutations):
> >
> > - c197 sends 07 AA 02 00 00/01 00
> > - c193 sends autonomous_mode=on/off
> >
> > And what if the sequence is reversed (another four permutations)?
>
> I tried all eight. Before each one the LEDs were back to the
> controller's effect (AA 01, autonomous on). "host" below means
> autonomous off plus all lamps set to green.
>
> c197 first: AA 00, host -> green
> AA 00, auto -> controller's effect
> AA 01, host -> controller's effect
> AA 01, auto -> controller's effect
>
> c193 first: host, AA 00 -> green
> auto, AA 00 -> controller's effect
> host, AA 01 -> controller's effect
> auto, AA 01 -> controller's effect
>
> So the order doesn't matter. The LampArray only shows with AA 00 and
> autonomous off. c193 keeps the colours it gets while AA is 01, and they
> show up as soon as AA 00 is sent, without sending them again. AA 01
> takes the LEDs back even when c193 is not in autonomous mode.
Thanks for the experiments.
AFAICS, we should be able to integrate both as a unified autonomous mode
trigger. Yay!
Thanks,
Rong
>
> > My implementation connects the LampArray application to hid-input, so any
> > HID driver with hid_hw_start(HID_CONNECT_DEFAULT) or
> > hid_hw_start(HID_CONNECT_HIDINPUT | ...) will initialize the LampArray
> > application. Therefore, I suppose the only thing we need is a simple glue
> > driver[1] for c193.
>
> [...]
>
> > Does that make sense to you?
>
> Yes, it makes sense to me.
>
> > I will CC you when I submit it. For now let's focus on the driver for
> > c197 first.
>
> Thanks, I'll test it here when it's out.
>
> Ciro