From: Jiale Yao <yaojiale02@163.com>
To: Lee Jones <lee@kernel.org>,
mfd@lists.linux.dev, linux-kernel@vger.kernel.org
Cc: Jiale Yao <yaojiale02@163.com>
Subject: [PATCH 1/2] mfd: si476x: queue polling work on freezable workqueue
Date: Fri, 16 Oct 2026 18:05:02 +0800 [thread overview]
Message-ID: <20261016100503.2581955-2-yaojiale02@163.com> (raw)
In-Reply-To: <20261016100503.2581955-1-yaojiale02@163.com>
SI476x devices without an interrupt continuously poll their status over
I2C. The polling callback runs on the non-freezable system workqueue and
can issue a transfer after the adapter has been suspended.
Queue status polling on system_freezable_wq so it stops before device
suspend and continues after resume.
Signed-off-by: Jiale Yao <yaojiale02@163.com>
---
drivers/mfd/si476x-i2c.c | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/drivers/mfd/si476x-i2c.c b/drivers/mfd/si476x-i2c.c
index 9bce720a0a08..8d952113f8a6 100644
--- a/drivers/mfd/si476x-i2c.c
+++ b/drivers/mfd/si476x-i2c.c
@@ -17,6 +17,7 @@
#include <linux/regulator/consumer.h>
#include <linux/i2c.h>
#include <linux/err.h>
+#include <linux/workqueue.h>
#include <linux/mfd/si476x-core.h>
@@ -97,8 +98,8 @@ static int si476x_core_config_pinmux(struct si476x_core *core)
static inline void si476x_core_schedule_polling_work(struct si476x_core *core)
{
- schedule_delayed_work(&core->status_monitor,
- usecs_to_jiffies(SI476X_STATUS_POLL_US));
+ queue_delayed_work(system_freezable_wq, &core->status_monitor,
+ usecs_to_jiffies(SI476X_STATUS_POLL_US));
}
/**
--
2.34.1
next prev parent reply other threads:[~2026-10-16 10:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-16 10:05 [PATCH 0/2] mfd: freeze delayed I/O work during suspend Jiale Yao
2026-10-16 10:05 ` Jiale Yao [this message]
2026-10-17 7:19 ` Re:[PATCH 1/2] mfd: si476x: queue polling work on freezable workqueue jiale yao
2026-10-16 10:05 ` [PATCH 2/2] mfd: tps65010: queue I/O " Jiale Yao
2026-10-17 7:20 ` jiale yao
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=20261016100503.2581955-2-yaojiale02@163.com \
--to=yaojiale02@163.com \
--cc=lee@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mfd@lists.linux.dev \
/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®