Add snapshot of dcvs dt bindings as of qcom-6.1
commit 96af901712d3 ("dt-bindings: soc: qcom: Document
CRMB and CRMC regs").
Change-Id: I305f06bee1895feabec2b85b2c5ed4fa80895f83
Signed-off-by: Amir Vajid <quic_avajid@quicinc.com>
Signed-off-by: Gurbir Arora <quic_gurbaror@quicinc.com>
38 lines
993 B
YAML
38 lines
993 B
YAML
# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
|
|
%YAML 1.2
|
|
---
|
|
$id: http://devicetree.org/schemas/soc/qcom/qcom,cpucp-log.yaml#
|
|
$schema: http://devicetree.org/meta-schemas/core.yaml#
|
|
|
|
title: Qualcomm Technologies, Inc. CPUCP Logging
|
|
|
|
description: |
|
|
CPUCP logging is a device that uses mailbox to collect the logs
|
|
generated from cpucp, and dump them into a dedicated log buffer
|
|
through ipc_logging framework.
|
|
An instance of cpucp-log should have the mailbox controller phandle and
|
|
addresses of log buffer set aside for this purpose.
|
|
|
|
properties:
|
|
compatible:
|
|
const: qcom,cpucp-log
|
|
|
|
mboxes:
|
|
description:
|
|
reference to "cpucp" mailbox, as described in mailbox/mailbox.txt.
|
|
|
|
required:
|
|
- compatible
|
|
- mboxes
|
|
- reg
|
|
|
|
examples:
|
|
- |
|
|
cpucp_log: qcom,cpucp_log@fd04780 {
|
|
#address-cells = <2>;
|
|
#size-cells = <2>;
|
|
compatible = "qcom,cpucp-log";
|
|
reg = <0x0fd04580 0x200>, <0x0fd04780 0x200>;
|
|
mboxes = <&cpucp 1>;
|
|
};
|