scsi: ufs: change the clock scaling polling period and up threshold

We have noticed that UFS load based clock scaling is ramping up to highest
frequency during low power usecases but never scales back to lower
frequency during the remaining usecase run period. This increases the
oveall power consumption for a given low power usecase. We analyzed UFS
data transfer pattern for different low power usecases and updated clock
scaling polling period & up threshold which helps with power numbers
without affecting performance numbers.

Change-Id: I74cf8a1f07d1b1a0ac112f28fc98a8a82cac1d28
Signed-off-by: Subhash Jadavani <subhashj@codeaurora.org>
This commit is contained in:
Subhash Jadavani 2017-10-12 14:32:35 -07:00 committed by Timi
parent c5e11ae58d
commit 33f0ce8ba8

View file

@ -389,8 +389,8 @@ static int ufshcd_devfreq_get_dev_status(struct device *dev,
#if IS_ENABLED(CONFIG_DEVFREQ_GOV_SIMPLE_ONDEMAND)
static struct devfreq_simple_ondemand_data ufshcd_ondemand_data = {
.upthreshold = 35,
.downdifferential = 30,
.upthreshold = 70,
.downdifferential = 65,
.simple_scaling = 1,
};
@ -400,7 +400,7 @@ static void *gov_data;
#endif
static struct devfreq_dev_profile ufs_devfreq_profile = {
.polling_ms = 40,
.polling_ms = 60,
.target = ufshcd_devfreq_target,
.get_dev_status = ufshcd_devfreq_get_dev_status,
};