Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756644Ab3HFVgY (ORCPT ); Tue, 6 Aug 2013 17:36:24 -0400 Received: from mail-oa0-f50.google.com ([209.85.219.50]:60855 "EHLO mail-oa0-f50.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756118Ab3HFVgI (ORCPT ); Tue, 6 Aug 2013 17:36:08 -0400 MIME-Version: 1.0 In-Reply-To: References: <1373391071-6312-1-git-send-email-dianders@chromium.org> <1373411961-23812-1-git-send-email-dianders@chromium.org> <1373411961-23812-4-git-send-email-dianders@chromium.org> <002a01ce7d7d$6bd9e870$438db950$%jun@samsung.com> <003f01ce8154$2f5ea1d0$8e1be570$%jun@samsung.com> Date: Tue, 6 Aug 2013 14:36:07 -0700 X-Google-Sender-Auth: jBwOtUU_NyVi4wATIYZ_cKx5SeU Message-ID: Subject: Re: [PATCH v2 3/5] mmc: dw_mmc: Add exynos resume_noirq callback to clear WAKEUP_INT From: Doug Anderson To: Seungwon Jeon Cc: Chris Ball , Olof Johansson , Jaehoon Chung , James Hogan , Grant Grundler , Alim Akhtar , Abhilash Kesavan , Tomasz Figa , Kukjin Kim , "linux-mmc@vger.kernel.org" , "linux-arm-kernel@lists.infradead.org" , linux-samsung-soc , "linux-kernel@vger.kernel.org" Content-Type: text/plain; charset=ISO-8859-1 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1426 Lines: 33 Seungwon, On Wed, Jul 31, 2013 at 9:18 AM, Doug Anderson wrote: > Seungwon, > > On Mon, Jul 15, 2013 at 5:09 AM, Seungwon Jeon wrote: >> Sorry for late response. >> Yes, it's not clear. >> If you get the confirmation, could you share this problem? >> Possibly, auto-clear may not be implemented. >> Then, manual should be correct. > > I just got an update from my contacts. They confirm that bit 11 is > not automatically cleared and that writing to it will clear it. > Hopefully this information will make it into the next version of any > documentation that you receive as well. > > It is still unclear exactly why the WAKEUP_INT was being asserted on > our board despite the fact that all of the wakeup control signals > (bits 10:8) were 0. That is still being investigated. I have further confirmed from my contacts at Samsung that this is a real silicon errata and that clearing the WAKEUP_INT as I am doing in this series is the right workaround. New patch coming shortly based against ToT linux (v3.11-rc4-20-g0fff106). I have confirmed that it applies cleanly to mmc-next, though I haven't tried booting with that tree. -- 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/