[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1683133352-10046-11-git-send-email-quic_mojha@quicinc.com>
Date: Wed, 3 May 2023 22:32:24 +0530
From: Mukesh Ojha <quic_mojha@...cinc.com>
To: <agross@...nel.org>, <andersson@...nel.org>,
<konrad.dybcio@...aro.org>, <corbet@....net>,
<keescook@...omium.org>, <tony.luck@...el.com>,
<gpiccoli@...lia.com>, <catalin.marinas@....com>,
<will@...nel.org>, <krzysztof.kozlowski+dt@...aro.org>,
<robh+dt@...nel.org>, <linus.walleij@...aro.org>,
<linux-gpio@...r.kernel.org>, <srinivas.kandagatla@...aro.org>
CC: <linux-arm-msm@...r.kernel.org>,
<linux-remoteproc@...r.kernel.org>, <linux-kernel@...r.kernel.org>,
<linux-hardening@...r.kernel.org>,
<linux-arm-kernel@...ts.infradead.org>,
<linux-doc@...r.kernel.org>, "Mukesh Ojha" <quic_mojha@...cinc.com>
Subject: [PATCH v3 10/18] dt-bindings: reserved-memory: Add qcom,ramoops-minidump binding
Qualcomm ramoops minidump 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.
Add qcom,ramoops-minidump binding under "/reserved-memory", and is named
"qcom,ramoops-minidump" and the reason of naming like this is because
as it is going to contain ramoops frontend data and this content will
be collected via Qualcomm minidump infrastructure provided from the
boot firmware.
Signed-off-by: Mukesh Ojha <quic_mojha@...cinc.com>
---
.../reserved-memory/qcom,ramoops-minidump.yaml | 69 ++++++++++++++++++++++
1 file changed, 69 insertions(+)
create mode 100644 Documentation/devicetree/bindings/reserved-memory/qcom,ramoops-minidump.yaml
diff --git a/Documentation/devicetree/bindings/reserved-memory/qcom,ramoops-minidump.yaml b/Documentation/devicetree/bindings/reserved-memory/qcom,ramoops-minidump.yaml
new file mode 100644
index 0000000..a308db0
--- /dev/null
+++ b/Documentation/devicetree/bindings/reserved-memory/qcom,ramoops-minidump.yaml
@@ -0,0 +1,69 @@
+# SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
+%YAML 1.2
+---
+$id: "http://devicetree.org/schemas/reserved-memory/qcom,ramoops-minidump.yaml#"
+$schema: "http://devicetree.org/meta-schemas/core.yaml#"
+
+title: Qualcomm Ramoops minidump logger
+
+description: |
+ Qualcomm ramoops minidump 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.
+
+ This is a child-node of "/reserved-memory", and is named "qcom_ramoops_md_region"
+ and the reason of naming like this is because as it is going to contain ramoops
+ frontend data and this content will be collected via Qualcomm minidump
+ infrastructure provided from the boot firmware.
+
+maintainers:
+ - Mukesh Ojha <quic_mojha@...cinc.com>
+
+allOf:
+ - $ref: "reserved-memory.yaml"
+
+properties:
+ compatible:
+ items:
+ - enum:
+ - qcom,sm8450-ramoops-minidump
+ - const: qcom,ramoops-minidump
+
+ memory-region:
+ maxItems: 1
+ items:
+ - description: handle to memory reservation for qcom,ramoops-minidump region.
+
+ no-map: true
+
+unevaluatedProperties: false
+
+required:
+ - compatible
+ - memory-region
+
+examples:
+ - |
+ / {
+ compatible = "foo";
+ model = "foo";
+ #address-cells = <2>;
+ #size-cells = <2>;
+
+ reserved-memory {
+ #address-cells = <2>;
+ #size-cells = <2>;
+ ranges;
+
+ qcom_ramoops_md_region@...m_ramoops_md {
+ alloc-ranges = <0x0 0x00000000 0xffffffff 0xffffffff>;
+ size = <0x0 0x200000>;
+ no-map
+ };
+ };
+
+ qcom_ramoops_md {
+ compatible = "qcom,sm8450-ramoops-minidump", "qcom,ramoops-minidump";
+ memory-region = <&qcom_ramoops_md_region>;
+ };
+ };
--
2.7.4
Powered by blists - more mailing lists