public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Peter Kästle" <peter@piie.net>
To: "Daniel Lezcano" <daniel.lezcano@linaro.org>,
	hdegoede@redhat.com, mgross@linux.intel.com
Cc: platform-driver-x86@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 2/2] platform/x86/drivers/acerhdf: Check the interval value when it is set
Date: Thu, 03 Dec 2020 21:22:02 +0000	[thread overview]
Message-ID: <92e330ff28a10b1fb92d91c083fa3cac@piie.net> (raw)
In-Reply-To: <20201203071738.2363701-2-daniel.lezcano@linaro.org>

3. Dezember 2020 08:17, "Daniel Lezcano" <daniel.lezcano@linaro.org> schrieb:

> Currently the code checks the interval value when the temperature is
> read which is bad for two reasons:
> 
> - checking and setting the interval in the get_temp callback is
> inaccurate and awful, that can be done when changing the value.
> 
> - Changing the thermal zone structure internals is an abuse of the
> exported structure, moreover no lock is taken here.
> 
> The goal of this patch is to solve the first item by using the 'set'
> function called when changing the interval. The check is done there
> and removed from the get_temp function. If the thermal zone was not
> initialized yet, the interval is not updated in this case as that will
> happen in the init function when registering the thermal zone device.

Thanks for your effort.  This improves the code, good finding.

 
> I don't have any hardware to test the changes.

Tests successfully executed on my good old AOA110.


> Signed-off-by: Daniel Lezcano <daniel.lezcano@linaro.org>

Acked-by: Peter Kaestle <peter@piie.net>


> ---
> V2:
> - Fixed static function annotation
> ---
> drivers/platform/x86/acerhdf.c | 22 ++++++++++++++++++----
> 1 file changed, 18 insertions(+), 4 deletions(-)
> 
> diff --git a/drivers/platform/x86/acerhdf.c b/drivers/platform/x86/acerhdf.c
> index 19fc8ff2225c..b6aa6e5514f4 100644
> --- a/drivers/platform/x86/acerhdf.c
> +++ b/drivers/platform/x86/acerhdf.c
> @@ -334,7 +334,10 @@ static void acerhdf_check_param(struct thermal_zone_device *thermal)
> }
> if (verbose)
> pr_notice("interval changed to: %d\n", interval);
> - thermal->polling_delay = interval*1000;
> +
> + if (thermal)
> + thermal->polling_delay = interval*1000;
> +
> prev_interval = interval;
> }
> }
> @@ -349,8 +352,6 @@ static int acerhdf_get_ec_temp(struct thermal_zone_device *thermal, int *t)
> {
> int temp, err = 0;
> 
> - acerhdf_check_param(thermal);
> -
> err = acerhdf_get_temp(&temp);
> if (err)
> return err;
> @@ -823,8 +824,21 @@ MODULE_ALIAS("dmi:*:*Acer*:pnExtensa*5420*:");
> module_init(acerhdf_init);
> module_exit(acerhdf_exit);
> 
> +static int interval_set_uint(const char *val, const struct kernel_param *kp)
> +{
> + int ret;
> +
> + ret = param_set_uint(val, kp);
> + if (ret)
> + return ret;
> +
> + acerhdf_check_param(thz_dev);
> +
> + return 0;
> +}
> +
> static const struct kernel_param_ops interval_ops = {
> - .set = param_set_uint,
> + .set = interval_set_uint,
> .get = param_get_uint,
> };
> 
> -- 
> 2.25.1

  reply	other threads:[~2020-12-03 21:22 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-03  7:17 [PATCH v2 1/2] platform/x86/drivers/acerhdf: Use module_param_cb to set/get polling interval Daniel Lezcano
2020-12-03  7:17 ` [PATCH v2 2/2] platform/x86/drivers/acerhdf: Check the interval value when it is set Daniel Lezcano
2020-12-03 21:22   ` Peter Kästle [this message]
2020-12-04 11:43     ` Daniel Lezcano
2020-12-07 14:54       ` Hans de Goede
2020-12-07 15:59         ` Daniel Lezcano
2020-12-03 21:17 ` [PATCH v2 1/2] platform/x86/drivers/acerhdf: Use module_param_cb to set/get polling interval Peter Kästle

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=92e330ff28a10b1fb92d91c083fa3cac@piie.net \
    --to=peter@piie.net \
    --cc=daniel.lezcano@linaro.org \
    --cc=hdegoede@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mgross@linux.intel.com \
    --cc=platform-driver-x86@vger.kernel.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