Received: by 2002:a05:6a10:1287:0:0:0:0 with SMTP id d7csp4276993pxv; Tue, 27 Jul 2021 03:25:22 -0700 (PDT) X-Google-Smtp-Source: ABdhPJxrCh2d5AJL+sdaQ3btR7eKoGFCE7sRXjc7qcuR0UEySpX+WvsTx6i1rkwyfZpeHW0etAv3 X-Received: by 2002:aa7:d342:: with SMTP id m2mr3176039edr.40.1627381522066; Tue, 27 Jul 2021 03:25:22 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1627381522; cv=none; d=google.com; s=arc-20160816; b=c2CQs012wm+XD/C3aOp+qCuyf0djicYflS0acxG3eeKULJaHI/INpiCttUht3gqvDW P3si3bVxnixA78jgr4kDLLdf0e5rBdnYl2bxlRQcdnViEy4fzcg8SmC37cttN8nIvRhL A9SJKYs5Fx/scGpuB3thvOKzcHH/S8VIIenc7+r6vgpJZ63bUEtx1MwfIEfdNMoukjQj 5Vo/wc/kQpDYqP+TGA+8ikWjsgyLQ0Z6OLdFumgnezrWNDtHCJEDhgHyLmDy3XjUELZj wh4lVpt2l2L9pHg1V8hG/wf9A6ASSXW3aFtm7ya/MzvrlHWLt4LqYlcWBmU3BjnLekJ5 Q1kg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:mime-version :references:in-reply-to:message-id:date:subject:cc:to:from; bh=+gVEqK4IJ/u5XQpnu73Eeo9ObB0UBegbWT9PKUuMmaU=; b=Zl2DkjzrI4CJQjNVrg6QjDcr7IHoK/8TVnh+C9rH4xtKlb9bIioNDxIqZgP3poWBWp moDw15jq0BK5xAJYkLw4o0BMO5Z7P60ypcpqoGDhf//V1i6rZoIiD3ytqOK+MXbPWuuP +Z4owMj6z3OtjlUOJQf+HNFIGf9JRUgMbEmjxYbYfIwpWJYLbagYOrig0wBJBkZnsK5p TxRGW56HwEB1ebFYK6l5c03mi4jFBQlpX7eolD3BrbrXUhuUKrzSE1Hm5LiwfhI+/Kw1 ydIxC+ZP7q0l8PBWjccR6+P9gQK57kEGEPHWmhB/KpcRv4RonDwT0m71J4k+kJzKEn0T x1hg== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-crypto-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-crypto-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id 1si2470291eje.240.2021.07.27.03.24.58; Tue, 27 Jul 2021 03:25:22 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-crypto-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-crypto-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-crypto-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S236110AbhG0KYq (ORCPT + 99 others); Tue, 27 Jul 2021 06:24:46 -0400 Received: from muru.com ([72.249.23.125]:55854 "EHLO muru.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S236292AbhG0KYF (ORCPT ); Tue, 27 Jul 2021 06:24:05 -0400 Received: from hillo.muru.com (localhost [127.0.0.1]) by muru.com (Postfix) with ESMTP id DA87E8171; Tue, 27 Jul 2021 10:24:21 +0000 (UTC) From: Tony Lindgren To: "David S . Miller" , Herbert Xu , linux-kernel@vger.kernel.org, linux-omap@vger.kernel.org Cc: linux-crypto@vger.kernel.org, Lokesh Vutla , Tero Kristo Subject: [PATCH 6/6] crypto: omap-sham - drop pm_runtime_irqsafe() usage Date: Tue, 27 Jul 2021 13:23:39 +0300 Message-Id: <20210727102339.49141-6-tony@atomide.com> X-Mailer: git-send-email 2.32.0 In-Reply-To: <20210727102339.49141-1-tony@atomide.com> References: <20210727102339.49141-1-tony@atomide.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Precedence: bulk List-ID: X-Mailing-List: linux-crypto@vger.kernel.org Commit b0a3d8986a76 ("crypto: omap-sham - Use pm_runtime_irq_safe()") added the use of pm_runtime_irq_safe() as pm_runtime_get_sync() was called from a tasklet. We now use the crypto engine queue instead of a custom queue since commit 33c3d434d91 ("crypto: omap-sham - convert to use crypto engine"). We want to drop the use of pm_runtime_irq_safe() in general as it takes a permanent usage count on the parent device causing issues for power management. Based on testing with CONFIG_DEBUG_ATOMIC_SLEEP=y, modprobe omap-sham, followed by modprobe tcrypt sec=1 mode=423, I have not been able to reproduce the scheduling while atomic issue seen earlier with current kernels and we can just drop the call to pm_runtime_irq_safe(). Cc: Lokesh Vutla Cc: Tero Kristo Signed-off-by: Tony Lindgren --- drivers/crypto/omap-sham.c | 1 - 1 file changed, 1 deletion(-) diff --git a/drivers/crypto/omap-sham.c b/drivers/crypto/omap-sham.c --- a/drivers/crypto/omap-sham.c +++ b/drivers/crypto/omap-sham.c @@ -2113,7 +2113,6 @@ static int omap_sham_probe(struct platform_device *pdev) dd->fallback_sz = OMAP_SHA_DMA_THRESHOLD; pm_runtime_enable(dev); - pm_runtime_irq_safe(dev); err = pm_runtime_get_sync(dev); if (err < 0) { -- 2.32.0