From: Krzysztof Kozlowski <krzysztof.kozlowski@canonical.com>
To: "Rafał Miłecki" <zajec5@gmail.com>,
"Florian Fainelli" <f.fainelli@gmail.com>,
"Rob Herring" <robh+dt@kernel.org>
Cc: linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
bcm-kernel-feedback-list@broadcom.com,
"Rafał Miłecki" <rafal@milecki.pl>
Subject: Re: [PATCH] dt-bindings: arm: bcm: document BCM4912 bindings
Date: Wed, 16 Mar 2022 17:15:05 +0100 [thread overview]
Message-ID: <a158beb0-9eee-24ba-3ffe-1a02011c4be0@canonical.com> (raw)
In-Reply-To: <20220315184403.17217-1-zajec5@gmail.com>
On 15/03/2022 19:44, Rafał Miłecki wrote:
> From: Rafał Miłecki <rafal@milecki.pl>
>
> BCM4912 is a successor family to the BCM4908. It includes BCM4912,
> BCM4915 and BCM49418. It's mostly used in home routers.
>
> Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
> ---
> .../bindings/arm/bcm/brcm,bcm4912.yaml | 38 +++++++++++++++++++
> 1 file changed, 38 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/arm/bcm/brcm,bcm4912.yaml
>
> diff --git a/Documentation/devicetree/bindings/arm/bcm/brcm,bcm4912.yaml b/Documentation/devicetree/bindings/arm/bcm/brcm,bcm4912.yaml
> new file mode 100644
> index 000000000000..438a6f20ca93
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/arm/bcm/brcm,bcm4912.yaml
> @@ -0,0 +1,38 @@
> +# SPDX-License-Identifier: GPL-2.0 OR BSD-2-Clause
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/arm/bcm/brcm,bcm4912.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: Broadcom BCM4912 device tree bindings
> +
> +description:
> + Broadcom BCM4912 / BCM4915 / BCM49418 Wi-Fi/network SoCs with Brahma CPUs.
> +
> +maintainers:
> + - Rafał Miłecki <rafal@milecki.pl>
> +
> +properties:
> + $nodename:
> + const: '/'
> + compatible:
> + oneOf:
> + - description: BCM4912 based boards
> + items:
> + - enum:
> + - asus,gt-ax6000
> + - const: brcm,bcm4912
> +
> + - description: BCM4915 based boards
> + items:
> + - const: brcm,bcm4915
> + - const: brcm,bcm4912
> +
> + - description: BCM49418 based boards
> + items:
> + - const: brcm,bcm49418
> + - const: brcm,bcm4908
The last two entries do not look correct currently. You don't have any
boards. Maybe just skip them? Unless you plan to use these compatibles
in DTSI?
Best regards,
Krzysztof
prev parent reply other threads:[~2022-03-16 16:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-15 18:44 [PATCH] dt-bindings: arm: bcm: document BCM4912 bindings Rafał Miłecki
2022-03-16 16:15 ` Krzysztof Kozlowski [this message]
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=a158beb0-9eee-24ba-3ffe-1a02011c4be0@canonical.com \
--to=krzysztof.kozlowski@canonical.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=devicetree@vger.kernel.org \
--cc=f.fainelli@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=rafal@milecki.pl \
--cc=robh+dt@kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).