Looks like I am missing the obvious and sorry for the noise in advance.
But I couldn't find any code that parses the "cooling-{min|max}-level" DT
bindings in the kernel. Yeah, almost every ARM platform have these properties
set for their CPU nodes in DT, but I don't see how these are getting used.
I even tried to remove them for my hikey platform and everything worked as if
nothing has changed (which I was expecting anyway). The deal is that the
->get_max_state() callback of the cooling drivers are getting called to get the
range at runtime and none of them refers to these bindings.
Removing code is always fun and I would be happy to post a series to clean
things up if everyone agrees. Please let me know if my understanding is correct
and if it would be fine to remove these bindings completely.
Thanks.
--
viresh
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
