Received: by 2002:ac0:a5a6:0:0:0:0:0 with SMTP id m35-v6csp3834705imm; Wed, 5 Sep 2018 06:48:58 -0700 (PDT) X-Google-Smtp-Source: ANB0VdaBGaTmNLJRd0KJpyAE5JnPr2RM/mfsJGyPgEJT6XtP3486MZ+9QbwkYqv0BYXtgFD9K0dQ X-Received: by 2002:a62:9e08:: with SMTP id s8-v6mr40875577pfd.23.1536155338060; Wed, 05 Sep 2018 06:48:58 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1536155338; cv=none; d=google.com; s=arc-20160816; b=OokMCAuJhngemayyMwsd1Nu8mz5NHvNPxevgVFtVytNmVp1OgRM2Z8Iu7BQYxjJsaS OIhVPSwvcwRSJYtMAZj7mJEqZJfviocK/cvzp+cHdH1HOvqLCcMJnFNLp6GAUnmy4XjV LnHG4TQGVzjIQgOqrSEAWV9T4yV7LQf7U//aVca+gqqj9YTzuVZL/iqzzVK2b79lrHmN SgtXGbRWAPPpKx0GXphX5SsOXK7im7GM2UFW28un/eOShHbMtyC5S+FtiEakps0G/vUk y/7M6XVTUf0AoBI8Ui4LkinNL8xEcMm3iIkZwdc2hO/7KCr3eQ6Xp5wMrrieUd2K5RHs LPvw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:dkim-signature; bh=8ryE6ieu2N06ldnfzCP4IFRQVc+IpJ8jnv5I1Holcg4=; b=cfKHStvbXiK6OBs0U7bEoyiQD/Nx7ZZ1itp84FxM4HHsHp4ubchI7TlG2G4Ky2uTUU dM/NODph6gvB1NMT+QOic8+2qlHSwtTEQGNThu3o9jiCbc3X7CBbukQcxO1dMNx8QRJI nE61WTGUmP/Vl2ciaiDccwcmYHsHz95kb7+t/h19bZkTayi+Nr47rDb5xzpGKmAjI2s5 YrFRWl/jnjQFcWuWva8vT1jh3kg7s/yCx3m9+KrWJkV1oImPib/bxMQThJLHeCLM+YP0 Buf8eaEqf+6JyI0ymlzhi0ZcXrfBMDPftiT+zBFs2WH6aykZOZ3bLXkPWFC39u3yNUFq 1Npw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=lZFRcdQy; 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; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id t1-v6si2020502plb.177.2018.09.05.06.48.42; Wed, 05 Sep 2018 06:48:58 -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=lZFRcdQy; 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; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727755AbeIESQp (ORCPT + 99 others); Wed, 5 Sep 2018 14:16:45 -0400 Received: from mail.kernel.org ([198.145.29.99]:48058 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727686AbeIESQp (ORCPT ); Wed, 5 Sep 2018 14:16:45 -0400 Received: from mail-wm0-f45.google.com (mail-wm0-f45.google.com [74.125.82.45]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id 8695020857; Wed, 5 Sep 2018 13:46:26 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1536155186; bh=iSuzQyl/6gmEtEttbIVROOZFt5p3dtvgWKo4PFkt3/A=; h=References:In-Reply-To:From:Date:Subject:To:Cc:From; b=lZFRcdQyHREFhiKzMKxH4ny3SNKl1XYRX7VTrWdQMcrycBgUqZUHEC+0e2W0FueJO jh9JqXkD5XKS2F9UI5Y9tCd38a2nvj/Bi+pVgq0CNU4wTbG0mIIBI+4/dCVRneVg7d sMWSr8Vr8wVj5dvrSKAZ46TxsTsxNM0YdcJ6+Y6s= Received: by mail-wm0-f45.google.com with SMTP id o18-v6so7851618wmc.0; Wed, 05 Sep 2018 06:46:26 -0700 (PDT) X-Gm-Message-State: APzg51BOp1go6iduLB9sQwhxrrm1N2O+T3I5cm99jHRCIn4WSbjzqVdv 2FGatwrAptOpI6MTrGn0HgbQZdYhnUp4rOcViJg= X-Received: by 2002:a1c:9c56:: with SMTP id f83-v6mr264226wme.135.1536155185081; Wed, 05 Sep 2018 06:46:25 -0700 (PDT) MIME-Version: 1.0 References: <20180905123043.22604-1-m.szyprowski@samsung.com> In-Reply-To: <20180905123043.22604-1-m.szyprowski@samsung.com> From: Krzysztof Kozlowski Date: Wed, 5 Sep 2018 15:46:13 +0200 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: [PATCH] mfd: max8997: Disable interrupt handling for suspend/resume cycle To: Marek Szyprowski Cc: linux-kernel@vger.kernel.org, "linux-samsung-soc@vger.kernel.org" , myungjoo.ham@samsung.com, lee.jones@linaro.org, =?UTF-8?B?QmFydMWCb21pZWogxbtvxYJuaWVya2lld2ljeg==?= Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, 5 Sep 2018 at 14:32, Marek Szyprowski wrote: > > Disable IRQs during suspend/resume cycle to ensure handling of wakeup > interrupts (i.e. RTC wake alarm) after max8997_resume(). This way it can > be properly handled when I2C bus is finally available. This pattern is > also used in other MAX PMIC MFD drivers. > > Signed-off-by: Marek Szyprowski > --- > drivers/mfd/max8997.c | 2 ++ > 1 file changed, 2 insertions(+) > > diff --git a/drivers/mfd/max8997.c b/drivers/mfd/max8997.c > index d1495d76bf2c..5a50ea976c70 100644 > --- a/drivers/mfd/max8997.c > +++ b/drivers/mfd/max8997.c > @@ -464,6 +464,7 @@ static int max8997_suspend(struct device *dev) > > if (device_may_wakeup(dev)) > irq_set_irq_wake(max8997->irq, 1); > + disable_irq(max8997->irq); > return 0; > } > > @@ -474,6 +475,7 @@ static int max8997_resume(struct device *dev) > > if (device_may_wakeup(dev)) > irq_set_irq_wake(max8997->irq, 0); > + enable_irq(max8997->irq); > return max8997_irq_resume(max8997); Looks good except that here and in some existing drivers we do not resume in reverse order of suspend. How about making it like in drivers/mfd/max77843.c? It should not differ from functional point of view, just logically it makes sense. Best regards, Krzysztof