From: Daniel Lezcano <daniel.lezcano@linaro.org>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
hslester96@gmail.com,
Geert Uytterhoeven <geert+renesas@glider.be>
Subject: [GIT PULL] clockevents for 5.6
Date: Mon, 4 Nov 2019 15:21:01 +0100 [thread overview]
Message-ID: <6fd4d800-b1f8-d757-458e-23742d20884c@linaro.org> (raw)
Hi Thomas,
here are the changes for v5.6 timer drivers.
Thanks
-- Daniel
The following changes since commit b9023b91dd020ad7e093baa5122b6968c48cc9e0:
tick: broadcast-hrtimer: Fix a race in bc_set_next (2019-09-27
14:45:55 +0200)
are available in the Git repository at:
https://git.linaro.org/people/daniel.lezcano/linux.git tags/timers-v5.6
for you to fetch changes up to 6e001f6a4cc73cd06fc7b8c633bc4906c33dd8ad:
clocksource/drivers/asm9260: Add a check for of_clk_get (2019-11-04
10:40:10 +0100)
----------------------------------------------------------------
- Some cleanups for the timer-of, use %p0F and the unique device name
(Geert Uytterhoeven)
- Use timer-of for the renesas-ostm and the device name to prevent
name collision in case of multiple timers (Geert Uytterhoeven)
- Check if there is an error after calling of_clk_get in asm9260
(Chuhong Yuan)
----------------------------------------------------------------
Chuhong Yuan (1):
clocksource/drivers/asm9260: Add a check for of_clk_get
Geert Uytterhoeven (4):
clocksource/drivers/timer-of: Convert last full_name to %pOF
clocksource/drivers/timer-of: Use unique device name instead of timer
clocksource/drivers/renesas-ostm: Convert to timer_of
clocksource/drivers/renesas-ostm: Use unique device name instead
of ostm
drivers/clocksource/Kconfig | 1 +
drivers/clocksource/asm9260_timer.c | 4 ++++
drivers/clocksource/renesas-ostm.c | 189
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++---------------------------------------------------------------------------------------------------------------------
drivers/clocksource/timer-of.c | 6 +++---
4 files changed, 80 insertions(+), 120 deletions(-)
--
<http://www.linaro.org/> Linaro.org │ Open source software for ARM SoCs
Follow Linaro: <http://www.facebook.com/pages/Linaro> Facebook |
<http://twitter.com/#!/linaroorg> Twitter |
<http://www.linaro.org/linaro-blog/> Blog
next reply other threads:[~2019-11-04 14:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-04 14:21 Daniel Lezcano [this message]
2019-11-04 14:22 ` [PATCH 1/5] clocksource/drivers/timer-of: Convert last full_name to %pOF Daniel Lezcano
2019-11-04 14:22 ` [PATCH 2/5] clocksource/drivers/timer-of: Use unique device name instead of timer Daniel Lezcano
2019-11-04 14:22 ` [PATCH 3/5] clocksource/drivers/renesas-ostm: Convert to timer_of Daniel Lezcano
2019-11-04 14:22 ` [PATCH 4/5] clocksource/drivers/renesas-ostm: Use unique device name instead of ostm Daniel Lezcano
2019-11-04 14:22 ` [PATCH 5/5] clocksource/drivers/asm9260: Add a check for of_clk_get Daniel Lezcano
2019-11-04 17:48 ` [GIT PULL] clockevents for 5.6 Thomas Gleixner
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=6fd4d800-b1f8-d757-458e-23742d20884c@linaro.org \
--to=daniel.lezcano@linaro.org \
--cc=geert+renesas@glider.be \
--cc=hslester96@gmail.com \
--cc=linux-kernel@vger.kernel.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).