From: Daniel Palmer <daniel@0x0f.com>
To: krzk+dt@kernel.org, romain.perier@gmail.com, robh@kernel.org,
conor+dt@kernel.org, linux-arm-kernel@lists.infradead.org
Cc: devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
Daniel Palmer <daniel@0x0f.com>
Subject: [PATCH v2 0/8] Sigmastar DT warnings fixing
Date: Thu, 1 Jan 2026 12:42:58 +0900 [thread overview]
Message-ID: <20260101034306.1233091-1-daniel@0x0f.com> (raw)
v2 heads up: I didn't ignore Krzysztof's request to squash some commits,
I wasn't sure what to squash and I thought since I've fixed everything now
it was better to send a v2 sooner than later.
I've now fixed all of the warnings except one remaining one that seems to
need a change in dt-schema itself to cleanup:
serial@221000 (ns16550a): reg-shift: 3 is not one of [0, 1, 2]
from schema $id: http://devicetree.org/schemas/reg.yaml
The way registers are connected in these chips is weird. I think
they took their peripheral block from an 8051 microcontroller
and jammed it onto 32bit CPUs so all of the registers have
weird spacing and it really does need reg-shift == 3.
v1 blurb:
I saw a slide at LPC that had sigmastar in the "hall of shame"
for DT warnings. I finally got some time to look at this so
I have fixed the ones that are obvious and quick to fix.
I'll fix the rest but they might take a bit longer i.e. one
of them is about the register shift for the UART registers,
that'll need the binding to be updated I think?
FWIW this platform isn't dead and I have been rebasing all
of the out of tree stuff that make it useful (Audio support,
display, hardware video decoding etc) but its basically stuck
on rewriting the clock driver so that it is mainline-able.
Some other people have taken the limited support in mainline
and my out of tree stuff and made it run on old MStar MIPS
machines too..
change log:
v2:
- Fix the regulator names as suggested by Krzysztof
- Adjust the opp table name
- Add a commit to fix the cpupll binding and clean up the
warnings for that
- Add a commit to fix the memory node in the infinity2m
dtsi to fix up the warnings about that.
- Add a commit to switch the default led trigger on breadbee
from the undocumented activity to cpu to fix up the
warnings for the that.
Daniel Palmer (8):
dt-bindings: clk: mstar msc313 cpupll: Correct clock-cells value
arm: dts: mstar: breadbee: Correct regulator names
arm: dts: mstar: breadbee: Correct LED names
arm: dts: mstar: breadbee: Switch from "activity" led trigger to "cpu"
arm: dts: mstar: infinity: Correct opp table name
arm: dts: mstar: infinity2m: ssd202d: Correct memory node name
arm: dts: mstar: v7: Move the reboot node
arm: dts: mstar: v7: Add sizes and ranges to sram
.../bindings/clock/mstar,msc313-cpupll.yaml | 5 ++---
.../mstar-infinity-breadbee-common.dtsi | 12 ++++++------
arch/arm/boot/dts/sigmastar/mstar-infinity.dtsi | 2 +-
.../dts/sigmastar/mstar-infinity2m-ssd202d.dtsi | 2 +-
arch/arm/boot/dts/sigmastar/mstar-v7.dtsi | 17 ++++++++++-------
5 files changed, 20 insertions(+), 18 deletions(-)
--
2.51.0
next reply other threads:[~2026-01-01 3:43 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-01 3:42 Daniel Palmer [this message]
2026-01-01 3:42 ` [PATCH v2 1/8] dt-bindings: clk: mstar msc313 cpupll: Correct clock-cells value Daniel Palmer
2026-01-01 4:33 ` Rob Herring (Arm)
2026-01-02 10:15 ` Krzysztof Kozlowski
2026-01-01 3:43 ` [PATCH v2 2/8] arm: dts: mstar: breadbee: Correct regulator names Daniel Palmer
2026-01-01 3:43 ` [PATCH v2 3/8] arm: dts: mstar: breadbee: Correct LED names Daniel Palmer
2026-01-01 3:43 ` [PATCH v2 4/8] arm: dts: mstar: breadbee: Switch from "activity" led trigger to "cpu" Daniel Palmer
2026-01-01 3:43 ` [PATCH v2 5/8] arm: dts: mstar: infinity: Correct opp table name Daniel Palmer
2026-01-01 3:43 ` [PATCH v2 6/8] arm: dts: mstar: infinity2m: ssd202d: Correct memory node name Daniel Palmer
2026-01-01 3:43 ` [PATCH v2 7/8] arm: dts: mstar: v7: Move the reboot node Daniel Palmer
2026-01-01 3:43 ` [PATCH v2 8/8] arm: dts: mstar: v7: Add sizes and ranges to sram Daniel Palmer
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=20260101034306.1233091-1-daniel@0x0f.com \
--to=daniel@0x0f.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@kernel.org \
--cc=romain.perier@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).