From: Steev Klimaszewski <steev@kali.org>
To: Stanley Chu <stanley.chu@mediatek.com>
Cc: Kyuho Choi <chlrbgh0@gmail.com>,
Avri Altman <Avri.Altman@wdc.com>,
Rob Clark <robdclark@gmail.com>,
Bjorn Andersson <bjorn.andersson@linaro.org>,
Asutosh Das <asutoshd@codeaurora.org>,
"cang@codeaurora.org" <cang@codeaurora.org>,
"martin.petersen@oracle.com" <martin.petersen@oracle.com>,
"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
linux-arm-msm <linux-arm-msm@vger.kernel.org>,
Alim Akhtar <alim.akhtar@samsung.com>,
"James E.J. Bottomley" <jejb@linux.ibm.com>,
Bean Huo <beanhuo@micron.com>,
Tomas Winkler <tomas.winkler@intel.com>,
Colin Ian King <colin.king@canonical.com>,
Bart Van Assche <bvanassche@acm.org>,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v1 1/3] scsi: ufs: add write booster feature support
Date: Wed, 24 Jun 2020 11:15:20 -0500 [thread overview]
Message-ID: <cd531342-cf8a-b3c1-0672-1101f7e4cb52@kali.org> (raw)
In-Reply-To: <1592963601.3278.1.camel@mtkswgap22>
On 6/23/20 8:53 PM, Stanley Chu wrote:
> Hi Steev,
>
> Please help try below simple patch to see if above WriteBooster messages
> can be eliminated.
>
>
> ---
> drivers/scsi/ufs/ufshcd.c | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/drivers/scsi/ufs/ufshcd.c b/drivers/scsi/ufs/ufshcd.c
> index f173ad1bd79f..089c0785f0b3 100644
> --- a/drivers/scsi/ufs/ufshcd.c
> +++ b/drivers/scsi/ufs/ufshcd.c
> @@ -6985,6 +6985,8 @@ static int ufs_get_device_desc(struct ufs_hba
> *hba)
> dev_info->wspecversion == 0x220 ||
> (hba->dev_quirks & UFS_DEVICE_QUIRK_SUPPORT_EXTENDED_FEATURES))
> ufshcd_wb_probe(hba, desc_buf);
> + else
> + hba->caps &= ~UFSHCD_CAP_WB_EN;
>
> /*
> * ufshcd_read_string_desc returns size of the string
Hi Stanley,
That worked.
1.
[ 0.704775] ufshcd-qcom 1d84000.ufshc: ufshcd_populate_vreg:
Unable to find vdd-hba-supply regulator, assuming enabled
2.
[ 0.704781] ufshcd-qcom 1d84000.ufshc: ufshcd_populate_vreg:
Unable to find vccq-supply regulator, assuming enabled
3.
[ 0.704783] ufshcd-qcom 1d84000.ufshc: ufshcd_populate_vreg:
Unable to find vccq2-supply regulator, assuming enabled
4.
[ 0.705618] ufshcd-qcom 1d84000.ufshc: Found QC Inline Crypto
Engine (ICE) v3.1.75
5.
[ 0.707496] scsi host0: ufshcd
6.
[ 0.720415] ALSA device list:
7.
[ 0.720422] No soundcards found.
8.
[ 0.734245] ufshcd-qcom 1d84000.ufshc: ufshcd_print_pwr_info:[RX,
TX]: gear=[1, 1], lane[1, 1], pwr[SLOWAUTO_MODE, SLOWAUTO_MODE],
rate = 0
9.
[ 0.845159] ufshcd-qcom 1d84000.ufshc: ufshcd_print_pwr_info:[RX,
TX]: gear=[3, 3], lane[2, 2], pwr[FAST MODE, FAST MODE], rate = 2
10.
[ 0.846399] ufshcd-qcom 1d84000.ufshc:
ufshcd_find_max_sup_active_icc_level: Regulator capability was not
set, actvIccLevel=0
11.
[ 0.849258] scsi 0:0:0:49488: Well-known LUN SAMSUNG
KLUDG4U1EA-B0C1 0500 PQ: 0 ANSI: 6
12.
[ 0.853372] scsi 0:0:0:49476: Well-known LUN SAMSUNG
KLUDG4U1EA-B0C1 0500 PQ: 0 ANSI: 6
13.
[ 0.855135] scsi 0:0:0:49456: Well-known LUN SAMSUNG
KLUDG4U1EA-B0C1 0500 PQ: 0 ANSI: 6
14.
[ 0.857050] scsi 0:0:0:0: Direct-Access SAMSUNG
KLUDG4U1EA-B0C1 0500 PQ: 0 ANSI: 6
15.
[ 0.858297] sd 0:0:0:0: Power-on or device reset occurred
16.
[ 0.859985] scsi 0:0:0:1: Direct-Access SAMSUNG
KLUDG4U1EA-B0C1 0500 PQ: 0 ANSI: 6
17.
[ 0.860702] sd 0:0:0:0: [sda] 29765632 4096-byte logical blocks:
(122 GB/114 GiB)
(full dmesg output at https://pastebin.com/Pvfqe42P )
I guess you can throw my Tested-by on there.
Thanks
--Steev
next prev parent reply other threads:[~2020-06-24 16:16 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-08 21:48 [PATCH v1 0/3] WriteBooster Feature Support Asutosh Das
2020-04-08 21:48 ` [PATCH v1 1/3] scsi: ufs: add write booster feature support Asutosh Das
2020-04-08 21:48 ` [PATCH v1 2/3] ufs-qcom: scsi: configure write booster type Asutosh Das
2020-04-08 21:48 ` [PATCH v1 3/3] ufs: sysfs: add sysfs entries for write booster Asutosh Das
2020-04-12 12:43 ` [PATCH v1 1/3] scsi: ufs: add write booster feature support Avri Altman
2020-04-21 20:01 ` Asutosh Das (asd)
2020-06-20 21:13 ` Rob Clark
2020-06-21 7:40 ` Avri Altman
2020-06-21 7:55 ` Bjorn Andersson
2020-06-21 16:50 ` Rob Clark
2020-06-21 17:50 ` Steev Klimaszewski
2020-06-23 4:34 ` Kyuho Choi
2020-06-23 6:09 ` Avri Altman
2020-06-23 6:51 ` Kyuho Choi
2020-06-24 1:10 ` Steev Klimaszewski
2020-06-24 1:53 ` Stanley Chu
2020-06-24 2:06 ` Kyuho Choi
2020-06-24 2:49 ` Stanley Chu
2020-06-24 16:15 ` Steev Klimaszewski [this message]
2020-06-25 3:29 ` Stanley Chu
2020-06-24 1:54 ` Kyuho Choi
2020-04-21 22:54 ` [PATCH v1 0/3] WriteBooster Feature Support Asutosh Das
2020-04-21 22:54 ` [PATCH v2 1/3] scsi: ufs: add write booster feature support Asutosh Das
2020-04-21 22:54 ` [PATCH v2 2/3] ufs: sysfs: add sysfs entries for write booster Asutosh Das
2020-04-22 8:49 ` Avri Altman
2020-04-21 22:54 ` [PATCH v2 3/3] ufs-qcom: scsi: configure write booster type Asutosh Das
2020-04-22 8:51 ` Avri Altman
2020-04-22 10:28 ` [PATCH v2 1/3] scsi: ufs: add write booster feature support Avri Altman
2020-04-22 10:35 ` Avri Altman
2020-04-22 21:41 ` [PATCH v3 0/3] WriteBooster Feature Support Asutosh Das
2020-04-22 21:41 ` [PATCH v3 1/3] scsi: ufs: add write booster feature support Asutosh Das
2020-04-22 21:41 ` [PATCH v3 2/3] ufs: sysfs: add sysfs entries for write booster Asutosh Das
2020-04-22 21:41 ` [PATCH v3 3/3] ufs-qcom: scsi: configure write booster type Asutosh Das
2020-04-23 8:30 ` [PATCH v3 0/3] WriteBooster Feature Support Avri Altman
2020-04-27 22:49 ` [PATCH v1 " Martin K. Petersen
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=cd531342-cf8a-b3c1-0672-1101f7e4cb52@kali.org \
--to=steev@kali.org \
--cc=Avri.Altman@wdc.com \
--cc=alim.akhtar@samsung.com \
--cc=asutoshd@codeaurora.org \
--cc=beanhuo@micron.com \
--cc=bjorn.andersson@linaro.org \
--cc=bvanassche@acm.org \
--cc=cang@codeaurora.org \
--cc=chlrbgh0@gmail.com \
--cc=colin.king@canonical.com \
--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=robdclark@gmail.com \
--cc=stanley.chu@mediatek.com \
--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).