Changes in Kconfig

dff054e6 - firmware: coreboot: framebuffer: Allow building with simpledrm

Tue, 25 Jul 2023 17:43:33 +0000

firmware: coreboot: framebuffer: Allow building with simpledrmThe coreboot framebuffer driver registers a "simple-framebuffer" devicebased on the information from the firmware, after checking that it'scompatible with the formats listed in simplefb.h. It was added beforesimpledrm, and its Kconfig marked as dependent on the simplefb driver.The simpledrm driver can also handle "simple-framebuffer" devices andthe coreboot framebuffer works fine with it on a 'Lick' Chromebook.Allow building the coreboot framebuffer driver with simpledrm as well.Signed-off-by: Alper Nebi Yasak Reviewed-by: Brian Norris Link: https://lore.kernel.org/r/20230725174334.887485-1-alpernebiyasak@gmail.comSigned-off-by: Greg Kroah-Hartman List of files: /linux-6.15/drivers/firmware/google/Kconfig

e42af722 - firmware: coreboot: Remove GOOGLE_COREBOOT_TABLE_ACPI/OF Kconfig entries

Tue, 07 Feb 2023 16:12:00 +0000

firmware: coreboot: Remove GOOGLE_COREBOOT_TABLE_ACPI/OF Kconfig entriesEver since commit a28aad66da8b ("firmware: coreboot: Collapse platformdrivers into bus core") the Kconfig entries GOOGLE_COREBOOT_TABLE_OFand GOOGLE_COREBOOT_TABLE_ACPI have been dead. They have no "help"text and thus aren't user choosable. They also aren't "select"ed byanything. They also control the compilation of no code.Let's remove them.Fixes: a28aad66da8b ("firmware: coreboot: Collapse platform drivers into bus core")Signed-off-by: Douglas Anderson Reviewed-by: Guenter Roeck Reviewed-by: Jack Rosenthal Acked-by: Stephen Boyd Link: https://lore.kernel.org/r/20230207081130.1.I657776750156793721efa247ce6293445137bc8a@changeidSigned-off-by: Greg Kroah-Hartman List of files: /linux-6.15/drivers/firmware/google/Kconfig

19d54020 - firmware: google: Implement cbmem in sysfs driver

Fri, 04 Nov 2022 16:15:28 +0000

firmware: google: Implement cbmem in sysfs driverThe CBMEM area is a downward-growing memory region used by coreboot todynamically allocate tagged data structures ("CBMEM entries") thatremain resident during boot.This implements a driver which exports access to the CBMEM entriesvia sysfs under /sys/bus/coreboot/devices/cbmem-.This implementation is quite versatile. Examples of how it could beused are given below:* Tools like util/cbmem from the coreboot tree could use this driver instead of finding CBMEM in /dev/mem directly. Alternatively, firmware developers debugging an issue may find the sysfs interface more ergonomic than the cbmem tool and choose to use it directly.* The crossystem tool, which exposes verified boot variables, can use this driver to read the vboot work buffer.* Tools which read the BIOS SPI flash (e.g., flashrom) can find the flash layout in CBMEM directly, which is significantly faster than searching the flash directly.Write access is provided to all CBMEM regions via/sys/bus/coreboot/devices/cbmem-/mem, as the existing cbmemtooling updates this memory region, and envisioned use cases withcrossystem can benefit from updating memory regions.Link: https://issuetracker.google.com/239604743Cc: Stephen Boyd Cc: Tzung-Bi Shih Reviewed-by: Guenter Roeck Reviewed-by: Julius Werner Tested-by: Jack Rosenthal Signed-off-by: Jack Rosenthal Link: https://lore.kernel.org/r/20221104161528.531248-1-jrosenth@chromium.orgSigned-off-by: Greg Kroah-Hartman List of files: /linux-6.15/drivers/firmware/google/Kconfig

37fd8391 - firmware: google: Properly state IOMEM dependency

Fri, 25 Feb 2022 04:15:02 +0000

firmware: google: Properly state IOMEM dependencyThe Google Coreboot implementation requires IOMEM functions(memmremap, memunmap, devm_memremap), but does not specify this is itsKconfig. This results in build errors when HAS_IOMEM is not set, such ason some UML configurations:/usr/bin/ld: drivers/firmware/google/coreboot_table.o: in function `coreboot_table_probe':coreboot_table.c:(.text+0x311): undefined reference to `memremap'/usr/bin/ld: coreboot_table.c:(.text+0x34e): undefined reference to `memunmap'/usr/bin/ld: drivers/firmware/google/memconsole-coreboot.o: in function `memconsole_probe':memconsole-coreboot.c:(.text+0x12d): undefined reference to `memremap'/usr/bin/ld: memconsole-coreboot.c:(.text+0x17e): undefined reference to `devm_memremap'/usr/bin/ld: memconsole-coreboot.c:(.text+0x191): undefined reference to `memunmap'/usr/bin/ld: drivers/firmware/google/vpd.o: in function `vpd_section_destroy.isra.0':vpd.c:(.text+0x300): undefined reference to `memunmap'/usr/bin/ld: drivers/firmware/google/vpd.o: in function `vpd_section_init':vpd.c:(.text+0x382): undefined reference to `memremap'/usr/bin/ld: vpd.c:(.text+0x459): undefined reference to `memunmap'/usr/bin/ld: drivers/firmware/google/vpd.o: in function `vpd_probe':vpd.c:(.text+0x59d): undefined reference to `memremap'/usr/bin/ld: vpd.c:(.text+0x5d3): undefined reference to `memunmap'collect2: error: ld returned 1 exit statusFixes: a28aad66da8b ("firmware: coreboot: Collapse platform drivers into bus core")Acked-By: anton ivanov Acked-By: Julius Werner Signed-off-by: David Gow Link: https://lore.kernel.org/r/20220225041502.1901806-1-davidgow@google.comSigned-off-by: Greg Kroah-Hartman List of files: /linux-6.15/drivers/firmware/google/Kconfig

d185a346 - firmware: Update Kconfig help text for Google firmware

Mon, 18 Jun 2018 22:55:40 +0000

firmware: Update Kconfig help text for Google firmwareThe help text for GOOGLE_FIRMWARE states that it should only beenabled when building a kernel for Google's own servers. However,many of the drivers dependent on it are also useful on Chromebooks oron any platform using coreboot.Update the help text to reflect this double duty.Fixes: d384d6f43d1e ("firmware: google memconsole: Add coreboot support")Reviewed-by: Julius Werner Signed-off-by: Ben Hutchings Link: https://lore.kernel.org/r/20180618225540.GD14131@decadent.org.ukSigned-off-by: Greg Kroah-Hartman List of files: /linux-6.15/drivers/firmware/google/Kconfig

9846d860 - efi: gsmi: fix false dependency on CONFIG_EFI_VARS

Wed, 23 Sep 2020 08:18:31 +0000

efi: gsmi: fix false dependency on CONFIG_EFI_VARSThe gsmi code does not actually rely on CONFIG_EFI_VARS, since it onlyuses the efivars abstraction that is included unconditionally whenCONFIG_EFI is defined. CONFIG_EFI_VARS controls the inclusion of thecode that exposes the sysfs entries, and which has been deprecated forsome time.Signed-off-by: Ard Biesheuvel List of files: /linux-6.15/drivers/firmware/google/Kconfig

ec8f24b7 - treewide: Add SPDX license identifier - Makefile/Kconfig

Sun, 19 May 2019 12:07:45 +0000

treewide: Add SPDX license identifier - Makefile/KconfigAdd SPDX license identifiers to all Make/Kconfig files which: - Have no license information of any formThese files fall under the project license, GPL v2 only. The resulting SPDXlicense identifier is: GPL-2.0-onlySigned-off-by: Thomas Gleixner Signed-off-by: Greg Kroah-Hartman List of files: /linux-6.15/drivers/firmware/google/Kconfig

d31655ba - gsmi: Remove autoselected dependency on EFI and EFI_VARS

Fri, 12 Oct 2018 16:04:47 +0000

gsmi: Remove autoselected dependency on EFI and EFI_VARSInstead of selecting EFI and EFI_VARS automatically when GSMI isenabled let that portion of the driver be conditionally compiledif EFI and EFI_VARS are enabled.This allows the rest of the driver (specifically event log) tobe used if EFI_VARS is not enabled.To test:1) verify that EFI_VARS is not automatically selected whenCONFIG_GOOGLE_GSMI is enabled2) verify that the kernel boots on Link and that GSMI event logis still available and functional3) specifically boot the kernel on Alex to ensure it does nottry to load efivars and that gsmi also does not load because itis not in the supported DMI tableSigned-off-by: Duncan Laurie Reviewed-by: Olof Johansson Signed-off-by: Benson Leung Signed-off-by: Ben Zhang Signed-off-by: Filipe Brandenburger Signed-off-by: Furquan Shaikh Tested-by: Furquan Shaikh Reviewed-by: Aaron Durbin [zwisler: update changelog for upstream]Signed-off-by: Ross Zwisler Reviewed-by: Guenter Roeck Signed-off-by: Greg Kroah-Hartman List of files: /linux-6.15/drivers/firmware/google/Kconfig

a28aad66 - firmware: coreboot: Collapse platform drivers into bus core

Wed, 15 Aug 2018 20:37:06 +0000

firmware: coreboot: Collapse platform drivers into bus coreThe DT based and ACPI based platform drivers here do the same thing; mapsome memory and hand it over to the coreboot bus to populate devices.The only major difference is that the DT based driver doesn't map thecoreboot table header to figure out how large of a region to map for thewhole coreboot table and it uses of_iomap() instead of ioremap_cache().A cached or non-cached mapping shouldn't matter here and mapping somesmaller region first before mapping the whole table is just more workbut should be OK. In the end, we can remove two files and combine thecode all in one place making it easier to reason about things.We leave the old Kconfigs in place for a little while longer but makethem hidden and select the previously hidden config option. This wayusers can upgrade without having to know to reselect this config in thefuture. Later on we can remove the old hidden configs.Cc: Wei-Ning Huang Cc: Julius Werner Cc: Brian Norris Cc: Samuel Holland Signed-off-by: Stephen Boyd Reviewed-by: Julius Werner Signed-off-by: Greg Kroah-Hartman List of files: /linux-6.15/drivers/firmware/google/Kconfig

851b4c14 - firmware: coreboot: Add coreboot framebuffer driver

Thu, 25 Jan 2018 01:41:20 +0000

firmware: coreboot: Add coreboot framebuffer driverRegister a simplefb framebuffer when the coreboot table contains aframebuffer entry.Signed-off-by: Samuel Holland Signed-off-by: Greg Kroah-Hartman List of files: /linux-6.15/drivers/firmware/google/Kconfig

049a59db - firmware: Google VPD sysfs driver

Wed, 12 Apr 2017 16:56:19 +0000

firmware: Google VPD sysfs driverThis patch introduces the Google Vital Product Data driver.This driver reads Vital Product Data from coreboot tables and thencreates the corresponding sysfs entries under /sys/firmware/vpd toprovide easy access for userspace programs (does not require flashrom).The sysfs is structured as follow: /sys/firmware/vpd |-- ro | |-- key1 | `-- key2 |-- ro_raw |-- rw | `-- key1 `-- rw_rawWhere ro_raw and rw_raw contain the raw VPD partition. The files underro and rw correspond to the key name in the VPD and the the file contentis the value for the key.Signed-off-by: Wei-Ning Huang Signed-off-by: Thierry Escande Signed-off-by: Greg Kroah-Hartman List of files: /linux-6.15/drivers/firmware/google/Kconfig

a1d6f9cf - firmware: google memconsole: Add ARM/ARM64 support

Tue, 28 Mar 2017 16:11:29 +0000

firmware: google memconsole: Add ARM/ARM64 supportThis patch expands the Google firmware memory console driver to alsowork on certain tree based platforms running coreboot, such as ARM/ARM64Chromebooks. This patch now adds another path to find the coreboot tablethrough the device tree. In order to find that, a second levelbootloader must have installed the 'coreboot' compatible device treenode that describes its base address and size.This patch is a rework/split/merge of patches from the chromeos v4.4kernel tree originally authored by: Wei-Ning Huang Julius Werner Brian Norris Signed-off-by: Thierry Escande Signed-off-by: Greg Kroah-Hartman List of files: /linux-6.15/drivers/firmware/google/Kconfig

d384d6f4 - firmware: google memconsole: Add coreboot support

Tue, 28 Mar 2017 16:11:27 +0000

firmware: google memconsole: Add coreboot supportCoreboot (http://www.coreboot.org) allows to save the firmware consoleoutput in a memory buffer. With this patch, the address of this memorybuffer is obtained from coreboot tables on x86 chromebook devicesdeclaring an ACPI device with name matching GOOGCB00 or BOOT0000.If the memconsole-coreboot driver is able to find the coreboot table,the memconsole driver sets the cbmem_console address and initializes thememconsole sysfs entries.The coreboot_table-acpi driver is responsible for setting the address ofthe coreboot table header when probed. If this address is not yet setwhen memconsole-coreboot is probed, then the probe is deferred byreturning -EPROBE_DEFER.This patch is a rework/split/merge of patches from the chromeos v4.4kernel tree originally authored by: Vadim Bendebury Wei-Ning Huang Yuji Sasaki Duncan Laurie Julius Werner Brian Norris Signed-off-by: Thierry Escande Signed-off-by: Greg Kroah-Hartman List of files: /linux-6.15/drivers/firmware/google/Kconfig

afe9dba4 - firmware: google memconsole: Move specific EBDA parts

Tue, 28 Mar 2017 16:11:26 +0000

firmware: google memconsole: Move specific EBDA partsThis patch splits memconsole.c in 2 parts. One containing thearchitecture-independent part and the other one containing the EBDAspecific part. This prepares the integration of coreboot support for thememconsole.The memconsole driver is now named as memconsole-x86-legacy.Signed-off-by: Thierry Escande Signed-off-by: Greg Kroah-Hartman List of files: /linux-6.15/drivers/firmware/google/Kconfig

f952a401 - firmware: google memconsole: Remove useless submenu in Kconfig

Tue, 28 Mar 2017 16:11:25 +0000

firmware: google memconsole: Remove useless submenu in KconfigThis patch removes the "Google Firmware Drivers" menu containing amenuconfig entry with the exact same name. The menuconfig is nowdirectly under the "Firmware Drivers" entry.Signed-off-by: Thierry Escande Signed-off-by: Greg Kroah-Hartman List of files: /linux-6.15/drivers/firmware/google/Kconfig

c2218e26 - firmware/google: drop 'select EFI' to avoid recursive dependency

Tue, 28 Jan 2014 01:07:21 +0000

firmware/google: drop 'select EFI' to avoid recursive dependencyThe GOOGLE_SMI Kconfig symbol depends on DMI and selects EFI. Thiscauses problems on other archs when introducing DMI support that dependson EFI, as it results in a recursive dependency: arch/arm/Kconfig:1845:error: recursive dependency detected! arch/arm/Kconfig:1845: symbol DMI depends on EFIFix by changing the 'select EFI' to a 'depends on EFI'.Signed-off-by: Ard Biesheuvel Cc: David Rientjes Acked-by: Mike Waychison Signed-off-by: Andrew Morton Signed-off-by: Linus Torvalds List of files: /linux-6.15/drivers/firmware/google/Kconfig

5daf538a - firmware: fix GOOGLE_SMI kconfig dependency warning

Mon, 23 May 2011 00:38:02 +0000

firmware: fix GOOGLE_SMI kconfig dependency warningIs it meaningful/useful to enable EFI_VARS but not EFI?That's what GOOGLE_SMI does. Make it enable EFI also.Fixes this kconfig dependency warning:warning: (GOOGLE_SMI) selects EFI_VARS which has unmet direct dependencies (EFI)Signed-off-by: Randy Dunlap Acked-by: Mike Waychison Signed-off-by: Greg Kroah-Hartman List of files: /linux-6.15/drivers/firmware/google/Kconfig

a1d9a09a - Introduce CONFIG_GOOGLE_FIRMWARE

Sat, 30 Apr 2011 00:39:31 +0000

Introduce CONFIG_GOOGLE_FIRMWAREIn order to keep Google's firmware drivers organized amongst themselves,all Google firmware drivers are gated on CONFIG_GOOGLE_FIRMWARE=y, whichdefaults to 'n' in the kernel build.Signed-off-by: Mike Waychison Signed-off-by: Greg Kroah-Hartman List of files: /linux-6.15/drivers/firmware/google/Kconfig

e561bc45 - driver: Google Memory Console

Sat, 30 Apr 2011 00:39:25 +0000

driver: Google Memory ConsoleThis patch introduces the 'memconsole' driver.Our firmware gives us access to an in-memory log of the firmware'soutput. This gives us visibility in a data-center of headless machinesas to what the firmware is doing.The memory console is found by the driver by finding a header block inthe EBDA. The buffer is then copied out, and is exported to userland inthe file /sys/firmware/log.Signed-off-by: San Mehat Signed-off-by: Mike Waychison Signed-off-by: Greg Kroah-Hartman List of files: /linux-6.15/drivers/firmware/google/Kconfig

74c5b31c - driver: Google EFI SMI

Sat, 30 Apr 2011 00:39:19 +0000

driver: Google EFI SMIThe "gsmi" driver bridges userland with firmware specific routines foraccessing hardware.Currently, this driver only supports NVRAM and eventlog information.Deprecated functions have been removed from the driver, though theirop-codes are left in place so that they are not re-used.This driver works by trampolining into the firmware via the smi_commandoutlined in the FADT table. Three protocols are used due to variouslimitations over time, but all are included herein.This driver should only ever load on Google boards, identified by eithera "Google, Inc." board vendor string in DMI, or "GOOGLE" in the OEMstrings of the FADT ACPI table. This logic happens ingsmi_system_valid().Signed-off-by: Duncan Laurie Signed-off-by: Aaron Durbin Signed-off-by: Mike Waychison Signed-off-by: Greg Kroah-Hartman List of files: /linux-6.15/drivers/firmware/google/Kconfig