From: Lukasz Luba <lukasz.luba@arm.com>
To: Daniel Lezcano <daniel.lezcano@linaro.org>
Cc: linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org,
rafael@kernel.org, quic_manafm@quicinc.com,
Amit Kucheria <amitk@kernel.org>, Zhang Rui <rui.zhang@intel.com>
Subject: Re: [PATCH 3/3] thermal/sysfs: Remove cooling device sysfs statistics
Date: Wed, 1 Jun 2022 16:33:20 +0100 [thread overview]
Message-ID: <be8395e3-98d7-7a8f-7153-c491b22d4463@arm.com> (raw)
In-Reply-To: <20220601151441.9128-3-daniel.lezcano@linaro.org>
Hi Daniel,
On 6/1/22 16:14, Daniel Lezcano wrote:
> The statistics are for debugging purpose and belong to debugfs rather
> than sysfs. As the previous changes introduced the same statistics in
> debugfs, those in sysfs are no longer needed and can be removed.
I just want to let you know that in current Android kernels we cannot
even compile the kernel with CONFIG_DEBUG_FS. I have this pain with
Energy Model there... Some vendors might see useful info via this
sysfs interface in bring-up of the SoC.
I don't know if there are user-space tools tracking this
information via sysfs. We probably should check that.
I agree that these statistics look more like debug info, rather than
something useful for control.
Furthermore, we have trace events for the cooling state changes, which
should be good enough for bring-up and experiments.
I don't have strong preferences here. I tend to agree to remove this
interface if there are no user-space tools using it.
Regards,
Lukasz
next prev parent reply other threads:[~2022-06-01 15:33 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-01 15:14 [PATCH 1/3] thermal/core: Encapsulate the set_cur_state function Daniel Lezcano
2022-06-01 15:14 ` [PATCH 2/3] thermal/debugfs: Add debugfs information Daniel Lezcano
2022-06-01 22:55 ` kernel test robot
2022-06-02 0:39 ` kernel test robot
2022-06-02 20:20 ` kernel test robot
2022-06-01 15:14 ` [PATCH 3/3] thermal/sysfs: Remove cooling device sysfs statistics Daniel Lezcano
2022-06-01 15:33 ` Lukasz Luba [this message]
2022-06-02 8:37 ` Daniel Lezcano
2022-06-02 9:16 ` Lukasz Luba
2022-06-02 19:02 ` Todd Kjos
2022-06-03 11:04 ` Daniel Lezcano
2022-06-24 6:02 ` Wei Wang
2022-06-28 15:26 ` Daniel Lezcano
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=be8395e3-98d7-7a8f-7153-c491b22d4463@arm.com \
--to=lukasz.luba@arm.com \
--cc=amitk@kernel.org \
--cc=daniel.lezcano@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=quic_manafm@quicinc.com \
--cc=rafael@kernel.org \
--cc=rui.zhang@intel.com \
/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
all inboxes | Powered by JetHome®