Re: [PATCH 2/6] platform/x86/uniwill: Handle more WMI events required for TUXEDO devices

From: Werner Sembach
Date: Mon Nov 24 2025 - 13:41:00 EST


Hi

Am 20.11.25 um 01:53 schrieb Armin Wolf:
[snip]

Anyway, i attached the patch with the device descriptor infrastructure. The callback called during probe cannot modify
the feature bitmap anymore, but i suggest that you simply set the limit for cTGP to zero. The code responsible for
initializing cTGP support can then check if the cTGP limit is zero and return early.

Looked into it: whats the reason for the "__ro_after_init" in "static struct uniwill_device_descriptor device_descriptor __ro_after_init;"?

The thing Ilpo wrote sounded like just .driver_data itself should be read only, but as soon as it has an indirection, like here being copied over to a static variable, read/write is ok.

Also: Why not just copy the device_descriptor over to uniwill_data instead of a static variable?

And do I get that correctly: All you can do during the init callback is doing more sophisticated DMI matching?

Best regards,

Werner

[snip]