From: Viresh Kumar <viresh.kumar@linaro.org>
To: Chanwoo Choi <cw00.choi@samsung.com>
Cc: Hsin-Yi Wang <hsinyi@chromium.org>,
"Viresh Kumar )" <vireshk@kernel.org>, Nishanth Menon <nm@ti.com>,
Stephen Boyd <sboyd@kernel.org>,
linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org,
"andrew-sh . cheng" <andrew-sh.cheng@mediatek.com>
Subject: Re: [PATCH] opp: of: Allow lazy-linking of required-opps to non genpd
Date: Thu, 17 Jun 2021 09:03:51 +0530 [thread overview]
Message-ID: <20210617033351.44pxdpjicm62byuh@vireshk-i7> (raw)
In-Reply-To: <742b2623-e8ff-db1f-9168-bdbde98110dd@samsung.com>
On 17-06-21, 10:13, Chanwoo Choi wrote:
> The devfreq driver(exynos-bus.c) has used the dev_pm_opp_set_rate()
> and used the passive governor without the required-opp property.
Which is fine.
> I have a plan to use the required-opp property
> between devfreq drivers (exynos-bus.c) with dev_pm_opp_set_rate().
>
> I'll support them on later if this approach doesn't break the any
> rule of required-opp property.
You will be required to make some changes in core for that I am
afraid. It won't work automatically.
--
viresh
next prev parent reply other threads:[~2021-06-17 3:33 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-16 5:33 [PATCH] opp: of: Allow lazy-linking of required-opps to non genpd Hsin-Yi Wang
2021-06-16 5:58 ` Viresh Kumar
2021-06-16 6:25 ` Hsin-Yi Wang
2021-06-16 7:09 ` Viresh Kumar
2021-06-16 7:55 ` Viresh Kumar
2021-06-16 8:47 ` Chanwoo Choi
2021-06-16 9:09 ` Viresh Kumar
2021-06-16 9:20 ` Hsin-Yi Wang
2021-06-17 1:13 ` Chanwoo Choi
2021-06-17 3:33 ` Viresh Kumar [this message]
2021-06-17 4:09 ` Chanwoo Choi
2021-06-17 4:00 ` Viresh Kumar
2021-06-17 4:27 ` Chanwoo Choi
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20210617033351.44pxdpjicm62byuh@vireshk-i7 \
--to=viresh.kumar@linaro.org \
--cc=andrew-sh.cheng@mediatek.com \
--cc=cw00.choi@samsung.com \
--cc=hsinyi@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=nm@ti.com \
--cc=sboyd@kernel.org \
--cc=vireshk@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).