From: "Niklas Söderlund" <niklas.soderlund+renesas@ragnatech.se>
To: Geert Uytterhoeven <geert+renesas@glider.be>,
Rob Herring <robh+dt@kernel.org>,
devicetree@vger.kernel.org
Cc: linux-renesas-soc@vger.kernel.org,
"Niklas Söderlund" <niklas.soderlund+renesas@ragnatech.se>
Subject: [PATCH 0/2] arm64: dts: renesas: r8a7796{1,5}: Add CMT nodes
Date: Wed, 9 Dec 2020 21:07:36 +0100 [thread overview]
Message-ID: <20201209200738.811173-1-niklas.soderlund+renesas@ragnatech.se> (raw)
Hi,
Add CMT nodes to Renesas R-Car M3-W+ and D3 that for unknown reasons are
missing these nodes. I only have access to the M3-W+ and I have tested
this series on this (and H3, M3-W, M3-) by enabling all CMT nodes in DT
and then using the kernel timer selftests located in
tools/testing/selftests/timers/
- clocksource-switch.c
- inconsistency-check.c
- nanosleep.c
And if the fix for a deadlock race when switching clocksource [1] also
is present the test pass on all SoCs mentioned above that I have access
to. I have no reason to believe it would not also work on D3.
1. [PATCH 0/2] timekeeping: Fix change_clocksource() for PM and sh_cmt
Niklas Söderlund (2):
arm64: dts: renesas: r8a77961: Add CMT nodes
arm64: dts: renesas: r8a77995: Add CMT nodes
arch/arm64/boot/dts/renesas/r8a77961.dtsi | 70 +++++++++++++++++++++++
arch/arm64/boot/dts/renesas/r8a77995.dtsi | 70 +++++++++++++++++++++++
2 files changed, 140 insertions(+)
--
2.29.2
next reply other threads:[~2020-12-09 20:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-09 20:07 Niklas Söderlund [this message]
2020-12-09 20:07 ` [PATCH 1/2] arm64: dts: renesas: r8a77961: Add CMT nodes Niklas Söderlund
2020-12-10 12:57 ` Geert Uytterhoeven
2020-12-09 20:07 ` [PATCH 2/2] arm64: dts: renesas: r8a77995: " Niklas Söderlund
2020-12-10 12:58 ` Geert Uytterhoeven
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=20201209200738.811173-1-niklas.soderlund+renesas@ragnatech.se \
--to=niklas.soderlund+renesas@ragnatech.se \
--cc=devicetree@vger.kernel.org \
--cc=geert+renesas@glider.be \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=robh+dt@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;
as well as URLs for NNTP newsgroup(s).