Hi Benjamin,
Am 25.03.24 um 16:56 schrieb Benjamin Tissoires:
On Mar 25 2024, Hans de Goede wrote:
+Cc: Bentiss, Jiri
Hi Werner,
On 3/20/24 12:16 PM, Werner Sembach wrote:
Hi Hans and the others,
Am 22.02.24 um 14:14 schrieb Werner Sembach:
Hi,
Thanks everyone for the exhaustive feedback. And at least this thread is a good comprehesive reference for the future ^^.
To recap the hopefully final UAPI for complex RGB lighting devices:
- By default there is a singular /sys/class/leds/* entry that treats the device as if it was a single zone RGB keyboard backlight with no special effects.
- There is an accompanying misc device with the sysfs attributes "name", "device_type", "firmware_version_string", "serial_number" for device identification and "use_leds_uapi" that defaults to 1.
- If set to 0 the /sys/class/leds/* entry disappears. The driver should keep the last state the backlight was in active if possible.
- If set 1 it appears again. The driver should bring it back to a static 1 zone setting while avoiding flicker if possible.
- If the device is not controllable by for example hidraw, the misc device might also implement additional ioctls or sysfs attributes to allow a more complex low level control for the keyboard backlight. This is will be a highly vendor specific UAPI.
So in the OpenRGB issue thread https://learn.microsoft.com/en-us/windows-hardware/design/component-guidelines/dynamic-lighting-devices aka HID LampArray was mentioned. I did dismiss it because I thought that is only relevant for firmware, but I now stumbled upon the Virtual HID Framework (VHF) https://learn.microsoft.com/en-us/windows-hardware/drivers/hid/virtual-hid-framework--vhf- and now I wonder if an equivalent exists for Linux? A quick search did not yield any results for me.
Oh, interesting. I did not know about the HID LampArray API.
About your question about virtual HID devices, there is uHID,
but as the name suggests this allows userspace to emulate a HID
device.
In your case you want to do the emulation in kernel so that you
can translate the proprietary WMI calls to something HID LampArray
compatible.
I guess you could do this by defining your own HID transport driver,
like how e.g. the i2c-hid code defines 1 i2c-hid parent + 1 HID
"client" for each device which talks HID over i2c in the machine.
Bentiss, Jiri, do you have any input on this. Would something like
that be acceptable to you (just based on the concept at least) ?
I just read the thread, and I think I now understand a little bit what
this request is :)
IMO working with the HID LampArray is the way forward. So I would
suggest to convert any non-HID RGB "LED display" that we are talking
about as a HID LampArray device through `hid_allocate_device()` in the
kernel. Basically what you are suggesting Hans. It's just that you don't
need a formal transport layer, just a child device that happens to be
HID.
The next question IMO is: do we want the kernel to handle such
machinery? Wouldn't it be simpler to just export the HID device and let
userspace talk to it through hidraw, like what OpenRGB does?
That's already part of my plan: The kernels main goal is to give devices a
LampArray interface that don't have one already (e.g. because they are no HID
devices to begin with).
The actual handling of LampArray will happen in userspace.
Exception is that maybe it could be useful to implement a small subset of
LampArray in a generic leds-subsystem driver for backwards compatibility to
userspace applications that only implement that (e.g. UPower). It would treat
the whole keyboard as a single led.
If the kernel already handles the custom protocol into generic HID, the
work for userspace is not too hard because they can deal with a known
protocol and can be cross-platform in their implementation.
I'm mentioning that cross-platform because SDL used to rely on the
input, LEDs, and other Linux peculiarities and eventually fell back on
using hidraw only because it's way more easier that way.
The other advantage of LampArray is that according to Microsoft's
document, new devices are going to support it out of the box, so they'll
be supported out of the box directly.
Most of the time my stance is "do not add new kernel API, you'll regret
it later". So in that case, given that we have a formally approved
standard, I would suggest to use it, and consider it your API.
The only new UAPI would be the use_leds_uapi switch to turn on/off the backwards
compatibility.
The control flow for the whole system would look something like this:
- System boots
- Kernel driver initializes keyboard (maybe stops rainbowpuke boot effects,
sets brightness to a default value, or initializes a solid color)
- systemd-backlight restores last keyboard backlight brightness
- UPower sees sysfs leds entry and exposes it to DBus for DEs to do
keyboard brightness handling
- If the user wants more control they (auto-)start OpenRGB
- OpenRGB disables sysfs leds entry via use_leds_uapi to prevent double
control of the same device by UPower
- OpenRGB directly interacts with hidraw device via LampArray API to give
fine granular control of the backlight
- When OpenRGB closes it should reenable the sysfs leds entry
- System shutdown
- Since OpenRGB reenables the sysfs leds entry, systemd-backlight can
correctly store a brightness value for next boot
Regards,
Werner
Side note to self: I really need to resurrect the hidraw revoke series
so we could export those hidraw node to userspace with uaccess through
logind...
Cheers,
Benjamin
