From: Bjorn Andersson <bjorn.andersson@linaro.org>
To: "Bao D. Nguyen" <nguyenb@codeaurora.org>
Cc: cang@codeaurora.org, asutoshd@codeaurora.org,
martin.petersen@oracle.com, linux-scsi@vger.kernel.org,
linux-arm-msm@vger.kernel.org,
Alim Akhtar <alim.akhtar@samsung.com>,
Avri Altman <avri.altman@wdc.com>,
"James E.J. Bottomley" <jejb@linux.ibm.com>,
Stanley Chu <stanley.chu@mediatek.com>,
Bean Huo <beanhuo@micron.com>,
Bart Van Assche <bvanassche@acm.org>,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v1 1/1] scsi: ufshcd: Properly set the device Icc Level
Date: Tue, 15 Sep 2020 02:54:01 +0000 [thread overview]
Message-ID: <20200915025401.GD471@uller> (raw)
In-Reply-To: <5c9d6f76303bbe5188bf839b2ea5e5bf530e7281.1598923023.git.nguyenb@codeaurora.org>
On Tue 01 Sep 01:19 UTC 2020, Bao D. Nguyen wrote:
> UFS version 3.0 and later devices require Vcc and Vccq power supplies
> with Vccq2 being optional. While earlier UFS version 2.0 and 2.1
> devices, the Vcc and Vccq2 are required with Vccq being optional.
> Check the required power supplies used by the device
> and set the device's supported Icc level properly.
>
> Signed-off-by: Can Guo <cang@codeaurora.org>
> Signed-off-by: Asutosh Das <asutoshd@codeaurora.org>
> Signed-off-by: Bao D. Nguyen <nguyenb@codeaurora.org>
> ---
> drivers/scsi/ufs/ufshcd.c | 5 +++--
> 1 file changed, 3 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/scsi/ufs/ufshcd.c b/drivers/scsi/ufs/ufshcd.c
> index 06e2439..fdd1d3e 100644
> --- a/drivers/scsi/ufs/ufshcd.c
> +++ b/drivers/scsi/ufs/ufshcd.c
> @@ -6845,8 +6845,9 @@ static u32 ufshcd_find_max_sup_active_icc_level(struct ufs_hba *hba,
> {
> u32 icc_level = 0;
>
> - if (!hba->vreg_info.vcc || !hba->vreg_info.vccq ||
> - !hba->vreg_info.vccq2) {
> + if (!hba->vreg_info.vcc ||
How did you test this?
devm_regulator_get() never returns NULL, so afaict this conditional will
never be taken with either the old or new version of the code.
Regards,
Bjorn
> + (!hba->vreg_info.vccq && hba->dev_info.wspecversion >= 0x300) ||
> + (!hba->vreg_info.vccq2 && hba->dev_info.wspecversion < 0x300)) {
> dev_err(hba->dev,
> "%s: Regulator capability was not set, actvIccLevel=%d",
> __func__, icc_level);
> --
> The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum,
> a Linux Foundation Collaborative Project
>
next prev parent reply other threads:[~2020-09-15 2:54 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-01 1:19 [PATCH v1 1/1] scsi: ufshcd: Properly set the device Icc Level Bao D. Nguyen
2020-09-10 1:28 ` nguyenb
[not found] ` <0101017475a11d00-6def34a7-db5d-472c-9dcc-215a80510402-000000@us-west-2.amazonses.com>
2020-09-10 10:02 ` Avri Altman
2020-09-14 16:34 ` nguyenb
2020-09-15 2:54 ` Bjorn Andersson [this message]
2020-09-15 8:49 ` nguyenb
2020-09-15 13:37 ` Bjorn Andersson
2020-09-17 0:53 ` nguyenb
2020-09-17 2:29 ` Bjorn Andersson
2020-09-29 2:35 ` nguyenb
2020-10-26 20:48 ` nguyenb
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200915025401.GD471@uller \
--to=bjorn.andersson@linaro.org \
--cc=alim.akhtar@samsung.com \
--cc=asutoshd@codeaurora.org \
--cc=avri.altman@wdc.com \
--cc=beanhuo@micron.com \
--cc=bvanassche@acm.org \
--cc=cang@codeaurora.org \
--cc=jejb@linux.ibm.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=nguyenb@codeaurora.org \
--cc=stanley.chu@mediatek.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).