From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S964778AbcGZSXD (ORCPT ); Tue, 26 Jul 2016 14:23:03 -0400 Received: from hqemgate15.nvidia.com ([216.228.121.64]:6429 "EHLO hqemgate15.nvidia.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1757852AbcGZSWj (ORCPT ); Tue, 26 Jul 2016 14:22:39 -0400 X-PGP-Universal: processed; by hqnvupgp07.nvidia.com on Tue, 26 Jul 2016 11:20:03 -0700 Subject: Re: [patch 61/66] timers: Convert to hotplug state machine To: References: <20160711122450.923603742@linutronix.de> <20160711122535.775201614@linutronix.de> <7d37714e-b072-ee90-f14f-364f4fd01f0d@nvidia.com> <20160725153543.GB10939@linutronix.de> <0b5a7bb5-6670-606b-e33d-63cd8b0fcedd@nvidia.com> <20160726144039.GB23707@linutronix.de> CC: Anna-Maria Gleixner , LKML , Peter Zijlstra , Ingo Molnar , Sebastian Andrzej Siewior , "linux-tegra@vger.kernel.org" From: Jon Hunter Message-ID: <42c161a2-fbb8-47ce-8ec4-a2ccfac3bfc7@nvidia.com> Date: Tue, 26 Jul 2016 19:22:31 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.2.0 MIME-Version: 1.0 In-Reply-To: <20160726144039.GB23707@linutronix.de> X-Originating-IP: [10.26.11.53] X-ClientProxiedBy: UKMAIL102.nvidia.com (10.26.138.15) To UKMAIL101.nvidia.com (10.26.138.13) Content-Type: text/plain; charset="windows-1252" Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Richard, On 26/07/16 15:40, rcochran@linutronix.de wrote: > Jon, > > On Tue, Jul 26, 2016 at 10:20:58AM +0100, Jon Hunter wrote: >> Thanks. I have not tried another ARM based device, but I would be >> curious if another ARM device sees this or not. > > I do see this stall on socfpga and on zynq, but in both cases the > suspend mechanism is flakey in other ways, too. At least I can > reproduce the stall sometimes. > > In your other mail you wrote that you test it like this: > > rtcwake -d rtc1 -m mem -s 3 > > But the stall appears only after 20 seconds. So the resume event > after three seconds (-s 3) is getting lost, right? I don't think so. I noticed that when the stall occurs, I don't see the board attempt to transition to the Tegra LP1 power state in suspend and appears to wake up straight away. So I think the wake-up is seen, but the stall prevents it from transitioning all the way to LP1. Cheers Jon -- nvpublic