devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Marek Behún" <kabel@kernel.org>
To: devicetree@vger.kernel.org, Rob Herring <robh+dt@kernel.org>
Cc: pali@kernel.org, "Marek Behún" <kabel@kernel.org>
Subject: [PATCH] dt-bindings: bus: add device tree bindings for fsl,p1021rdb-pc-cpld
Date: Tue,  5 Jul 2022 19:54:50 +0200	[thread overview]
Message-ID: <20220705175450.11886-1-kabel@kernel.org> (raw)

Add binding for CPLD bus interface of Freescale P1021RDB Combo Board
CPLD Design.

Signed-off-by: Marek Behún <kabel@kernel.org>
---
 .../bindings/bus/fsl,p1021rdb-pc-cpld.yaml    | 73 +++++++++++++++++++
 1 file changed, 73 insertions(+)
 create mode 100644 Documentation/devicetree/bindings/bus/fsl,p1021rdb-pc-cpld.yaml

diff --git a/Documentation/devicetree/bindings/bus/fsl,p1021rdb-pc-cpld.yaml b/Documentation/devicetree/bindings/bus/fsl,p1021rdb-pc-cpld.yaml
new file mode 100644
index 000000000000..822dfb93dcd8
--- /dev/null
+++ b/Documentation/devicetree/bindings/bus/fsl,p1021rdb-pc-cpld.yaml
@@ -0,0 +1,73 @@
+# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
+%YAML 1.2
+---
+$id: http://devicetree.org/schemas/bus/fsl,p1021rdb-pc-cpld.yaml#
+$schema: http://devicetree.org/meta-schemas/core.yaml#
+
+title: CPLD Bus Inteface for Freescale P1021RDB Combo Board CPLD Design
+
+maintainers:
+  - Pali Rohár <pali@kernel.org>
+
+description: |
+  A simple bus enabling access to peripherals on boards with use Freescale
+  P1021RDB Combo Board CPLD Design.
+
+  The "fsl,p1021rdb-pc-cpld" follows the "simple-bus" set of properties, as
+  specified in the Devicetree Specification. It is an extension of "simple-bus"
+  because some registers are CPLD specific and allows to identify if board has
+  wired CPLD according to Freescale P1021RDB Combo Board CPLD Design.
+
+select:
+  properties:
+    compatible:
+      contains:
+        const: fsl,p1021rdb-pc-cpld
+  required:
+    - compatible
+
+properties:
+  $nodename:
+    pattern: "^cpld(@[0-9a-f]+(,[0-9a-f]+)?)?$"
+
+  compatible:
+    items:
+      - const: fsl,p1021rdb-pc-cpld
+      - const: simple-bus
+
+  '#address-cells':
+    enum: [ 1, 2 ]
+
+  '#size-cells':
+    enum: [ 1, 2 ]
+
+  reg:
+    maxItems: 1
+
+  ranges: true
+
+required:
+  - compatible
+  - '#address-cells'
+  - '#size-cells'
+  - reg
+  - ranges
+
+additionalProperties:
+  type: object
+
+examples:
+  - |
+
+    localbus {
+        #address-cells = <2>;
+        #size-cells = <1>;
+
+        cpld@3,0 {
+            #address-cells = <1>;
+            #size-cells = <1>;
+            compatible = "fsl,p1021rdb-pc-cpld", "simple-bus";
+            reg = <0x3 0x0 0x20000>;
+            ranges = <0x0 0x3 0x0 0x20000>;
+        };
+    };
-- 
2.35.1


             reply	other threads:[~2022-07-05 17:55 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-05 17:54 Marek Behún [this message]
2022-07-05 19:18 ` [PATCH] dt-bindings: bus: add device tree bindings for fsl,p1021rdb-pc-cpld Rob Herring
2022-07-05 20:09 ` Rob Herring
2022-07-06 16:56   ` Marek Behún
2022-07-12 17:05     ` Rob Herring
2022-08-18 21:36       ` Pali Rohár
2022-08-31 11:46 ` Pali Rohár
2022-10-09 11:38   ` Pali Rohár
2022-11-01 22:27     ` Pali Rohár

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20220705175450.11886-1-kabel@kernel.org \
    --to=kabel@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=pali@kernel.org \
    --cc=robh+dt@kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).