intel/fsp_baytrail: Clear the GNVS area prior to filling

Zero out the GNVS area so that uninitialized portions are defined.

Tests using Microsoft Windows (XP/7/8) gave a bluescreen bugcheck: A5
(ACPI_BIOS_ERROR) with the first parameter (0x00001000)
(ACPI_BIOS_USING_OS_MEMORY). Some ACPI enumerated devices use the
GNVS area to define whether they're enabled and their MMIO regions.
On my custom baytrail-based board and build, these devices were
disabled but GNVS had uninitialized data indicating the devices
were enabled with improper MMIO regions.

Should investigate further to see where the GNVS device values are
set if enabled and make sure they're set to valid values even when
the devices are disabled via the mainboard/devicetree.cb.

Change-Id: I2b575c65bfaab58ae6206ac6f457c259c27a7d97
Signed-off-by: Scott Radcliffe <sradcliffe@microind.com>
Reviewed-on: http://review.coreboot.org/7040
Tested-by: build bot (Jenkins)
Reviewed-by: Paul Menzel <paulepanter@users.sourceforge.net>
Reviewed-by: Marc Jones <marc.jones@se-eng.com>
baytrail: Add padding to the end of device_nvs to match ACPI

ACPI globalnvs.asl expects the gnvs memory area size to be 0x2000.
Padding has been added to device_nvs struct to reserve the full
0x2000 bytes for gnvs usage.

No known issues are caused by having the GNVS area shorter than
what ACPI thinks. Since there's nothing defined in this area,
O/S shouldn't try to access it. Only problem might be if O/S
notices the SSDT is located within the GNVS defined area.

I verified that the next table written to memory (SSDT) is 0x2000
past GNVS start using a custom-designed Baytrail-I motherboard
based on the Intel Bayley Bay CRB.

Change-Id: I9792954c7a3403eba6f37d7e53ea4a9ed3a2e4ac
Signed-off-by: Scott Radcliffe <sradcliffe@microind.com>
Reviewed-on: http://review.coreboot.org/7039
Tested-by: build bot (Jenkins)
Reviewed-by: Paul Menzel <paulepanter@users.sourceforge.net>
Reviewed-by: Marc Jones <marc.jones@se-eng.com>
intel/fsp_baytrail: Add padding so device_nvs location matches ACPI

The offset of the device_nvs in the gnvs struct is expected to be
0x1000. It is actually 0x100 so padding is needed to move device_nvs
to the expected location. ACPI references to device_nvs objects will
be correct with the padding.

This was tested using a Micro Industries customized Baytrail-I board
based on the Intel Bayley Bay CRB. In intel/baytrail/nvs.h, there's
a Google customized structure located at 0x0100-0x0FFF that is
removed from the fsp_baytrail/nvs.h which explains the mismatch here.

Change-Id: I4721a79b53b5b3345ff9b0c053bdd31d2cf9cb61
Signed-off-by: Scott Radcliffe <sradcliffe@microind.com>
Reviewed-on: http://review.coreboot.org/7038
Reviewed-by: Paul Menzel <paulepanter@users.sourceforge.net>
Tested-by: build bot (Jenkins)
Reviewed-by: Marc Jones <marc.jones@se-eng.com>
gm45: Convert to per-device ACPI

Change-Id: Ib04b03b2dc2ad3bfa886b43df9dd6518bbb46e3f
Signed-off-by: Vladimir Serbinenko <phcoder@gmail.com>
Reviewed-on: http://review.coreboot.org/6803
Tested-by: build bot (Jenkins)
Reviewed-by: Aaron Durbin <adurbin@google.com>
i945: Convert to per-device ACPI

Change-Id: Iee3ee33ca58b8c722d2d38aae31e7130032512ad
Signed-off-by: Vladimir Serbinenko <phcoder@gmail.com>
Reviewed-on: http://review.coreboot.org/6804
Tested-by: build bot (Jenkins)
Reviewed-by: Aaron Durbin <adurbin@google.com>
google mainboards: Guard ACPI TPM Device with CONFIG_CHROMEOS

The TPM is currently only configured/enabled/used if CONFIG_CHROMEOS
is enabled, but the ACPI TPM device is defined always.

If CONFIG_CHROMEOS is not defined then the Linux kernel will timeout
trying to talk to the TPM on resume because it expects a defined TPM
to be sent the TPM Resume command before returning to the OS.

Change-Id: Ia1e88d52b94e74b0011810db24b114c1c7ff0cd8
Signed-off-by: Duncan Laurie <dlaurie@chromium.org>
google/panther: default to lowest (vs highest) fan speed if invalid reading

Change-Id: If919657f21765644158aa636f9f35bdceb80fbf2
Signed-off-by: Matt DeVillier <matt.devillier@gmail.com>
panther: add config file, build script, cfbs files

Change-Id: Ibaa12003736fc2fc28c889487f4990e1a48e5112
Signed-off-by: Matt DeVillier <matt.devillier@gmail.com>
ignore binary output files / checksum files

Change-Id: I27f27870eed44ab8f1cc488b99072364498eda5e
Signed-off-by: Matt DeVillier <matt.devillier@gmail.com>
vendorcode/google: remove ramoops dummy ACPI device GOOG/9999

Change-Id: Ic864d01e57b3c4f43a3f60bc92e461cf24ec36f1
Signed-off-by: Matt DeVillier <matt.devillier@gmail.com>