From: Sergio Paracuellos <sergio.paracuellos@gmail.com>
To: devicetree@vger.kernel.org
Cc: robh+dt@kernel.org, krzysztof.kozlowski+dt@linaro.org,
hauke@hauke-m.de, zajec5@gmail.com, tsbogend@alpha.franken.de,
linux-mips@vger.kernel.org, arinc.unal@arinc9.com
Subject: [PATCH v3 0/3] dt-bindings: mips: add CPU bindings for MIPS architecture
Date: Thu, 29 Sep 2022 09:20:01 +0200 [thread overview]
Message-ID: <20220929072004.874795-1-sergio.paracuellos@gmail.com> (raw)
Hi all,
This series tries to make the correct thing to represent in schema
all the current documentation related with MIPS CPUs.
Current 'arch/mips/boot/dts' folder dts files are a bit messy
for cpu nodes, so I set additionalProperties to true and only
make required for 'compatible' in mips/cpus.yaml schema.
Broadcom cpus node is a bit special and need to use the property
'mips-hpt-frequency'. Since 'compatible' string is not in the
'cpus' parent node itself, we need a way to filter this to be valid
only for Broadcom SoCs. To make this possible I have introduced two
new schemas:
- One to describe the Broadcom SoCs and its compatibles.
- One to describe the BMIPS CPU's referring inside to 'brcm/soc.yaml'
and 'mips/cpus.yaml' schemas.
Another thing to notice is that the root-node schema requires 'model'
as property and there is no model at all in any real DTS file for any
cpus node in 'arch/mips/boot/dts'. I have just added it in the schema
sample to avoid the following check fail:
/: 'model' is a required property
From schema: /home/sergio/.local/lib/python3.8/site-packages/dtschema/schemas/root-node.yaml
Don't really know if this is a way to go.
Thanks in advance for your time and comments.
Best regards,
Sergio Paracuellos
Changes in v3:
- cpus.yaml:
* address Krzysztof comment in v2:
* add Thomas as maintainer since this is architecture binding.
* s/cpu/CPU
* compatible goes first
* Add compatible 'mips,mips4Kc' as per Thomas request.
- Introduce two new schemas for Broadcom BMIPS:
* soc.yaml: describing the BRCM SoC's
* brcm,bmips-cpus.yaml: describing the cpu nodes for this platform.
Previous series:
v1: https://lore.kernel.org/all/CAMhs-H-eUTOHjAXAbywOXQJgc_j5Ex-1sB7eBZU_bWt1fpNVzA@mail.gmail.com/T/
v2: https://lore.kernel.org/all/20220918112245.GA5555@alpha.franken.de/T/
Thanks,
Sergio Paracuellos
Sergio Paracuellos (3):
dt-bindings: mips: add CPU bindings for MIPS architecture
dt-bindings: mips: brcm: convert Broadcom SoCs to schema
dt-bindings: mips: brcm: convert CPU bindings for BMIPS architecture
.../bindings/mips/brcm/brcm,bmips-cpus.yaml | 102 ++++++++++++++++++
.../bindings/mips/brcm/brcm,bmips.txt | 8 --
.../devicetree/bindings/mips/brcm/soc.yaml | 97 +++++++++++++++++
.../devicetree/bindings/mips/cpus.yaml | 66 ++++++++++++
4 files changed, 265 insertions(+), 8 deletions(-)
create mode 100644 Documentation/devicetree/bindings/mips/brcm/brcm,bmips-cpus.yaml
delete mode 100644 Documentation/devicetree/bindings/mips/brcm/brcm,bmips.txt
create mode 100644 Documentation/devicetree/bindings/mips/brcm/soc.yaml
create mode 100644 Documentation/devicetree/bindings/mips/cpus.yaml
--
2.25.1
next reply other threads:[~2022-09-29 7:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-29 7:20 Sergio Paracuellos [this message]
2022-09-29 7:20 ` [PATCH v3 1/3] dt-bindings: mips: add CPU bindings for MIPS architecture Sergio Paracuellos
2022-09-30 17:16 ` Rob Herring
2022-10-01 3:39 ` Sergio Paracuellos
2022-09-29 7:20 ` [PATCH v3 2/3] dt-bindings: mips: brcm: convert Broadcom SoCs to schema Sergio Paracuellos
2022-09-29 7:20 ` [PATCH v3 3/3] dt-bindings: mips: brcm: convert CPU bindings for BMIPS architecture Sergio Paracuellos
2022-09-30 17:43 ` Rob Herring
2022-10-01 3:44 ` 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=20220929072004.874795-1-sergio.paracuellos@gmail.com \
--to=sergio.paracuellos@gmail.com \
--cc=arinc.unal@arinc9.com \
--cc=devicetree@vger.kernel.org \
--cc=hauke@hauke-m.de \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-mips@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=tsbogend@alpha.franken.de \
--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