On Mon, Jul 09, 2012 at 01:32:56PM +0100, Mark Brown wrote: > If you end up having to write two whole drivers that sounds enormously > depressing especially for those of us working on devices that aren't > architecture specific. We've managed to avoid that thus far with device > tree and platform data, would it not be possible to mandate that people > use ACPI in a vaugley sane way which can support this too?
There's ongoing discussion about unifying ACPI and ftd representation, and once that's done this isn't a problem, but right now there's no terribly straightforward way to do this without a lot of basically boilerplate code. The biggest issue is that ACPI has a very different idea about event delivery and we'd need some way to abstract that. -- Matthew Garrett | mj...@srcf.ucam.org -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
