From: Bjorn Andersson <bjorn.andersson@linaro.org>
To: Stanley Chu <stanley.chu@mediatek.com>
Cc: linux-scsi@vger.kernel.org, martin.petersen@oracle.com,
avri.altman@wdc.com, alim.akhtar@samsung.com, jejb@linux.ibm.com,
beanhuo@micron.com, asutoshd@codeaurora.org, cang@codeaurora.org,
matthias.bgg@gmail.com, bvanassche@acm.org,
linux-mediatek@lists.infradead.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, nguyenb@codeaurora.org,
kuohong.wang@mediatek.com, peter.wang@mediatek.com,
chun-hung.wu@mediatek.com, andy.teng@mediatek.com,
chaotian.jing@mediatek.com, cc.chou@mediatek.com,
jiajie.hao@mediatek.com, alice.chao@mediatek.com
Subject: Re: [RFC PATCH v1] scsi: ufs: Remove pre-defined initial VCC voltage values
Date: Mon, 30 Nov 2020 17:09:32 -0600 [thread overview]
Message-ID: <X8V7rM6GJd2IOo1f@builder.lan> (raw)
In-Reply-To: <20201130091610.2752-1-stanley.chu@mediatek.com>
On Mon 30 Nov 03:16 CST 2020, Stanley Chu wrote:
> UFS specficication allows different VCC configurations for UFS devices,
> for example,
> (1). 2.70V - 3.60V (By default)
> (2). 1.70V - 1.95V (Activated if "vcc-supply-1p8" is declared in
> device tree)
> (3). 2.40V - 2.70V (Supported since UFS 3.x)
>
> With the introduction of UFS 3.x products, an issue is happening that
> UFS driver will use wrong "min_uV/max_uV" configuration to toggle VCC
> regulator on UFU 3.x products with VCC configuration (3) used.
>
> To solve this issue, we simply remove pre-defined initial VCC voltage
> values in UFS driver with below reasons,
>
> 1. UFS specifications do not define how to detect the VCC configuration
> supported by attached device.
>
> 2. Device tree already supports standard regulator properties.
>
> Therefore VCC voltage shall be defined correctly in device tree, and
> shall not be changed by UFS driver. What UFS driver needs to do is simply
> enabling or disabling the VCC regulator only.
>
> This is a RFC conceptional patch. Please help review this and feel
> free to feedback any ideas. Once this concept is accepted, and then
> I would post a more completed patch series to fix this issue.
>
> Signed-off-by: Stanley Chu <stanley.chu@mediatek.com>
Reviewed-by: Bjorn Andersson <bjorn.andersson@linaro.org>
This is the correct thing to do and I would prefer that we did the same
for vccq and vccq2 as well - and thereby remove the min_uV and max_uV
from ufs_vreg.
Regards,
Bjorn
> ---
> drivers/scsi/ufs/ufshcd-pltfrm.c | 10 +---------
> 1 file changed, 1 insertion(+), 9 deletions(-)
>
> diff --git a/drivers/scsi/ufs/ufshcd-pltfrm.c b/drivers/scsi/ufs/ufshcd-pltfrm.c
> index a6f76399b3ae..3965be03c136 100644
> --- a/drivers/scsi/ufs/ufshcd-pltfrm.c
> +++ b/drivers/scsi/ufs/ufshcd-pltfrm.c
> @@ -133,15 +133,7 @@ static int ufshcd_populate_vreg(struct device *dev, const char *name,
> vreg->max_uA = 0;
> }
>
> - if (!strcmp(name, "vcc")) {
> - if (of_property_read_bool(np, "vcc-supply-1p8")) {
> - vreg->min_uV = UFS_VREG_VCC_1P8_MIN_UV;
> - vreg->max_uV = UFS_VREG_VCC_1P8_MAX_UV;
> - } else {
> - vreg->min_uV = UFS_VREG_VCC_MIN_UV;
> - vreg->max_uV = UFS_VREG_VCC_MAX_UV;
> - }
> - } else if (!strcmp(name, "vccq")) {
> + if (!strcmp(name, "vccq")) {
> vreg->min_uV = UFS_VREG_VCCQ_MIN_UV;
> vreg->max_uV = UFS_VREG_VCCQ_MAX_UV;
> } else if (!strcmp(name, "vccq2")) {
> --
> 2.18.0
>
prev parent reply other threads:[~2020-11-30 23:10 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-30 9:16 [RFC PATCH v1] scsi: ufs: Remove pre-defined initial VCC voltage values Stanley Chu
2020-11-30 22:51 ` Asutosh Das (asd)
2020-11-30 23:14 ` Bjorn Andersson
2020-11-30 23:54 ` Asutosh Das (asd)
2020-12-01 1:25 ` Stanley Chu
2020-12-01 3:07 ` Asutosh Das (asd)
2020-12-01 6:54 ` Stanley Chu
2020-12-01 7:00 ` Avri Altman
2020-12-02 7:36 ` nguyenb
2020-12-01 2:53 ` Bjorn Andersson
2020-12-01 3:19 ` Asutosh Das (asd)
2020-12-01 3:29 ` Can Guo
2020-12-01 3:33 ` Bjorn Andersson
2020-11-30 23:09 ` Bjorn Andersson [this message]
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=X8V7rM6GJd2IOo1f@builder.lan \
--to=bjorn.andersson@linaro.org \
--cc=alice.chao@mediatek.com \
--cc=alim.akhtar@samsung.com \
--cc=andy.teng@mediatek.com \
--cc=asutoshd@codeaurora.org \
--cc=avri.altman@wdc.com \
--cc=beanhuo@micron.com \
--cc=bvanassche@acm.org \
--cc=cang@codeaurora.org \
--cc=cc.chou@mediatek.com \
--cc=chaotian.jing@mediatek.com \
--cc=chun-hung.wu@mediatek.com \
--cc=jejb@linux.ibm.com \
--cc=jiajie.hao@mediatek.com \
--cc=kuohong.wang@mediatek.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=matthias.bgg@gmail.com \
--cc=nguyenb@codeaurora.org \
--cc=peter.wang@mediatek.com \
--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).