On Thu, Nov 24, 2016 at 10:37:24AM +0530, Viresh Kumar wrote:
On 23-11-16, 12:29, Mark Brown wrote:
No, of course not. That would be completely incoherent, there would be no way for anything to use the data if the values can just be in any random order.
With the current implementation in this patchset, the order in which entries are present in the OPP node is _assumed_ to be known to the platform specific code, which will pass it on to the OPP core with some callbacks. So the order will not be completely random.
What we're reviewing here is the DT binding and the DT binding explicitly said the order doesn't matter. The DT binding is OS neutral so it needs to make sense without the code.
The "platform driver bindings" bit of this is very important here. This is a generic binding that is going to be used by platform specific drivers (as I understand it).
There is no platform specific binding here.
It seems like we're going to need one for this to be a comprehensible binding.
We can either get this information from DT (somehow) or hardcode it in platform specific code. This patch provided infrastructure for the later one.
If we indeed want to get this information from the DT then there are two options:
Why would we want to get it from DT when we can't get half the other information we need to make the data useful from DT?