From: Rob Herring <robh@kernel.org>
To: Sergio Paracuellos <sergio.paracuellos@gmail.com>
Cc: devicetree@vger.kernel.org, tsbogend@alpha.franken.de,
krzk+dt@kernel.org, arinc.unal@arinc9.com
Subject: Re: [PATCH] dt-bindings: mips: add CPU bindings for MIPS architecture
Date: Fri, 16 Sep 2022 14:34:47 -0500 [thread overview]
Message-ID: <20220916193447.GA1134515-robh@kernel.org> (raw)
In-Reply-To: <20220915055514.463241-1-sergio.paracuellos@gmail.com>
On Thu, Sep 15, 2022 at 07:55:14AM +0200, Sergio Paracuellos wrote:
> Add the yaml binding for available CPUs in MIPS architecture.
>
> Signed-off-by: Sergio Paracuellos <sergio.paracuellos@gmail.com>
> ---
> .../devicetree/bindings/mips/cpus.yaml | 66 +++++++++++++++++++
> 1 file changed, 66 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/mips/cpus.yaml
>
> diff --git a/Documentation/devicetree/bindings/mips/cpus.yaml b/Documentation/devicetree/bindings/mips/cpus.yaml
> new file mode 100644
> index 000000000000..4277adc65ed6
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/mips/cpus.yaml
> @@ -0,0 +1,66 @@
> +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/mips/cpus.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: MIPS CPUs bindings
> +
> +maintainers:
> + - Sergio Paracuellos <sergio.paracuellos@gmail.com>
> +
> +description: |+
> + The device tree allows to describe the layout of CPUs in a system through
> + the "cpus" node, which in turn contains a number of subnodes (ie "cpu")
> + defining properties for every cpu.
> +
> +properties:
> + reg:
> + maxItems: 1
> +
> + compatible:
> + enum:
> + - brcm,bmips3300
> + - brcm,bmips4350
> + - brcm,bmips4380
> + - brcm,bmips5000
> + - brcm,bmips5200
You need to remove bindings/mips/brcm/brcm,bmips.txt. But it also
defines a property which needs to be added.
I didn't check the rest for existing documentation...
> + - ingenic,xburst-mxu1.0
> + - ingenic,xburst-fpu1.0-mxu1.1
> + - ingenic,xburst-fpu2.0-mxu2.0
> + - loongson,gs264
> + - mips,mips1004Kc
> + - mips,m14Kc
> + - mips,mips24KEc
> + - mips,mips4KEc
> + - mips,mips74Kc
> + - mips,mips24Kc
> + - mti,mips24KEc
> + - mti,mips14KEc
> + - mti,mips14Kc
> + - mti,interaptiv
> +
> +required:
> + - compatible
> +
> +additionalProperties: true
> +
> +examples:
> + - |
> + cpus {
> + #size-cells = <0>;
> + #address-cells = <1>;
> +
> + cpu@0 {
> + device_type = "cpu";
> + compatible = "mips,mips1004Kc";
> + reg = <0>;
> + };
> +
> + cpu@1 {
> + device_type = "cpu";
> + compatible = "mips,mips1004Kc";
> + reg = <1>;
> + };
> + };
> +
> --
> 2.25.1
>
>
next prev parent reply other threads:[~2022-09-16 19:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-15 5:55 [PATCH] dt-bindings: mips: add CPU bindings for MIPS architecture Sergio Paracuellos
2022-09-16 19:34 ` Rob Herring [this message]
2022-09-17 4:15 ` 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=20220916193447.GA1134515-robh@kernel.org \
--to=robh@kernel.org \
--cc=arinc.unal@arinc9.com \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=sergio.paracuellos@gmail.com \
--cc=tsbogend@alpha.franken.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.