[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20180424221409.GE18510@minitux>
Date: Tue, 24 Apr 2018 15:14:09 -0700
From: Bjorn Andersson <bjorn.andersson@...aro.org>
To: Subhash Jadavani <subhashj@...eaurora.org>
Cc: Vinayak Holikatti <vinholikatti@...il.com>,
"James E.J. Bottomley" <jejb@...ux.vnet.ibm.com>,
"Martin K. Petersen" <martin.petersen@...cle.com>,
MyungJoo Ham <myungjoo.ham@...sung.com>,
Kyungmin Park <kyungmin.park@...sung.com>,
Chanwoo Choi <cw00.choi@...sung.com>,
linux-scsi@...r.kernel.org, linux-pm@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-arm-msm@...r.kernel.org,
Vivek Gautam <vivek.gautam@...eaurora.org>,
linux-scsi-owner@...r.kernel.org
Subject: Re: [PATCH 3/3] scsi: ufs: Use freq table with devfreq
On Tue 24 Apr 15:08 PDT 2018, Subhash Jadavani wrote:
> On 2018-04-23 17:20, Bjorn Andersson wrote:
> > devfreq requires that the client operates on actual frequencies, not
> > only 0 and UMAX_INT and as such UFS brok with the introduction of
> > f1d981eaecf8 ("PM / devfreq: Use the available min/max frequency").
> >
> > This patch registers the frequencies of the first clock with devfreq and
> > use these to determine if we're trying to step up or down.
> >
[..]
>
> Looks good to me.
> Reviewed-by: Subhash Jadavani <subhashj@...eaurora.org>
>
Thanks Subhash. Unfortunately I need to respin this to register the opp
table based on our freq table, so there will be a v2 of this soon.
Regards,
Bjorn
Powered by blists - more mailing lists