From: Sergio Paracuellos <sergio.paracuellos@gmail.com>
To: devicetree@vger.kernel.org
Cc: robh+dt@kernel.org, krzysztof.kozlowski+dt@linaro.org,
hauke@hauke-m.de, zajec5@gmail.com, tsbogend@alpha.franken.de,
linux-mips@vger.kernel.org, arinc.unal@arinc9.com
Subject: [PATCH v3 2/3] dt-bindings: mips: brcm: convert Broadcom SoCs to schema
Date: Thu, 29 Sep 2022 09:20:03 +0200 [thread overview]
Message-ID: <20220929072004.874795-3-sergio.paracuellos@gmail.com> (raw)
In-Reply-To: <20220929072004.874795-1-sergio.paracuellos@gmail.com>
Convert Broadcom cable/DSL/settop platforms to YAML schema.
Signed-off-by: Sergio Paracuellos <sergio.paracuellos@gmail.com>
---
.../devicetree/bindings/mips/brcm/soc.yaml | 97 +++++++++++++++++++
1 file changed, 97 insertions(+)
create mode 100644 Documentation/devicetree/bindings/mips/brcm/soc.yaml
diff --git a/Documentation/devicetree/bindings/mips/brcm/soc.yaml b/Documentation/devicetree/bindings/mips/brcm/soc.yaml
new file mode 100644
index 000000000000..37353709b5a7
--- /dev/null
+++ b/Documentation/devicetree/bindings/mips/brcm/soc.yaml
@@ -0,0 +1,97 @@
+# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
+%YAML 1.2
+---
+$id: http://devicetree.org/schemas/mips/brcm/soc.yaml#
+$schema: http://devicetree.org/meta-schemas/core.yaml#
+
+title: Broadcom cable/DSL/settop platforms Device Tree Bindings
+
+maintainers:
+ - Hauke Mehrtens <hauke@hauke-m.de>
+ - Rafał Miłecki <zajec5@gmail.com>
+
+description: |
+ Boards Broadcom cable/DSL/settop SoC shall have the following properties.
+ The experimental -viper variants are for running Linux on the 3384's
+ BMIPS4355 cable modem CPU instead of the BMIPS5000 application processor.
+
+properties:
+ $nodename:
+ const: '/'
+ compatible:
+ oneOf:
+ - description: Boards with Broadcom bcm3368 SoC
+ items:
+ - const: brcm,bcm3368
+
+ - description: Boards with Broadcom bcm3384 SoC
+ items:
+ - const: brcm,bcm3384
+
+ - description: Boards with Broadcom bcm33843 SoC
+ items:
+ - const: brcm,bcm33843
+
+ - description: Boards with Broadcom bcm3384-viper SoC
+ items:
+ - const: brcm,bcm3384-viper
+
+ - description: Boards with Broadcom bcm33843-viper SoC
+ items:
+ - const: brcm,bcm33843-viper
+
+ - description: Boards with Broadcom bcm6328 SoC
+ items:
+ - const: brcm,bcm6328
+
+ - description: Boards with Broadcom bcm6358 SoC
+ items:
+ - const: brcm,bcm6358
+
+ - description: Boards with Broadcom bcm6362 SoC
+ items:
+ - const: brcm,bcm6362
+
+ - description: Boards with Broadcom bcm6368 SoC
+ items:
+ - const: brcm,bcm6368
+
+ - description: Boards with Broadcom bcm63168 SoC
+ items:
+ - const: brcm,bcm63168
+
+ - description: Boards with Broadcom bcm63268 SoC
+ items:
+ - const: brcm,bcm63268
+
+ - description: Boards with Broadcom bcm7125 SoC
+ items:
+ - const: brcm,bcm7125
+
+ - description: Boards with Broadcom bcm7346 SoC
+ items:
+ - const: brcm,bcm7346
+
+ - description: Boards with Broadcom bcm7358 SoC
+ items:
+ - const: brcm,bcm7358
+
+ - description: Boards with Broadcom bcm7360 SoC
+ items:
+ - const: brcm,bcm7360
+
+ - description: Boards with Broadcom bcm7362 SoC
+ items:
+ - const: brcm,bcm7362
+
+ - description: Boards with Broadcom bcm7420 SoC
+ items:
+ - const: brcm,bcm7420
+
+ - description: Boards with Broadcom bcm7425 SoC
+ items:
+ - const: brcm,bcm7425
+
+additionalProperties: true
+
+...
--
2.25.1
next prev parent reply other threads:[~2022-09-29 7:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-29 7:20 [PATCH v3 0/3] dt-bindings: mips: add CPU bindings for MIPS architecture Sergio Paracuellos
2022-09-29 7:20 ` [PATCH v3 1/3] " Sergio Paracuellos
2022-09-30 17:16 ` Rob Herring
2022-10-01 3:39 ` Sergio Paracuellos
2022-09-29 7:20 ` Sergio Paracuellos [this message]
2022-09-29 7:20 ` [PATCH v3 3/3] dt-bindings: mips: brcm: convert CPU bindings for BMIPS architecture Sergio Paracuellos
2022-09-30 17:43 ` Rob Herring
2022-10-01 3:44 ` Sergio Paracuellos
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=20220929072004.874795-3-sergio.paracuellos@gmail.com \
--to=sergio.paracuellos@gmail.com \
--cc=arinc.unal@arinc9.com \
--cc=devicetree@vger.kernel.org \
--cc=hauke@hauke-m.de \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-mips@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=tsbogend@alpha.franken.de \
--cc=zajec5@gmail.com \
/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