dt-bindings: misc: Move esm-k3.txt to ti,j721e-esm.yaml
Move esm-k3.txt to ti,j721e-esm.yaml in line with the devicetree documentation in kernel. Signed-off-by: Neha Malcom Francis <n-francis@ti.com> Reviewed-by: Tom Rini <trini@konsulko.com>
This commit is contained in:
committed by
Tom Rini
parent
ef8489a21d
commit
d11f9f36da
@@ -1,25 +0,0 @@
|
||||
Texas Instruments K3 ESM Binding
|
||||
======================
|
||||
|
||||
ESM (Error Signaling Module) is an IP block on TI K3 devices that allows
|
||||
handling of safety events somewhat similar to what interrupt controller
|
||||
would do. The safety signals have their separate paths within the SoC,
|
||||
and they are handled by the ESM, which routes them to the proper
|
||||
destination, which can be system reset, interrupt controller, etc. In
|
||||
the simplest configuration the signals are just routed to reset the
|
||||
SoC.
|
||||
|
||||
Required properties :
|
||||
- compatible : "ti,j721e-esm"
|
||||
- ti,esm-pins : integer array of esm events IDs to route to external event
|
||||
pin which can be used to reset the SoC. The array can
|
||||
have arbitrary amount of event IDs listed on it.
|
||||
|
||||
Example
|
||||
=======
|
||||
|
||||
main_esm: esm@700000 {
|
||||
compatible = "ti,j721e-esm";
|
||||
reg = <0x0 0x700000 0x0 0x1000>;
|
||||
ti,esm-pins = <344>, <345>;
|
||||
};
|
||||
53
doc/device-tree-bindings/misc/ti,j721e-esm.yaml
Normal file
53
doc/device-tree-bindings/misc/ti,j721e-esm.yaml
Normal file
@@ -0,0 +1,53 @@
|
||||
# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
|
||||
# Copyright (C) 2022 Texas Instruments Incorporated
|
||||
%YAML 1.2
|
||||
---
|
||||
$id: http://devicetree.org/schemas/misc/ti,j721e-esm.yaml#
|
||||
$schema: http://devicetree.org/meta-schemas/core.yaml#
|
||||
|
||||
title: Texas Instruments K3 ESM
|
||||
|
||||
maintainers:
|
||||
- Neha Malcom Francis <n-francis@ti.com>
|
||||
|
||||
description:
|
||||
The ESM (Error Signaling Module) is an IP block on TI K3 devices
|
||||
that allows handling of safety events somewhat similar to what interrupt
|
||||
controller would do. The safety signals have their separate paths within
|
||||
the SoC, and they are handled by the ESM, which routes them to the proper
|
||||
destination, which can be system reset, interrupt controller, etc. In the
|
||||
simplest configuration the signals are just routed to reset the SoC.
|
||||
|
||||
properties:
|
||||
compatible:
|
||||
const: ti,j721e-esm
|
||||
|
||||
reg:
|
||||
maxItems: 1
|
||||
|
||||
ti,esm-pins:
|
||||
$ref: /schemas/types.yaml#/definitions/uint32-array
|
||||
description:
|
||||
integer array of ESM interrupt pins to route to external event pin
|
||||
which can be used to reset the SoC.
|
||||
minItems: 1
|
||||
maxItems: 255
|
||||
|
||||
required:
|
||||
- compatible
|
||||
- reg
|
||||
- ti,esm-pins
|
||||
|
||||
additionalProperties: false
|
||||
|
||||
examples:
|
||||
- |
|
||||
bus {
|
||||
#address-cells = <2>;
|
||||
#size-cells = <2>;
|
||||
esm@700000 {
|
||||
compatible = "ti,j721e-esm";
|
||||
reg = <0x0 0x700000 0x0 0x1000>;
|
||||
ti,esm-pins = <344>, <345>;
|
||||
};
|
||||
};
|
||||
Reference in New Issue
Block a user