On Wed, Aug 23, 2017 at 06:54:52PM -0400, Tom Rini wrote:
Ugh, typo on my part proving your point :) I meant _a_36afb... which is "ASoC: rt5677: Introduce proper table for ACPI enumeration". My gut
The code that's causing issues looks like it's generic ACPI code which is worrying me, it looks like it's dying setting up the PM. It could be that the trace is a bit misleading or that it's the result of earlier damage though.
feeling (and I'd be happy to be told how to poke ACPI to confirm this..) is that the ACPI table is in fact not including some information that the code expects and that's why the original patch added an I2C ID not an ACPI ID.
I'm pretty sure it's just that the people writing the code didn't really know how ACPI is supposed to work in Linux so used the fallback path which appears to have been copied from OF for some reason. It makes sense with OF because the IDs OF uses include the name of the part like the Linux internal IDs rather than just some random line noise like is apparently idiomatic for ACPI (this one is one of the better ones!) so there's a decent chance that a driver that gets found might do something sensible.