On Tue, Nov 25, 2014 at 08:00:12AM -0800, Darren Hart wrote:
On 11/25/14 04:11, Grant Likely wrote:
Also, since this patch is targeted at v3.19 or later, the device-properties API should be used. Don't create something custom.
Right. The ACPI/UEFI forum is managing the creation of new DSD bindings and ensuring they are documented online. I believe this is the... 3rd so far? So we're still optimizing the process. But yes, please, send the schema itself for review and let's get this documented and migrated over to _DSD.
To be clear the main reason I'm querying this is that it doesn't appear to be a _DSD based binding at all (as far as I understand it, the API it's using is from before the dawn of time or at least the dawn of git).
Given the design of _DSD is to share with DT and we already have device tree bindings for the device we should be using, it's not clear to me if we want to grind them all through UEFI and I suspect they'd be unhappy if we tried but pretty much all audio CODECs are good candidates for use with ACPI given the new hardware designs Intel have so if we are doing it I ought to be bouncing everyone to UEFI forum.