From: Guenter Roeck <linux@roeck-us.net>
To: Alexander Stein <alexander.stein@ew.tq-group.com>
Cc: "Jean Delvare" <jdelvare@suse.com>,
"Jonathan Corbet" <corbet@lwn.net>,
"Thierry Reding" <thierry.reding@gmail.com>,
"Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>,
"Lee Jones" <lee.jones@linaro.org>,
linux-hwmon@vger.kernel.org, linux-pwm@vger.kernel.org,
"Markus Niebel" <Markus.Niebel@ew.tq-group.com>
Subject: Re: [PATCH v4 2/6] hwmon: pwm-fan: Simplify enable/disable check
Date: Tue, 30 Aug 2022 06:43:38 -0700 [thread overview]
Message-ID: <20220830134338.GA229551@roeck-us.net> (raw)
In-Reply-To: <20220523110513.407516-3-alexander.stein@ew.tq-group.com>
On Mon, May 23, 2022 at 01:05:09PM +0200, Alexander Stein wrote:
> Instead of comparing the current to the new pwm duty to decide whether to
> enable the PWM, use a dedicated flag. Also apply the new PWM duty in any
> case. This is a preparation to enable/disable the regulator dynamically.
>
> Signed-off-by: Alexander Stein <alexander.stein@ew.tq-group.com>
> ---
> drivers/hwmon/pwm-fan.c | 37 +++++++++++++++++++++++++++++--------
> 1 file changed, 29 insertions(+), 8 deletions(-)
>
> diff --git a/drivers/hwmon/pwm-fan.c b/drivers/hwmon/pwm-fan.c
> index 831878daffe6..96b10d422828 100644
> --- a/drivers/hwmon/pwm-fan.c
> +++ b/drivers/hwmon/pwm-fan.c
> @@ -29,10 +29,13 @@ struct pwm_fan_tach {
> };
>
> struct pwm_fan_ctx {
> + struct device *dev;
> +
> struct mutex lock;
> struct pwm_device *pwm;
> struct pwm_state pwm_state;
> struct regulator *reg_en;
> + bool enabled;
>
> int tach_count;
> struct pwm_fan_tach *tachs;
> @@ -85,14 +88,21 @@ static void sample_timer(struct timer_list *t)
> static int pwm_fan_power_on(struct pwm_fan_ctx *ctx)
> {
> struct pwm_state *state = &ctx->pwm_state;
> - unsigned long period;
> int ret;
>
> - period = state->period;
> - state->duty_cycle = DIV_ROUND_UP(ctx->pwm_value * (period - 1), MAX_PWM);
> + if (ctx->enabled)
> + return 0;
> +
> state->enabled = true;
> ret = pwm_apply_state(ctx->pwm, state);
> + if (ret) {
> + dev_err(ctx->dev, "failed to enable PWM\n");
> + goto err;
There is no reason for this goto. Just return directly.
> + }
>
> + ctx->enabled = true;
> +
> +err:
> return ret;
> }
>
> @@ -100,26 +110,36 @@ static int pwm_fan_power_off(struct pwm_fan_ctx *ctx)
> {
> struct pwm_state *state = &ctx->pwm_state;
>
> + if (!ctx->enabled)
> + return 0;
> +
ctx->enabled will initially be false. How is it known that pwm is
disabled when the driver is loaded ? At the very least that warrants
an explanation.
> state->enabled = false;
> state->duty_cycle = 0;
> pwm_apply_state(ctx->pwm, state);
This code is a bit inconsistent with pwm_fan_power_on(). Why check for
error there, but not here ?
>
> + ctx->enabled = false;
> +
> return 0;
> }
>
> static int __set_pwm(struct pwm_fan_ctx *ctx, unsigned long pwm)
> {
> + struct pwm_state *state = &ctx->pwm_state;
> + unsigned long period;
> int ret = 0;
>
> mutex_lock(&ctx->lock);
> - if (ctx->pwm_value == pwm)
> - goto exit_set_pwm_err;
>
> - if (pwm > 0)
> + if (pwm > 0) {
> + period = state->period;
> + state->duty_cycle = DIV_ROUND_UP(pwm * (period - 1), MAX_PWM);
> + ret = pwm_apply_state(ctx->pwm, state);
> + if (ret)
> + goto exit_set_pwm_err;
> ret = pwm_fan_power_on(ctx);
> - else
> + } else {
> ret = pwm_fan_power_off(ctx);
> -
> + }
> if (!ret)
> ctx->pwm_value = pwm;
>
> @@ -326,6 +346,7 @@ static int pwm_fan_probe(struct platform_device *pdev)
>
> mutex_init(&ctx->lock);
>
> + ctx->dev = &pdev->dev;
> ctx->pwm = devm_of_pwm_get(dev, dev->of_node, NULL);
> if (IS_ERR(ctx->pwm))
> return dev_err_probe(dev, PTR_ERR(ctx->pwm), "Could not get PWM\n");
next prev parent reply other threads:[~2022-08-30 13:46 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-23 11:05 [PATCH v4 0/6] hwmon: pwm-fan: switch regulator dynamically Alexander Stein
2022-05-23 11:05 ` [PATCH v4 1/6] hwmon: pwm-fan: Refactor fan power on/off Alexander Stein
2022-08-30 13:45 ` Guenter Roeck
2022-05-23 11:05 ` [PATCH v4 2/6] hwmon: pwm-fan: Simplify enable/disable check Alexander Stein
2022-08-30 13:43 ` Guenter Roeck [this message]
2022-09-14 15:06 ` Alexander Stein
2022-05-23 11:05 ` [PATCH v4 3/6] hwmon: pwm-fan: Add dedicated power switch function Alexander Stein
2022-08-30 13:50 ` Guenter Roeck
2022-09-14 15:10 ` Alexander Stein
2022-05-23 11:05 ` [PATCH v4 4/6] hwmon: pwm-fan: split __set_pwm into locked/unlocked functions Alexander Stein
2022-08-30 13:52 ` Guenter Roeck
2022-05-23 11:05 ` [PATCH v4 5/6] hwmon: pwm-fan: Switch regulator dynamically Alexander Stein
2022-08-30 14:01 ` Guenter Roeck
2022-05-23 11:05 ` [PATCH v4 6/6] hwmon: pwm-fan: Remove internal duplicated pwm_state Alexander Stein
2022-05-23 12:46 ` Uwe Kleine-König
2022-05-23 13:55 ` Alexander Stein
2022-05-23 14:18 ` Guenter Roeck
2022-06-21 6:41 ` Alexander Stein
2022-06-21 7:22 ` Uwe Kleine-König
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=20220830134338.GA229551@roeck-us.net \
--to=linux@roeck-us.net \
--cc=Markus.Niebel@ew.tq-group.com \
--cc=alexander.stein@ew.tq-group.com \
--cc=corbet@lwn.net \
--cc=jdelvare@suse.com \
--cc=lee.jones@linaro.org \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-pwm@vger.kernel.org \
--cc=thierry.reding@gmail.com \
--cc=u.kleine-koenig@pengutronix.de \
/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