On Sat, Aug 16, 2014 at 09:06:05AM -0700, Darren Hart wrote: > On 8/15/14, 23:53, "Mika Westerberg" <mika.westerberg@xxxxxxxxxxxxxxx> > wrote: > > >The recent publication of the ACPI 5.1 specification [1] adds a reserved > >name > >for Device Specific Data (_DSD, Section 6.2.5). This mechanism allows for > >passing arbitrary hardware description data to the OS. The exact format > >of the > >_DSD data is specific to the UUID paired with it [2]. > > > >An ACPI Device Properties UUID has been defined [3] to provide a format > >compatible with existing device tree schemas. The purpose for this was to > >allow > >for the reuse of the existing schemas and encourage the development of > >firmware > >agnostic device drivers. > > > >This series accomplishes the following (as well as some other > >dependencies): > > > > * Add _DSD support to the ACPI core > > This simply reads the UUID and the accompanying Package > > > > * Add ACPI Device Properties _DSD format support > > This understands the hierarchical key:value pair structure > > defined by the Device Properties UUID > > > > * Add a unified device properties API with ACPI and OF backends > > This provides for the firmware agnostic device properties > > Interface to be used by drivers > > > > * Provides 2 example drivers that were previously Device Tree aware that > > can now be used with either Device Tree or ACPI Device Properties. The > > both drivers use an arbitrary _HID. > > > >This has been tested on Minnowboard with relevant parts of the modified > >DSDT at the end of this email. > > > This eliminates the need for the board files that were the subject of my > "How not to write x86 platform drivers" talk at ELC-E last year. With > These ACPI core changes and the small changes to the two example drivers, > the Minnowboard can now use the GPIO buttons and LEDs through these > drivers by adding the ASL fragment below to the DSDT. >From the drivers perspective I am less than impressed with the need to reshuffle all the drivers to support ACPI with the new API. I thought the plan was to try and keep OF API and try to translate as much as possible to it? The same goes for bringing arbitrary HIDs into the drivers. Can we have HID->OF naming hidden in ACPI (define a new property like "dt-name", "of_compat" or whatever) and have ACPI core map one to another. Thanks. -- Dmitry -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
