From: Wolfram Sang <wsa+renesas@sang-engineering.com>
To: linux-renesas-soc@vger.kernel.org
Cc: Wolfram Sang <wsa+renesas@sang-engineering.com>,
Conor Dooley <conor+dt@kernel.org>,
devicetree@vger.kernel.org,
Geert Uytterhoeven <geert+renesas@glider.be>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
linux-clk@vger.kernel.org, Magnus Damm <magnus.damm@gmail.com>,
Michael Turquette <mturquette@baylibre.com>,
Rob Herring <robh@kernel.org>, Stephen Boyd <sboyd@kernel.org>
Subject: [RFC PATCH 0/4] ARM: dts: renesas: mtd-rom has no clock and power domain
Date: Tue, 30 Sep 2025 12:16:56 +0200 [thread overview]
Message-ID: <20250930101656.33435-6-wsa+renesas@sang-engineering.com> (raw)
Addressing this dtb_check...
arch/arm/boot/dts/renesas/r7s72100-genmai.dtb: flash@18000000 (mtd-rom): Unevaluated properties are not allowed ('clocks', 'power-domains' were unexpected)
from schema $id: http://devicetree.org/schemas/mtd/mtd-physmap.yaml#
... I came to the solution proposed here that the clocks we cannot
define will be marked as critical. We could also try to add 'clocks' and
'power-domains' to MTD physmap but I could understand some objection to
that. Opinions?
Wolfram Sang (4):
clk: renesas: mstp: mark 'spibsc' clocks as critical
ARM: dts: renesas: genmai: mtd-rom has no clock and power domain
ARM: dts: renesas: gr-peach: mtd-rom has no clock and power domain
ARM: dts: renesas: rskrza1: mtd-rom has no clock and power domain
arch/arm/boot/dts/renesas/r7s72100-genmai.dts | 3 ---
arch/arm/boot/dts/renesas/r7s72100-gr-peach.dts | 3 ---
arch/arm/boot/dts/renesas/r7s72100-rskrza1.dts | 2 --
drivers/clk/renesas/clk-mstp.c | 7 +++++--
4 files changed, 5 insertions(+), 10 deletions(-)
--
2.47.2
next reply other threads:[~2025-09-30 10:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-30 10:16 Wolfram Sang [this message]
2025-09-30 10:16 ` [RFC PATCH 2/4] ARM: dts: renesas: genmai: mtd-rom has no clock and power domain Wolfram Sang
2025-09-30 10:16 ` [RFC PATCH 3/4] ARM: dts: renesas: gr-peach: " Wolfram Sang
2025-09-30 10:17 ` [RFC PATCH 4/4] ARM: dts: renesas: rskrza1: " Wolfram Sang
2025-10-01 7:55 ` [RFC PATCH 0/4] ARM: dts: renesas: " Geert Uytterhoeven
2025-10-01 13:10 ` Wolfram Sang
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=20250930101656.33435-6-wsa+renesas@sang-engineering.com \
--to=wsa+renesas@sang-engineering.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=geert+renesas@glider.be \
--cc=krzk+dt@kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=mturquette@baylibre.com \
--cc=robh@kernel.org \
--cc=sboyd@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