Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755828Ab1CBRNF (ORCPT ); Wed, 2 Mar 2011 12:13:05 -0500 Received: from bear.ext.ti.com ([192.94.94.41]:36642 "EHLO bear.ext.ti.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753457Ab1CBRND convert rfc822-to-8bit (ORCPT ); Wed, 2 Mar 2011 12:13:03 -0500 From: "Nori, Sekhar" To: Subhasish Ghosh , "davinci-linux-open-source@linux.davincidsp.com" CC: "linux-arm-kernel@lists.infradead.org" , "Watkins, Melissa" , "sachi@mistralsolutions.com" , Kevin Hilman , Russell King , Michael Williamson , "Chemparathy, Cyril" , Sergei Shtylyov , open list Date: Wed, 2 Mar 2011 22:42:43 +0530 Subject: RE: [PATCH 1/1] davinci: changed SRAM allocator to shared ram. Thread-Topic: [PATCH 1/1] davinci: changed SRAM allocator to shared ram. Thread-Index: AcvVrk3sdDgHpSlTSLiwuUzwIJ5gbwDTgBmQ Message-ID: References: <1297434088-27995-1-git-send-email-subhasish@mistralsolutions.com> <886E26C48DE446C3937D89ECF86030B2@subhasishg> <25DBF349769A4CF7B883D6D7FF01AD70@subhasishg> In-Reply-To: <25DBF349769A4CF7B883D6D7FF01AD70@subhasishg> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 8BIT MIME-Version: 1.0 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1186 Lines: 37 Hi Subhasish, On Sat, Feb 26, 2011 at 17:42:39, Subhasish Ghosh wrote: > Hi Sekhar, > > I tried this using MMC and Kelvin's suggestions, but it never came back. > Here is a log: Was this result with or without this patch applied? > > root@arago:~# rtcwake -d /dev/rtc0 -s 20 -m mem > wakeup from "mem" at Tue Apr 21 14:31:13 2009 > PM: Syncing filesystems ... done. > Freezing user space processes ... (elapsed 0.01 seconds) done. > Freezing remaining freezable tasks ... (elapsed 0.01 seconds) done. > Suspending console(s) (use no_console_suspend to debug) > > From the Kconfig I had enabled RTC_DRV_OMAP, CONFIG_PM, CONFIG_SUSPEND. Nothing stands out from these logs. One thing to verify is if the RTC Alarm interrupt is really working by using the test program present in the Documentation/ folder. Anyway, the easiest way for you to move quickly is to use ramdisk so you can bypass all driver specific issues. Thanks, Sekhar -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/