From: Geert Uytterhoeven <geert+renesas@glider.be>
To: Magnus Damm <magnus.damm@gmail.com>
Cc: linux-renesas-soc@vger.kernel.org,
Geert Uytterhoeven <geert+renesas@glider.be>,
linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 0/4] ARM: shmobile: Enable ARM_GLOBAL_TIMER on Cortex-A9 MPCore
Date: Wed, 11 Dec 2019 14:52:18 +0100 [thread overview]
Message-ID: <20191211135222.26770-1-geert+renesas@glider.be> (raw)
Hi all,
SH-Mobile AG5 and R-Car H1 SoCs are based on the Cortex-A9 MPCore, which
includes an ARM global timer.
Enable use of the global timer on these SoCs for scheduling and delay
loops, with the following impact:
- Scheduler accuracy is increased from 10 ms to a few ns,
- Calls to shmobile_init_delay() to preset loops-per-jiffies can be
removed.
Note that when using an old DTB lacking the global timer, the kernel
will still work, but the delay loop will need to be calibrated
during boot.
Note that we still need shmobile_init_delay() to setup loops-per-jiffies
for other SoCs lacking an architectured or global timer:
- emev2: Dual-core Cortex-A9 r1p3,
- r7s72100: single-core Cortex-A9 MPCore r3p0, global timer IRQ not
wired?
- r7s9210: single-core Cortex-A9 MPCore r4p1, global timer IRQ not
wired?
- r8a7740: single-core Cortex-A9 r2p4,
- r8a7778: single-core Cortex-A9 r2p2-00rel0.
Changes compared to v1:
- Rebased.
I have been using this on KZM-A9-GT (SH-Mobile AG5) and Marzen (R-Car
H1) for the last 18 months or so.
Hence I plan to queue the first 3 patches in renesas-devel for v5.6,
and postpone the 4th to v5.7.
Thanks!
Geert Uytterhoeven (4):
ARM: dts: sh73a0: Rename twd clock to periph clock
ARM: dts: sh73a0: Add device node for ARM global timer
ARM: dts: r8a7779: Add device node for ARM global timer
ARM: shmobile: Enable ARM_GLOBAL_TIMER on Cortex-A9 MPCore SoCs
arch/arm/boot/dts/r8a7779.dtsi | 8 ++++++++
arch/arm/boot/dts/sh73a0.dtsi | 11 +++++++++--
arch/arm/mach-shmobile/setup-r8a7779.c | 1 -
arch/arm/mach-shmobile/setup-sh73a0.c | 1 -
drivers/soc/renesas/Kconfig | 2 ++
5 files changed, 19 insertions(+), 4 deletions(-)
--
2.17.1
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
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next reply other threads:[~2019-12-11 13:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-11 13:52 Geert Uytterhoeven [this message]
2019-12-11 13:52 ` [PATCH v2 1/4] ARM: dts: sh73a0: Rename twd clock to periph clock Geert Uytterhoeven
2019-12-11 13:52 ` [PATCH v2 2/4] ARM: dts: sh73a0: Add device node for ARM global timer Geert Uytterhoeven
2019-12-11 13:52 ` [PATCH v2 3/4] ARM: dts: r8a7779: " Geert Uytterhoeven
2019-12-11 13:52 ` [PATCH v2 4/4] ARM: shmobile: Enable ARM_GLOBAL_TIMER on Cortex-A9 MPCore SoCs 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=20191211135222.26770-1-geert+renesas@glider.be \
--to=geert+renesas@glider.be \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=magnus.damm@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).