[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <187f2f21e6ca55a9ab26a026f01dd893@codeaurora.org>
Date: Tue, 05 May 2020 02:01:25 +0530
From: Sibi Sankar <sibis@...eaurora.org>
To: Georgi Djakov <georgi.djakov@...aro.org>
Cc: vireshk@...nel.org, nm@...com, sboyd@...nel.org,
robh+dt@...nel.org, rjw@...ysocki.net, saravanak@...gle.com,
rnayak@...eaurora.org, bjorn.andersson@...aro.org,
vincent.guittot@...aro.org, jcrouse@...eaurora.org,
evgreen@...omium.org, linux-pm@...r.kernel.org,
devicetree@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v7 1/7] dt-bindings: opp: Introduce opp-peak-kBps and
opp-avg-kBps bindings
On 2020-04-24 21:23, Georgi Djakov wrote:
> From: Saravana Kannan <saravanak@...gle.com>
>
> Interconnects often quantify their performance points in terms of
> bandwidth. So, add opp-peak-kBps (required) and opp-avg-kBps (optional)
> to
> allow specifying Bandwidth OPP tables in DT.
>
> opp-peak-kBps is a required property that replaces opp-hz for Bandwidth
> OPP
> tables.
>
> opp-avg-kBps is an optional property that can be used in Bandwidth OPP
> tables.
>
Reviewed-by: Sibi Sankar <sibis@...eaurora.org>
> Signed-off-by: Saravana Kannan <saravanak@...gle.com>
> Signed-off-by: Georgi Djakov <georgi.djakov@...aro.org>
> ---
> v7:
> * I have dropped Rob's Reviewed-by, because of the minor change below:
> * In order to store the bandwidth values for multiple paths, the
> opp-peak-kBps and opp-avg-kBps are now defined as arrays of integers,
> instead of just integers.
> * Improved wording (Viresh)
...
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project.
Powered by blists - more mailing lists