| Andrew Scull | b4b6d4a | 2019-01-02 15:54:55 +0000 | [diff] [blame] | 1 | menuconfig GOOGLE_FIRMWARE |
| 2 | bool "Google Firmware Drivers" |
| 3 | default n |
| 4 | help |
| 5 | These firmware drivers are used by Google's servers. They are |
| 6 | only useful if you are working directly on one of their |
| 7 | proprietary servers. If in doubt, say "N". |
| 8 | |
| 9 | if GOOGLE_FIRMWARE |
| 10 | |
| 11 | config GOOGLE_SMI |
| 12 | tristate "SMI interface for Google platforms" |
| 13 | depends on X86 && ACPI && DMI && EFI |
| 14 | select EFI_VARS |
| 15 | help |
| 16 | Say Y here if you want to enable SMI callbacks for Google |
| 17 | platforms. This provides an interface for writing to and |
| 18 | clearing the EFI event log and reading and writing NVRAM |
| 19 | variables. |
| 20 | |
| 21 | config GOOGLE_COREBOOT_TABLE |
| 22 | tristate |
| 23 | depends on GOOGLE_COREBOOT_TABLE_ACPI || GOOGLE_COREBOOT_TABLE_OF |
| 24 | |
| 25 | config GOOGLE_COREBOOT_TABLE_ACPI |
| 26 | tristate "Coreboot Table Access - ACPI" |
| 27 | depends on ACPI |
| 28 | select GOOGLE_COREBOOT_TABLE |
| 29 | help |
| 30 | This option enables the coreboot_table module, which provides other |
| 31 | firmware modules to access to the coreboot table. The coreboot table |
| 32 | pointer is accessed through the ACPI "GOOGCB00" object. |
| 33 | If unsure say N. |
| 34 | |
| 35 | config GOOGLE_COREBOOT_TABLE_OF |
| 36 | tristate "Coreboot Table Access - Device Tree" |
| 37 | depends on OF |
| 38 | select GOOGLE_COREBOOT_TABLE |
| 39 | help |
| 40 | This option enable the coreboot_table module, which provide other |
| 41 | firmware modules to access coreboot table. The coreboot table pointer |
| 42 | is accessed through the device tree node /firmware/coreboot. |
| 43 | If unsure say N. |
| 44 | |
| 45 | config GOOGLE_MEMCONSOLE |
| 46 | tristate |
| 47 | depends on GOOGLE_MEMCONSOLE_X86_LEGACY || GOOGLE_MEMCONSOLE_COREBOOT |
| 48 | |
| 49 | config GOOGLE_MEMCONSOLE_X86_LEGACY |
| 50 | tristate "Firmware Memory Console - X86 Legacy support" |
| 51 | depends on X86 && ACPI && DMI |
| 52 | select GOOGLE_MEMCONSOLE |
| 53 | help |
| 54 | This option enables the kernel to search for a firmware log in |
| 55 | the EBDA on Google servers. If found, this log is exported to |
| 56 | userland in the file /sys/firmware/log. |
| 57 | |
| 58 | config GOOGLE_FRAMEBUFFER_COREBOOT |
| 59 | tristate "Coreboot Framebuffer" |
| 60 | depends on FB_SIMPLE |
| 61 | depends on GOOGLE_COREBOOT_TABLE |
| 62 | help |
| 63 | This option enables the kernel to search for a framebuffer in |
| 64 | the coreboot table. If found, it is registered with simplefb. |
| 65 | |
| 66 | config GOOGLE_MEMCONSOLE_COREBOOT |
| 67 | tristate "Firmware Memory Console" |
| 68 | depends on GOOGLE_COREBOOT_TABLE |
| 69 | select GOOGLE_MEMCONSOLE |
| 70 | help |
| 71 | This option enables the kernel to search for a firmware log in |
| 72 | the coreboot table. If found, this log is exported to userland |
| 73 | in the file /sys/firmware/log. |
| 74 | |
| 75 | config GOOGLE_VPD |
| 76 | tristate "Vital Product Data" |
| 77 | depends on GOOGLE_COREBOOT_TABLE |
| 78 | help |
| 79 | This option enables the kernel to expose the content of Google VPD |
| 80 | under /sys/firmware/vpd. |
| 81 | |
| 82 | endif # GOOGLE_FIRMWARE |