MIRRORS/linux-imx
1
0
Fork 0
mirror of https://github.com/nxp-imx/linux-imx.git synced 2025-09-03 02:16:09 +02:00
Code Issues Actions Packages Projects Releases Wiki Activity
lf-6.6.y
linux-imx/Documentation/ABI/stable/sysfs-firmware-opal-dump
Mauro Carvalho Chehab 98913408c5 docs: ABI: stable: make files ReST compatible 
Several entries at the stable ABI files won't parse if we pass
them directly to the ReST output.

Adjust them, in order to allow adding their contents as-is at
the stable ABI book.

Acked-by: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>
Acked-by: Jonathan Corbet <corbet@lwn.net>
Signed-off-by: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
Link: https://lore.kernel.org/r/467a0dfbcdf00db710a629d3fe4a2563750339d8.1604042072.git.mchehab+huawei@kernel.org
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
2020-10-30 13:07:01 +01:00

1.7 KiB
Raw Permalink Blame History

What: /sys/firmware/opal/dump Date: Feb 2014 Contact: Stewart Smith stewart@linux.vnet.ibm.com Description: This directory exposes interfaces for interacting with the FSP and platform dumps through OPAL firmware interface.

	This is only for the powerpc/powernv platform.

	=============== ===============================================
	initiate_dump:	When '1' is written to it,
			we will initiate a dump.
			Read this file for supported commands.

	0xXX-0xYYYY:	A directory for dump of type 0xXX and
			id 0xYYYY (in hex). The name of this
			directory should not be relied upon to
			be in this format, only that it's unique
			among all dumps. For determining the type
			and ID of the dump, use the id and type files.
			Do not rely on any particular size of dump
			type or dump id.
	=============== ===============================================

	Each dump has the following files:

	=============== ===============================================
	id:		An ASCII representation of the dump ID
			in hex (e.g. '0x01')
	type:		An ASCII representation of the type of
			dump in the format "0x%x %s" with the ID
			in hex and a description of the dump type
			(or 'unknown').
			Type '0xffffffff unknown' is used when
			we could not get the type from firmware.
			e.g. '0x02 System/Platform Dump'
	dump:		A binary file containing the dump.
			The size of the dump is the size of this file.
	acknowledge:	When 'ack' is written to this, we will
			acknowledge that we've retrieved the
			dump to the service processor. It will
			then remove it, making the dump
			inaccessible.
			Reading this file will get a list of
			supported actions.
	=============== ===============================================