diff for duplicates of <87y5uz6juz.fsf@ti.com> diff --git a/a/1.txt b/N1/1.txt index 8cd15e2..f7f6f42 100644 --- a/a/1.txt +++ b/N1/1.txt @@ -8,14 +8,14 @@ >>>> 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 +>>> 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 +>>> 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 +>>> ? # 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 @@ -30,7 +30,3 @@ 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" in -the body of a message to majordomo@vger.kernel.org -More majordomo info at http://vger.kernel.org/majordomo-info.html diff --git a/a/content_digest b/N1/content_digest index e73f6af..cab84f7 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -2,15 +2,10 @@ "ref\087obwsg9ua.fsf@ti.com\0" "ref\0CAC83ZvKd3iBrQS5wESnAok8W_a4z-3jZYz17wy376sZJw6sCWg@mail.gmail.com\0" "ref\0CAC83Zv++T96AZRHbEiS_UaGp=Dmu+zQ8se97oaBLhg_+eW-smA@mail.gmail.com\0" - "From\0Kevin Hilman <khilman@ti.com>\0" - "Subject\0Re: [PATCH v8 00/24] gpio/omap: driver cleanup and fixes\0" + "From\0khilman@ti.com (Kevin Hilman)\0" + "Subject\0[PATCH v8 00/24] gpio/omap: driver cleanup and fixes\0" "Date\0Tue, 29 Nov 2011 07:15:00 -0800\0" - "To\0DebBarma" - " Tarun Kanti <tarun.kanti@ti.com>\0" - "Cc\0Santosh Shilimkar <santosh.shilimkar@ti.com>" - linux-omap@vger.kernel.org - linux-arm-kernel@lists.infradead.org - " Tony Lindgren <tony@atomide.com>\0" + "To\0linux-arm-kernel@lists.infradead.org\0" "\00:1\0" "b\0" "\"DebBarma, Tarun Kanti\" <tarun.kanti@ti.com> writes:\n" @@ -23,14 +18,14 @@ ">>>> This series is continuation of cleanup of OMAP GPIO driver and fixes.\n" ">>>\n" ">>> Using this series on 3630/Zoom3, UART wakeups no longer work from\n" - ">>> suspend. \302\240That suggests that GPIO wakeups from retention/off are not\n" + ">>> suspend. ?That suggests that GPIO wakeups from retention/off are not\n" ">>> working.\n" ">>>\n" - ">>> Please test GPIO wakeups from retention/off. \302\240One way is to use Zoom3\n" + ">>> Please test GPIO wakeups from retention/off. ?One way is to use Zoom3\n" ">>> UART wakeup from suspend using by enabling UART wakeups and suspending:\n" ">>>\n" - ">>> \302\240 # echo enabled > /sys/devices/platform/serial8250.0/tty/ttyS0/power/wakeup\n" - ">>> \302\240 # echo mem > /sys/power/state\n" + ">>> ? # echo enabled > /sys/devices/platform/serial8250.0/tty/ttyS0/power/wakeup\n" + ">>> ? # echo mem > /sys/power/state\n" ">> Ok, I will test and make necessary fix.\n" "> I have done retention test of the latest series on Zoom3. When I try\n" "> running off mode\n" @@ -44,10 +39,6 @@ "The rest of the dump seems to point to an MMC driver problem. Please\n" "take this with the MMC driver folks.\n" "\n" - "Kevin\n" - "--\n" - "To unsubscribe from this list: send the line \"unsubscribe linux-omap\" in\n" - "the body of a message to majordomo@vger.kernel.org\n" - More majordomo info at http://vger.kernel.org/majordomo-info.html + Kevin -f0cfa00f7184c7ee64b544465d87c55bf07ae30cb2349d1ae5206980fcaea530 +6c0f630d5f2c68bdebd1a6d5da098209141936215643af568de5966485c48310
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.