From: William Zhang <william.zhang@broadcom.com>
To: Linux ARM List <linux-arm-kernel@lists.infradead.org>,
Broadcom Kernel List <bcm-kernel-feedback-list@broadcom.com>
Cc: kursad.oney@broadcom.com, florian.fainelli@broadcom.com,
joel.peshkin@broadcom.com, tomer.yacoby@broadcom.com,
samyon.furman@broadcom.com, philippe.reynes@softathome.com,
anand.gore@broadcom.com, dan.beygelman@broadcom.com,
William Zhang <william.zhang@broadcom.com>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Rob Herring <robh+dt@kernel.org>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH 1/5] dt-bindings: arm64: add BCM63158 soc to binding document
Date: Sat, 14 May 2022 16:27:56 -0700 [thread overview]
Message-ID: <20220514232800.24653-2-william.zhang@broadcom.com> (raw)
In-Reply-To: <20220514232800.24653-1-william.zhang@broadcom.com>
[-- Attachment #1: Type: text/plain, Size: 867 bytes --]
Add BCM63158 SOC device tree description to bcmbca binding document.
Signed-off-by: William Zhang <william.zhang@broadcom.com>
---
Documentation/devicetree/bindings/arm/bcm/brcm,bcmbca.yaml | 7 +++++++
1 file changed, 7 insertions(+)
diff --git a/Documentation/devicetree/bindings/arm/bcm/brcm,bcmbca.yaml b/Documentation/devicetree/bindings/arm/bcm/brcm,bcmbca.yaml
index 5fb455840417..4e3a1a5391f6 100644
--- a/Documentation/devicetree/bindings/arm/bcm/brcm,bcmbca.yaml
+++ b/Documentation/devicetree/bindings/arm/bcm/brcm,bcmbca.yaml
@@ -28,6 +28,13 @@ properties:
- const: brcm,bcm47622
- const: brcm,bcmbca
+ - description: BCM63158 based boards
+ items:
+ - enum:
+ - brcm,bcm963158
+ - const: brcm,bcm63158
+ - const: brcm,bcmbca
+
additionalProperties: true
...
--
2.17.1
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4212 bytes --]
next prev parent reply other threads:[~2022-05-14 23:28 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-14 23:27 [PATCH 0/5] arm64: bcmbca: add bcm63158 soc support William Zhang
2022-05-14 23:27 ` William Zhang [this message]
2022-05-16 16:06 ` [PATCH 1/5] dt-bindings: arm64: add BCM63158 soc to binding document Rob Herring
2022-05-16 17:51 ` William Zhang
2022-05-17 14:23 ` Rob Herring
2022-05-18 20:08 ` Florian Fainelli
2022-05-14 23:27 ` [PATCH 2/5] arm64: bcmbca: add arch bcmbca machine entry William Zhang
2022-05-18 20:05 ` Florian Fainelli
2022-05-14 23:27 ` [PATCH 3/5] arm64: dts: add dts files for bcmbca soc 63158 William Zhang
2022-05-18 20:05 ` Florian Fainelli
2022-05-14 23:27 ` [PATCH 4/5] MAINTAINERS: add bcm63158 to bcmbca arch entry William Zhang
2022-05-18 20:08 ` Florian Fainelli
2022-05-14 23:28 ` [PATCH 5/5] arm64: defconfig: enable bcmbca soc support William Zhang
2022-05-18 20:07 ` Florian Fainelli
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=20220514232800.24653-2-william.zhang@broadcom.com \
--to=william.zhang@broadcom.com \
--cc=anand.gore@broadcom.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=dan.beygelman@broadcom.com \
--cc=devicetree@vger.kernel.org \
--cc=florian.fainelli@broadcom.com \
--cc=joel.peshkin@broadcom.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=kursad.oney@broadcom.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=philippe.reynes@softathome.com \
--cc=robh+dt@kernel.org \
--cc=samyon.furman@broadcom.com \
--cc=tomer.yacoby@broadcom.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;
as well as URLs for NNTP newsgroup(s).