From: cang@codeaurora.org
To: Avri Altman <Avri.Altman@wdc.com>
Cc: asutoshd@codeaurora.org, nguyenb@codeaurora.org,
rnayak@codeaurora.org, linux-scsi@vger.kernel.org,
kernel-team@android.com, saravanak@google.com,
salyzyn@google.com, Alim Akhtar <alim.akhtar@samsung.com>,
Pedro Sousa <pedrom.sousa@synopsys.com>,
"James E.J. Bottomley" <jejb@linux.ibm.com>,
"Martin K. Petersen" <martin.petersen@oracle.com>,
Tomas Winkler <tomas.winkler@intel.com>,
Subhash Jadavani <subhashj@codeaurora.org>,
Stanley Chu <stanley.chu@mediatek.com>,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v1 3/5] scsi: ufs: Update VCCQ2 and VCCQ min voltage hard codes
Date: Wed, 13 Nov 2019 10:56:22 +0800 [thread overview]
Message-ID: <b49ed789b22bc3caa2e7decfbd951c1d@codeaurora.org> (raw)
In-Reply-To: <MN2PR04MB6991D2D4444BB8E319CF916AFC770@MN2PR04MB6991.namprd04.prod.outlook.com>
On 2019-11-12 15:56, Avri Altman wrote:
>>
>>
>> Per UFS 3.0 JEDEC standard, the VCCQ2 min voltage is 1.7v and the VCCQ
>> min
>> voltage is 1.14v, update their hard codes accordingly.
>>
>> Signed-off-by: Can Guo <cang@codeaurora.org>
> AFAIK, Vccq2 is 1.7 - 1.95 in UFS2.1 as well.
> Current constants applies to UFS1.1, as indicated in the original
> patch.
> Vccq is <1.1 - 1.3> in UFS2.1, and <1.14 - 1.26>, so need to update
> the max as well, and
> make the assignments in ufshcd_populate_vreg depends on
> hba->ufs_version?
>
Hi Avri,
Thank you for the comments. I will also update max voltage of VCCQ in
next series.
BTW, making the assignments in ufshcd_populate_vregs depends on
hba->ufs_version is
not practical. #1. hba->ufs_version is only get after vregs and clocks
are ON,
which is way after ufshcd_populate_vregs. #2. hba->ufs_version is the
version
of HCI, but we need to know the version of the connected UFS device.
The purpose of this change is to make sure the voltages of VCCQ and
VCCQ2 work in
a safe range for all ver 1.1/2.0/2.1/3.0 UFS devices that can be
connected to a host.
Best Regards,
Can Guo.
>> ---
>> drivers/scsi/ufs/ufs.h | 4 ++--
>> 1 file changed, 2 insertions(+), 2 deletions(-)
>>
>> diff --git a/drivers/scsi/ufs/ufs.h b/drivers/scsi/ufs/ufs.h index
>> 385bac8..9df4f4d
>> 100644
>> --- a/drivers/scsi/ufs/ufs.h
>> +++ b/drivers/scsi/ufs/ufs.h
>> @@ -500,9 +500,9 @@ struct ufs_query_res {
>> #define UFS_VREG_VCC_MAX_UV 3600000 /* uV */
>> #define UFS_VREG_VCC_1P8_MIN_UV 1700000 /* uV */
>> #define UFS_VREG_VCC_1P8_MAX_UV 1950000 /* uV */
>> -#define UFS_VREG_VCCQ_MIN_UV 1100000 /* uV */
>> +#define UFS_VREG_VCCQ_MIN_UV 1140000 /* uV */
>> #define UFS_VREG_VCCQ_MAX_UV 1300000 /* uV */
>> -#define UFS_VREG_VCCQ2_MIN_UV 1650000 /* uV */
>> +#define UFS_VREG_VCCQ2_MIN_UV 1700000 /* uV */
>> #define UFS_VREG_VCCQ2_MAX_UV 1950000 /* uV */
>>
>> /*
>> --
>> The Qualcomm Innovation Center, Inc. is a member of the Code Aurora
>> Forum,
>> a Linux Foundation Collaborative Project
next prev parent reply other threads:[~2019-11-13 2:56 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1573200932-384-1-git-send-email-cang@codeaurora.org>
2019-11-08 8:15 ` [PATCH v1 1/5] scsi: ufs: Recheck bkops level if bkops is disabled Can Guo
2019-11-12 7:10 ` Avri Altman
2019-11-13 21:35 ` [EXT] " Bean Huo (beanhuo)
2019-11-08 8:15 ` [PATCH v1 2/5] scsi: ufs: Add new bit field PA_INIT to UECDL register Can Guo
2019-11-12 7:53 ` Avri Altman
2019-11-13 0:41 ` cang
2019-11-08 8:15 ` [PATCH v1 3/5] scsi: ufs: Update VCCQ2 and VCCQ min voltage hard codes Can Guo
2019-11-12 7:56 ` Avri Altman
2019-11-13 2:56 ` cang [this message]
2019-11-08 8:15 ` [PATCH v1 4/5] scsi: ufs: Avoid messing up the compl_time_stamp of lrbs Can Guo
2019-11-12 8:06 ` Avri Altman
2019-11-08 8:15 ` [PATCH v1 5/5] scsi: ufs: Complete pending requests in host reset and restore path Can Guo
2019-11-13 2:24 ` Alim Akhtar
2019-11-13 3:01 ` cang
2019-11-13 22:04 ` [EXT] " Bean Huo (beanhuo)
2019-11-14 1:03 ` cang
2019-11-14 1:18 ` cang
2019-11-14 13:03 ` Bean Huo (beanhuo)
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=b49ed789b22bc3caa2e7decfbd951c1d@codeaurora.org \
--to=cang@codeaurora.org \
--cc=Avri.Altman@wdc.com \
--cc=alim.akhtar@samsung.com \
--cc=asutoshd@codeaurora.org \
--cc=jejb@linux.ibm.com \
--cc=kernel-team@android.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=nguyenb@codeaurora.org \
--cc=pedrom.sousa@synopsys.com \
--cc=rnayak@codeaurora.org \
--cc=salyzyn@google.com \
--cc=saravanak@google.com \
--cc=stanley.chu@mediatek.com \
--cc=subhashj@codeaurora.org \
--cc=tomas.winkler@intel.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).