From: Roman Volkov <v1ron@mail.ru> To: Tony Prisk <linux@prisktech.co.nz> Cc: Daniel Lezcano <daniel.lezcano@linaro.org>, Thomas Gleixner <tglx@linutronix.de>, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, Roman Volkov <rvolkov@v1ros.org> Subject: [PATCH 0/4] clocksource/vt8500: Fix hangs in small delays Date: Mon, 21 Dec 2015 01:28:08 +0300 [thread overview] Message-ID: <1450650492-18996-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 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(-) -- 2.6.2
WARNING: multiple messages have this Message-ID (diff)
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 01:28:08 +0300 [thread overview] Message-ID: <1450650492-18996-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 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(-) -- 2.6.2
next reply other threads:[~2015-12-20 22:42 UTC|newest] Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-12-20 22:28 Roman Volkov [this message] 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 ` Roman Volkov 2015-12-20 22:28 ` [PATCH 2/4] clocksource/vt8500: Remove the 'loops' variable Roman Volkov 2015-12-20 22:28 ` 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 ` Roman Volkov 2015-12-20 22:28 ` [PATCH 4/4] clocksource/vt8500: Add register R/W functions Roman Volkov 2015-12-20 22:28 ` Roman Volkov 2015-12-21 9:54 ` Alexey Charkov 2015-12-21 8:29 ` [PATCH 0/4] clocksource/vt8500: Fix hangs in small delays Roman Volkov 2015-12-21 8:29 ` Roman Volkov 2015-12-21 20:33 ` Roman Volkov 2015-12-21 20:33 ` Roman Volkov 2015-12-22 9:09 ` Alexey Charkov 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=1450650492-18996-1-git-send-email-v1ron@mail.ru \ --to=v1ron@mail.ru \ --cc=daniel.lezcano@linaro.org \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=linux-kernel@vger.kernel.org \ --cc=linux@prisktech.co.nz \ --cc=rvolkov@v1ros.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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.