From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757626AbcBJJ6V (ORCPT ); Wed, 10 Feb 2016 04:58:21 -0500 Received: from eusmtp01.atmel.com ([212.144.249.242]:32516 "EHLO eusmtp01.atmel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752674AbcBJJ6S (ORCPT ); Wed, 10 Feb 2016 04:58:18 -0500 From: Ludovic Desroches To: CC: , , , Ludovic Desroches Subject: [RFC PATCH] mmc: sdhci-of-at91: don't put device in suspend after probe Date: Wed, 10 Feb 2016 10:58:03 +0100 Message-ID: <1455098283-14500-1-git-send-email-ludovic.desroches@atmel.com> X-Mailer: git-send-email 2.7.0 MIME-Version: 1.0 Content-Type: text/plain Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org By putting the device in suspend at the end of the probe, it is impossible to wake up on non software event such as card insertion/removal. Signed-off-by: Ludovic Desroches --- Hi, Since I had no feedback on this topic: http://permalink.gmane.org/gmane.linux.kernel.mmc/35160 I would like to no more put the device in suspend at the end of the probe. If my device is suspended at the end of the probe, I have no issue to resume on a software event such as mounting my sdcard but hardware event such as card insertion and removal do not trigger a resume. It seems there are only two sdhci drivers using runtime pm so maybe nobody has noticed this issue. Regards Ludovic drivers/mmc/host/sdhci-of-at91.c | 2 -- 1 file changed, 2 deletions(-) diff --git a/drivers/mmc/host/sdhci-of-at91.c b/drivers/mmc/host/sdhci-of-at91.c index 9cb86fb..ae24dea 100644 --- a/drivers/mmc/host/sdhci-of-at91.c +++ b/drivers/mmc/host/sdhci-of-at91.c @@ -210,8 +210,6 @@ static int sdhci_at91_probe(struct platform_device *pdev) if (ret) goto pm_runtime_disable; - pm_runtime_put_autosuspend(&pdev->dev); - return 0; pm_runtime_disable: -- 2.7.0