Linux IIO development
 help / color / mirror / Atom feed
From: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
To: Joao Paulo Menezes Linaris <jplinaris@usp.br>
Cc: wbg@kernel.org, Guilherme Dias <guilhermeabreu200105@usp.br>,
	 linux-iio@vger.kernel.org
Subject: Re: [PATCH v3] counter: intel-qep: Replace manual mutex logic with lock guards
Date: Wed, 13 May 2026 13:34:57 +0300 (EEST)	[thread overview]
Message-ID: <2d880cda-1baf-3b12-f79f-44b7eae74e77@linux.intel.com> (raw)
In-Reply-To: <20260512173058.14858-1-jplinaris@usp.br>

[-- Attachment #1: Type: text/plain, Size: 4214 bytes --]

On Tue, 12 May 2026, Joao Paulo Menezes Linaris wrote:

> Use guard() for handling mutex lock instead of locking and unlocking
> mutex explicitly. This improves readability by eliminating the need for
> gotos and by clearly indicating mutex will be locked only when
> execution is in guard scope.
> 
> Signed-off-by: Joao Paulo Menezes Linaris <jplinaris@usp.br>
> Co-developed-by: Guilherme Dias <guilhermeabreu200105@usp.br>
> Signed-off-by: Guilherme Dias <guilhermeabreu200105@usp.br>

Thanks.

Reviewed-by: Ilpo Järvinen <ilpo.jarvinen@linux.intel.com>

-- 
 i.

> ---
> v2 -> v3:
>  - add blank line between guard(mutex)() and other code
> 
>  drivers/counter/intel-qep.c | 50 +++++++++++++------------------------
>  1 file changed, 18 insertions(+), 32 deletions(-)
> 
> diff --git a/drivers/counter/intel-qep.c b/drivers/counter/intel-qep.c
> index c49c17805..9c6536f75 100644
> --- a/drivers/counter/intel-qep.c
> +++ b/drivers/counter/intel-qep.c
> @@ -188,25 +188,21 @@ static int intel_qep_ceiling_write(struct counter_device *counter,
>  				   struct counter_count *count, u64 max)
>  {
>  	struct intel_qep *qep = counter_priv(counter);
> -	int ret = 0;
>  
>  	/* Intel QEP ceiling configuration only supports 32-bit values */
>  	if (max != (u32)max)
>  		return -ERANGE;
>  
> -	mutex_lock(&qep->lock);
> -	if (qep->enabled) {
> -		ret = -EBUSY;
> -		goto out;
> -	}
> +	guard(mutex)(&qep->lock);
> +
> +	if (qep->enabled)
> +		return -EBUSY;
>  
>  	pm_runtime_get_sync(qep->dev);
>  	intel_qep_writel(qep, INTEL_QEPMAX, max);
>  	pm_runtime_put(qep->dev);
>  
> -out:
> -	mutex_unlock(&qep->lock);
> -	return ret;
> +	return 0;
>  }
>  
>  static int intel_qep_enable_read(struct counter_device *counter,
> @@ -226,10 +222,11 @@ static int intel_qep_enable_write(struct counter_device *counter,
>  	u32 reg;
>  	bool changed;
>  
> -	mutex_lock(&qep->lock);
> +	guard(mutex)(&qep->lock);
> +
>  	changed = val ^ qep->enabled;
>  	if (!changed)
> -		goto out;
> +		return 0;
>  
>  	pm_runtime_get_sync(qep->dev);
>  	reg = intel_qep_readl(qep, INTEL_QEPCON);
> @@ -246,8 +243,6 @@ static int intel_qep_enable_write(struct counter_device *counter,
>  	pm_runtime_put(qep->dev);
>  	qep->enabled = val;
>  
> -out:
> -	mutex_unlock(&qep->lock);
>  	return 0;
>  }
>  
> @@ -279,7 +274,6 @@ static int intel_qep_spike_filter_ns_write(struct counter_device *counter,
>  	struct intel_qep *qep = counter_priv(counter);
>  	u32 reg;
>  	bool enable;
> -	int ret = 0;
>  
>  	/*
>  	 * Spike filter length is (MAX_COUNT + 2) clock periods.
> @@ -300,11 +294,10 @@ static int intel_qep_spike_filter_ns_write(struct counter_device *counter,
>  	if (length > INTEL_QEPFLT_MAX_COUNT(length))
>  		return -ERANGE;
>  
> -	mutex_lock(&qep->lock);
> -	if (qep->enabled) {
> -		ret = -EBUSY;
> -		goto out;
> -	}
> +	guard(mutex)(&qep->lock);
> +
> +	if (qep->enabled)
> +		return -EBUSY;
>  
>  	pm_runtime_get_sync(qep->dev);
>  	reg = intel_qep_readl(qep, INTEL_QEPCON);
> @@ -316,9 +309,7 @@ static int intel_qep_spike_filter_ns_write(struct counter_device *counter,
>  	intel_qep_writel(qep, INTEL_QEPCON, reg);
>  	pm_runtime_put(qep->dev);
>  
> -out:
> -	mutex_unlock(&qep->lock);
> -	return ret;
> +	return 0;
>  }
>  
>  static int intel_qep_preset_enable_read(struct counter_device *counter,
> @@ -342,13 +333,11 @@ static int intel_qep_preset_enable_write(struct counter_device *counter,
>  {
>  	struct intel_qep *qep = counter_priv(counter);
>  	u32 reg;
> -	int ret = 0;
>  
> -	mutex_lock(&qep->lock);
> -	if (qep->enabled) {
> -		ret = -EBUSY;
> -		goto out;
> -	}
> +	guard(mutex)(&qep->lock);
> +
> +	if (qep->enabled)
> +		return -EBUSY;
>  
>  	pm_runtime_get_sync(qep->dev);
>  	reg = intel_qep_readl(qep, INTEL_QEPCON);
> @@ -360,10 +349,7 @@ static int intel_qep_preset_enable_write(struct counter_device *counter,
>  	intel_qep_writel(qep, INTEL_QEPCON, reg);
>  	pm_runtime_put(qep->dev);
>  
> -out:
> -	mutex_unlock(&qep->lock);
> -
> -	return ret;
> +	return 0;
>  }
>  
>  static struct counter_comp intel_qep_count_ext[] = {
> 

      reply	other threads:[~2026-05-13 10:35 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-12 17:30 [PATCH v3] counter: intel-qep: Replace manual mutex logic with lock guards Joao Paulo Menezes Linaris
2026-05-13 10:34 ` Ilpo Järvinen [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=2d880cda-1baf-3b12-f79f-44b7eae74e77@linux.intel.com \
    --to=ilpo.jarvinen@linux.intel.com \
    --cc=guilhermeabreu200105@usp.br \
    --cc=jplinaris@usp.br \
    --cc=linux-iio@vger.kernel.org \
    --cc=wbg@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