| Message ID | 20200502143555.543636-4-pasha.tatashin@soleen.com |
|---|---|
| State | New |
| Headers | show |
| Series | allow ramoops to collect all kmesg_dump events | expand |
diff --git a/Documentation/devicetree/bindings/reserved-memory/ramoops.txt b/Documentation/devicetree/bindings/reserved-memory/ramoops.txt index 0eba562fe5c6..3ce424c9ad4c 100644 --- a/Documentation/devicetree/bindings/reserved-memory/ramoops.txt +++ b/Documentation/devicetree/bindings/reserved-memory/ramoops.txt @@ -47,5 +47,8 @@ Optional properties: - no-dump-oops: if present, only dump panics (defaults to panics and oops) +- dump-all: if present, dump kernel messages during all kmesg dump events. + Reasons are specified in include/linux/kmsg_dump.h KMSG_DUMP_* + - flags: if present, pass ramoops behavioral flags (defaults to 0, see include/linux/pstore_ram.h RAMOOPS_FLAG_* for flag values).
Currently, it is possible to dump kmesges for panic, or oops. With dump_all it is possible to dump messages for kmesg_dump events, for example reboot, halt, shutdown, kexec. Signed-off-by: Pavel Tatashin <pasha.tatashin@soleen.com> --- Documentation/devicetree/bindings/reserved-memory/ramoops.txt | 3 +++ 1 file changed, 3 insertions(+)