From: "Rafał Miłecki" <zajec5@gmail.com>
To: Sergio Paracuellos <sergio.paracuellos@gmail.com>,
devicetree@vger.kernel.org
Cc: robh+dt@kernel.org, krzysztof.kozlowski+dt@linaro.org,
hauke@hauke-m.de, tsbogend@alpha.franken.de,
zhouyanjie@wanyeetech.com, linux-mips@vger.kernel.org,
arinc.unal@arinc9.com, f.fainelli@gmail.com,
Rob Herring <robh@kernel.org>
Subject: Re: [PATCH v6 2/2] dt-bindings: mips: brcm: add Broadcom SoCs bindings
Date: Tue, 4 Oct 2022 07:14:24 +0200 [thread overview]
Message-ID: <d73089a7-f7ad-2f45-8307-3c4ec20cbb79@gmail.com> (raw)
In-Reply-To: <20221004050924.986211-3-sergio.paracuellos@gmail.com>
On 4.10.2022 07:09, Sergio Paracuellos wrote:
> Add the yaml binding for MIPS Broadcom cable/DSL/settop platforms.
>
> Acked-by: Florian Fainelli <f.fainelli@gmail.com>
> Reviewed-by: Rob Herring <robh@kernel.org>
> Signed-off-by: Sergio Paracuellos <sergio.paracuellos@gmail.com>
> ---
> .../devicetree/bindings/mips/brcm/soc.yaml | 98 +++++++++++++++++++
> 1 file changed, 98 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..39b4609cd1cc
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/mips/brcm/soc.yaml
> @@ -0,0 +1,98 @@
> +# 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
> +
> +maintainers:
> + - Hauke Mehrtens <hauke@hauke-m.de>
> + - Rafał Miłecki <zajec5@gmail.com>
> + - Florian Fainelli <f.fainelli@gmail.com>
The only MIPS SoCs I really worked on were BCM47xx. I didn't do any real
work on cable/DSL/STB.
I don't really feel up to like maintaining those SoCs.
> +
> +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:
> + enum:
> + - brcm,bcm3368
> + - brcm,bcm3384
> + - brcm,bcm33843
> + - brcm,bcm3384-viper
> + - brcm,bcm33843-viper
> + - brcm,bcm6328
> + - brcm,bcm6358
> + - brcm,bcm6362
> + - brcm,bcm6368
> + - brcm,bcm63168
> + - brcm,bcm63268
> + - brcm,bcm7125
> + - brcm,bcm7346
> + - brcm,bcm7358
> + - brcm,bcm7360
> + - brcm,bcm7362
> + - brcm,bcm7420
> + - brcm,bcm7425
> +
> + cpus:
> + type: object
> + additionalProperties: false
> + properties:
> + '#address-cells':
> + const: 1
> +
> + '#size-cells':
> + const: 0
> +
> + mips-hpt-frequency:
> + description: MIPS counter high precision timer frequency.
> + This is common to all CPUs in the system so it lives
> + under the "cpus" node.
> + $ref: /schemas/types.yaml#/definitions/uint32
> +
> + patternProperties:
> + "^cpu@[0-9]$":
> + type: object
> + $ref: /schemas/mips/cpus.yaml#
> + unevaluatedProperties: false
> +
> + required:
> + - mips-hpt-frequency
> +
> +additionalProperties: true
> +
> +examples:
> + - |
> + / {
> + compatible = "brcm,bcm3368";
> + #address-cells = <1>;
> + #size-cells = <1>;
> + model = "Broadcom 3368";
> +
> + cpus {
> + #address-cells = <1>;
> + #size-cells = <0>;
> +
> + mips-hpt-frequency = <150000000>;
> +
> + cpu@0 {
> + compatible = "brcm,bmips4350";
> + device_type = "cpu";
> + reg = <0>;
> + };
> +
> + cpu@1 {
> + compatible = "brcm,bmips4350";
> + device_type = "cpu";
> + reg = <1>;
> + };
> + };
> + };
> +...
next prev parent reply other threads:[~2022-10-04 5:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-04 5:09 [PATCH v6 0/2] dt-bindings: mips: add CPU bindings for MIPS architecture Sergio Paracuellos
2022-10-04 5:09 ` [PATCH v6 1/2] " Sergio Paracuellos
2022-10-04 5:09 ` [PATCH v6 2/2] dt-bindings: mips: brcm: add Broadcom SoCs bindings Sergio Paracuellos
2022-10-04 5:14 ` Rafał Miłecki [this message]
2022-10-04 5:20 ` Sergio Paracuellos
2022-10-05 20:32 ` Hauke Mehrtens
2022-10-06 4:25 ` 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=d73089a7-f7ad-2f45-8307-3c4ec20cbb79@gmail.com \
--to=zajec5@gmail.com \
--cc=arinc.unal@arinc9.com \
--cc=devicetree@vger.kernel.org \
--cc=f.fainelli@gmail.com \
--cc=hauke@hauke-m.de \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-mips@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=robh@kernel.org \
--cc=sergio.paracuellos@gmail.com \
--cc=tsbogend@alpha.franken.de \
--cc=zhouyanjie@wanyeetech.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).