Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1259808
| From | Stephen Boyd <sboyd@codeaurora.org> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: [PATCH 1/3] PM / OPP: Add "opp-supported-hw" binding |
| Date | 2015-10-30 22:50 +0100 |
| Message-ID | <qppIB-2BU-5@gated-at.bofh.it> (permalink) |
| References | <qp6FY-7Nj-7@gated-at.bofh.it> <qp6FY-7Nj-11@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
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 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Back to linux.kernel | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
[PATCH 1/3] PM / OPP: Add "opp-supported-hw" binding Viresh Kumar <viresh.kumar@linaro.org> - 2015-10-30 02:30 +0100
Re: [PATCH 1/3] PM / OPP: Add "opp-supported-hw" binding Stephen Boyd <sboyd@codeaurora.org> - 2015-10-30 22:50 +0100
Re: [PATCH 1/3] PM / OPP: Add "opp-supported-hw" binding Viresh Kumar <viresh.kumar@linaro.org> - 2015-10-31 03:20 +0100
Re: [PATCH 1/3] PM / OPP: Add "opp-supported-hw" binding Stephen Boyd <sboyd@codeaurora.org> - 2015-11-02 20:30 +0100
Re: [PATCH 1/3] PM / OPP: Add "opp-supported-hw" binding Viresh Kumar <viresh.kumar@linaro.org> - 2015-11-03 03:20 +0100
Re: [PATCH 1/3] PM / OPP: Add "opp-supported-hw" binding Stephen Boyd <sboyd@codeaurora.org> - 2015-11-04 23:20 +0100
Re: [PATCH 1/3] PM / OPP: Add "opp-supported-hw" binding Viresh Kumar <viresh.kumar@linaro.org> - 2015-11-02 17:10 +0100
Re: [PATCH 1/3] PM / OPP: Add "opp-supported-hw" binding Stephen Boyd <sboyd@codeaurora.org> - 2015-10-30 23:20 +0100
Re: [PATCH 1/3] PM / OPP: Add "opp-supported-hw" binding Viresh Kumar <viresh.kumar@linaro.org> - 2015-10-31 03:30 +0100
Re: [PATCH 1/3] PM / OPP: Add "opp-supported-hw" binding Rob Herring <robh+dt@kernel.org> - 2015-11-02 16:20 +0100
Re: [PATCH 1/3] PM / OPP: Add "opp-supported-hw" binding Viresh Kumar <viresh.kumar@linaro.org> - 2015-11-02 17:10 +0100
Re: [PATCH 1/3] PM / OPP: Add "opp-supported-hw" binding Stephen Boyd <sboyd@codeaurora.org> - 2015-11-02 20:30 +0100
Re: [PATCH 1/3] PM / OPP: Add "opp-supported-hw" binding Viresh Kumar <viresh.kumar@linaro.org> - 2015-11-03 03:40 +0100
Re: [PATCH 1/3] PM / OPP: Add "opp-supported-hw" binding Stephen Boyd <sboyd@codeaurora.org> - 2015-11-04 23:10 +0100
csiph-web