From: Viresh Kumar <viresh.kumar@linaro.org> To: ulf.hansson@linaro.org, Kevin Hilman <khilman@kernel.org>, robh+dt@kernel.org, Nishanth Menon <nm@ti.com>, "Rafael J. Wysocki" <rjw@rjwysocki.net>, Stephen Boyd <sboyd@codeaurora.org>, Viresh Kumar <vireshk@kernel.org> Cc: linux-pm@vger.kernel.org, Vincent Guittot <vincent.guittot@linaro.org>, rnayak@codeaurora.org, sudeep.holla@arm.com, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH V8 0/3] OPP: Allow OPP table to be used for power-domains Date: Wed, 3 Jan 2018 12:50:47 +0530 [thread overview] Message-ID: <20180103072047.GD15166@vireshk-i7> (raw) In-Reply-To: <cover.1513591822.git.viresh.kumar@linaro.org> On 18-12-17, 15:51, Viresh Kumar wrote: > Hi, > > Now that the performance state of PM domains are supported by the kernel > (merged in linux-next), I am trying once again to define the bindings > which we dropped until the code is merged first. > > Summary: > > Power-domains can also have their active states and this patchset > enhances the OPP binding to define those. > > The power domains can use the OPP bindings mostly as is. Though there > are some changes required to support special cases: > > - Allow "operating-points-v2" to contain multiple phandles for power > domain providers providing multiple domains. > > - A new property "required-opp" is added for the devices to specify the > minimum required OPP of the master domain or any other type of device. > > - Allow some of the OPP properties to accept magic values (firmware > dependent) as the OS doesn't know the real freq/voltage values. > > V7->V8: > - V7 1/2 divided into two patches. 1/3 is unchanged from V7. > - 2/3 renamed the property from "power-domain-opp" to "required-opp", as > suggested by Rob. > - Added Ulf's reviewed-by for 1/3 and 3/3. > > -- > viresh > > Viresh Kumar (3): > OPP: Allow OPP table to be used for power-domains > OPP: Introduce "required-opp" property > OPP: Allow "opp-hz" and "opp-microvolt" to contain magic values Discussions are still going on for the last commit, though the first two are already Acked by Rob and Ulf and are quite independent of the third one. Any objections to getting the first two merged for 4.16-rc1 ? I will send them to Rafael on Friday if no one objects. -- viresh
WARNING: multiple messages have this Message-ID (diff)
From: Viresh Kumar <viresh.kumar-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org> To: ulf.hansson-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org, Kevin Hilman <khilman-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>, robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org, Nishanth Menon <nm-l0cyMroinI0@public.gmane.org>, "Rafael J. Wysocki" <rjw-LthD3rsA81gm4RdzfppkhA@public.gmane.org>, Stephen Boyd <sboyd-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>, Viresh Kumar <vireshk-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org> Cc: linux-pm-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, Vincent Guittot <vincent.guittot-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>, rnayak-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org, sudeep.holla-5wv7dgnIgG8@public.gmane.org, devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org Subject: Re: [PATCH V8 0/3] OPP: Allow OPP table to be used for power-domains Date: Wed, 3 Jan 2018 12:50:47 +0530 [thread overview] Message-ID: <20180103072047.GD15166@vireshk-i7> (raw) In-Reply-To: <cover.1513591822.git.viresh.kumar-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org> On 18-12-17, 15:51, Viresh Kumar wrote: > Hi, > > Now that the performance state of PM domains are supported by the kernel > (merged in linux-next), I am trying once again to define the bindings > which we dropped until the code is merged first. > > Summary: > > Power-domains can also have their active states and this patchset > enhances the OPP binding to define those. > > The power domains can use the OPP bindings mostly as is. Though there > are some changes required to support special cases: > > - Allow "operating-points-v2" to contain multiple phandles for power > domain providers providing multiple domains. > > - A new property "required-opp" is added for the devices to specify the > minimum required OPP of the master domain or any other type of device. > > - Allow some of the OPP properties to accept magic values (firmware > dependent) as the OS doesn't know the real freq/voltage values. > > V7->V8: > - V7 1/2 divided into two patches. 1/3 is unchanged from V7. > - 2/3 renamed the property from "power-domain-opp" to "required-opp", as > suggested by Rob. > - Added Ulf's reviewed-by for 1/3 and 3/3. > > -- > viresh > > Viresh Kumar (3): > OPP: Allow OPP table to be used for power-domains > OPP: Introduce "required-opp" property > OPP: Allow "opp-hz" and "opp-microvolt" to contain magic values Discussions are still going on for the last commit, though the first two are already Acked by Rob and Ulf and are quite independent of the third one. Any objections to getting the first two merged for 4.16-rc1 ? I will send them to Rafael on Friday if no one objects. -- viresh -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2018-01-03 7:20 UTC|newest] Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top 2017-12-18 10:21 [PATCH V8 0/3] OPP: Allow OPP table to be used for power-domains Viresh Kumar 2017-12-18 10:21 ` Viresh Kumar 2017-12-18 10:21 ` [PATCH V8 1/3] " Viresh Kumar 2017-12-21 22:06 ` Rob Herring 2017-12-21 22:06 ` Rob Herring 2017-12-18 10:21 ` [PATCH V8 2/3] OPP: Introduce "required-opp" property Viresh Kumar 2017-12-18 10:21 ` Viresh Kumar 2017-12-20 8:23 ` Ulf Hansson 2017-12-20 8:26 ` Viresh Kumar 2017-12-21 22:26 ` Rob Herring 2017-12-21 22:26 ` Rob Herring 2017-12-22 5:28 ` Viresh Kumar 2017-12-18 10:21 ` [PATCH V8 3/3] OPP: Allow "opp-hz" and "opp-microvolt" to contain magic values Viresh Kumar 2017-12-26 20:29 ` Rob Herring 2017-12-26 20:29 ` Rob Herring 2017-12-27 8:56 ` Viresh Kumar 2017-12-27 8:56 ` Viresh Kumar 2017-12-27 21:54 ` Rob Herring 2017-12-27 21:54 ` Rob Herring 2017-12-28 4:37 ` Viresh Kumar 2017-12-28 4:37 ` Viresh Kumar 2017-12-29 0:32 ` Stephen Boyd 2017-12-29 0:32 ` Stephen Boyd 2017-12-29 4:58 ` Viresh Kumar 2017-12-29 4:58 ` Viresh Kumar 2018-01-05 22:19 ` Stephen Boyd 2018-01-05 22:19 ` Stephen Boyd 2018-01-08 4:16 ` Viresh Kumar 2018-01-08 4:16 ` Viresh Kumar 2018-01-10 2:54 ` Stephen Boyd 2018-01-10 2:54 ` Stephen Boyd 2018-01-10 5:37 ` Viresh Kumar 2018-01-10 5:37 ` Viresh Kumar 2018-01-13 0:46 ` Stephen Boyd 2018-01-13 0:46 ` Stephen Boyd 2018-01-02 6:05 ` Rajendra Nayak 2018-01-02 6:05 ` Rajendra Nayak 2018-01-02 6:33 ` Viresh Kumar 2018-01-02 6:33 ` Viresh Kumar 2018-01-03 7:20 ` Viresh Kumar [this message] 2018-01-03 7:20 ` [PATCH V8 0/3] OPP: Allow OPP table to be used for power-domains Viresh Kumar
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=20180103072047.GD15166@vireshk-i7 \ --to=viresh.kumar@linaro.org \ --cc=devicetree@vger.kernel.org \ --cc=khilman@kernel.org \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-pm@vger.kernel.org \ --cc=nm@ti.com \ --cc=rjw@rjwysocki.net \ --cc=rnayak@codeaurora.org \ --cc=robh+dt@kernel.org \ --cc=sboyd@codeaurora.org \ --cc=sudeep.holla@arm.com \ --cc=ulf.hansson@linaro.org \ --cc=vincent.guittot@linaro.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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.