From: Gerard Marull-Paretas <gerard@teslabs.com>
To: Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Lorenzo Pieralisi <lpieralisi@kernel.org>
Cc: devicetree@vger.kernel.org
Subject: [PATCH 2/2] dt-bindings: arm: cpus: Add Arm China STAR-MC1
Date: Sun, 22 Nov 2026 10:33:59 +0100 [thread overview]
Message-ID: <20261122093359.69352-3-gerard@teslabs.com> (raw)
In-Reply-To: <20261122093359.69352-1-gerard@teslabs.com>
Document the compatible of the Arm China STAR-MC1 core, an Armv8-M
Mainline core compatible with the Cortex-M33.
These schemas are now used by PebbleOS, which runs on the SiFli SF32LB52
and SF32LB57 SoCs, built around STAR-MC1 cores.
Signed-off-by: Gerard Marull-Paretas <gerard@teslabs.com>
---
Notes:
Checked with dtschema 2026.9: the steps of dt_binding_check run by hand (host make too old), yamllint and dt-check-style --mode=strict.
Documentation/devicetree/bindings/arm/cpus.yaml | 1 +
1 file changed, 1 insertion(+)
diff --git a/Documentation/devicetree/bindings/arm/cpus.yaml b/Documentation/devicetree/bindings/arm/cpus.yaml
index da12be7f5119..75e79aa49ab7 100644
--- a/Documentation/devicetree/bindings/arm/cpus.yaml
+++ b/Documentation/devicetree/bindings/arm/cpus.yaml
@@ -190,6 +190,7 @@ properties:
- arm,neoverse-v3
- arm,neoverse-v3ae
- arm,rainier
+ - armchina,star-mc1
- brcm,brahma-b15
- brcm,brahma-b53
- brcm,vulcan
--
2.45.2
prev parent reply other threads:[~2026-11-22 9:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-22 9:33 [PATCH 0/2] dt-bindings: arm: cpus: Add Cortex-M33 and STAR-MC1 Gerard Marull-Paretas
2026-11-22 9:33 ` [PATCH 1/2] dt-bindings: arm: cpus: Add Cortex-M33 Gerard Marull-Paretas
2026-11-22 9:33 ` Gerard Marull-Paretas [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=20261122093359.69352-3-gerard@teslabs.com \
--to=gerard@teslabs.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=lpieralisi@kernel.org \
--cc=robh@kernel.org \
/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