Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755057AbbDGPJ0 (ORCPT ); Tue, 7 Apr 2015 11:09:26 -0400 Received: from mail-ob0-f178.google.com ([209.85.214.178]:32912 "EHLO mail-ob0-f178.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754086AbbDGPJY (ORCPT ); Tue, 7 Apr 2015 11:09:24 -0400 MIME-Version: 1.0 In-Reply-To: <1428411814-21098-1-git-send-email-javier.martinez@collabora.co.uk> References: <1428411814-21098-1-git-send-email-javier.martinez@collabora.co.uk> Date: Tue, 7 Apr 2015 08:09:16 -0700 X-Google-Sender-Auth: Lv8iNf5RsRlbK9fIu3wx2_0CrVI Message-ID: Subject: Re: [PATCH 1/1] ARM: dts: Add keep-power-in-suspend to WiFi SDIO node for Peach Boards From: Doug Anderson To: Javier Martinez Canillas Cc: Kukjin Kim , Olof Johansson , Kevin Hilman , Tyler Baker , Abhilash Kesavan , "linux-arm-kernel@lists.infradead.org" , linux-samsung-soc , "linux-kernel@vger.kernel.org" Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1074 Lines: 26 Javier, On Tue, Apr 7, 2015 at 6:03 AM, Javier Martinez Canillas wrote: > The Marvell mwifiex driver prevents the system to enter into a suspend > state if the card power is not preserved during a suspend/resume cycle. > > So Suspend-to-RAM and Suspend-to-idle is failing on Exynos5800 Peach Pi > and Exynos5420 Peach Pit Chromebooks. > > Add the keep-power-in-suspend Power Management property to the SDIO/MMC > node so the mwifiex suspend handler doesn't fail and the system is able > to enter into a suspend state. > > Signed-off-by: Javier Martinez Canillas > --- > arch/arm/boot/dts/exynos5420-peach-pit.dts | 1 + > arch/arm/boot/dts/exynos5800-peach-pi.dts | 1 + > 2 files changed, 2 insertions(+) Reviewed-by: Doug Anderson -- 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/