All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Boyd <sboyd@codeaurora.org>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: Rafael Wysocki <rjw@rjwysocki.net>,
	robh+dt@kernel.org, lee.jones@linaro.org,
	linaro-kernel@lists.linaro.org, linux-pm@vger.kernel.org,
	mark.rutland@arm.com, pawel.moll@arm.com,
	ijc+devicetree@hellion.org.uk, galak@codeaurora.org, nm@ti.com,
	devicetree@vger.kernel.org,
	open list <linux-kernel@vger.kernel.org>,
	"Rafael J. Wysocki" <rafael.j.wysocki@intel.com>
Subject: Re: [PATCH 1/3] PM / OPP: Add "opp-supported-hw" binding
Date: Fri, 30 Oct 2015 14:49:07 -0700	[thread overview]
Message-ID: <20151030214907.GJ19782@codeaurora.org> (raw)
In-Reply-To: <2d52388bd7d3cc546ac3ab5afeb47bfcb3012213.1446167359.git.viresh.kumar@linaro.org>

On 10/30, Viresh Kumar wrote:
> +- opp-supported-hw: User defined array containing a hierarchy of hardware
> +  version numbers, supported by the OPP. For example: a platform with hierarchy
> +  of three levels of versions (A, B and C), this field should be like <X Y Z>,
> +  where X corresponds to Version hierarchy A, Y corresponds to version hierarchy
> +  B and Z corresponds to version hierarchy C.
> +
> +  Each level of hierarchy is represented by a 32 bit value, and so there can be
> +  only 32 different supported version per hierarchy. i.e. 1 bit per version. A
> +  value of 0xFFFFFFFF will enable the OPP for all versions for that hierarchy
> +  level. And a value of 0x00000000 will disable the OPP completely, and so we
> +  never want that to happen.

I suppose if you wanted to have 64 possible combinations of some
attribute you would just extend it to two 32 bit numbers in
sequence? I don't see the limitation here, and hopefully there
isn't a limitation so that we can specify sufficiently large
numbers with more bits if we need to.

-- 
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project

  reply	other threads:[~2015-10-30 21:49 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-30  1:25 [PATCH 0/3] PM / OPP: opp-supported-hw and <prop>-name bindings Viresh Kumar
     [not found] ` <cover.1446167359.git.viresh.kumar-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
2015-10-30  1:25   ` [PATCH 1/3] PM / OPP: Add "opp-supported-hw" binding Viresh Kumar
2015-10-30  1:25     ` Viresh Kumar
2015-10-30 21:49     ` Stephen Boyd [this message]
2015-10-31  2:16       ` Viresh Kumar
2015-11-02 19:21         ` Stephen Boyd
2015-11-03  2:12           ` Viresh Kumar
2015-11-04 22:10             ` Stephen Boyd
2015-11-04 22:10               ` Stephen Boyd
2015-11-02 16:07       ` Viresh Kumar
2015-10-30 22:18     ` Stephen Boyd
     [not found]       ` <20151030221826.GM19782-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
2015-10-31  2:20         ` Viresh Kumar
2015-10-31  2:20           ` Viresh Kumar
2015-11-02 15:13           ` Rob Herring
2015-11-02 16:08             ` Viresh Kumar
2015-11-02 19:20           ` Stephen Boyd
2015-11-02 19:20             ` Stephen Boyd
2015-11-03  2:29       ` Viresh Kumar
2015-11-04 22:08         ` Stephen Boyd
2015-10-30  1:25 ` [PATCH 2/3] PM / OPP: Add {opp-microvolt|opp-microamp|turbo-mode|opp-suspend}-<name> binding Viresh Kumar
2015-10-30  1:25   ` Viresh Kumar
2015-10-30 21:54   ` Stephen Boyd
2015-10-30  1:25 ` [PATCH 3/3] PM / OPP: Remove 'operating-points-names' binding Viresh Kumar
2015-10-30  1:25   ` Viresh Kumar
2015-10-30 21:54   ` Stephen Boyd
2015-10-30 17:26 ` [PATCH 0/3] PM / OPP: opp-supported-hw and <prop>-name bindings Rob Herring
2015-10-31  2:41   ` 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=20151030214907.GJ19782@codeaurora.org \
    --to=sboyd@codeaurora.org \
    --cc=devicetree@vger.kernel.org \
    --cc=galak@codeaurora.org \
    --cc=ijc+devicetree@hellion.org.uk \
    --cc=lee.jones@linaro.org \
    --cc=linaro-kernel@lists.linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=nm@ti.com \
    --cc=pawel.moll@arm.com \
    --cc=rafael.j.wysocki@intel.com \
    --cc=rjw@rjwysocki.net \
    --cc=robh+dt@kernel.org \
    --cc=viresh.kumar@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 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.