From mboxrd@z Thu Jan 1 00:00:00 1970 From: Kevin Hilman Subject: Re: Broken cpuidle on PM branch? Date: Wed, 14 Oct 2009 06:06:41 -0700 Message-ID: <87aazugm5a.fsf@deeprootsystems.com> References: <20091012192347.GI32041@smtp.gmail.com> <20091013133151.GA8028@esdhcp037198.research.nokia.com> <87r5t7mfbm.fsf@deeprootsystems.com> <20091014064822.GA1000@esdhcp037198.research.nokia.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from mail-px0-f194.google.com ([209.85.216.194]:38751 "EHLO mail-px0-f194.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1760128AbZJNNHU (ORCPT ); Wed, 14 Oct 2009 09:07:20 -0400 Received: by pxi32 with SMTP id 32so999781pxi.16 for ; Wed, 14 Oct 2009 06:06:44 -0700 (PDT) In-Reply-To: <20091014064822.GA1000@esdhcp037198.research.nokia.com> (Eduardo Valentin's message of "Wed\, 14 Oct 2009 09\:48\:22 +0300") Sender: linux-omap-owner@vger.kernel.org List-Id: linux-omap@vger.kernel.org To: eduardo.valentin@nokia.com Cc: "linux-omap@vger.kernel.org" Eduardo Valentin writes: > On Tue, Oct 13, 2009 at 06:25:17PM +0200, ext Kevin Hilman wrote: >> Eduardo Valentin writes: >> >> > Hello Amit, >> > >> > On Mon, Oct 12, 2009 at 09:23:47PM +0200, ext Amit Kucheria wrote: >> >> Hi, >> >> >> >> I am testing twl4030 script optimisations on the current PM branch. But I am >> >> seeing the board (RX51) freeze when CPU_IDLE is enabled in the config. >> >> >> >> Is it known to work on other boards? >> > >> > I'm actually seeing this same behavior. But the board actually does not >> > freeze. If you keep a key pressed of send a sysrq through serial line >> > then you eventually get it back. >> > >> > It seams to be something related to serial driver and wakeup ? >> > >> >> Do you see this problem after doing >> >> # echo 1 > /debug/pm_debug/sleep_while_idle >> > > No I don't. The problem is gone it seams. > > similar effect happens if we > > # echo 0 > /sys/devices/platform/serial8250.2/sleep_timeout > > Of course, this would prevent device go to sleep I guess. > Yes, there is a problem with UART3 (in PER) going idle independently of CORE/MPU that I have not yet found. Kevin