The example includes a board-specific compatible property, this is wrong as the example should be board agnostic and should represent the particular binding. Also, the file includes two similar examples but with a different compatible. So, drop the entire second example Suggested-by: Bjorn Andersson <bjorn.andersson@linaro.org> Signed-off-by: Sinthu Raja <sinthu.raja@ti.com> Reviewed-by: Rob Herring <robh@kernel.org> Acked-by: Suman Anna <s-anna@ti.com> Signed-off-by: Bjorn Andersson <bjorn.andersson@linaro.org> Link: https://lore.kernel.org/r/20210920123152.32751-1-sinthu.raja@ti.com
47 lines
1.1 KiB
YAML
47 lines
1.1 KiB
YAML
# SPDX-License-Identifier: (GPL-2.0-only or BSD-2-Clause)
|
|
%YAML 1.2
|
|
---
|
|
$id: http://devicetree.org/schemas/hwlock/ti,omap-hwspinlock.yaml#
|
|
$schema: http://devicetree.org/meta-schemas/core.yaml#
|
|
|
|
title: TI HwSpinlock for OMAP and K3 based SoCs
|
|
|
|
maintainers:
|
|
- Suman Anna <s-anna@ti.com>
|
|
|
|
properties:
|
|
compatible:
|
|
enum:
|
|
- ti,omap4-hwspinlock # for OMAP44xx, OMAP54xx, AM33xx, AM43xx, DRA7xx SoCs
|
|
- ti,am64-hwspinlock # for K3 AM64x SoCs
|
|
- ti,am654-hwspinlock # for K3 AM65x, J721E and J7200 SoCs
|
|
|
|
reg:
|
|
maxItems: 1
|
|
|
|
"#hwlock-cells":
|
|
const: 1
|
|
description: |
|
|
The OMAP hwspinlock users will use a 0-indexed relative hwlock number as
|
|
the argument specifier value for requesting a specific hwspinlock within
|
|
a hwspinlock bank.
|
|
|
|
Please look at the generic hwlock binding for usage information for
|
|
consumers, "Documentation/devicetree/bindings/hwlock/hwlock.txt"
|
|
|
|
required:
|
|
- compatible
|
|
- reg
|
|
- "#hwlock-cells"
|
|
|
|
additionalProperties: false
|
|
|
|
examples:
|
|
|
|
- |
|
|
spinlock@4a0f6000 {
|
|
compatible = "ti,omap4-hwspinlock";
|
|
reg = <0x4a0f6000 0x1000>;
|
|
#hwlock-cells = <1>;
|
|
};
|