On 2020-10-05 12:11 p.m., Limonciello, Mario wrote:
Excuse my ignorance, but I don't really see why this interface would be tied
to
ACPI devices? Why is it not possible to write a driver that implements this
interface
and directly modifies device registers? Am I missing something obvious here?
When implemented for the two vendors mentioned here, it would be using a
proprietary "firmware API" implemented by those two vendors. For example write
arguments (0x1, 0x2) to ACPI-WMI method WMFT and it will cause firmware to coordinate
using undisclosed protocol to affect the platform changes desirable.
This is different in my mind from "kernel writes to a specific register" to set
power properties of a specific device.
Just curious on this point - isn't that (mostly) what all hardware does?
You write to it and the device does "stuff" to achieve the required
effect. Yes this is in proprietary firmware, but from my experience with
hardware devices that's not uncommon these days anyway.
Let me know if I'm misunderstanding something here. I couldn't see the
difference between a register written to via ACPI and one written to via
some other protocol (SMBUS? or whatever)
Mark
