From: Geert Uytterhoeven <geert@linux-m68k.org>
To: "Niklas Söderlund" <niklas.soderlund+renesas@ragnatech.se>
Cc: Rob Herring <robh+dt@kernel.org>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@vger.kernel.org>,
Linux-Renesas <linux-renesas-soc@vger.kernel.org>
Subject: Re: [PATCH v2 0/6] [PATCH 0/6] arm64: dts: renesas: Add TMU nodes
Date: Fri, 11 Dec 2020 13:43:34 +0100 [thread overview]
Message-ID: <CAMuHMdWPFDLKh_10_D+yfPAoDgLTgR5nKCxy2Qnh23UDbSFKbg@mail.gmail.com> (raw)
In-Reply-To: <20201210152705.1535156-1-niklas.soderlund+renesas@ragnatech.se>
Hi Niklas,
On Thu, Dec 10, 2020 at 4:27 PM Niklas Söderlund
<niklas.soderlund+renesas@ragnatech.se> wrote:
> Add TMU nodes to Renesas R-Car H3, M3-W, M3-W+, D3, M3-N and E3. I have
> tested this on all but D3 and E3 SoCs which I do not have access to. I
> tested by enabling all TMU nodes in DT and then used the kernel timer
> selftests located in tools/testing/selftests/timers/
>
> - clocksource-switch.c
> - inconsistency-check.c
> - nanosleep.c
>
> The test passes for all SoCs I have access to and I no reason to believe
> it would not also work on D3 and E3.
>
> Niklas Söderlund (6):
> arm64: dts: renesas: r8a77951: Add TMU nodes
> arm64: dts: renesas: r8a77960: Add TMU nodes
> arm64: dts: renesas: r8a77961: Add TMU nodes
> arm64: dts: renesas: r8a77965: Add TMU nodes
> arm64: dts: renesas: r8a77990: Add TMU nodes
> arm64: dts: renesas: r8a77995: Add TMU nodes
>
> arch/arm64/boot/dts/renesas/r8a77951.dtsi | 65 +++++++++++++++++++++++
> arch/arm64/boot/dts/renesas/r8a77960.dtsi | 65 +++++++++++++++++++++++
> arch/arm64/boot/dts/renesas/r8a77961.dtsi | 65 +++++++++++++++++++++++
> arch/arm64/boot/dts/renesas/r8a77965.dtsi | 65 +++++++++++++++++++++++
> arch/arm64/boot/dts/renesas/r8a77990.dtsi | 65 +++++++++++++++++++++++
> arch/arm64/boot/dts/renesas/r8a77995.dtsi | 65 +++++++++++++++++++++++
> 6 files changed, 390 insertions(+)
Would you mind if I would squash these into a single commit while applying?
Thanks!
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
next prev parent reply other threads:[~2020-12-11 12:45 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-10 15:26 [PATCH v2 0/6] [PATCH 0/6] arm64: dts: renesas: Add TMU nodes Niklas Söderlund
2020-12-10 15:27 ` [PATCH v2 1/6] arm64: dts: renesas: r8a77951: " Niklas Söderlund
2020-12-11 12:39 ` Geert Uytterhoeven
2020-12-10 15:27 ` [PATCH v2 2/6] arm64: dts: renesas: r8a77960: " Niklas Söderlund
2020-12-11 12:39 ` Geert Uytterhoeven
2020-12-10 15:27 ` [PATCH v2 3/6] arm64: dts: renesas: r8a77961: " Niklas Söderlund
2020-12-11 12:40 ` Geert Uytterhoeven
2020-12-10 15:27 ` [PATCH v2 4/6] arm64: dts: renesas: r8a77965: " Niklas Söderlund
2020-12-11 12:41 ` Geert Uytterhoeven
2020-12-10 15:27 ` [PATCH v2 5/6] arm64: dts: renesas: r8a77990: " Niklas Söderlund
2020-12-11 12:41 ` Geert Uytterhoeven
2020-12-10 15:27 ` [PATCH v2 6/6] arm64: dts: renesas: r8a77995: " Niklas Söderlund
2020-12-11 12:42 ` Geert Uytterhoeven
2020-12-11 12:43 ` Geert Uytterhoeven [this message]
2020-12-15 8:55 ` [PATCH v2 0/6] [PATCH 0/6] arm64: dts: renesas: " Niklas Söderlund
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=CAMuHMdWPFDLKh_10_D+yfPAoDgLTgR5nKCxy2Qnh23UDbSFKbg@mail.gmail.com \
--to=geert@linux-m68k.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=niklas.soderlund+renesas@ragnatech.se \
--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).