diff options
| author | Stanley Chu <[email protected]> | 2020-12-08 21:56:34 +0800 |
|---|---|---|
| committer | Martin K. Petersen <[email protected]> | 2020-12-09 12:11:48 -0500 |
| commit | bd14bf0e4a084514aa62d24d2109e0f09a93822f (patch) | |
| tree | 5479a7f51f0667a18f4ad52235835277de90ffa3 /tools/perf/util/scripting-engines/trace-event-python.c | |
| parent | 5213dc7940e0aa4c094413e015790c4a310ef36c (diff) | |
scsi: ufs: Re-enable WriteBooster after device reset
UFS 3.1 specification mentions that the WriteBooster flags listed below
will be set to their default values, i.e. disabled, after power cycle or
any type of reset event. Thus we need to reset the flag variables kept in
struct hba to align with the device status and ensure that
WriteBooster-related functions are configured properly after device reset.
Without this fix, WriteBooster will not be enabled successfully after by
ufshcd_wb_ctrl() after device reset because hba->wb_enabled remains true.
Flags required to be reset to default values:
- fWriteBoosterEn: hba->wb_enabled
- fWriteBoosterBufferFlushEn: hba->wb_buf_flush_enabled
- fWriteBoosterBufferFlushDuringHibernate: No variable mapped
Link: https://lore.kernel.org/r/[email protected]
Fixes: 3d17b9b5ab11 ("scsi: ufs: Add write booster feature support")
Reviewed-by: Bean Huo <[email protected]>
Signed-off-by: Stanley Chu <[email protected]>
Signed-off-by: Martin K. Petersen <[email protected]>
Diffstat (limited to 'tools/perf/util/scripting-engines/trace-event-python.c')
0 files changed, 0 insertions, 0 deletions