From: Andy Shevchenko <andriy.shevchenko@intel.com>
To: Maxwell Doose <m32285159@gmail.com>
Cc: rafael@kernel.org, lenb@kernel.org, andy@kernel.org,
linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] acpi: pmic: Replace mutex_lock/unlock() with guard()/scoped_guard()
Date: Fri, 24 Apr 2026 12:13:36 +0300 [thread overview]
Message-ID: <aes0QGXqZEpsZozV@ashevche-desk.local> (raw)
In-Reply-To: <20260424035501.219946-1-m32285159@gmail.com>
On Thu, Apr 23, 2026 at 10:55:01PM -0500, Maxwell Doose wrote:
> Replace mutex_lock() and unlock() macros with the newer guard() and
> scoped_guard() macros. This will help modernize and clean the code.
>
> In intel_soc_pmic_exec_mipi_pmic_seq_element(): While at it, remove
> now redundant "ret" variable.
...
> static acpi_status intel_pmic_thermal_handler(u32 function,
> - mutex_lock(&opregion->lock);
> + scoped_guard(&opregion->lock) {
>
> if (pmic_thermal_is_temp(address))
> result = pmic_thermal_temp(opregion, reg, function, value64);
> else
> result = -EINVAL;
>
> - mutex_unlock(&opregion->lock);
> + }
No. You need to either split a helper and use guard()() there, or indent the
body of scoped_guard() accordingly.
...
> int intel_soc_pmic_exec_mipi_pmic_seq_element(u16 i2c_address, u32 reg_address,
> - mutex_lock(&intel_pmic_opregion->lock);
> + guard(&intel_pmic_opregion->lock);
>
> if (d->exec_mipi_pmic_seq_element) {
> - ret = d->exec_mipi_pmic_seq_element(intel_pmic_opregion->regmap,
> + return d->exec_mipi_pmic_seq_element(intel_pmic_opregion->regmap,
> i2c_address, reg_address,
> value, mask);
> } else if (d->pmic_i2c_address) {
> if (i2c_address == d->pmic_i2c_address) {
> - ret = regmap_update_bits(intel_pmic_opregion->regmap,
> + return regmap_update_bits(intel_pmic_opregion->regmap,
> reg_address, mask, value);
> } else {
> pr_err("%s: Unexpected i2c-addr: 0x%02x (reg-addr 0x%x value 0x%x mask 0x%x)\n",
> __func__, i2c_address, reg_address, value, mask);
> - ret = -ENXIO;
> + return -ENXIO;
> }
> } else {
> pr_warn("%s: Not implemented\n", __func__);
> pr_warn("%s: i2c-addr: 0x%x reg-addr 0x%x value 0x%x mask 0x%x\n",
> __func__, i2c_address, reg_address, value, mask);
> - ret = -EOPNOTSUPP;
> + return -EOPNOTSUPP;
> }
> -
> - mutex_unlock(&intel_pmic_opregion->lock);
> -
> - return ret;
This is not a switch-case and direct returns in if-else-if makes it harder to
follow. What you need is to drop now redundant 'else':s and leave the last one
unconditionally as the last code in the function.
> }
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2026-04-24 9:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-24 3:55 [PATCH] acpi: pmic: Replace mutex_lock/unlock() with guard()/scoped_guard() Maxwell Doose
2026-04-24 9:13 ` Andy Shevchenko [this message]
2026-04-24 13:16 ` Maxwell Doose
2026-04-29 12:08 ` kernel test robot
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=aes0QGXqZEpsZozV@ashevche-desk.local \
--to=andriy.shevchenko@intel.com \
--cc=andy@kernel.org \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=m32285159@gmail.com \
--cc=rafael@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