From: Jeff LaBundy <jeff@labundy.com>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: linux-input@vger.kernel.org,
Michael Hennerich <michael.hennerich@analog.com>,
Ville Syrjala <syrjala@sci.fi>,
Support Opensource <support.opensource@diasemi.com>,
Eddie James <eajames@linux.ibm.com>,
Andrey Moiseev <o2g.org.ru@gmail.com>,
Hans de Goede <hdegoede@redhat.com>,
Javier Carrasco <javier.carrasco.cruz@gmail.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 12/22] Input: iqs269a - use guard notation when acquiring mutex
Date: Sun, 8 Sep 2024 17:05:36 -0500 [thread overview]
Message-ID: <Zt4fsJI4SFhBo5ZX@nixie71> (raw)
In-Reply-To: <20240904044756.1047629-1-dmitry.torokhov@gmail.com>
Hi Dmitry,
On Tue, Sep 03, 2024 at 09:47:55PM -0700, Dmitry Torokhov wrote:
> Using guard notation makes the code more compact and error handling
> more robust by ensuring that mutexes are released in all code paths
> when control leaves critical section.
>
> Signed-off-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Reviewed-by: Jeff LaBundy <jeff@labundy.com>
> ---
> drivers/input/misc/iqs269a.c | 46 +++++++++++++-----------------------
> 1 file changed, 16 insertions(+), 30 deletions(-)
>
> diff --git a/drivers/input/misc/iqs269a.c b/drivers/input/misc/iqs269a.c
> index 843f8a3f3410..c34d847fa4af 100644
> --- a/drivers/input/misc/iqs269a.c
> +++ b/drivers/input/misc/iqs269a.c
> @@ -365,7 +365,7 @@ static int iqs269_ati_mode_set(struct iqs269_private *iqs269,
> if (mode > IQS269_CHx_ENG_A_ATI_MODE_MAX)
> return -EINVAL;
>
> - mutex_lock(&iqs269->lock);
> + guard(mutex)(&iqs269->lock);
>
> engine_a = be16_to_cpu(ch_reg[ch_num].engine_a);
>
> @@ -375,8 +375,6 @@ static int iqs269_ati_mode_set(struct iqs269_private *iqs269,
> ch_reg[ch_num].engine_a = cpu_to_be16(engine_a);
> iqs269->ati_current = false;
>
> - mutex_unlock(&iqs269->lock);
> -
> return 0;
> }
>
> @@ -389,9 +387,9 @@ static int iqs269_ati_mode_get(struct iqs269_private *iqs269,
> if (ch_num >= IQS269_NUM_CH)
> return -EINVAL;
>
> - mutex_lock(&iqs269->lock);
> + guard(mutex)(&iqs269->lock);
> +
> engine_a = be16_to_cpu(ch_reg[ch_num].engine_a);
> - mutex_unlock(&iqs269->lock);
>
> engine_a &= IQS269_CHx_ENG_A_ATI_MODE_MASK;
> *mode = (engine_a >> IQS269_CHx_ENG_A_ATI_MODE_SHIFT);
> @@ -429,7 +427,7 @@ static int iqs269_ati_base_set(struct iqs269_private *iqs269,
> return -EINVAL;
> }
>
> - mutex_lock(&iqs269->lock);
> + guard(mutex)(&iqs269->lock);
>
> engine_b = be16_to_cpu(ch_reg[ch_num].engine_b);
>
> @@ -439,8 +437,6 @@ static int iqs269_ati_base_set(struct iqs269_private *iqs269,
> ch_reg[ch_num].engine_b = cpu_to_be16(engine_b);
> iqs269->ati_current = false;
>
> - mutex_unlock(&iqs269->lock);
> -
> return 0;
> }
>
> @@ -453,9 +449,9 @@ static int iqs269_ati_base_get(struct iqs269_private *iqs269,
> if (ch_num >= IQS269_NUM_CH)
> return -EINVAL;
>
> - mutex_lock(&iqs269->lock);
> + guard(mutex)(&iqs269->lock);
> +
> engine_b = be16_to_cpu(ch_reg[ch_num].engine_b);
> - mutex_unlock(&iqs269->lock);
>
> switch (engine_b & IQS269_CHx_ENG_B_ATI_BASE_MASK) {
> case IQS269_CHx_ENG_B_ATI_BASE_75:
> @@ -491,7 +487,7 @@ static int iqs269_ati_target_set(struct iqs269_private *iqs269,
> if (target > IQS269_CHx_ENG_B_ATI_TARGET_MAX)
> return -EINVAL;
>
> - mutex_lock(&iqs269->lock);
> + guard(mutex)(&iqs269->lock);
>
> engine_b = be16_to_cpu(ch_reg[ch_num].engine_b);
>
> @@ -501,8 +497,6 @@ static int iqs269_ati_target_set(struct iqs269_private *iqs269,
> ch_reg[ch_num].engine_b = cpu_to_be16(engine_b);
> iqs269->ati_current = false;
>
> - mutex_unlock(&iqs269->lock);
> -
> return 0;
> }
>
> @@ -515,10 +509,9 @@ static int iqs269_ati_target_get(struct iqs269_private *iqs269,
> if (ch_num >= IQS269_NUM_CH)
> return -EINVAL;
>
> - mutex_lock(&iqs269->lock);
> - engine_b = be16_to_cpu(ch_reg[ch_num].engine_b);
> - mutex_unlock(&iqs269->lock);
> + guard(mutex)(&iqs269->lock);
>
> + engine_b = be16_to_cpu(ch_reg[ch_num].engine_b);
> *target = (engine_b & IQS269_CHx_ENG_B_ATI_TARGET_MASK) * 32;
>
> return 0;
> @@ -1199,7 +1192,7 @@ static int iqs269_dev_init(struct iqs269_private *iqs269)
> {
> int error;
>
> - mutex_lock(&iqs269->lock);
> + guard(mutex)(&iqs269->lock);
>
> /*
> * Early revisions of silicon require the following workaround in order
> @@ -1210,19 +1203,19 @@ static int iqs269_dev_init(struct iqs269_private *iqs269)
> error = regmap_multi_reg_write(iqs269->regmap, iqs269_tws_init,
> ARRAY_SIZE(iqs269_tws_init));
> if (error)
> - goto err_mutex;
> + return error;
> }
>
> error = regmap_update_bits(iqs269->regmap, IQS269_HALL_UI,
> IQS269_HALL_UI_ENABLE,
> iqs269->hall_enable ? ~0 : 0);
> if (error)
> - goto err_mutex;
> + return error;
>
> error = regmap_raw_write(iqs269->regmap, IQS269_SYS_SETTINGS,
> &iqs269->sys_reg, sizeof(iqs269->sys_reg));
> if (error)
> - goto err_mutex;
> + return error;
>
> /*
> * The following delay gives the device time to deassert its RDY output
> @@ -1232,10 +1225,7 @@ static int iqs269_dev_init(struct iqs269_private *iqs269)
>
> iqs269->ati_current = true;
>
> -err_mutex:
> - mutex_unlock(&iqs269->lock);
> -
> - return error;
> + return 0;
> }
>
> static int iqs269_input_init(struct iqs269_private *iqs269)
> @@ -1580,13 +1570,11 @@ static ssize_t hall_enable_store(struct device *dev,
> if (error)
> return error;
>
> - mutex_lock(&iqs269->lock);
> + guard(mutex)(&iqs269->lock);
>
> iqs269->hall_enable = val;
> iqs269->ati_current = false;
>
> - mutex_unlock(&iqs269->lock);
> -
> return count;
> }
>
> @@ -1643,13 +1631,11 @@ static ssize_t rx_enable_store(struct device *dev,
> if (val > 0xFF)
> return -EINVAL;
>
> - mutex_lock(&iqs269->lock);
> + guard(mutex)(&iqs269->lock);
>
> ch_reg[iqs269->ch_num].rx_enable = val;
> iqs269->ati_current = false;
>
> - mutex_unlock(&iqs269->lock);
> -
> return count;
> }
>
> --
> 2.46.0.469.g59c65b2a67-goog
>
Kind regards,
Jeff LaBundy
next prev parent reply other threads:[~2024-09-08 22:05 UTC|newest]
Thread overview: 63+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-04 4:42 [PATCH 00/22] Convert misc input drivers to use new cleanup facilities Dmitry Torokhov
2024-09-04 4:42 ` [PATCH 01/22] Input: ad714x - use guard notation when acquiring mutex Dmitry Torokhov
2024-09-04 18:47 ` Javier Carrasco
2024-09-04 4:42 ` [PATCH 02/22] Input: ati_remote2 " Dmitry Torokhov
2024-09-04 18:49 ` Javier Carrasco
2024-09-04 4:42 ` [PATCH 03/22] Input: cm109 - use guard notation when acquiring mutex and spinlock Dmitry Torokhov
2024-09-04 19:44 ` Javier Carrasco
2024-09-04 4:42 ` [PATCH 04/22] Input: cma3000_d0x - use guard notation when acquiring mutex Dmitry Torokhov
2024-09-04 18:51 ` Javier Carrasco
2024-09-04 4:42 ` [PATCH 05/22] Input: da7280 - use guard notation when acquiring mutex and spinlock Dmitry Torokhov
2024-09-04 19:02 ` Javier Carrasco
2024-09-04 4:42 ` [PATCH 06/22] Input: kxtj9 - use guard notation when acquiring mutex/disabling irq Dmitry Torokhov
2024-09-04 19:03 ` Javier Carrasco
2024-09-04 4:42 ` [PATCH 07/22] Input: drv260x - use guard notation when acquiring mutex Dmitry Torokhov
2024-09-04 19:05 ` Javier Carrasco
2024-09-04 4:42 ` [PATCH 08/22] Input: drv2665 " Dmitry Torokhov
2024-09-04 19:07 ` Javier Carrasco
2024-09-04 4:42 ` [PATCH 09/22] Input: drv2667 " Dmitry Torokhov
2024-09-04 19:08 ` Javier Carrasco
2024-09-04 4:42 ` [PATCH 10/22] Input: ideapad_slidebar - use guard notation when acquiring spinlock Dmitry Torokhov
2024-09-04 19:09 ` Javier Carrasco
2024-09-04 4:47 ` [PATCH 11/22] Input: ibm-panel " Dmitry Torokhov
2024-09-04 19:11 ` Javier Carrasco
2024-09-04 21:56 ` Eddie James
2024-09-04 4:47 ` [PATCH 12/22] Input: iqs269a - use guard notation when acquiring mutex Dmitry Torokhov
2024-09-04 13:53 ` Javier Carrasco
2024-09-04 18:21 ` Dmitry Torokhov
2024-09-04 18:41 ` Javier Carrasco
2024-09-04 18:53 ` Dmitry Torokhov
2024-09-08 22:05 ` Jeff LaBundy [this message]
2024-09-04 4:48 ` [PATCH 13/22] Input: iqs269a - use cleanup facility for fwnodes Dmitry Torokhov
2024-09-04 11:13 ` Javier Carrasco
2024-09-08 22:08 ` Jeff LaBundy
2024-09-04 4:48 ` [PATCH 14/22] Input: iqs626a " Dmitry Torokhov
2024-09-04 11:10 ` Javier Carrasco
2024-09-09 0:02 ` Jeff LaBundy
2024-09-09 1:31 ` Dmitry Torokhov
2024-09-10 15:12 ` Jeff LaBundy
2024-09-04 4:48 ` [PATCH 15/22] Input: iqs7222 " Dmitry Torokhov
2024-09-04 10:50 ` Javier Carrasco
2024-09-04 18:26 ` Dmitry Torokhov
2024-09-04 18:46 ` Javier Carrasco
2024-09-09 0:12 ` Jeff LaBundy
2024-09-09 1:34 ` Dmitry Torokhov
2024-09-10 15:14 ` Jeff LaBundy
2024-09-04 4:48 ` [PATCH 16/22] Input: max8997_haptic - use guard notation when acquiring mutex Dmitry Torokhov
2024-09-04 19:12 ` Javier Carrasco
2024-09-04 4:48 ` [PATCH 17/22] Input: pegasus_notetaker " Dmitry Torokhov
2024-09-04 19:52 ` Javier Carrasco
2024-09-04 20:59 ` [PATCH v2 " Dmitry Torokhov
2024-09-04 4:49 ` [PATCH 18/22] Input: powermate - use guard notation when acquiring spinlock Dmitry Torokhov
2024-09-04 19:16 ` Javier Carrasco
2024-09-04 4:49 ` [PATCH 19/22] Input: pwm-beeper " Dmitry Torokhov
2024-09-04 19:22 ` Javier Carrasco
2024-09-04 4:49 ` [PATCH 20/22] Input: regulator-haptic - use guard notation when acquiring mutex Dmitry Torokhov
2024-09-04 19:27 ` Javier Carrasco
2024-09-04 20:55 ` [PATCH v2 " Dmitry Torokhov
2024-09-04 21:41 ` Javier Carrasco
2024-09-07 3:40 ` [PATCH " kernel test robot
2024-09-04 4:49 ` [PATCH 21/22] Input: rotary_encoder " Dmitry Torokhov
2024-09-04 19:32 ` Javier Carrasco
2024-09-04 4:49 ` [PATCH 22/22] Input: sparcspkr - use guard notation when acquiring spinlock Dmitry Torokhov
2024-09-04 19:33 ` Javier Carrasco
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=Zt4fsJI4SFhBo5ZX@nixie71 \
--to=jeff@labundy.com \
--cc=dmitry.torokhov@gmail.com \
--cc=eajames@linux.ibm.com \
--cc=hdegoede@redhat.com \
--cc=javier.carrasco.cruz@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michael.hennerich@analog.com \
--cc=o2g.org.ru@gmail.com \
--cc=support.opensource@diasemi.com \
--cc=syrjala@sci.fi \
/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;
as well as URLs for NNTP newsgroup(s).