aboutsummaryrefslogtreecommitdiffstats
path: root/Documentation/devicetree/bindings/firmware
diff options
context:
space:
mode:
authorThierry Escande <thierry.escande@collabora.com>2017-03-28 18:11:27 +0200
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>2017-04-08 18:05:36 +0200
commitd384d6f43d1ec3f1225ab0275fd592c5980bd830 (patch)
tree417fd90c8d439adb8af497c319f420e1a846b97a /Documentation/devicetree/bindings/firmware
parentfirmware: google memconsole: Move specific EBDA parts (diff)
downloadlinux-dev-d384d6f43d1ec3f1225ab0275fd592c5980bd830.tar.xz
linux-dev-d384d6f43d1ec3f1225ab0275fd592c5980bd830.zip
firmware: google memconsole: Add coreboot support
Coreboot (http://www.coreboot.org) allows to save the firmware console output in a memory buffer. With this patch, the address of this memory buffer is obtained from coreboot tables on x86 chromebook devices declaring 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 the memconsole sysfs entries. The coreboot_table-acpi driver is responsible for setting the address of the coreboot table header when probed. If this address is not yet set when memconsole-coreboot is probed, then the probe is deferred by returning -EPROBE_DEFER. This patch is a rework/split/merge of patches from the chromeos v4.4 kernel tree originally authored by: Vadim Bendebury <vbendeb@chromium.org> Wei-Ning Huang <wnhuang@google.com> Yuji Sasaki <sasakiy@google.com> Duncan Laurie <dlaurie@chromium.org> Julius Werner <jwerner@chromium.org> Brian Norris <briannorris@chromium.org> Signed-off-by: Thierry Escande <thierry.escande@collabora.com> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'Documentation/devicetree/bindings/firmware')
0 files changed, 0 insertions, 0 deletions