[PATCH 000/108] RFC: dm: Add programatic generation of ACPI tables
sjg at chromium.org
Sun Feb 23 23:34:07 CET 2020
On Wed, 29 Jan 2020 at 19:17, Simon Glass <sjg at chromium.org> wrote:
> On Sun, 26 Jan 2020 at 22:07, Simon Glass <sjg at chromium.org> wrote:
> > At present on x86 U-Boot supports creating ACPI (Advanced Configuration
> > and Power Interface) tables using the Intel ACPI Source Language (ASL)
> > compiler.
> > This is good enough for basic operation but some devices need to add
> > their information dynamically at runtime. An example is a device that
> > needs to report its enable GPIO. This is described in the device tree,
> > so we want to add code in the driver to convert that device-tree
> > description into an ACPI description for use on Linux.
> > This series adds support for generation of ACPI tables and fragments by
> > devices. The core support is built into driver model.
> > Several files are brought over from coreboot to do the actual generation.
> > As an example of using this new feature, chromebook_coral is updated to
> > write out a wide array of ACPI tables including DSDT and SSDT.
> > This initial version of the series lays out the general approach. More
> > work is needed to figure out the difference between CONFIG_ACPIGEN and
> > CONFIG_GENERATE_ACPI_TABLE with respect to what is built.
> > Simon Glass (108):
> > cpu: Support querying the address width
> This is available at u-boot-dm/coral-working
I have a few updates to this based on comments so far, but I don't
really want to send the whole series again until you've taken a look
at more of it. What do you think?
More information about the U-Boot