From: Stephen Boyd <sboyd@codeaurora.org> To: Viresh Kumar <viresh.kumar@linaro.org> Cc: Rafael Wysocki <rjw@rjwysocki.net>, rob.herring@linaro.org, linaro-kernel@lists.linaro.org, linux-pm@vger.kernel.org, arnd.bergmann@linaro.org, nm@ti.com, broonie@kernel.org, mike.turquette@linaro.org, grant.likely@linaro.org, olof@lixom.net, Sudeep.Holla@arm.com, devicetree@vger.kernel.org, viswanath.puttagunta@linaro.org, l.stach@pengutronix.de, thomas.petazzoni@free-electrons.com, linux-arm-kernel@lists.infradead.org, ta.omasab@gmail.com, kesavan.abhilash@gmail.com, khilman@linaro.org, santosh.shilimkar@oracle.com Subject: Re: [PATCH V6 1/3] OPP: Add new bindings to address shortcomings of existing bindings Date: Tue, 2 Jun 2015 11:31:20 -0700 [thread overview] Message-ID: <20150602183120.GB24349@codeaurora.org> (raw) In-Reply-To: <96d49e7e6747c1a65c5f285d70600795126641cc.1432797343.git.viresh.kumar@linaro.org> On 05/28, Viresh Kumar wrote: > Current OPP (Operating performance point) device tree bindings have been > insufficient due to the inflexible nature of the original bindings. Over > time, we have realized that Operating Performance Point definitions and > usage is varied depending on the SoC and a "single size (just frequency, > voltage) fits all" model which the original bindings attempted and > failed. > > The proposed next generation of the bindings addresses by providing a > expandable binding for OPPs and introduces the following common > shortcomings seen with the original bindings: > > - Getting clock/voltage/current rails sharing information between CPUs. > Shared by all cores vs independent clock per core vs shared clock per > cluster. > > - Support for specifying current levels along with voltages. > > - Support for multiple regulators. > > - Support for turbo modes. > > - Other per OPP settings: transition latencies, disabled status, etc.? > > - Expandability of OPPs in future. > > This patch introduces new bindings "operating-points-v2" to get these problems > solved. Refer to the bindings for more details. > > We now have multiple versions of OPP binding and only one of them should > be used per device. > > Reviewed-by: Rob Herring <robh@kernel.org> > Signed-off-by: Viresh Kumar <viresh.kumar@linaro.org> > --- It looks pretty good. Just one question below on the regulator stuff. Also, is there already code written to handle these new bindings in the OPP library? If not, it would be good to write some to flush out any problems that may be lurking in actual implementation. > + > +Example 1: Single cluster Dual-core ARM cortex A9, switch DVFS states together. > + > +/ { > + cpus { > + #address-cells = <1>; > + #size-cells = <0>; > + > + cpu@0 { > + compatible = "arm,cortex-a9"; > + reg = <0>; > + next-level-cache = <&L2>; > + clocks = <&clk_controller 0>; > + clock-names = "cpu"; > + opp-supply = <&cpu_supply0>; opp-supply isn't mentioned anywhere. Is that intentional? Is it supposed to be cpu-supply still? It isn't clear to me from the previous discussion where this all ended up, but I'm not sure how the in-kernel API is going to match up regulators with OPPs. I mean, how are we going to ask the OPP library what the min/max/target voltage is at a particular frequency when we have multiple regulators? Is that some string based interface? dev_pm_opp_get_voltage(name, &target, &min, &max); Or a regulator pointer interface? dev_pm_opp_get_voltage(regulator, &target, &min, &max); Or something else? Does this mean the OPP library is going to get the CPU device to request the opp-supply from the CPU node? Furthermore, why don't we care about opp-clocks? Are clocks somehow special? -- Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, a Linux Foundation Collaborative Project
WARNING: multiple messages have this Message-ID (diff)
From: sboyd@codeaurora.org (Stephen Boyd) To: linux-arm-kernel@lists.infradead.org Subject: [PATCH V6 1/3] OPP: Add new bindings to address shortcomings of existing bindings Date: Tue, 2 Jun 2015 11:31:20 -0700 [thread overview] Message-ID: <20150602183120.GB24349@codeaurora.org> (raw) In-Reply-To: <96d49e7e6747c1a65c5f285d70600795126641cc.1432797343.git.viresh.kumar@linaro.org> On 05/28, Viresh Kumar wrote: > Current OPP (Operating performance point) device tree bindings have been > insufficient due to the inflexible nature of the original bindings. Over > time, we have realized that Operating Performance Point definitions and > usage is varied depending on the SoC and a "single size (just frequency, > voltage) fits all" model which the original bindings attempted and > failed. > > The proposed next generation of the bindings addresses by providing a > expandable binding for OPPs and introduces the following common > shortcomings seen with the original bindings: > > - Getting clock/voltage/current rails sharing information between CPUs. > Shared by all cores vs independent clock per core vs shared clock per > cluster. > > - Support for specifying current levels along with voltages. > > - Support for multiple regulators. > > - Support for turbo modes. > > - Other per OPP settings: transition latencies, disabled status, etc.? > > - Expandability of OPPs in future. > > This patch introduces new bindings "operating-points-v2" to get these problems > solved. Refer to the bindings for more details. > > We now have multiple versions of OPP binding and only one of them should > be used per device. > > Reviewed-by: Rob Herring <robh@kernel.org> > Signed-off-by: Viresh Kumar <viresh.kumar@linaro.org> > --- It looks pretty good. Just one question below on the regulator stuff. Also, is there already code written to handle these new bindings in the OPP library? If not, it would be good to write some to flush out any problems that may be lurking in actual implementation. > + > +Example 1: Single cluster Dual-core ARM cortex A9, switch DVFS states together. > + > +/ { > + cpus { > + #address-cells = <1>; > + #size-cells = <0>; > + > + cpu at 0 { > + compatible = "arm,cortex-a9"; > + reg = <0>; > + next-level-cache = <&L2>; > + clocks = <&clk_controller 0>; > + clock-names = "cpu"; > + opp-supply = <&cpu_supply0>; opp-supply isn't mentioned anywhere. Is that intentional? Is it supposed to be cpu-supply still? It isn't clear to me from the previous discussion where this all ended up, but I'm not sure how the in-kernel API is going to match up regulators with OPPs. I mean, how are we going to ask the OPP library what the min/max/target voltage is at a particular frequency when we have multiple regulators? Is that some string based interface? dev_pm_opp_get_voltage(name, &target, &min, &max); Or a regulator pointer interface? dev_pm_opp_get_voltage(regulator, &target, &min, &max); Or something else? Does this mean the OPP library is going to get the CPU device to request the opp-supply from the CPU node? Furthermore, why don't we care about opp-clocks? Are clocks somehow special? -- Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, a Linux Foundation Collaborative Project
next prev parent reply other threads:[~2015-06-02 18:31 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-05-28 7:29 [PATCH V6 0/3] OPP: Introduce OPP (V2) bindings Viresh Kumar 2015-05-28 7:29 ` Viresh Kumar 2015-05-28 7:29 ` [PATCH V6 1/3] OPP: Add new bindings to address shortcomings of existing bindings Viresh Kumar 2015-05-28 7:29 ` Viresh Kumar 2015-06-02 18:31 ` Stephen Boyd [this message] 2015-06-02 18:31 ` Stephen Boyd [not found] ` <20150602183120.GB24349-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org> 2015-06-02 19:14 ` Mark Brown 2015-06-02 19:14 ` Mark Brown 2015-06-03 4:40 ` Viresh Kumar 2015-06-03 4:40 ` Viresh Kumar 2015-05-28 7:29 ` [PATCH V6 2/3] OPP: Allow multiple OPP tables to be passed via DT Viresh Kumar 2015-05-28 7:29 ` Viresh Kumar 2015-05-28 7:29 ` [PATCH V6 3/3] OPP: Add binding for 'opp-suspend' Viresh Kumar 2015-05-28 7:29 ` 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=20150602183120.GB24349@codeaurora.org \ --to=sboyd@codeaurora.org \ --cc=Sudeep.Holla@arm.com \ --cc=arnd.bergmann@linaro.org \ --cc=broonie@kernel.org \ --cc=devicetree@vger.kernel.org \ --cc=grant.likely@linaro.org \ --cc=kesavan.abhilash@gmail.com \ --cc=khilman@linaro.org \ --cc=l.stach@pengutronix.de \ --cc=linaro-kernel@lists.linaro.org \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=linux-pm@vger.kernel.org \ --cc=mike.turquette@linaro.org \ --cc=nm@ti.com \ --cc=olof@lixom.net \ --cc=rjw@rjwysocki.net \ --cc=rob.herring@linaro.org \ --cc=santosh.shilimkar@oracle.com \ --cc=ta.omasab@gmail.com \ --cc=thomas.petazzoni@free-electrons.com \ --cc=viresh.kumar@linaro.org \ --cc=viswanath.puttagunta@linaro.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.