[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAJMQK-ihjnTWXVuKZXE=cX2TpVaFMTreZ7fdieWm7PRbB8byxg@mail.gmail.com>
Date: Thu, 28 Jan 2021 13:05:02 +0800
From: Hsin-Yi Wang <hsinyi@...omium.org>
To: Viresh Kumar <viresh.kumar@...aro.org>
Cc: Sibi Sankar <sibis@...eaurora.org>,
Saravana Kannan <saravanak@...gle.com>,
MyungJoo Ham <myungjoo.ham@...sung.com>,
Kyungmin Park <kyungmin.park@...sung.com>,
Chanwoo Choi <cw00.choi@...sung.com>,
Viresh Kumar <vireshk@...nel.org>, Nishanth Menon <nm@...com>,
Stephen Boyd <sboyd@...nel.org>,
"Rafael J. Wysocki" <rjw@...ysocki.net>,
Android Kernel Team <kernel-team@...roid.com>,
Linux PM <linux-pm@...r.kernel.org>,
lkml <linux-kernel@...r.kernel.org>,
"Andrew-sh.Cheng" <andrew-sh.cheng@...iatek.com>
Subject: Re: [PATCH v3 3/5] OPP: Improve require-opps linking
On Thu, Jan 28, 2021 at 12:13 PM Viresh Kumar <viresh.kumar@...aro.org> wrote:
>
> On 27-01-21, 22:40, Hsin-Yi Wang wrote:
> > Hi Viresh,
> >
> > I tested this patch with devfreq passive governor[1] and mt8183
> > cci[2]. It's also working as expected.
>
> I hope I can add your Tested-by for the patch then, right ?
>
Yes, thanks!
Tested-by: Hsin-Yi Wang <hsinyi@...omium.org>
> > [1] https://patchwork.kernel.org/project/linux-pm/cover/20190724014222.110767-1-saravanak@google.com/
> > (patch 2,4,5)
> > [2] https://patchwork.kernel.org/project/linux-mediatek/cover/1594348284-14199-1-git-send-email-andrew-sh.cheng@mediatek.com/
> >
> > In my testing case, required_opp_table is not genpd case (mt8183 cci
> > is not genpd), so I remove the following constraint. Does that make
> > sense to you?
> >
> > @@ -377,13 +377,6 @@ static void lazy_link_required_opp_table(struct
> > opp_table *new_table)
> > struct dev_pm_opp *opp;
> > int i, ret;
> >
> > - /*
> > - * We only support genpd's OPPs in the "required-opps" for now,
> > - * as we don't know much about other cases.
> > - */
> > - if (!new_table->is_genpd)
> > - return;
> > -
> > mutex_lock(&opp_table_lock);
>
> We will perhaps need more changes than that, but those should be done
> separately when you try to add a user for the same.
>
Ack.
> --
> viresh
Powered by blists - more mailing lists