From: Daniel Lezcano <daniel.lezcano@linaro.org>
To: Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Cc: Tao Ren <taoren@fb.com>, Keerthy <j-keerthy@ti.com>
Subject: [GIT PULL] clocksource fixes for 4.19-rc
Date: Mon, 24 Sep 2018 07:49:10 +0200 [thread overview]
Message-ID: <f2ad506a-e537-97cf-465a-593361116b10@linaro.org> (raw)
Thomas, Ingo,
This pull request for clockevents / clocksource contains two fixes and
is based on tip/timers/urgent:
- Add the CLOCK_SOURCE_SUSPEND_NONSTOP for non-am43 SoCs (Keerthy)
- Fix set_next_event handler for the fttmr010 (Tao Ren)
Thanks !
-- Daniel
The following changes since commit e2c631ba75a7e727e8db0a9d30a06bfd434adb3a:
clocksource: Revert "Remove kthread" (2018-09-06 23:38:35 +0200)
are available in the git repository at:
https://git.linaro.org/people/daniel.lezcano/linux.git
clockevents/4.19-fixes
for you to fetch changes up to 4451d3f59f2a6f95e5d205c2d04ea072955d080d:
clocksource/drivers/fttmr010: Fix set_next_event handler (2018-09-24
06:13:31 +0200)
----------------------------------------------------------------
Keerthy (1):
clocksource/drivers/ti-32k: Add CLOCK_SOURCE_SUSPEND_NONSTOP flag
for non-am43 SoCs
Tao Ren (1):
clocksource/drivers/fttmr010: Fix set_next_event handler
drivers/clocksource/timer-fttmr010.c | 18 +++++++++++-------
drivers/clocksource/timer-ti-32k.c | 3 +++
2 files changed, 14 insertions(+), 7 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:[~2018-09-24 5:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-24 5:49 Daniel Lezcano [this message]
2018-09-24 5:50 ` [PATCH 1/2] clocksource/drivers/ti-32k: Add CLOCK_SOURCE_SUSPEND_NONSTOP flag for non-am43 SoCs Daniel Lezcano
2018-09-24 5:50 ` [PATCH 2/2] clocksource/drivers/fttmr010: Fix set_next_event handler Daniel Lezcano
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=f2ad506a-e537-97cf-465a-593361116b10@linaro.org \
--to=daniel.lezcano@linaro.org \
--cc=j-keerthy@ti.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=taoren@fb.com \
--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).