linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Anand Gore <anand.gore@broadcom.com>
To: Linux ARM List <linux-arm-kernel@lists.infradead.org>
Cc: kursad.oney@broadcom.com, tomer.yacoby@broadcom.com,
	William Zhang <william.zhang@broadcom.com>,
	florian.fainelli@broadcom.com, joel.peshkin@broadcom.com,
	samyon.furman@broadcom.com, dan.beygelman@broadcom.com,
	Anand Gore <anand.gore@broadcom.com>,
	Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
	Broadcom internal kernel review list 
	<bcm-kernel-feedback-list@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 v3 2/3] dt-bindings: arm64: add BCM6858 soc
Date: Wed,  1 Jun 2022 13:19:57 -0700	[thread overview]
Message-ID: <20220601131944.v3.2.I2bc1418dd24a902e941c7073bbadab00568b4f5d@changeid> (raw)
In-Reply-To: <20220601201958.3072173-1-anand.gore@broadcom.com>

[-- Attachment #1: Type: text/plain, Size: 1014 bytes --]

Add BCM6858 SOC device tree description to bcmbca binding document.

Signed-off-by: Anand Gore <anand.gore@broadcom.com>
Reviewed-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>

---

(no changes since v2)

Changes in v2:
- Remove extra empty lines
- Simplify subject line

 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 24357cf09888..97e5b1c4619e 100644
--- a/Documentation/devicetree/bindings/arm/bcm/brcm,bcmbca.yaml
+++ b/Documentation/devicetree/bindings/arm/bcm/brcm,bcmbca.yaml
@@ -35,6 +35,13 @@ properties:
           - const: brcm,bcm63178
           - const: brcm,bcmbca
 
+      - description: BCM6858 based boards
+        items:
+          - enum:
+              - brcm,bcm96858
+          - const: brcm,bcm6858
+          - const: brcm,bcmbca
+
 additionalProperties: true
 
 ...
-- 
2.25.1


[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4203 bytes --]

  parent reply	other threads:[~2022-06-01 20:46 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-01 20:19 [PATCH v3 0/3] arm64: bcmbca: add bcm6858 soc support Anand Gore
2022-06-01 20:19 ` [PATCH v3 1/3] ARM64: dts: add dts files for bcmbca SoC bcm6858 Anand Gore
2022-06-01 20:19 ` Anand Gore [this message]
2022-06-08  8:38   ` [PATCH v3 2/3] dt-bindings: arm64: add BCM6858 soc Florian Fainelli
2022-06-01 20:19 ` [PATCH v3 3/3] MAINTAINERS: add bcm6858 to bcmbca arch entry Anand Gore
2022-06-08  8:59 ` [PATCH v3 0/3] arm64: bcmbca: add bcm6858 soc support 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=20220601131944.v3.2.I2bc1418dd24a902e941c7073bbadab00568b4f5d@changeid \
    --to=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=krzysztof.kozlowski@linaro.org \
    --cc=kursad.oney@broadcom.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robh+dt@kernel.org \
    --cc=samyon.furman@broadcom.com \
    --cc=tomer.yacoby@broadcom.com \
    --cc=william.zhang@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).