From: Akshat Rawat <akshatrawat095@gmail.com>
To: wim@linux-watchdog.org, linux@roeck-us.net
Cc: linux-watchdog@vger.kernel.org, linux-omap@vger.kernel.org,
linux-kernel@vger.kernel.org,
Akshat Rawat <akshatrawat095@gmail.com>
Subject: [PATCH] watchdog: omap_wdt: use guard(mutex) to simplify locking
Date: Sat, 7 Nov 2026 06:31:50 +0000 [thread overview]
Message-ID: <20261107063151.441-1-akshatrawat095@gmail.com> (raw)
Replace manual mutex_lock() and mutex_unlock() calls with the modern
guard(mutex) constructor from <linux/cleanup.h>.
In each function, the mutex is held across the entire function scope.
Using guard(mutex) eliminates manual unlock boilerplate and guarantees
that the lock is released upon function exit.
Signed-off-by: Akshat Rawat <akshatrawat095@gmail.com>
---
drivers/watchdog/omap_wdt.c | 24 +++++++++---------------
1 file changed, 9 insertions(+), 15 deletions(-)
diff --git a/drivers/watchdog/omap_wdt.c b/drivers/watchdog/omap_wdt.c
index 2a6de73e6f0b..956d9513a81c 100644
--- a/drivers/watchdog/omap_wdt.c
+++ b/drivers/watchdog/omap_wdt.c
@@ -27,6 +27,7 @@
#define pr_fmt(fmt) KBUILD_MODNAME ": " fmt
#include <linux/module.h>
+#include <linux/cleanup.h>
#include <linux/types.h>
#include <linux/kernel.h>
#include <linux/mm.h>
@@ -133,7 +134,7 @@ static int omap_wdt_start(struct watchdog_device *wdog)
struct omap_wdt_dev *wdev = to_omap_wdt_dev(wdog);
void __iomem *base = wdev->base;
- mutex_lock(&wdev->lock);
+ guard(mutex)(&wdev->lock);
wdev->omap_wdt_users = true;
@@ -158,8 +159,6 @@ static int omap_wdt_start(struct watchdog_device *wdog)
omap_wdt_reload(wdev); /* trigger loading of new timeout value */
omap_wdt_enable(wdev);
- mutex_unlock(&wdev->lock);
-
return 0;
}
@@ -167,11 +166,11 @@ static int omap_wdt_stop(struct watchdog_device *wdog)
{
struct omap_wdt_dev *wdev = to_omap_wdt_dev(wdog);
- mutex_lock(&wdev->lock);
+ guard(mutex)(&wdev->lock);
omap_wdt_disable(wdev);
pm_runtime_put_sync(wdev->dev);
wdev->omap_wdt_users = false;
- mutex_unlock(&wdev->lock);
+
return 0;
}
@@ -179,9 +178,8 @@ static int omap_wdt_ping(struct watchdog_device *wdog)
{
struct omap_wdt_dev *wdev = to_omap_wdt_dev(wdog);
- mutex_lock(&wdev->lock);
+ guard(mutex)(&wdev->lock);
omap_wdt_reload(wdev);
- mutex_unlock(&wdev->lock);
return 0;
}
@@ -191,13 +189,12 @@ static int omap_wdt_set_timeout(struct watchdog_device *wdog,
{
struct omap_wdt_dev *wdev = to_omap_wdt_dev(wdog);
- mutex_lock(&wdev->lock);
+ guard(mutex)(&wdev->lock);
omap_wdt_disable(wdev);
omap_wdt_set_timer(wdev, timeout);
omap_wdt_enable(wdev);
omap_wdt_reload(wdev);
wdog->timeout = timeout;
- mutex_unlock(&wdev->lock);
return 0;
}
@@ -298,12 +295,11 @@ static void omap_wdt_shutdown(struct platform_device *pdev)
{
struct omap_wdt_dev *wdev = platform_get_drvdata(pdev);
- mutex_lock(&wdev->lock);
+ guard(mutex)(&wdev->lock);
if (wdev->omap_wdt_users) {
omap_wdt_disable(wdev);
pm_runtime_put_sync(wdev->dev);
}
- mutex_unlock(&wdev->lock);
}
static void omap_wdt_remove(struct platform_device *pdev)
@@ -324,12 +320,11 @@ static int omap_wdt_suspend(struct platform_device *pdev, pm_message_t state)
{
struct omap_wdt_dev *wdev = platform_get_drvdata(pdev);
- mutex_lock(&wdev->lock);
+ guard(mutex)(&wdev->lock);
if (wdev->omap_wdt_users) {
omap_wdt_disable(wdev);
pm_runtime_put_sync(wdev->dev);
}
- mutex_unlock(&wdev->lock);
return 0;
}
@@ -338,13 +333,12 @@ static int omap_wdt_resume(struct platform_device *pdev)
{
struct omap_wdt_dev *wdev = platform_get_drvdata(pdev);
- mutex_lock(&wdev->lock);
+ guard(mutex)(&wdev->lock);
if (wdev->omap_wdt_users) {
pm_runtime_get_sync(wdev->dev);
omap_wdt_enable(wdev);
omap_wdt_reload(wdev);
}
- mutex_unlock(&wdev->lock);
return 0;
}
--
2.56.0.windows.4
reply other threads:[~2026-11-07 6:31 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20261107063151.441-1-akshatrawat095@gmail.com \
--to=akshatrawat095@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=wim@linux-watchdog.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
all inboxes | Powered by JetHome®