Files
android_kernel_samsung_sm87…/bindings/reserved-memory/qcom,ramoops.yaml
Mukesh Ojha 8def3aeb71 dt-bindings: soc: qcom: Add qcom,ramoops device binding
Add qcom,ramoops binding for its device and it is exactly copy of
ramoops device but differ in just memory is dynamically reserved
during early boot.

Change-Id: I2b2b288061ba001aa8cc9a73fad1176a01ce4769
Signed-off-by: Mukesh Ojha <quic_mojha@quicinc.com>
2024-02-26 21:26:36 +05:30

125 lines
3.8 KiB
YAML

# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
%YAML 1.2
---
$id: "http://devicetree.org/schemas/reserved-memory/qcom,ramoops.yaml#"
$schema: "http://devicetree.org/meta-schemas/core.yaml#"
title: Qualcomm Technologies, Inc. Dynamic ramoops
description: |
Qualcomm Technologies, Inc. dynamic ramoops logger provide a means
of storing the ramoops data to some dynamically reserved memory
instead of traditionally implemented ramoops where the region should
be statically fixed ram region. Because of its similarity with ramoops
it will also have same set of property what ramoops have it in its
schema and is going to contain traditional ramoops frontend data and
this region will be collected via Qualcomm Technologies, Inc. Minidump
infrastructure provided from the boot firmware.
maintainers:
- Mukesh Ojha <quic_mojha@quicinc.com>
properties:
compatible:
items:
- const: qcom,ramoops
memory-region:
maxItems: 1
description: handle to memory reservation for qcom,ramoops region.
ecc-size:
$ref: /schemas/types.yaml#/definitions/uint32
description: enables ECC support and specifies ECC buffer size in bytes
default: 0 # no ECC
record-size:
$ref: /schemas/types.yaml#/definitions/uint32
description: maximum size in bytes of each kmsg dump
default: 0
console-size:
$ref: /schemas/types.yaml#/definitions/uint32
description: size in bytes of log buffer reserved for kernel messages
default: 0
ftrace-size:
$ref: /schemas/types.yaml#/definitions/uint32
description: size in bytes of log buffer reserved for function tracing and profiling
default: 0
pmsg-size:
$ref: /schemas/types.yaml#/definitions/uint32
description: size in bytes of log buffer reserved for userspace messages
default: 0
mem-type:
$ref: /schemas/types.yaml#/definitions/uint32
description: if present, sets the type of mapping is to be used to map the reserved region.
default: 0
oneOf:
- const: 0
description: write-combined
- const: 1
description: unbuffered
- const: 2
description: cached
max-reason:
$ref: /schemas/types.yaml#/definitions/uint32
default: 2 # log oopses and panics
maximum: 0x7fffffff
description: |
If present, sets maximum type of kmsg dump reasons to store.
This can be set to INT_MAX to store all kmsg dumps.
See include/linux/kmsg_dump.h KMSG_DUMP_* for other kmsg dump reason values.
Setting this to 0 (KMSG_DUMP_UNDEF), means the reason filtering will be
controlled by the printk.always_kmsg_dump boot param.
If unset, it will be 2 (KMSG_DUMP_OOPS), otherwise 5 (KMSG_DUMP_MAX).
flags:
$ref: /schemas/types.yaml#/definitions/uint32
default: 0
description: |
If present, pass ramoops behavioral flags
(see include/linux/pstore_ram.h RAMOOPS_FLAG_* for flag values).
no-dump-oops:
deprecated: true
type: boolean
description: |
Use max_reason instead. If present, and max_reason is not specified,
it is equivalent to max_reason = 1 (KMSG_DUMP_PANIC).
unbuffered:
deprecated: true
type: boolean
description: |
Use mem_type instead. If present, and mem_type is not specified,
it is equivalent to mem_type = 1 and uses unbuffered mappings to map
the reserved region (defaults to buffered mappings mem_type = 0).
If both are specified -- "mem_type" overrides "unbuffered".
unevaluatedProperties: false
required:
- compatible
- memory-region
anyOf:
- required: [record-size]
- required: [console-size]
- required: [ftrace-size]
- required: [pmsg-size]
examples:
- |
qcom_ramoops {
compatible = "qcom,ramoops";
memory-region = <&qcom_ramoops_region>;
console-size = <0x8000>; /* 32kB */
record-size = <0x400>; /* 1kB */
ecc-size = <16>;
};