[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200509093716.21010-1-stanley.chu@mediatek.com>
Date: Sat, 9 May 2020 17:37:12 +0800
From: Stanley Chu <stanley.chu@...iatek.com>
To: <linux-scsi@...r.kernel.org>, <martin.petersen@...cle.com>,
<avri.altman@....com>, <alim.akhtar@...sung.com>,
<jejb@...ux.ibm.com>, <asutoshd@...eaurora.org>
CC: <beanhuo@...ron.com>, <cang@...eaurora.org>,
<matthias.bgg@...il.com>, <bvanassche@....org>,
<linux-mediatek@...ts.infradead.org>,
<linux-arm-kernel@...ts.infradead.org>,
<linux-kernel@...r.kernel.org>, <kuohong.wang@...iatek.com>,
<peter.wang@...iatek.com>, <chun-hung.wu@...iatek.com>,
<andy.teng@...iatek.com>, Stanley Chu <stanley.chu@...iatek.com>
Subject: [PATCH v2 0/4] scsi: ufs: allow customizable WriteBooster flush policy
Hi,
This patch set tries to allow vendors to modify the WriteBooster flush policy.
In the same time, collect all customizable parameters to an unified structure to make UFS driver more clean.
v1 -> v2:
- Squash patch [3] and [4]
- Remove a dummy "new line" in patch [3]
- Fix commit message in patch [3]
Stanley Chu (4):
scsi: ufs: introduce ufs_hba_variant_params to collect customizable
parameters
scsi: ufs-mediatek: change the way to use customizable parameters
scsi: ufs: customize flush threshold for WriteBooster
scsi: ufs-mediatek: customize WriteBooster flush policy
drivers/scsi/ufs/ufs-mediatek.c | 5 ++--
drivers/scsi/ufs/ufs.h | 5 +---
drivers/scsi/ufs/ufshcd.c | 45 ++++++++++++++-------------------
drivers/scsi/ufs/ufshcd.h | 9 ++++++-
4 files changed, 31 insertions(+), 33 deletions(-)
--
2.18.0
Powered by blists - more mailing lists