On 26/05/2023 17:35, Mao Jinlong wrote: > Adds new coresight-csr.yaml file describing the bindings required > to define csr in the device trees. > > Signed-off-by: Mao Jinlong <quic_jinlmao@xxxxxxxxxxx> > --- > .../bindings/arm/qcom,coresight-csr.yaml | 62 +++++++++++++++++++ > 1 file changed, 62 insertions(+) > create mode 100644 Documentation/devicetree/bindings/arm/qcom,coresight-csr.yaml > > diff --git a/Documentation/devicetree/bindings/arm/qcom,coresight-csr.yaml b/Documentation/devicetree/bindings/arm/qcom,coresight-csr.yaml > new file mode 100644 > index 000000000000..a79b4f6a8bdf > --- /dev/null > +++ b/Documentation/devicetree/bindings/arm/qcom,coresight-csr.yaml > @@ -0,0 +1,62 @@ > +# SPDX-License-Identifier: GPL-2.0-only or BSD-2-Clause > +# Copyright (c) 2023 Qualcomm Innovation Center, Inc. All rights reserved. > +%YAML 1.2 > +--- > +$id: http://devicetree.org/schemas/arm/qcom,coresight-csr.yaml# > +$schema: http://devicetree.org/meta-schemas/core.yaml# > + > +title: CoreSight Slave Register - TPDA > + > +description: | > + CoreSight Slave Register block hosts miscellaneous configuration registers. > + Those configuration registers can be used to control, various coresight > + configurations. > + > +maintainers: > + - Mao Jinlong <quic_jinlmao@xxxxxxxxxxx> > + - Hao Zhang <quic_hazha@xxxxxxxxxxx> > + > +properties: > + $nodename: > + pattern: "^csr(@[0-9a-f]+)$" Drop nodename, we do not enforce it for device schemas. > + compatible: > + items: > + - const: qcom,coresight-csr Why qcom, not arm? Description and title suggests it is generic. If it is SoC specific, then what is it exactly? IP block of SoC? Then it would miss SoC specific compatibles. > + > + reg: > + minItems: 1 > + maxItems: 2 You need to describe the items > + > + clocks: > + maxItems: 1 > + > + clock-names: > + items: > + - const: apb_pclk > + > + qcom,set-byte-cntr-support: > + $ref: /schemas/types.yaml#/definitions/flag > + description: > + If set, indicates that CSR supports to set ETR_IRQ_CTRL register. Why this cannot be deducted from SoC-specific compatible? > + > +required: > + - compatible > + - reg > + - clocks > + - clock-names > + > +additionalProperties: false > + > +examples: > + # minimum CSR definition. Drop comment > + - | > + csr@10001000 { Best regards, Krzysztof
