For any "new" attributes it's better to put them in that API than code
duplication of the BIOS attributes API as well as a random sysfs file
API that you can never discard.
Do you mean the firmware_attributes API? If so, I'm not opposed to adding all the existing ROG attributes to it also.
If I'm understanding the docs correctly, for example this apu_mem attr would then become:
- /sys/class/firmware-attributes/asus-bios/attributes/apu_mem/type
- /sys/class/firmware-attributes/*/attributes/apu_mem/current_value
- /sys/class/firmware-attributes/*/attributes/apu_mem/default_value
- /sys/class/firmware-attributes/*/attributes/apu_mem/display_name
- /sys/class/firmware-attributes/*/attributes/apu_mem/possible_values
- ..etc
That's absolutely much better than what I've been doing and I wish I'd known about it sooner.
So if I go ahead and convert all the new attr to this are there any issues with also converting much of the previous attr? And I'm aware of "don't break userspace" so really I'm a bit unsure how best to manage that (would a new module be better here also? "asus-bios.c" perhaps).
What I don't want is a split between platform and firmware_attributes.