From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Biju Das <biju.das@bp.renesas.com>
Cc: Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Simon Horman <horms@verge.net.au>,
Magnus Damm <magnus.damm@gmail.com>,
Linux-Renesas <linux-renesas-soc@vger.kernel.org>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@vger.kernel.org>,
Geert Uytterhoeven <geert+renesas@glider.be>,
Chris Paterson <Chris.Paterson2@renesas.com>,
Daniel Lezcano <daniel.lezcano@linaro.org>,
Thomas Gleixner <tglx@linutronix.de>,
John Stultz <john.stultz@linaro.org>,
Fabrizio Castro <fabrizio.castro@bp.renesas.com>,
Samuel Holland <samuel@sholland.org>
Subject: Re: [PATCH] arm64: dts: renesas: r8a7796: Add CMT device nodes
Date: Thu, 24 Jan 2019 11:15:56 +0100 [thread overview]
Message-ID: <CAMuHMdW-qt+3iNit1wVxN2JyRwCArJzBNvvjDZJyxYRjvDkLuA@mail.gmail.com> (raw)
In-Reply-To: <1540542307-63158-1-git-send-email-biju.das@bp.renesas.com>
Hi Biju,
On Fri, Oct 26, 2018 at 10:32 AM Biju Das <biju.das@bp.renesas.com> wrote:
> This patch adds CMT{0|1|2|3} device nodes for r8a7796 SoC.
>
> Signed-off-by: Biju Das <biju.das@bp.renesas.com>
> ---
> This patch is tested against renesas-dev
>
> I have executed on inconsistency-check, nanosleep and clocksource_switch
> selftests on this arm64 SoC. The inconsistency-check and nanosleep tests
> are working fine.The clocksource_switch asynchronous test is failing due
> to inconsistency-check failure on "arch_sys_counter".
>
> But if i skip the clocksource_switching of "arch_sys_counter", the
> asynchronous test is passing for CMT0/1/2/3 timer.
>
> Has any one noticed this issue?
clockevents/next now has commit 7cd6dca3600d8d71
("clocksource/drivers/arch_timer: Workaround for Allwinner A64 timer
instability"). Perhaps this is related, and the same test program may
indicate similar issues?
See also https://lore.kernel.org/lkml/20190113021719.46457-2-samuel@sholland.org/
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:[~2019-01-24 10:16 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-26 8:25 [PATCH] arm64: dts: renesas: r8a7796: Add CMT device nodes Biju Das
2018-10-26 9:48 ` Fabrizio Castro
2018-11-19 8:27 ` Biju Das
2018-11-19 9:36 ` Daniel Lezcano
2018-11-19 10:26 ` Daniel Lezcano
2018-11-19 10:32 ` Geert Uytterhoeven
2018-11-19 10:35 ` Biju Das
2018-11-19 11:01 ` Daniel Lezcano
2018-11-19 15:50 ` Biju Das
2018-11-19 17:14 ` Daniel Lezcano
2018-11-22 9:46 ` Biju Das
2018-11-22 13:47 ` Daniel Lezcano
2018-11-22 15:16 ` Biju Das
2018-11-22 15:30 ` Daniel Lezcano
2018-11-22 15:55 ` Marc Zyngier
2018-11-21 10:24 ` Simon Horman
2018-11-21 10:27 ` Biju Das
2018-11-23 12:37 ` Simon Horman
2019-01-24 10:15 ` Geert Uytterhoeven [this message]
2019-01-25 11:30 ` Biju Das
2019-01-25 12:26 ` Biju Das
2019-01-25 14:06 ` Vincent Guittot
2019-01-25 14:29 ` Biju Das
2019-01-25 14:44 ` Biju Das
2019-01-25 14:48 ` Vincent Guittot
2019-01-25 14:53 ` Vincent Guittot
2019-01-25 15:12 ` Biju Das
2019-01-25 15:20 ` Vincent Guittot
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=CAMuHMdW-qt+3iNit1wVxN2JyRwCArJzBNvvjDZJyxYRjvDkLuA@mail.gmail.com \
--to=geert@linux-m68k.org \
--cc=Chris.Paterson2@renesas.com \
--cc=biju.das@bp.renesas.com \
--cc=daniel.lezcano@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=fabrizio.castro@bp.renesas.com \
--cc=geert+renesas@glider.be \
--cc=horms@verge.net.au \
--cc=john.stultz@linaro.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=mark.rutland@arm.com \
--cc=robh+dt@kernel.org \
--cc=samuel@sholland.org \
--cc=tglx@linutronix.de \
/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).