All of lore.kernel.org
 help / color / mirror / Atom feed
From: Javier Martinez Canillas <javier.martinez@collabora.co.uk>
To: Kukjin Kim <kgene@kernel.org>, kgene.kim@samsung.com
Cc: Doug Anderson <dianders@chromium.org>,
	Olof Johansson <olof@lixom.net>,
	Kevin Hilman <khilman@linaro.org>,
	Tyler Baker <tyler.baker@linaro.org>,
	Abhilash Kesavan <kesavan.abhilash@gmail.com>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>,
	linux-samsung-soc <linux-samsung-soc@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/1] ARM: dts: Add keep-power-in-suspend to WiFi SDIO node for Peach Boards
Date: Thu, 30 Apr 2015 02:41:31 +0200	[thread overview]
Message-ID: <55417A3B.8090708@collabora.co.uk> (raw)
In-Reply-To: <552E1C39.4070104@collabora.co.uk>

Hello Kukjin,

On 04/15/2015 10:07 AM, Javier Martinez Canillas wrote:
> 
> On 04/07/2015 05:09 PM, Doug Anderson wrote:
>> Javier,
>> 
>> On Tue, Apr 7, 2015 at 6:03 AM, Javier Martinez Canillas
>> <javier.martinez@collabora.co.uk> 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 <javier.martinez@collabora.co.uk>
>>> ---
>>>  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 <dianders@chromium.org>
>> 
> 
> Any comments on this patch?
> 
> Best regards,
> Javier
> 

Gentle reminder about this patch.

Best regards,
Javier

WARNING: multiple messages have this Message-ID (diff)
From: javier.martinez@collabora.co.uk (Javier Martinez Canillas)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/1] ARM: dts: Add keep-power-in-suspend to WiFi SDIO node for Peach Boards
Date: Thu, 30 Apr 2015 02:41:31 +0200	[thread overview]
Message-ID: <55417A3B.8090708@collabora.co.uk> (raw)
In-Reply-To: <552E1C39.4070104@collabora.co.uk>

Hello Kukjin,

On 04/15/2015 10:07 AM, Javier Martinez Canillas wrote:
> 
> On 04/07/2015 05:09 PM, Doug Anderson wrote:
>> Javier,
>> 
>> On Tue, Apr 7, 2015 at 6:03 AM, Javier Martinez Canillas
>> <javier.martinez@collabora.co.uk> 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 <javier.martinez@collabora.co.uk>
>>> ---
>>>  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 <dianders@chromium.org>
>> 
> 
> Any comments on this patch?
> 
> Best regards,
> Javier
> 

Gentle reminder about this patch.

Best regards,
Javier

  reply	other threads:[~2015-04-30  0:41 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-07 13:03 [PATCH 1/1] ARM: dts: Add keep-power-in-suspend to WiFi SDIO node for Peach Boards Javier Martinez Canillas
2015-04-07 13:03 ` Javier Martinez Canillas
2015-04-07 15:09 ` Doug Anderson
2015-04-07 15:09   ` Doug Anderson
2015-04-15  8:07   ` Javier Martinez Canillas
2015-04-15  8:07     ` Javier Martinez Canillas
2015-04-30  0:41     ` Javier Martinez Canillas [this message]
2015-04-30  0:41       ` Javier Martinez Canillas

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=55417A3B.8090708@collabora.co.uk \
    --to=javier.martinez@collabora.co.uk \
    --cc=dianders@chromium.org \
    --cc=kesavan.abhilash@gmail.com \
    --cc=kgene.kim@samsung.com \
    --cc=kgene@kernel.org \
    --cc=khilman@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-samsung-soc@vger.kernel.org \
    --cc=olof@lixom.net \
    --cc=tyler.baker@linaro.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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.