Received: by 2002:a25:8b91:0:0:0:0:0 with SMTP id j17csp14695824ybl; Mon, 30 Dec 2019 15:25:50 -0800 (PST) X-Google-Smtp-Source: APXvYqz0BWNT23XsHyJjz98A4sW9Vzz2jSUFQq314zwlNozRdu15qHU4Lokbx8EIre0CiXnw9+OC X-Received: by 2002:a9d:74c4:: with SMTP id a4mr77930646otl.119.1577748350285; Mon, 30 Dec 2019 15:25:50 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1577748350; cv=none; d=google.com; s=arc-20160816; b=V4eZLlYtJM0/0RidKr3hHEA7hfNrjQFB9FwMSayrHufDW1Z77GiPqqZ5y2acbq/KKM gPV2W0igqsfsIDrg+grZjOHBvDi3Gtq5c4h/i2WTZ0p2IFIFogtIgzzhqWUXPeYbZN5S 0YA7ljUriwG1c6zHDIV98LNHZeeVcTwA2mVI23YrZ9gjvkf8+Lx69fvir5d6zGdO5RW5 jo5UDLwHHIq5xfBAVCl+Ch4Q/MDuZQs9n4wkBiAu0BnEbYiA4FtLq5W8MUyRFCrYV1nD A7wt7Zs+DbROvACkFSTsrbvLXDA0WgVFLBTQT7zNi1jujlJgSn0S9daX5Q7w27UiT4rM xUQg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:message-id:references :in-reply-to:subject:cc:to:from:date:content-transfer-encoding :mime-version:dkim-signature; bh=vBXvyWu/WmFpK3s/9QyjuCrueKEXWqV2Lek88cSNWSQ=; b=iJJGbf5zIik2dwjvixnTbNa341NF63fg+Qwq8giMB+X8Tm+uTQcnr7p5OZxlkJCqIY 0RoFm99+oi5kMUWSolntPnyobA1e8HvgJjLJERnUgC2jYfTnlfqkB452XLFdaj6caVBZ COT3JnQIFqGefoMAR0/g7ebe7Ex+VKeY5FvWqu9Z4tZomyrHHjKW7sq9eaHv8jNU516E ozBQK8WAQ6dJLcpAhtjYA8WNJb8AeLmA9MWCQV09VZYy73897v9PixG6eOGo+5VQx1fF nEoM7KvZkswNza2Ztmqmvdp5914n13ifNuTgpr+0yTAPdFLZ0g7mmTy7f0/UL15+Ce2v ohsw== ARC-Authentication-Results: i=1; mx.google.com; dkim=fail header.i=@mg.codeaurora.org header.s=smtp header.b=f3cUoSm0; 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 h13si17493843otk.291.2019.12.30.15.25.38; Mon, 30 Dec 2019 15:25:50 -0800 (PST) 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=fail header.i=@mg.codeaurora.org header.s=smtp header.b=f3cUoSm0; 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 S1727774AbfL3XY6 (ORCPT + 99 others); Mon, 30 Dec 2019 18:24:58 -0500 Received: from mail25.static.mailgun.info ([104.130.122.25]:64108 "EHLO mail25.static.mailgun.info" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727750AbfL3XY6 (ORCPT ); Mon, 30 Dec 2019 18:24:58 -0500 DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=mg.codeaurora.org; q=dns/txt; s=smtp; t=1577748297; h=Message-ID: References: In-Reply-To: Subject: Cc: To: From: Date: Content-Transfer-Encoding: Content-Type: MIME-Version: Sender; bh=vBXvyWu/WmFpK3s/9QyjuCrueKEXWqV2Lek88cSNWSQ=; b=f3cUoSm0oeTnc+wYp/kPMhuVJ00VqBNQ1arvsjeTc1kuEtLatJiHPzk70Rad6h5uosE0O7tp oNGFq4LZHtQorAwRK0MjIWxIRM3/0NPJB/S2sQUTo5tvZ++O7JQ0rgbZVA+Y11ncUaZF5L1g iw2VJTxpNFhrCxTH8H7g58+9m5w= X-Mailgun-Sending-Ip: 104.130.122.25 X-Mailgun-Sid: WyI0MWYwYSIsICJsaW51eC1rZXJuZWxAdmdlci5rZXJuZWwub3JnIiwgImJlOWU0YSJd Received: from smtp.codeaurora.org (ec2-35-166-182-171.us-west-2.compute.amazonaws.com [35.166.182.171]) by mxa.mailgun.org with ESMTP id 5e0a8748.7fe87b388298-smtp-out-n02; Mon, 30 Dec 2019 23:24:56 -0000 (UTC) Received: by smtp.codeaurora.org (Postfix, from userid 1001) id 0007AC447A4; Mon, 30 Dec 2019 23:24:55 +0000 (UTC) X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-caf-mail-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-1.0 required=2.0 tests=ALL_TRUSTED,URIBL_BLOCKED autolearn=unavailable autolearn_force=no version=3.4.0 Received: from mail.codeaurora.org (localhost.localdomain [127.0.0.1]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: asutoshd) by smtp.codeaurora.org (Postfix) with ESMTPSA id 9A397C43383; Mon, 30 Dec 2019 23:24:54 +0000 (UTC) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit Date: Mon, 30 Dec 2019 15:24:54 -0800 From: asutoshd@codeaurora.org To: Stanley Chu Cc: linux-scsi@vger.kernel.org, martin.petersen@oracle.com, avri.altman@wdc.com, alim.akhtar@samsung.com, pedrom.sousa@synopsys.com, jejb@linux.ibm.com, matthias.bgg@gmail.com, bvanassche@acm.org, subhashj@codeaurora.org, beanhuo@micron.com, cang@codeaurora.org, linux-mediatek@lists.infradead.org, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, kuohong.wang@mediatek.com, peter.wang@mediatek.com, chun-hung.wu@mediatek.com, andy.teng@mediatek.com, stable@vger.kernel.org, linux-scsi-owner@vger.kernel.org Subject: Re: [PATCH v1 1/2] scsi: ufs: set device as default active power mode during initialization only In-Reply-To: <1577693546-7598-2-git-send-email-stanley.chu@mediatek.com> References: <1577693546-7598-1-git-send-email-stanley.chu@mediatek.com> <1577693546-7598-2-git-send-email-stanley.chu@mediatek.com> Message-ID: X-Sender: asutoshd@codeaurora.org User-Agent: Roundcube Webmail/1.3.9 Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Stanley, On 2019-12-30 00:12, Stanley Chu wrote: > Currently ufshcd_probe_hba() always sets device status as "active". > This shall be by an assumption that device is already in active state > during the boot stage before kernel. > > However, if link is configured as "off" state and device is requested > to enter "sleep" or "powerdown" power mode during suspend flow, device > will NOT be waken up to "active" power mode during resume flow because > device is already set as "active" power mode in ufhcd_probe_hba(). > > Fix it by setting device as default active power mode during > initialization only, and skipping changing mode during PM flow > in ufshcd_probe_hba(). > > Fixes: 7caf489b99a4 (scsi: ufs: issue link starup 2 times if device > isn't active) > Cc: Alim Akhtar > Cc: Avri Altman > Cc: Bart Van Assche > Cc: Bean Huo > Cc: Can Guo > Cc: Matthias Brugger > Cc: Subhash Jadavani > Cc: stable@vger.kernel.org > Signed-off-by: Stanley Chu > --- > drivers/scsi/ufs/ufshcd.c | 3 ++- > 1 file changed, 2 insertions(+), 1 deletion(-) > > diff --git a/drivers/scsi/ufs/ufshcd.c b/drivers/scsi/ufs/ufshcd.c > index ed02a704c1c2..9abb7085a5d0 100644 > --- a/drivers/scsi/ufs/ufshcd.c > +++ b/drivers/scsi/ufs/ufshcd.c > @@ -6986,7 +6986,8 @@ static int ufshcd_probe_hba(struct ufs_hba *hba) > ufshcd_tune_unipro_params(hba); > > /* UFS device is also active now */ > - ufshcd_set_ufs_dev_active(hba); > + if (!hba->pm_op_in_progress) > + ufshcd_set_ufs_dev_active(hba); > ufshcd_force_reset_auto_bkops(hba); > hba->wlun_dev_clr_ua = true; I see that there's a get_sync done before. So, how would the suspend be triggered in that case? Thanks, asd