From: Viresh Kumar <viresh.kumar@linaro.org>
To: Nishanth Menon <nm@ti.com>
Cc: Rafael Wysocki <rjw@rjwysocki.net>,
rob.herring@linaro.org, arnd.bergmann@linaro.org,
broonie@kernel.org, mike.turquette@linaro.org,
sboyd@codeaurora.org, linaro-kernel@lists.linaro.org,
linux-pm@vger.kernel.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 V5 3/3] OPP: Add binding for 'opp-suspend'
Date: Thu, 21 May 2015 11:19:35 +0530 [thread overview]
Message-ID: <20150521054935.GG22904@linux> (raw)
In-Reply-To: <555D6DD3.7000404@ti.com>
On 21-05-15, 00:32, Nishanth Menon wrote:
> Why not just mark it as a property of an OPP rather than a phandle? just
> thinking that this might setup a precedence for future needs like
> "shutdown OPP" or "Reboot OPP" or something different that some other
> SoC might have..
AFAIU, a property should be present in the OPP if and only if any OPP
can set it. But in this case, only one OPP from the entire list can
set it. So, its more a property of the list rather than every OPP
within it. And then there wouldn't be any need to code that would
check bugs in dtbs where multiple OPPs have it set.
--
viresh
next prev parent reply other threads:[~2015-05-21 5:49 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-20 3:41 [PATCH V5 0/3] OPP: Introduce OPP (V2) bindings Viresh Kumar
2015-05-20 3:41 ` [PATCH V5 1/3] OPP: Redefine bindings to overcome shortcomings Viresh Kumar
2015-05-20 13:27 ` Rob Herring
[not found] ` <CAL_JsqKR0-TcBjCnoaLBR9M2wGHCOuO2KSyL+4U+dpTvHGzubQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-05-20 13:35 ` Viresh Kumar
2015-05-21 5:27 ` Nishanth Menon
2015-05-21 5:46 ` Viresh Kumar
2015-05-21 5:58 ` Nishanth Menon
2015-05-21 6:06 ` Viresh Kumar
2015-05-22 15:55 ` Rob Herring
[not found] ` <CAL_JsqKhpyLgh5_1jZ_u0OP7=Piw=pgqZdQJ0K4Rm7DQ5ve+gA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-05-26 5:20 ` Viresh Kumar
2015-05-26 5:14 ` Viresh Kumar
2015-05-20 3:41 ` [PATCH V5 2/3] OPP: Allow multiple OPP tables to be passed via DT Viresh Kumar
2015-05-21 5:34 ` Nishanth Menon
2015-05-21 5:50 ` Viresh Kumar
2015-05-26 4:51 ` Viresh Kumar
2015-05-20 3:41 ` [PATCH V5 3/3] OPP: Add binding for 'opp-suspend' Viresh Kumar
2015-05-21 5:32 ` Nishanth Menon
2015-05-21 5:49 ` Viresh Kumar [this message]
2015-05-21 6:04 ` Nishanth Menon
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=20150521054935.GG22904@linux \
--to=viresh.kumar@linaro.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=sboyd@codeaurora.org \
--cc=ta.omasab@gmail.com \
--cc=thomas.petazzoni@free-electrons.com \
--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: 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).