From: "Rafael J. Wysocki" <rjw@rjwysocki.net>
To: Daniel Lezcano <daniel.lezcano@linaro.org>,
Lukasz Luba <lukasz.luba@arm.com>
Cc: Linux PM <linux-pm@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>,
Zhang Rui <rui.zhang@intel.com>
Subject: [PATCH v3 2/2] thermal: sysfs: Rework the reading of trip point attributes
Date: Mon, 04 Dec 2023 15:52:22 +0100 [thread overview]
Message-ID: <4855368.GXAFRqVoOG@kreacher> (raw)
In-Reply-To: <12338384.O9o76ZdvQC@kreacher>
From: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Rework the _show() callback functions for the trip point temperature,
hysteresis and type attributes to avoid copying the values of struct
thermal_trip fields that they do not use and to make them carry out
validation checks with the help of check_thermal_zone_and_trip_id(),
like the corresponding _store() callback functions.
No intentional functional impact.
Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
---
v2 -> v3: Drop a redundant 'ret' check at the end of trip_point_hyst_show.
v1 -> v2: Do not drop thermal zone locking from the _store() callback functions.
---
drivers/thermal/thermal_sysfs.c | 55 ++++++++++++++++++++--------------------
1 file changed, 28 insertions(+), 27 deletions(-)
Index: linux-pm/drivers/thermal/thermal_sysfs.c
===================================================================
--- linux-pm.orig/drivers/thermal/thermal_sysfs.c
+++ linux-pm/drivers/thermal/thermal_sysfs.c
@@ -96,25 +96,25 @@ trip_point_type_show(struct device *dev,
char *buf)
{
struct thermal_zone_device *tz = to_thermal_zone(dev);
- struct thermal_trip trip;
- int trip_id, result;
+ enum thermal_trip_type type;
+ int trip_id, ret;
if (sscanf(attr->attr.name, "trip_point_%d_type", &trip_id) != 1)
return -EINVAL;
mutex_lock(&tz->lock);
- if (device_is_registered(dev))
- result = __thermal_zone_get_trip(tz, trip_id, &trip);
- else
- result = -ENODEV;
+ ret = check_thermal_zone_and_trip_id(dev, tz, trip_id);
+ if (ret) {
+ mutex_unlock(&tz->lock);
+ return ret;
+ }
- mutex_unlock(&tz->lock);
+ type = tz->trips[trip_id].type;
- if (result)
- return result;
+ mutex_unlock(&tz->lock);
- switch (trip.type) {
+ switch (type) {
case THERMAL_TRIP_CRITICAL:
return sprintf(buf, "critical\n");
case THERMAL_TRIP_HOT:
@@ -175,25 +175,24 @@ trip_point_temp_show(struct device *dev,
char *buf)
{
struct thermal_zone_device *tz = to_thermal_zone(dev);
- struct thermal_trip trip;
- int trip_id, ret;
+ int trip_id, ret, temp;
if (sscanf(attr->attr.name, "trip_point_%d_temp", &trip_id) != 1)
return -EINVAL;
mutex_lock(&tz->lock);
- if (device_is_registered(dev))
- ret = __thermal_zone_get_trip(tz, trip_id, &trip);
- else
- ret = -ENODEV;
+ ret = check_thermal_zone_and_trip_id(dev, tz, trip_id);
+ if (ret) {
+ mutex_unlock(&tz->lock);
+ return ret;
+ }
- mutex_unlock(&tz->lock);
+ temp = tz->trips[trip_id].temperature;
- if (ret)
- return ret;
+ mutex_unlock(&tz->lock);
- return sprintf(buf, "%d\n", trip.temperature);
+ return sprintf(buf, "%d\n", temp);
}
static ssize_t
@@ -243,22 +242,24 @@ trip_point_hyst_show(struct device *dev,
char *buf)
{
struct thermal_zone_device *tz = to_thermal_zone(dev);
- struct thermal_trip trip;
- int trip_id, ret;
+ int trip_id, ret, hyst;
if (sscanf(attr->attr.name, "trip_point_%d_hyst", &trip_id) != 1)
return -EINVAL;
mutex_lock(&tz->lock);
- if (device_is_registered(dev))
- ret = __thermal_zone_get_trip(tz, trip_id, &trip);
- else
- ret = -ENODEV;
+ ret = check_thermal_zone_and_trip_id(dev, tz, trip_id);
+ if (ret) {
+ mutex_unlock(&tz->lock);
+ return ret;
+ }
+
+ hyst = tz->trips[trip_id].hysteresis;
mutex_unlock(&tz->lock);
- return ret ? ret : sprintf(buf, "%d\n", trip.hysteresis);
+ return sprintf(buf, "%d\n", hyst);
}
static ssize_t
prev parent reply other threads:[~2023-12-04 14:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-04 14:46 [PATCH v3 0/2] thermal: sysfs: Simplifications of trip point attribute callbacks Rafael J. Wysocki
2023-12-04 14:50 ` [PATCH v3 1/2] thermal: sysfs: Rework the handling of trip point updates Rafael J. Wysocki
2023-12-04 16:55 ` Daniel Lezcano
2023-12-04 17:47 ` Rafael J. Wysocki
2023-12-04 21:44 ` Daniel Lezcano
2023-12-04 14:52 ` Rafael J. Wysocki [this message]
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=4855368.GXAFRqVoOG@kreacher \
--to=rjw@rjwysocki.net \
--cc=daniel.lezcano@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=lukasz.luba@arm.com \
--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