From: v1ron@mail.ru (Roman Volkov)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/4] clocksource/vt8500: Fix hangs in small delays
Date: Mon, 21 Dec 2015 11:29:16 +0300 [thread overview]
Message-ID: <20151221112916.40373d2f@anonymous> (raw)
In-Reply-To: <1450650492-18996-1-git-send-email-v1ron@mail.ru>
On Mon, 21 Dec 2015 01:28:08 +0300
Roman Volkov <v1ron@mail.ru> wrote:
> 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
>
> Roman Volkov (4):
> clocksource/vt8500: Use [read\write]l_relaxed()
> clocksource/vt8500: Remove the 'loops' variable
> clocksource/vt8500: Use MIN_OSCR_DELTA from PXA
> clocksource/vt8500: Add register R/W functions
>
> drivers/clocksource/vt8500_timer.c | 98
> +++++++++++++++++++++++++++----------- 1 file changed, 69
> insertions(+), 29 deletions(-)
>
Please note that vt8500 maintainer (Tony Prisk) was silent in the last
year. Any suggestions on this?
Regards,
Roman
next prev parent reply other threads:[~2015-12-21 8:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-20 22:28 [PATCH 0/4] clocksource/vt8500: Fix hangs in small delays Roman Volkov
2015-12-20 22:28 ` [PATCH 1/4] clocksource/vt8500: Use [read\write]l_relaxed() Roman Volkov
2015-12-20 22:28 ` [PATCH 2/4] clocksource/vt8500: Remove the 'loops' variable Roman Volkov
2015-12-20 22:28 ` [PATCH 3/4] clocksource/vt8500: Use MIN_OSCR_DELTA from PXA Roman Volkov
2015-12-20 22:28 ` [PATCH 4/4] clocksource/vt8500: Add register R/W functions Roman Volkov
2015-12-21 8:29 ` Roman Volkov [this message]
2015-12-21 20:33 ` [PATCH 0/4] clocksource/vt8500: Fix hangs in small delays Roman Volkov
2015-12-22 9:09 ` Alexey Charkov
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=20151221112916.40373d2f@anonymous \
--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).