From: Rob Herring <robh@kernel.org>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: Rafael Wysocki <rjw@rjwysocki.net>,
Viresh Kumar <vireshk@kernel.org>, Nishanth Menon <nm@ti.com>,
Stephen Boyd <sboyd@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
linux-pm@vger.kernel.org,
Vincent Guittot <vincent.guittot@linaro.org>,
devicetree@vger.kernel.org, Ulf Hansson <ulf.hansson@linaro.org>
Subject: Re: [PATCH V2 resend] PM / OPP: dt-bindings: Make "opp-hz" optional for power domains
Date: Tue, 8 May 2018 10:42:07 -0500 [thread overview]
Message-ID: <20180508154207.GA27069@rob-hp-laptop> (raw)
In-Reply-To: <525112ef4e6148d8fc46d92c0554bd516e24952f.1525750390.git.viresh.kumar@linaro.org>
On Tue, May 08, 2018 at 09:04:42AM +0530, Viresh Kumar wrote:
> The "opp-hz" property is not relevant across all the devices that use
> the OPP tables now. For example, for a power domain a frequency value
> wouldn't mean anything. Though they must have another property, which
> may be implementation defined, which uniquely identifies the OPP nodes.
>
> Make "opp-hz" optional for such devices.
>
> Signed-off-by: Viresh Kumar <viresh.kumar@linaro.org>
> Reviewed-by: Ulf Hansson <ulf.hansson@linaro.org>
> ---
> Resending to get Ack from Rob.
>
> Documentation/devicetree/bindings/opp/opp.txt | 5 ++++-
> 1 file changed, 4 insertions(+), 1 deletion(-)
Reviewed-by: Rob Herring <robh@kernel.org>
prev parent reply other threads:[~2018-05-08 15:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cover.1523273291.git.viresh.kumar@linaro.org>
[not found] ` <5c4a3a3fb4bf7320e592aabf582bfb6bdec4ee69.1523273291.git.viresh.kumar@linaro.org>
2018-05-03 4:27 ` [PATCH V2 02/11] PM / OPP: dt-bindings: Make "opp-hz" optional for power domains Viresh Kumar
2018-05-08 3:34 ` [PATCH V2 resend] " Viresh Kumar
2018-05-08 15:42 ` Rob Herring [this message]
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=20180508154207.GA27069@rob-hp-laptop \
--to=robh@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=nm@ti.com \
--cc=rjw@rjwysocki.net \
--cc=sboyd@kernel.org \
--cc=ulf.hansson@linaro.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