From: Bjorn Andersson <bjorn.andersson@linaro.org>
To: Sibi Sankar <sibis@codeaurora.org>
Cc: Viresh Kumar <viresh.kumar@linaro.org>,
Rajendra Nayak <rnayak@codeaurora.org>,
Georgi Djakov <georgi.djakov@linaro.org>,
vireshk@kernel.org, sboyd@kernel.org, nm@ti.com,
robh+dt@kernel.org, mark.rutland@arm.com, rjw@rjwysocki.net,
jcrouse@codeaurora.org, vincent.guittot@linaro.org,
amit.kucheria@linaro.org, seansw@qti.qualcomm.com,
daidavid1@codeaurora.org, evgreen@chromium.org,
linux-pm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-arm-msm@vger.kernel.org
Subject: Re: [PATCH v2 1/5] dt-bindings: opp: Introduce bandwidth-MBps bindings
Date: Wed, 24 Apr 2019 21:24:50 -0700 [thread overview]
Message-ID: <20190425042450.GB2867@tuxbook-pro> (raw)
Message-ID: <20190425042450.a5BSM9DbmAOTmhpsBBgP8reDdjoGGLeYWc2WhwCXKpc@z> (raw)
In-Reply-To: <dd6f055c-e7df-13e8-72aa-2973d3c664d0@codeaurora.org>
On Wed 24 Apr 02:00 PDT 2019, Sibi Sankar wrote:
> On 4/24/19 12:19 PM, Viresh Kumar wrote:
> > On 24-04-19, 12:16, Rajendra Nayak wrote:
> > > On 4/23/2019 6:58 PM, Georgi Djakov wrote:
[..]
> > > > +/ {
> > > > + cpus {
> > > > + CPU0: cpu@0 {
> > > > + compatible = "arm,cortex-a53", "arm,armv8";
> > > > + ...
> > > > + operating-points-v2 = <&cpu_opp_table>;
> > > > + /* path between CPU and DDR memory and CPU and L3 */
> > > > + interconnects = <&noc MASTER_CPU &noc SLAVE_DDR>,
> > > > + <&noc MASTER_CPU &noc SLAVE_L3>;
> > > > + };
> > > > + };
> > > > +
> > > > + cpu_opp_table: cpu_opp_table {
> > > > + compatible = "operating-points-v2";
> > > > + opp-shared;
> > > > +
> > > > + opp-200000000 {
> > > > + opp-hz = /bits/ 64 <200000000>;
> > > > + /* CPU<->DDR bandwidth: 457 MB/s average, 1525 MB/s peak */
> > > > + * CPU<->L3 bandwidth: 914 MB/s average, 3050 MB/s peak */
> > > > + bandwidth-MBps = <457 1525>, <914 3050>;
> > >
> > > Should this also have a bandwidth-MBps-name perhaps? Without that I guess we assume
> > > the order in which we specify the interconnects is the same as the order here?
> >
> > Right, so I suggested not to add the -name property and to rely on the
> > order. Though I missed that he hasn't mentioned the order thing here.
>
> by skipping names, aren't we forced to specify all the specified paths
> bandwidths for each opp even if it is redundant? i.e if the first/second
> icc path doesn't have to change across a few opps but if the other path
> does need to change this scheme would force it to be included and will
> try to set the first/second path again.
>
>
> e.g: Here the first path does not have to change across these two opps
> but have to specified nonetheless since we omit names.
>
If this is a pair in the middle of the list, we would either have to
define how non-specified values are inherited from neighbouring nodes or
you will get different behavior if you're coming from a lower or a
higher opp.
I think it looks clearer to just be explicit and repeat the values.
Regards,
Bjorn
> + opp-1200000000 {
> + opp-hz = /bits/ 64 <1200000000>;
> + bandwidth-MBps = <457 1525>, <914 3050>;
> + };
> + opp-1400000000 {
> + opp-hz = /bits/ 64 <1400000000>;
> + bandwidth-MBps = <457 1525>, <1828 6102>;
> + };
next prev parent reply other threads:[~2019-04-25 4:24 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-23 13:28 [PATCH v2 0/5] Introduce OPP bandwidth bindings Georgi Djakov
2019-04-23 13:28 ` Georgi Djakov
2019-04-23 13:28 ` [PATCH v2 1/5] dt-bindings: opp: Introduce bandwidth-MBps bindings Georgi Djakov
2019-04-23 13:28 ` Georgi Djakov
2019-04-24 5:33 ` Viresh Kumar
2019-04-24 5:33 ` Viresh Kumar
2019-04-24 6:46 ` Rajendra Nayak
2019-04-24 6:46 ` Rajendra Nayak
2019-04-24 6:49 ` Viresh Kumar
2019-04-24 6:49 ` Viresh Kumar
2019-04-24 9:00 ` Sibi Sankar
2019-04-24 9:00 ` Sibi Sankar
2019-04-24 9:05 ` Viresh Kumar
2019-04-24 9:05 ` Viresh Kumar
2019-04-25 4:24 ` Bjorn Andersson [this message]
2019-04-25 4:24 ` Bjorn Andersson
2019-04-24 8:44 ` Sibi Sankar
2019-04-24 8:44 ` Sibi Sankar
2019-04-23 13:28 ` [PATCH v2 2/5] interconnect: Add of_icc_get_by_index() helper function Georgi Djakov
2019-04-23 13:28 ` Georgi Djakov
2019-05-07 11:59 ` Sibi Sankar
2019-05-07 11:59 ` Sibi Sankar
2019-06-27 5:56 ` Sibi Sankar
2019-04-23 13:28 ` [PATCH v2 3/5] OPP: Add support for parsing the interconnect bandwidth Georgi Djakov
2019-04-23 13:28 ` Georgi Djakov
2019-04-24 5:52 ` Viresh Kumar
2019-04-24 5:52 ` Viresh Kumar
2019-06-27 6:27 ` Sibi Sankar
2019-04-23 13:28 ` [PATCH v2 4/5] OPP: Update the bandwidth on OPP frequency changes Georgi Djakov
2019-04-23 13:28 ` Georgi Djakov
2019-04-24 5:55 ` Viresh Kumar
2019-04-24 5:55 ` Viresh Kumar
2019-04-24 10:05 ` Sibi Sankar
2019-04-24 10:05 ` Sibi Sankar
2019-04-23 13:28 ` [PATCH v2 5/5] cpufreq: dt: Add support for interconnect bandwidth scaling Georgi Djakov
2019-04-23 13:28 ` Georgi Djakov
2019-06-01 2:12 ` [PATCH v2 0/5] Introduce OPP bandwidth bindings Saravana Kannan
2019-06-03 15:56 ` Jordan Crouse
2019-06-03 19:12 ` Saravana Kannan
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=20190425042450.GB2867@tuxbook-pro \
--to=bjorn.andersson@linaro.org \
--cc=amit.kucheria@linaro.org \
--cc=daidavid1@codeaurora.org \
--cc=devicetree@vger.kernel.org \
--cc=evgreen@chromium.org \
--cc=georgi.djakov@linaro.org \
--cc=jcrouse@codeaurora.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=nm@ti.com \
--cc=rjw@rjwysocki.net \
--cc=rnayak@codeaurora.org \
--cc=robh+dt@kernel.org \
--cc=sboyd@kernel.org \
--cc=seansw@qti.qualcomm.com \
--cc=sibis@codeaurora.org \
--cc=vincent.guittot@linaro.org \
--cc=viresh.kumar@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: 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).