Received: by 2002:a5b:505:0:0:0:0:0 with SMTP id o5csp73432ybp; Thu, 3 Oct 2019 10:20:40 -0700 (PDT) X-Google-Smtp-Source: APXvYqwGTB4stpRGAZoH2N2BOFDGwH96wOIVXNNuBwsQVwJ2S5eL/bauyyi41UmqVYB2JENYpzeg X-Received: by 2002:a17:906:6c8:: with SMTP id v8mr8815702ejb.252.1570123240502; Thu, 03 Oct 2019 10:20:40 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1570123240; cv=none; d=google.com; s=arc-20160816; b=yOOfqERiH0reASczDhJUf6UXFoOK7xOduMvExthrkIEp/+5+r4xmWzaI9m+oiYky8S GQeWG8kI34Y/icmlq7L5IH6pjHhoTiPiZMtgNEOHkeOIloA/pXCT3nJr5ZnIOVPzQ+aY g2jxBg0mQWWoii+wpLVkMDgvlt54SuKz2kMAzFt0W3BjX4v2rpL/UEfyYNlq3yI0RrMI KJquVayBQdKzMi2qTsspsYKBn8tW2g+FcsiOUo/j2pyFuUjXx5fbG1iQQHfxbz3ZUfYe ZqOPxDG4f0e8UqzBuzmx+gyFJ6wQS9bO7wyp8747yqjf/T0fRm0qHQbKgPU4d56kUAWa 1z8g== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:mime-version :user-agent:references:in-reply-to:message-id:date:subject:cc:to :from:dkim-signature; bh=YtNiCp9tv6jPL6Tl8j8y3bz6AR2tFrlYDEM4Bhl/18A=; b=IWt9z6F1LUjmNrPoAUVE4ibxp4oOCCklaazJP77m5OQ7lnwsS/UgAwtxmaZtlbRMDn Db9DR4648rSKY9wnY5fOD2KzQDJi9NyNTx38TWYipea4rnSvaKmUNTwAf5hU7XKi6eBv uiTNQMUMqXzPocfMb7A7+/axNoVzklCi55c54Agh1iptaO2jSsmtTiGvgOITqYTkU3h7 Aibrw0W1olZRJ1g4XrUYCpMlu/g2WSm5MBhr6fKGRQbyx1mV5WTWbrO9NzpLIEh43AlX 0KUVlK2DP88rTSSvnd5ZS8I62I0+UMYIdBGGGpLymsrBPyCo6EnxOwXlEePkz3nC9p57 NunQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=SBH6riL5; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id f8si1506202ejd.270.2019.10.03.10.20.15; Thu, 03 Oct 2019 10:20:40 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=SBH6riL5; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2387637AbfJCQUe (ORCPT + 99 others); Thu, 3 Oct 2019 12:20:34 -0400 Received: from mail.kernel.org ([198.145.29.99]:48298 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1731517AbfJCQUd (ORCPT ); Thu, 3 Oct 2019 12:20:33 -0400 Received: from localhost (83-86-89-107.cable.dynamic.v4.ziggo.nl [83.86.89.107]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id 90DB720865; Thu, 3 Oct 2019 16:20:32 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1570119633; bh=+hiAlNfbSBPF8qKfDkfN4sNImtyxNSb/HIggk7vL2UE=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=SBH6riL5/qd/BA9nrJf1OjUpZAune74uhhx5DzC0qoPVx/us5Eaj/aXg/q+ch1xkV iGexVsgvcCQRaJs6AkLekpgQM+fFUto3lAqzf+KjljNJJK+ddGvugo48lZ2q5FSQlB JB57GzYXeESN6iFQUrOB82LpGJ1wR6cWNkvYbnio= From: Greg Kroah-Hartman To: linux-kernel@vger.kernel.org Cc: Greg Kroah-Hartman , stable@vger.kernel.org, Matthias Kaehlcke , Ulf Hansson , Douglas Anderson , Sasha Levin Subject: [PATCH 4.19 136/211] mmc: dw_mmc: Re-store SDIO IRQs mask at system resume Date: Thu, 3 Oct 2019 17:53:22 +0200 Message-Id: <20191003154518.185905298@linuxfoundation.org> X-Mailer: git-send-email 2.23.0 In-Reply-To: <20191003154447.010950442@linuxfoundation.org> References: <20191003154447.010950442@linuxfoundation.org> User-Agent: quilt/0.66 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org From: Ulf Hansson [ Upstream commit 7c526608d5afb62cbc967225e2ccaacfdd142e9d ] In cases when SDIO IRQs have been enabled, runtime suspend is prevented by the driver. However, this still means dw_mci_runtime_suspend|resume() gets called during system suspend/resume, via pm_runtime_force_suspend|resume(). This means during system suspend/resume, the register context of the dw_mmc device most likely loses its register context, even in cases when SDIO IRQs have been enabled. To re-enable the SDIO IRQs during system resume, the dw_mmc driver currently relies on the mmc core to re-enable the SDIO IRQs when it resumes the SDIO card, but this isn't the recommended solution. Instead, it's better to deal with this locally in the dw_mmc driver, so let's do that. Tested-by: Matthias Kaehlcke Signed-off-by: Ulf Hansson Reviewed-by: Douglas Anderson Signed-off-by: Ulf Hansson Signed-off-by: Sasha Levin --- drivers/mmc/host/dw_mmc.c | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/drivers/mmc/host/dw_mmc.c b/drivers/mmc/host/dw_mmc.c index 942da07c9eb87..22c454c7aaca6 100644 --- a/drivers/mmc/host/dw_mmc.c +++ b/drivers/mmc/host/dw_mmc.c @@ -3486,6 +3486,10 @@ int dw_mci_runtime_resume(struct device *dev) /* Force setup bus to guarantee available clock output */ dw_mci_setup_bus(host->slot, true); + /* Re-enable SDIO interrupts. */ + if (sdio_irq_claimed(host->slot->mmc)) + __dw_mci_enable_sdio_irq(host->slot, 1); + /* Now that slots are all setup, we can enable card detect */ dw_mci_enable_cd(host); -- 2.20.1