From: hongwus@codeaurora.org
To: Can Guo <cang@codeaurora.org>
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>,
Avri Altman <avri.altman@wdc.com>,
Pedro Sousa <pedrom.sousa@synopsys.com>,
"James E.J. Bottomley" <jejb@linux.ibm.com>,
"Martin K. Petersen" <martin.petersen@oracle.com>,
Stanley Chu <stanley.chu@mediatek.com>,
Venkat Gopalakrishnan <venkatg@codeaurora.org>,
Tomas Winkler <tomas.winkler@intel.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 2/8] scsi: ufs: set load before setting voltage in regulators
Date: Thu, 23 Jan 2020 15:50:01 +0800 [thread overview]
Message-ID: <5e18c16a6f01043ccf4756ea7677441b@codeaurora.org> (raw)
In-Reply-To: <1579764349-15578-3-git-send-email-cang@codeaurora.org>
Hi Can,
It makes sense that set the load before enable regulator or set
voltage. Just avoid voltage drop.
On 2020-01-23 15:25, Can Guo wrote:
> From: Asutosh Das <asutoshd@codeaurora.org>
>
> This sequence change is required to avoid dips in voltage
> during boot-up.
>
> Apparently, this dip is caused because in the original
> sequence, the regulators are initialized in lpm mode.
> And then when the load is set to high, and more current
> is drawn, than is allowed in lpm, the dip is seen.
>
> Signed-off-by: Asutosh Das <asutoshd@codeaurora.org>
> Signed-off-by: Can Guo <cang@codeaurora.org>
> ---
> drivers/scsi/ufs/ufshcd.c | 10 +++++-----
> 1 file changed, 5 insertions(+), 5 deletions(-)
>
> diff --git a/drivers/scsi/ufs/ufshcd.c b/drivers/scsi/ufs/ufshcd.c
> index c2de29f..c386c2d 100644
> --- a/drivers/scsi/ufs/ufshcd.c
> +++ b/drivers/scsi/ufs/ufshcd.c
> @@ -7225,6 +7225,11 @@ static int ufshcd_config_vreg(struct device
> *dev,
> name = vreg->name;
>
> if (regulator_count_voltages(reg) > 0) {
> + uA_load = on ? vreg->max_uA : 0;
> + ret = ufshcd_config_vreg_load(dev, vreg, uA_load);
> + if (ret)
> + goto out;
> +
> if (vreg->min_uV && vreg->max_uV) {
> min_uV = on ? vreg->min_uV : 0;
> ret = regulator_set_voltage(reg, min_uV, vreg->max_uV);
> @@ -7235,11 +7240,6 @@ static int ufshcd_config_vreg(struct device
> *dev,
> goto out;
> }
> }
> -
> - uA_load = on ? vreg->max_uA : 0;
> - ret = ufshcd_config_vreg_load(dev, vreg, uA_load);
> - if (ret)
> - goto out;
> }
> out:
> return ret;
Reviewed-by: Hongwu Su <hongwus@codeaurora.org>
next prev parent reply other threads:[~2020-01-23 7:50 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1579764349-15578-1-git-send-email-cang@codeaurora.org>
2020-01-23 7:25 ` [PATCH v4 1/8] scsi: ufs: Flush exception event before suspend Can Guo
2020-01-23 23:09 ` [EXT] " Bean Huo (beanhuo)
2020-01-26 3:29 ` Bart Van Assche
2020-02-03 6:23 ` Can Guo
2020-02-04 3:12 ` Bart Van Assche
2020-02-04 6:28 ` Can Guo
2020-01-23 7:25 ` [PATCH v4 2/8] scsi: ufs: set load before setting voltage in regulators Can Guo
2020-01-23 7:50 ` hongwus [this message]
2020-01-23 7:25 ` [PATCH v4 3/8] scsi: ufs: Remove the check before call setup clock notify vops Can Guo
2020-01-23 7:25 ` [PATCH v4 4/8] scsi: ufs-qcom: Adjust bus bandwidth voting and unvoting Can Guo
2020-01-23 7:25 ` [PATCH v4 5/8] scsi: ufs: Fix ufshcd_hold() caused scheduling while atomic Can Guo
2020-01-24 18:07 ` Asutosh Das (asd)
2020-01-23 7:25 ` [PATCH v4 6/8] scsi: ufs: Add dev ref clock gating wait time support Can Guo
2020-01-23 23:11 ` [EXT] " Bean Huo (beanhuo)
2020-02-03 7:17 ` Can Guo
2020-01-24 18:06 ` Asutosh Das (asd)
2020-01-26 3:34 ` Bart Van Assche
2020-02-03 7:16 ` Can Guo
2020-02-03 22:30 ` Bart Van Assche
2020-01-23 7:25 ` [PATCH v4 7/8] scsi: ufs-qcom: Delay specific time before gate ref clk Can Guo
2020-01-24 18:04 ` Asutosh Das (asd)
2020-01-23 7:25 ` [PATCH v4 8/8] scsi: ufs: Select INITIAL adapt for HS Gear4 Can Guo
2020-01-24 18:03 ` Asutosh Das (asd)
2020-01-26 3:38 ` Bart Van Assche
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=5e18c16a6f01043ccf4756ea7677441b@codeaurora.org \
--to=hongwus@codeaurora.org \
--cc=alim.akhtar@samsung.com \
--cc=asutoshd@codeaurora.org \
--cc=avri.altman@wdc.com \
--cc=cang@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=tomas.winkler@intel.com \
--cc=venkatg@codeaurora.org \
/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).