All of lore.kernel.org
 help / color / mirror / Atom feed
From: Guenter Roeck <linux@roeck-us.net>
To: Dmitry Osipenko <digetx@gmail.com>
Cc: Zhang Rui <rui.zhang@intel.com>,
	Daniel Lezcano <daniel.lezcano@linaro.org>,
	Amit Kucheria <amitk@kernel.org>,
	Jean Delvare <jdelvare@suse.com>,
	linux-hwmon@vger.kernel.org, linux-pm@vger.kernel.org,
	linux-kernel@vger.kernel.org, linux-tegra@vger.kernel.org
Subject: Re: [PATCH v3 2/2] hwmon: Support set_trips() of thermal device ops
Date: Mon, 21 Jun 2021 13:30:44 -0700	[thread overview]
Message-ID: <20210621203044.GA631670@roeck-us.net> (raw)
In-Reply-To: <20210621184058.4110-3-digetx@gmail.com>

On Mon, Jun 21, 2021 at 09:40:58PM +0300, Dmitry Osipenko wrote:
> Support set_trips() callback of thermal device ops. This allows HWMON
> device to operatively notify thermal core about temperature changes, which
> is very handy to have in a case where HWMON sensor is used by CPU thermal
> zone that performs passive cooling and emergency shutdown on overheat.
> Thermal core will be able to react faster to temperature changes.
> 

I think that warrants an explanation why it doesn't matter if the
code doesn't really set any trip points.

> Signed-off-by: Dmitry Osipenko <digetx@gmail.com>
> ---
>  drivers/hwmon/hwmon.c | 32 ++++++++++++++++++++++++++++++++
>  1 file changed, 32 insertions(+)
> 
> diff --git a/drivers/hwmon/hwmon.c b/drivers/hwmon/hwmon.c
> index fd47ab4e6892..e74dc81e650d 100644
> --- a/drivers/hwmon/hwmon.c
> +++ b/drivers/hwmon/hwmon.c
> @@ -153,8 +153,40 @@ static int hwmon_thermal_get_temp(void *data, int *temp)
>  	return 0;
>  }
>  
> +static int hwmon_thermal_set_trips(void *data, int low, int high)
> +{
> +	struct hwmon_thermal_data *tdata = data;
> +	struct hwmon_device *hwdev = to_hwmon_device(tdata->dev);
> +	const struct hwmon_chip_info *chip = hwdev->chip;
> +	const struct hwmon_channel_info **info = chip->info;
> +	unsigned int i;
> +
> +	if (!chip->ops->write)
> +		return 0;
> +
> +	for (i = 1; info[i] && info[i]->type != hwmon_temp; i++)
> +		continue;

Why start with index 1 ? While index 0 is commonly used for chip data,
that is not mandatory.

> +
> +	if (info[i] && info[i]->config[tdata->index] & HWMON_T_MIN) {
> +		int err = chip->ops->write(tdata->dev, hwmon_temp,
> +					   hwmon_temp_min, tdata->index, low);

checkpatch will complain here because it expects an empty line after a
declaration. Since err is used in multiple conditionals, I would suggest
to declare it once in the function header.

> +		if (err < 0 && err != -EOPNOTSUPP)

"< 0" is unnecessary.

> +			return err;
> +	}
> +
> +	if (info[i] && info[i]->config[tdata->index] & HWMON_T_MAX) {
> +		int err = chip->ops->write(tdata->dev, hwmon_temp,
> +					   hwmon_temp_max, tdata->index, high);
> +		if (err < 0 && err != -EOPNOTSUPP)

"< 0" is unnecessary.

> +			return err;
> +	}
> +
> +	return 0;
> +}
> +
>  static const struct thermal_zone_of_device_ops hwmon_thermal_ops = {
>  	.get_temp = hwmon_thermal_get_temp,
> +	.set_trips = hwmon_thermal_set_trips,
>  };
>  
>  static void hwmon_thermal_remove_sensor(void *data)

  reply	other threads:[~2021-06-21 20:30 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-21 18:40 [PATCH v3 0/2] Support temperature trips by HWMON core and LM90 driver Dmitry Osipenko
2021-06-21 18:40 ` [PATCH v3 1/2] hwmon: (lm90) Prevent integer underflows of temperature calculations Dmitry Osipenko
2021-06-21 18:40 ` [PATCH v3 2/2] hwmon: Support set_trips() of thermal device ops Dmitry Osipenko
2021-06-21 20:30   ` Guenter Roeck [this message]
2021-06-21 20:45     ` Dmitry Osipenko

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=20210621203044.GA631670@roeck-us.net \
    --to=linux@roeck-us.net \
    --cc=amitk@kernel.org \
    --cc=daniel.lezcano@linaro.org \
    --cc=digetx@gmail.com \
    --cc=jdelvare@suse.com \
    --cc=linux-hwmon@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=linux-tegra@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.