- Add a new SMBIOS parser and enable it when booting from coreboot
- Fix up various driver names to avoid dtoc warnings
- Fully enable ACPI support on Google Chromebook Coral
- Add a way to set SMBIOS properties using the devicetree
- Update existing boards to use devicetree for SMBIOS using a new
  default sysinfo driver
This commit is contained in:
Tom Rini
2020-11-06 08:41:49 -05:00
144 changed files with 1645 additions and 590 deletions

View File

@@ -740,6 +740,14 @@ Note that this is a development feature only. It is not intended for use in
production environments. Also it is not currently part of the automated tests
so may break in the future.
SMBIOS tables
-------------
To generate SMBIOS tables in U-Boot, for use by the OS, enable the
CONFIG_GENERATE_SMBIOS_TABLE option. The easiest way to provide the values to
use is via the device tree. For details see
device-tree-bindings/sysinfo/smbios.txt
TODO List
---------
- Audio

View File

@@ -1,11 +1,11 @@
gdsys Gazerbeam board driver
gdsys Gazerbeam sysinfo driver
This driver provides capabilities to access the gdsys Gazerbeam board's device
information. Furthermore, phandles to some internal devices are provided for
the board files.
Required properties:
- compatible: should be "gdsys,board_gazerbeam"
- compatible: should be "gdsys,sysinfo-gazerbeam"
- csb: phandle to the board's coherent system bus (CSB) device node
- rxaui[0-3]: phandles to the rxaui control device nodes
- fpga[0-1]: phandles to the board's gdsys FPGA device nodes
@@ -17,8 +17,8 @@ Required properties:
Example:
board {
compatible = "gdsys,board_gazerbeam";
sysinfo {
compatible = "gdsys,sysinfo-gazerbeam";
csb = <&board_soc>;
serdes = <&SERDES>;
rxaui0 = <&RXAUI0>;

View File

@@ -0,0 +1,77 @@
SMBIOS sysinfo information
==========================
This binding allows the values for the SMBIOS tables to be specified in the
devicetree, as below.
Required properties:
- compatible: "u-boot,smbios" or any other string depending on your board
This driver allows providing board-specific features such as power control
GPIOs. In addition, the SMBIOS values can be specified in the device tree,
as below:
An optional 'smbios' subnode can be used to provide these properties. Within
that, the properties are broken down by table type, as in the System Management
BIOS (Basic Input/Output System) Specification.
Available subnodes for each table type are:
- 1 : system
- 2 : baseboard
- 3 : chassis
Within each subnode the following tables are recognised:
"system" subnode optional properties:
- manufacturer: Product manufacturer for system
- product: Product name
- version: Product version string
- serial: Serial number for system (note that this can be overridden by
the serial# environment variable)
- sku: Product SKU (Stock-Keeping Unit)
- family: Product family
"baseboard" subnode optional properties:
- manufacturer: Product manufacturer for baseboard
- product: Product name
- asset-tag: Asset tag for the motherboard, sometimes used in organisations
to track devices
"chassis" subnode optional properties:
- manufacturer: Product manufacturer for chassis
Example:
sysinfo {
compatible = "sandbox,sysinfo-sandbox";
smbios {
/* Type 1 table */
system {
manufacturer = "Google";
product = "Coral";
version = "rev2";
serial = "123456789";
sku = "sku3";
family = "Google_Coral";
};
/* Type 2 table */
baseboard {
manufacturer = "Google";
product = "Coral";
asset-tag = "ABC123";
};
/* Type 3 table */
chassis {
manufacturer = "Google";
};
};
};

View File

@@ -0,0 +1,19 @@
Sysinfo
=======
This provides capabilities to access information about a board/system, for
use by drivers.
Required properties:
- compatible: any suitable string where the driver is in the UCLASS_SYSINFO
class
See also smbios.txt
Example
sysinfo {
compatible = "sandbox,sysinfo-sandbox";
};