From mboxrd@z Thu Jan 1 00:00:00 1970 From: Kevin Hilman Subject: Re: [PATCH v8 00/24] gpio/omap: driver cleanup and fixes Date: Tue, 29 Nov 2011 07:15:00 -0800 Message-ID: <87y5uz6juz.fsf@ti.com> References: <1317803593-12259-1-git-send-email-tarun.kanti@ti.com> <87obwsg9ua.fsf@ti.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: QUOTED-PRINTABLE Return-path: Received: from na3sys009aog120.obsmtp.com ([74.125.149.140]:49501 "EHLO na3sys009aog120.obsmtp.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753679Ab1K2PPJ convert rfc822-to-8bit (ORCPT ); Tue, 29 Nov 2011 10:15:09 -0500 Received: by mail-yw0-f51.google.com with SMTP id 1so4732393yws.24 for ; Tue, 29 Nov 2011 07:15:08 -0800 (PST) In-Reply-To: (Tarun Kanti DebBarma's message of "Fri, 25 Nov 2011 16:00:27 +0530") Sender: linux-omap-owner@vger.kernel.org List-Id: linux-omap@vger.kernel.org To: "DebBarma, Tarun Kanti" Cc: Santosh Shilimkar , linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org, Tony Lindgren "DebBarma, Tarun Kanti" writes: > On Fri, Nov 4, 2011 at 2:57 PM, DebBarma, Tarun Kanti > wrote: >> On Fri, Nov 4, 2011 at 3:14 AM, Kevin Hilman wrote: >>> Tarun Kanti DebBarma writes: >>> >>>> This series is continuation of cleanup of OMAP GPIO driver and fix= es. >>> >>> Using this series on 3630/Zoom3, UART wakeups no longer work from >>> suspend. =C2=A0That suggests that GPIO wakeups from retention/off a= re not >>> working. >>> >>> Please test GPIO wakeups from retention/off. =C2=A0One way is to us= e Zoom3 >>> UART wakeup from suspend using by enabling UART wakeups and suspend= ing: >>> >>> =C2=A0 # echo enabled > /sys/devices/platform/serial8250.0/tty/ttyS= 0/power/wakeup >>> =C2=A0 # echo mem > /sys/power/state >> Ok, I will test and make necessary fix. > I have done retention test of the latest series on Zoom3. When I try > running off mode > test it says support is not present because of an errata.=20 Specifically, CORE off is not supported on that rev of 36xx due to an errata. Can you try on a newer 36xx? > Here is the overall log: The rest of the dump seems to point to an MMC driver problem. Please take this with the MMC driver folks. Kevin -- To unsubscribe from this list: send the line "unsubscribe linux-omap" i= n the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html From mboxrd@z Thu Jan 1 00:00:00 1970 From: khilman@ti.com (Kevin Hilman) Date: Tue, 29 Nov 2011 07:15:00 -0800 Subject: [PATCH v8 00/24] gpio/omap: driver cleanup and fixes In-Reply-To: (Tarun Kanti DebBarma's message of "Fri, 25 Nov 2011 16:00:27 +0530") References: <1317803593-12259-1-git-send-email-tarun.kanti@ti.com> <87obwsg9ua.fsf@ti.com> Message-ID: <87y5uz6juz.fsf@ti.com> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org "DebBarma, Tarun Kanti" writes: > On Fri, Nov 4, 2011 at 2:57 PM, DebBarma, Tarun Kanti > wrote: >> On Fri, Nov 4, 2011 at 3:14 AM, Kevin Hilman wrote: >>> Tarun Kanti DebBarma writes: >>> >>>> This series is continuation of cleanup of OMAP GPIO driver and fixes. >>> >>> Using this series on 3630/Zoom3, UART wakeups no longer work from >>> suspend. ?That suggests that GPIO wakeups from retention/off are not >>> working. >>> >>> Please test GPIO wakeups from retention/off. ?One way is to use Zoom3 >>> UART wakeup from suspend using by enabling UART wakeups and suspending: >>> >>> ? # echo enabled > /sys/devices/platform/serial8250.0/tty/ttyS0/power/wakeup >>> ? # echo mem > /sys/power/state >> Ok, I will test and make necessary fix. > I have done retention test of the latest series on Zoom3. When I try > running off mode > test it says support is not present because of an errata. Specifically, CORE off is not supported on that rev of 36xx due to an errata. Can you try on a newer 36xx? > Here is the overall log: The rest of the dump seems to point to an MMC driver problem. Please take this with the MMC driver folks. Kevin