On Wed, 2013-06-26 at 05:36 +0000, Matthew Garrett wrote: > On Tue, 2013-06-25 at 22:32 -0700, Darren Hart wrote: > > > are all board-specific. They map GPIO to their fixed functions and > > provide an API for board-specific queries (minnowboard.c), they provide > > example uses (minnowboard-gpio and minnowboard-keys) which aid in > > experimentation and the development of new drivers. > > > > Which of these make sense as ACPI devices in your opinion? > > Does the firmware contain a corresponding ACPI device with a specific > _HID that defines the programming model? If so, it should have an ACPI > driver. If not, it shouldn't. It does not currently. However, the firmware is being developed along with the hardware and the OS. We have the opportunity to do whatever makes the most sense. My next-steps here were to get a basic ACPI ID setup for each of the three drivers just so they could be enumerated over ACPI rather than just loaded manually. Beyond that I'll be looking to Len and Rafael for guidance. -- Darren Hart Intel Open Source Technology Center Yocto Project - Technical Lead - Linux Kernel -- To unsubscribe from this list: send the line "unsubscribe platform-driver-x86" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
