From: Viresh Kumar <viresh.kumar@linaro.org>
To: Zhang Rui <rui.zhang@intel.com>, Eduardo Valentin <edubezval@gmail.com>
Cc: Vincent Guittot <vincent.guittot@linaro.org>,
linux-pm@vger.kernel.org, robh+dt@kernel.org,
devicetree@vger.kernel.org, daniel.lezcano@linaro.org,
Punit.Agrawal@arm.com, ionela.voinescu@arm.com
Subject: [Query] thermal: Who is using "cooling-{min|max}-level}" properties ?
Date: Wed, 7 Feb 2018 12:29:59 +0530 [thread overview]
Message-ID: <20180207065959.GN28462@vireshk-i7> (raw)
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
next reply other threads:[~2018-02-07 6:59 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-07 6:59 Viresh Kumar [this message]
2018-02-07 10:04 ` [Query] thermal: Who is using "cooling-{min|max}-level}" properties ? Daniel Lezcano
[not found] ` <c7bd6ed5-b93e-3a07-b4a2-4c3b1eef5fac-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
2018-02-07 10:24 ` Viresh Kumar
2018-02-07 10:45 ` Daniel Lezcano
2018-02-09 6:42 ` Viresh Kumar
2018-02-09 9:15 ` Daniel Lezcano
[not found] ` <539699c7-9509-dea2-2b31-c5f6749c99c4-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
2018-02-09 9:24 ` Viresh Kumar
2018-02-09 12:14 ` Daniel Lezcano
[not found] ` <5722441d-c8be-4d29-fab7-28b4e5716961-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
2018-02-12 6:10 ` Viresh Kumar
2018-02-12 8:39 ` Daniel Lezcano
2018-02-12 8:52 ` Viresh Kumar
2018-02-12 9:52 ` Daniel Lezcano
2018-02-12 10:17 ` 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=20180207065959.GN28462@vireshk-i7 \
--to=viresh.kumar@linaro.org \
--cc=Punit.Agrawal@arm.com \
--cc=daniel.lezcano@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=edubezval@gmail.com \
--cc=ionela.voinescu@arm.com \
--cc=linux-pm@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=rui.zhang@intel.com \
--cc=vincent.guittot@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