Re: [PATCH v4 0/5] Add required-opps support to devfreq passive gov
From: Saravana Kannan
Date: Thu Jul 25 2019 - 11:01:26 EST
On Wed, Jul 24, 2019 at 7:30 PM Viresh Kumar <viresh.kumar@xxxxxxxxxx> wrote:
> On 23-07-19, 18:42, Saravana Kannan wrote:
> > The devfreq passive governor scales the frequency of a "child" device based
> > on the current frequency of a "parent" device (not parent/child in the
> > sense of device hierarchy). As of today, the passive governor requires one
> > of the following to work correctly:
> > 1. The parent and child device have the same number of frequencies
> > 2. The child device driver passes a mapping function to translate from
> > parent frequency to child frequency.
> > v3 -> v4:
> > - Fixed documentation comments
> > - Fixed order of functions in .h file
> > - Renamed the new xlate API
> > - Caused _set_required_opps() to fail if all required opps tables aren't
> > linked.
> We are already in the middle of a discussion for your previous version
> and I haven't said yet that I am happy with what you suggested just 2
> days back. Why send another version so soon ?
I wanted you to see how I addressed your comments. It didn't look like
you were going to make more comments on the code.
> The next merge window is
> also very far in time from now.
> Please wait for a few days before sending newer versions, I will
> continue discussion on the previous version only for now.