Received: by 2002:a05:6a10:9e8c:0:0:0:0 with SMTP id y12csp785727pxx; Mon, 26 Oct 2020 23:37:12 -0700 (PDT) X-Google-Smtp-Source: ABdhPJx24ALNWzOLkVEOFRrTSj6Ihmnwh/HJovVnF9s4uiYqy0lx3Uz6sb4aSYguIPuVKNVHq4ak X-Received: by 2002:a17:906:742:: with SMTP id z2mr846913ejb.57.1603780632164; Mon, 26 Oct 2020 23:37:12 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1603780632; cv=none; d=google.com; s=arc-20160816; b=QIIRHCuOo6JleEtAA0SSB/mPeSMKXI/r6utbrozCvMrQc3m1aYX6na/dfmmTme9clq zicNGoTz+3Ci9uXfgqeA/oaPnx7EM1hbPKDkubkHUcZOVEF9yjUWYq2RT8gUAYM3opmU 5ULlPKM9zHRATuigjoSgtvwjc0FV3qaFM0sufRuTzfYdZtuNFpm0xNHu3P6p1D8nqqZB KzAbUlOsFO4Xs6Q3AWl+I6kMvxafXlBR0qRLcOK9HtL/gfnXGh8lu1d+kd6SI0Tz2eBP vUIQE5lnmad4bqvSE70jyaDFzurHmMIXX90ehHX3giiWI5WsY29aCp3KT5shCD0caMYI s95Q== 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 :dkim-signature; bh=6DibjnlclyptH43I71Ev5fLzqAN4jltrXgwx96thlh0=; b=uaWqOHD7oH4fXkSY6o5i67Ys2ZxDxI5GOUS1oUX0PKzT8emotzStmwMmeqm2EKjFr8 IG8NksK/5qNS9Di5zpAGAfD+jl3fz2ILLgknrvgJ0j2WcYQjSUS7cwc+Amx2FcxylNhc I8F/uqCiQ4EKnPhO5dw0SFe+tOgBCT1XWDDdIopHx1QudXeAAtBgpHI2dWv+OLwA4Btd Q9x2t6DczCYE36C9GDW0sxOt4Wkr5KYcDWvSgzdd6y24pBvQFVHQt837XRKQM/xf0jOU EfItek7Cv0gTh10+7Zfi1ZmXARPgnpgykvtIO8Qv+PCO0N3NA4Pi8JmhMQlVavfPWvnr K0pw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=SFt+gE8+; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 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. [23.128.96.18]) by mx.google.com with ESMTP id 8si220622edx.366.2020.10.26.23.36.49; Mon, 26 Oct 2020 23:37:12 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=SFt+gE8+; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 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 S1728904AbgJZTvd (ORCPT + 99 others); Mon, 26 Oct 2020 15:51:33 -0400 Received: from mail.kernel.org ([198.145.29.99]:47484 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1728866AbgJZTvb (ORCPT ); Mon, 26 Oct 2020 15:51:31 -0400 Received: from localhost (unknown [104.132.1.66]) (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 3D4C320773; Mon, 26 Oct 2020 19:51:31 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1603741891; bh=+RZ6OrpUHqjqPkrvv4eFRdslvghe++1OiSQEyk8BH0s=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=SFt+gE8+XGt7IjZb8F1YsfvY2bCqhJzTFgp2NYaDJ+XKJcPFmEycBnyQDVddeX4hk K1Nbu8MgIvmm+kdxE4KpfAgRU/z/iYlmYa2o48IDckNH5uDi+Tz1pGdmAie4f4HMa4 2BjZio7eTOzQrJ2ZEX4wY+u21kVU4EVOXXrbqC88= From: Jaegeuk Kim To: linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org, kernel-team@android.com Cc: cang@codeaurora.org, alim.akhtar@samsung.com, avri.altman@wdc.com, bvanassche@acm.org, Jaegeuk Kim Subject: [PATCH v4 1/5] scsi: ufs: atomic update for clkgating_enable Date: Mon, 26 Oct 2020 12:51:20 -0700 Message-Id: <20201026195124.363096-2-jaegeuk@kernel.org> X-Mailer: git-send-email 2.29.0.rc1.297.gfa9743e501-goog In-Reply-To: <20201026195124.363096-1-jaegeuk@kernel.org> References: <20201026195124.363096-1-jaegeuk@kernel.org> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org From: Jaegeuk Kim When giving a stress test which enables/disables clkgating, we hit device timeout sometimes. This patch avoids subtle racy condition to address it. Note that, this requires a patch to address the device stuck by REQ_CLKS_OFF in __ufshcd_release(). The fix is "scsi: ufs: avoid to call REQ_CLKS_OFF to CLKS_OFF". Signed-off-by: Jaegeuk Kim --- drivers/scsi/ufs/ufshcd.c | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/drivers/scsi/ufs/ufshcd.c b/drivers/scsi/ufs/ufshcd.c index cc8d5f0c3fdc..6c9269bffcbd 100644 --- a/drivers/scsi/ufs/ufshcd.c +++ b/drivers/scsi/ufs/ufshcd.c @@ -1808,19 +1808,19 @@ static ssize_t ufshcd_clkgate_enable_store(struct device *dev, return -EINVAL; value = !!value; + + spin_lock_irqsave(hba->host->host_lock, flags); if (value == hba->clk_gating.is_enabled) goto out; - if (value) { - ufshcd_release(hba); - } else { - spin_lock_irqsave(hba->host->host_lock, flags); + if (value) + __ufshcd_release(hba); + else hba->clk_gating.active_reqs++; - spin_unlock_irqrestore(hba->host->host_lock, flags); - } hba->clk_gating.is_enabled = value; out: + spin_unlock_irqrestore(hba->host->host_lock, flags); return count; } -- 2.29.0.rc1.297.gfa9743e501-goog