From: Daniel Lezcano <daniel.lezcano@linaro.org>
To: "Rafael J. Wysocki" <rafael@kernel.org>
Cc: "Rafael J. Wysocki" <rjw@rjwysocki.net>,
Linux PM <linux-pm@vger.kernel.org>,
Linux ACPI <linux-acpi@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Lukasz Luba <lukasz.luba@arm.com>,
Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>,
Zhang Rui <rui.zhang@intel.com>,
Laura Nao <laura.nao@collabora.com>
Subject: Re: [PATCH v1] thermal: core: Do not fail cdev registration because of invalid initial state
Date: Thu, 6 Jun 2024 17:46:25 +0200 [thread overview]
Message-ID: <3ab5357f-9577-4985-b09e-b686e66b7b5e@linaro.org> (raw)
In-Reply-To: <CAJZ5v0jurx=TfT2GHCeMt7xhTFRQwpS_H6-fDss=bt+HodvBoQ@mail.gmail.com>
On 06/06/2024 17:15, Rafael J. Wysocki wrote:
[ ... ]
> OK, so arguably the driver could set the initial state of the cooling
> device to 0. That may or may not be the right thing to do depending
> on the thermal state of the system at the moment. Then it would need
> to wait for the governor to pick up a more suitable state for it or
> leave it at 0. This could address the particular case at hand.
>
> However, should the core fail the cooling device registration if it
> gets an error from .get_cur_state() to start with? It didn't do that
> before. Indeed, it didn't even call .get_cur_state() then in the
> first place. Moreover, the current state of the cooling device is not
> even needed to register it except for the initialization of the debug
> code for that cooling device, so why fail the registration of it?
Indeed, the simpler way would be to not register the debugfs if we can't
get the initial cooling device state, with a message, so the driver
responsible of that will appear and hopefully encourage someone to fix it.
--
<http://www.linaro.org/> Linaro.org │ Open source software for ARM SoCs
Follow Linaro: <http://www.facebook.com/pages/Linaro> Facebook |
<http://twitter.com/#!/linaroorg> Twitter |
<http://www.linaro.org/linaro-blog/> Blog
next prev parent reply other threads:[~2024-06-06 15:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-05 19:17 [PATCH v1] thermal: core: Do not fail cdev registration because of invalid initial state Rafael J. Wysocki
2024-06-06 3:41 ` srinivas pandruvada
2024-06-06 9:47 ` Rafael J. Wysocki
2024-06-06 13:07 ` Daniel Lezcano
2024-06-06 13:42 ` Rafael J. Wysocki
2024-06-06 14:18 ` Rafael J. Wysocki
2024-06-06 14:50 ` Daniel Lezcano
2024-06-06 15:15 ` Rafael J. Wysocki
2024-06-06 15:46 ` Daniel Lezcano [this message]
2024-06-06 15:52 ` Rafael J. Wysocki
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=3ab5357f-9577-4985-b09e-b686e66b7b5e@linaro.org \
--to=daniel.lezcano@linaro.org \
--cc=laura.nao@collabora.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=lukasz.luba@arm.com \
--cc=rafael@kernel.org \
--cc=rjw@rjwysocki.net \
--cc=rui.zhang@intel.com \
--cc=srinivas.pandruvada@linux.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