scsi: ufs: Fix WriteBooster and cleanup UFS driver
Subsystems (2)
v4 cover scsi: ufs: Fix WriteBooster and cleanup UFS driver
Hi,
This patch set fixes some WriteBooster issues and do small cleanup in UFS driver
v3 -> v4
- Squash patch [4] and [5] (Asutosh)
- Fix commit message in patch [4]
v2 -> v3
- Introduce patch [5] to fix possible VCC power drain during runtime suspend (Asutosh)
v1 -> v2
- Remove dummy new line in patch [4] (Asutosh)
- Add more limitation to allow WriteBooster flush during Hibern8 in runtime-suspend. Now the device power mode is kept as Active power mode only if link is put in Hibern8 or Auto-Hibern8 is enabled during runtime-suspend (Asutosh)
Stanley Chu (4):
scsi: ufs: Remove unnecessary memset for dev_info
scsi: ufs: Allow WriteBooster on UFS 2.2 devices
scsi: ufs: Fix index of attributes query for WriteBooster feature
scsi: ufs: Fix WriteBooster flush during runtime suspend
drivers/scsi/ufs/ufs-sysfs.c | 13 ++++- drivers/scsi/ufs/ufs.h | 2 +- drivers/scsi/ufs/ufshcd.c | 99 +++++++++++++++++++++++++----------- drivers/scsi/ufs/ufshcd.h | 3 +- 4 files changed, 82 insertions(+), 35 deletions(-)
Signature · 1 line
2.18.0
PATCH v4 1/4 scsi: ufs: Remove unnecessary memset for dev_info
The whole UFS host instance has been zero-initialized by scsi_host_alloc(), thus UFS driver does not need to clear "dev_info" member specifically in ufshcd_device_params_init().
Simply remove the unnecessary code.
--- drivers/scsi/ufs/ufshcd.c | 3 --- 1 file changed, 3 deletions(-)
drivers/scsi/ufs/ufshcd.c +0 -3
@@ -7267,9 +7267,6 @@ static int ufshcd_device_params_init(struct ufs_hba *hba)bool flag;int ret; -/* Clear any previous UFS device information */ -memset (&hba->dev_info,0 ,sizeof (hba->dev_info)); -/* Init check for device descriptor sizes */ ufshcd_init_desc_sizes (hba);
Signature · 1 line
2.18.0
PATCH v4 2/4 scsi: ufs: Allow WriteBooster on UFS 2.2 devices
In reply to Stanley ChuAccording to the UFS specification, WriteBooster is officially supported by UFS 2.2.
Since UFS 2.2 specification has been finalized in JEDEC and such devices have also showed up in the market, modify the checking rule for ufshcd_wb_probe() to allow these devices to enable WriteBooster.
--- drivers/scsi/ufs/ufshcd.c | 1 + 1 file changed, 1 insertion(+)
drivers/scsi/ufs/ufshcd.c +1 -0
@@ -6930,6 +6930,7 @@ static int ufs_get_device_desc(struct ufs_hba *hba)* UFS_DEVICE_QUIRK_SUPPORT_EXTENDED_FEATURES enabled */ if (dev_info->wspecversion >=0x310 || + dev_info->wspecversion ==0x220 || (hba->dev_quirks &UFS_DEVICE_QUIRK_SUPPORT_EXTENDED_FEATURES ))ufshcd_wb_probe (hba, desc_buf);
Signature · 1 line
2.18.0
PATCH v4 3/4 scsi: ufs: Fix index of attributes query for WriteBooster feature
In reply to Stanley ChuFor WriteBooster feature related attributes, the index used by query shall be LUN ID if LU Dedicated buffer mode is enabled.
--- drivers/scsi/ufs/ufs-sysfs.c | 13 +++++++++++-- drivers/scsi/ufs/ufshcd.c | 16 ++++++++++------ drivers/scsi/ufs/ufshcd.h | 2 +- 3 files changed, 22 insertions(+), 9 deletions(-)
drivers/scsi/ufs/ufs-sysfs.c +11 -2
@@ -637,7 +637,7 @@ static ssize_t _name##_show(struct device *dev, \int ret; \struct ufs_hba *hba =dev_get_drvdata (dev); \ if (ufshcd_is_wb_flags(QUERY_FLAG_IDN##_uname)) \ - index =ufshcd_wb_get_flag_index (hba); \ + index =ufshcd_wb_get_query_index (hba); \pm_runtime_get_sync (hba->dev); \ ret =ufshcd_query_flag (hba,UPIU_QUERY_OPCODE_READ_FLAG , \ QUERY_FLAG_IDN##_uname, index, &flag); \
@@ -680,6 +680,12 @@ static const struct attribute_group ufs_sysfs_flags_group = { .attrs = ufs_sysfs_device_flags, }; +static inline bool ufshcd_is_wb_attrs (enum attr_idn idn) +{ +return ((idn >=QUERY_ATTR_IDN_WB_FLUSH_STATUS ) && + (idn <=QUERY_ATTR_IDN_CURR_WB_BUFF_SIZE )); +} +#define UFS_ATTRIBUTE (_name, _uname) \ static ssize_t _name##_show(struct device *dev, \ struct device_attribute *attr, char *buf) \
@@ -687,9 +693,12 @@ static ssize_t _name##_show(struct device *dev, \struct ufs_hba *hba =dev_get_drvdata (dev); \u32 value; \int ret; \ +u8 index =0 ; \ + if (ufshcd_is_wb_attrs(QUERY_ATTR_IDN##_uname)) \ + index =ufshcd_wb_get_query_index (hba); \pm_runtime_get_sync (hba->dev); \ ret =ufshcd_query_attr (hba,UPIU_QUERY_OPCODE_READ_ATTR , \ - QUERY_ATTR_IDN##_uname, 0, 0, &value); \ + QUERY_ATTR_IDN##_uname, index, 0, &value); \pm_runtime_put_sync (hba->dev); \if (ret) \return -EINVAL ; \
drivers/scsi/ufs/ufshcd.c +10 -6
@@ -5199,7 +5199,7 @@ static int ufshcd_wb_ctrl(struct ufs_hba *hba, bool enable)else opcode =UPIU_QUERY_OPCODE_CLEAR_FLAG ; - index =ufshcd_wb_get_flag_index (hba); + index =ufshcd_wb_get_query_index (hba); ret =ufshcd_query_flag_retry (hba, opcode,QUERY_FLAG_IDN_WB_EN , index,NULL );if (ret) {
@@ -5225,7 +5225,7 @@ static int ufshcd_wb_toggle_flush_during_h8(struct ufs_hba *hba, bool set)else val =UPIU_QUERY_OPCODE_CLEAR_FLAG ; - index =ufshcd_wb_get_flag_index (hba); + index =ufshcd_wb_get_query_index (hba);return ufshcd_query_flag_retry (hba, val,QUERY_FLAG_IDN_WB_BUFF_FLUSH_DURING_HIBERN8 , index,NULL );
@@ -5248,7 +5248,7 @@ static int ufshcd_wb_buf_flush_enable(struct ufs_hba *hba)if (!ufshcd_is_wb_allowed (hba) || hba->wb_buf_flush_enabled)return 0 ; - index =ufshcd_wb_get_flag_index (hba); + index =ufshcd_wb_get_query_index (hba); ret =ufshcd_query_flag_retry (hba,UPIU_QUERY_OPCODE_SET_FLAG ,QUERY_FLAG_IDN_WB_BUFF_FLUSH_EN , index,NULL );
@@ -5270,7 +5270,7 @@ static int ufshcd_wb_buf_flush_disable(struct ufs_hba *hba)if (!ufshcd_is_wb_allowed (hba) || !hba->wb_buf_flush_enabled)return 0 ; - index =ufshcd_wb_get_flag_index (hba); + index =ufshcd_wb_get_query_index (hba); ret =ufshcd_query_flag_retry (hba,UPIU_QUERY_OPCODE_CLEAR_FLAG ,QUERY_FLAG_IDN_WB_BUFF_FLUSH_EN , index,NULL );
@@ -5290,10 +5290,12 @@ static bool ufshcd_wb_presrv_usrspc_keep_vcc_on(struct ufs_hba *hba, {u32 cur_buf;int ret; +u8 index; + index =ufshcd_wb_get_query_index (hba); ret =ufshcd_query_attr_retry (hba,UPIU_QUERY_OPCODE_READ_ATTR ,QUERY_ATTR_IDN_CURR_WB_BUFF_SIZE , -0 ,0 , &cur_buf); + index,0 , &cur_buf);if (ret) {dev_err (hba->dev,"%s dCurWriteBoosterBufferSize read failed %d\n" , __func__, ret);
@@ -5316,6 +5318,7 @@ static bool ufshcd_wb_keep_vcc_on(struct ufs_hba *hba) {int ret;u32 avail_buf; +u8 index;if (!ufshcd_is_wb_allowed (hba))return false;
@@ -5330,9 +5333,10 @@ static bool ufshcd_wb_keep_vcc_on(struct ufs_hba *hba)* buffer (dCurrentWriteBoosterBufferSize). There's no point in * keeping vcc on when current buffer is empty. */ + index =ufshcd_wb_get_query_index (hba); ret =ufshcd_query_attr_retry (hba,UPIU_QUERY_OPCODE_READ_ATTR ,QUERY_ATTR_IDN_AVAIL_WB_BUFF_SIZE , -0 ,0 , &avail_buf); + index,0 , &avail_buf);if (ret) {dev_warn (hba->dev,"%s dAvailableWriteBoosterBufferSize read failed %d\n" , __func__, ret);
drivers/scsi/ufs/ufshcd.h +1 -1
@@ -868,7 +868,7 @@ static inline bool ufshcd_keep_autobkops_enabled_except_suspend(return hba->caps &UFSHCD_CAP_KEEP_AUTO_BKOPS_ENABLED_EXCEPT_SUSPEND ; } -static inline u8 ufshcd_wb_get_flag_index (struct ufs_hba *hba) +static inline u8 ufshcd_wb_get_query_index (struct ufs_hba *hba) {if (hba->dev_info.b_wb_buffer_type ==WB_BUF_MODE_LU_DEDICATED )return hba->dev_info.wb_dedicated_lu;
Signature · 1 line
2.18.0
PATCH v4 4/4 scsi: ufs: Fix WriteBooster flush during runtime suspend
In reply to Stanley ChuCurrently UFS host driver promises VCC supply if UFS device needs to do WriteBooster flush during runtime suspend.
However the UFS specification mentions,
"While the flushing operation is in progress, the device is in Active power mode."
Therefore UFS host driver needs to promise more: Keep UFS device as "Active power mode", otherwise UFS device shall not do any flush if device enters Sleep or PowerDown power mode. Similarly, the same promises shall be applied if device needs urgent BKOP during runtime suspend.
Fix this by not changing device power mode if WriteBooster flush or urgent BKOP is required in ufshcd_suspend().
Now, if device finishes its job but not resumed for a very long time, system will have unnecessary power drain because VCC is still supplied. A method to re-check the threshold of keeping VCC supply is required to fix the power drain. However, the threshold re-check needs to re-activate the link first because the decision depends on the latest device status.
So, also introduce a delayed work to force runtime resume after a certain delay during runtime suspend. This makes threshold re-check happen natually in the entrance of next runtime-suspend. The device can continue its WriteBooster flush or urgent BKOP jobs soon after resumed if device has no upcoming requests and link enters hibern8 state either by Auto-Hibern8 or hibern8 during clk-gating scheme. This solution not only prevents power drain but also makes as much use of time as possible for device's background jobs.
--- drivers/scsi/ufs/ufs.h | 2 +- drivers/scsi/ufs/ufshcd.c | 79 ++++++++++++++++++++++++++++----------- drivers/scsi/ufs/ufshcd.h | 1 + 3 files changed, 59 insertions(+), 23 deletions(-)
drivers/scsi/ufs/ufs.h +1 -1
@@ -574,7 +574,7 @@ struct ufs_dev_info {u32 d_ext_ufs_feature_sup;u8 b_wb_buffer_type;u32 d_wb_alloc_units; -bool keep_vcc_on; +bool b_rpm_dev_flush_capable;u8 b_presrv_uspc_en; };
drivers/scsi/ufs/ufshcd.c +57 -22
132 lines not on this page · raw message
drivers/scsi/ufs/ufshcd.h +1 -0
@@ -745,6 +745,7 @@ struct ufs_hba {struct request_queue *bsg_queue;bool wb_buf_flush_enabled;bool wb_enabled; +struct delayed_work rpm_dev_flush_recheck_work; };/* Returns true if clocks can be gated. Otherwise false */
Signature · 1 line
2.18.0
Quoted 21 lines · Stanley Chu
Hi,
This patch set fixes some WriteBooster issues and do small cleanup in UFS driver
v3 -> v4
- Squash patch [4] and [5] (Asutosh)
- Fix commit message in patch [4]v2 -> v3
- Introduce patch [5] to fix possible VCC power drain during runtime suspend (Asutosh)v1 -> v2
- Remove dummy new line in patch [4] (Asutosh)
- Add more limitation to allow WriteBooster flush during Hibern8 in runtime-suspend. Now the device power mode is kept as Active power mode only if link is put in Hibern8 or Auto-Hibern8 is enabled during runtime-suspend (Asutosh)Stanley Chu (4):
scsi: ufs: Remove unnecessary memset fordev_info
scsi: ufs: Allow WriteBooster on UFS 2.2 devices
scsi: ufs: Fix index of attributes query for WriteBooster feature
scsi: ufs: Fix WriteBooster flush during runtime suspend
Quoted 6 lines
drivers/scsi/ufs/ufs-sysfs.c | 13 ++++- drivers/scsi/ufs/ufs.h | 2 +- drivers/scsi/ufs/ufshcd.c | 99 +++++++++++++++++++++++++----------- drivers/scsi/ufs/ufshcd.h | 3 +- 4 files changed, 82 insertions(+), 35 deletions(-)
This set looks good to me.
Signature · 2 lines
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum, Linux Foundation Collaborative Project
Martin K. Petersen
AppliedQuoted 10 lines · Stanley Chu
This patch set fixes some WriteBooster issues and do small cleanup in UFS driver
v3 -> v4
- Squash patch [4] and [5] (Asutosh)
- Fix commit message in patch [4]v2 -> v3
- Introduce patch [5] to fix possible VCC power drain during runtime suspend (Asutosh)[...]
Applied to 5.8/scsi-queue, thanks!
[1/4] scsi: ufs: Remove unnecessary memset for dev_info
https://git.kernel.org/mkp/scsi/c/3a66ae512b09 [2/4] scsi: ufs: Allow WriteBooster on UFS 2.2 devices https://git.kernel.org/mkp/scsi/c/c7cee3e746a5 [3/4] scsi: ufs: Fix index of attributes query for WriteBooster feature https://git.kernel.org/mkp/scsi/c/e31011ab3709 [4/4] scsi: ufs: Fix WriteBooster flush during runtime suspend https://git.kernel.org/mkp/scsi/c/51dd905bd2f6
Signature · 6 lines
Martin K. Petersen Oracle Linux Engineering _______________________________________________ Linux-mediatek mailing list [email protected] http://lists.infradead.org/mailman/listinfo/linux-mediatek