From: v1ron@mail.ru (Roman Volkov)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 0/3] clocksource/vt8500: Fix hangs in small delays
Date: Fri, 1 Jan 2016 16:24:40 +0300 [thread overview]
Message-ID: <1451654683-2401-1-git-send-email-v1ron@mail.ru> (raw)
From: Roman Volkov <rvolkov@v1ros.org>
vt8500 hangs in nanosleep() function, starting from commit
c6eb3f70d4482806dc2d3e1e3c7736f497b1d418, making the system unusable.
Per investigation, looks like set_next_event() now receives too small
delta and fails with -ETIME.
Google group discussion:
https://groups.google.com/forum/#!topic/vt8500-wm8505-linux-kernel/vDMF_mDOb1k
v2:
Address comments by Alexey Charkov. Merge patches to get less amount of
changes (three patches instead of four).
v3:
Address comments by Thomas Gleixner. Edit the changelog.
Tested on my WM8650, no issues in three days uptime.
Roman Volkov (3):
clocksource/vt8500: Use MIN_OSCR_DELTA from PXA
clocksource/vt8500: Remove the 'loops' variable
clocksource/vt8500: Add register R/W functions
drivers/clocksource/vt8500_timer.c | 98 +++++++++++++++++++++++++++-----------
1 file changed, 69 insertions(+), 29 deletions(-)
--
2.6.2
next reply other threads:[~2016-01-01 13:24 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-01 13:24 Roman Volkov [this message]
2016-01-01 13:24 ` [PATCH v3 1/3] clocksource/vt8500: Increase the minimum delta Roman Volkov
2016-01-05 9:01 ` Daniel Lezcano
2016-01-05 9:42 ` Roman Volkov
2016-01-05 10:00 ` Russell King - ARM Linux
2016-01-05 10:31 ` Daniel Lezcano
2016-01-05 11:08 ` Roman Volkov
2016-01-05 10:09 ` Daniel Lezcano
2016-01-01 13:24 ` [PATCH v3 2/3] clocksource/vt8500: Remove the 'loops' variable Roman Volkov
2016-01-01 13:24 ` [PATCH v3 3/3] clocksource/vt8500: Add register R/W functions Roman Volkov
2016-01-06 14:24 ` [PATCH v3 0/3] clocksource/vt8500: Fix hangs in small delays Daniel Lezcano
2016-01-06 15:30 ` Roman Volkov
2016-01-07 10:49 ` 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=1451654683-2401-1-git-send-email-v1ron@mail.ru \
--to=v1ron@mail.ru \
--cc=linux-arm-kernel@lists.infradead.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).