From: Sanjay Chitroda <sanjayembeddedse@gmail.com>
To: jic23@kernel.org
Cc: dlechner@baylibre.com, nuno.sa@analog.com, andy@kernel.org,
sanjayembeddedse@gmail.com, tglx@kernel.org,
christophe.jaillet@wanadoo.fr, mingo@kernel.org,
nabijaczleweli@nabijaczleweli.xyz, kees@kernel.org,
linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH v6 3/7] iio: ssp_sensors: factor out pending list add/remove helper(s)
Date: Wed, 15 Apr 2026 10:37:45 +0530 [thread overview]
Message-ID: <20260415050749.3858046-4-sanjayembedded@gmail.com> (raw)
In-Reply-To: <20260415050749.3858046-1-sanjayembedded@gmail.com>
From: Sanjay Chitroda <sanjayembeddedse@gmail.com>
The SSP SPI transfer path manipulates the pending message list in
multiple places, each time open-coding the same locking and list
operations.
Re-factor the pending list add and delete logic into small helper
functions and drop use_no_irq variable to avoid duplication and
simplify transfer flow to follow.
No functional change intended.
Signed-off-by: Sanjay Chitroda <sanjayembeddedse@gmail.com>
Suggested-by: Andy Shevchenko <andriy.shevchenko@intel.com>
---
Changes in v6:
- Include tag for the suggestion of helper functions
- Drop completely use_no_irq variable with review comment from Andy
- Link to v5: https://lore.kernel.org/all/20260406080852.2727453-1-sanjayembedded@gmail.com/
---
drivers/iio/common/ssp_sensors/ssp_spi.c | 55 +++++++++++++-----------
1 file changed, 30 insertions(+), 25 deletions(-)
diff --git a/drivers/iio/common/ssp_sensors/ssp_spi.c b/drivers/iio/common/ssp_sensors/ssp_spi.c
index 08ed92859be0..92418721ff82 100644
--- a/drivers/iio/common/ssp_sensors/ssp_spi.c
+++ b/drivers/iio/common/ssp_sensors/ssp_spi.c
@@ -174,15 +174,32 @@ static int ssp_check_lines(struct ssp_data *data, bool state)
return 0;
}
+static inline void ssp_pending_add(struct ssp_data *data,
+ struct ssp_msg *msg)
+{
+ if (msg->length == 0)
+ return;
+
+ mutex_lock(&data->pending_lock);
+ list_add_tail(&msg->list, &data->pending_list);
+ mutex_unlock(&data->pending_lock);
+}
+
+static inline void ssp_pending_del(struct ssp_data *data,
+ struct ssp_msg *msg)
+{
+ if (msg->length == 0)
+ return;
+
+ mutex_lock(&data->pending_lock);
+ list_del(&msg->list);
+ mutex_unlock(&data->pending_lock);
+}
+
static int ssp_do_transfer(struct ssp_data *data, struct ssp_msg *msg,
struct completion *done, int timeout)
{
int status;
- /*
- * check if this is a short one way message or the whole transfer has
- * second part after an interrupt
- */
- const bool use_no_irq = msg->length == 0;
if (data->shut_down)
return -EPERM;
@@ -202,35 +219,23 @@ static int ssp_do_transfer(struct ssp_data *data, struct ssp_msg *msg,
goto _error_locked;
}
- if (!use_no_irq) {
- mutex_lock(&data->pending_lock);
- list_add_tail(&msg->list, &data->pending_list);
- mutex_unlock(&data->pending_lock);
- }
+ ssp_pending_add(data, msg);
status = ssp_check_lines(data, true);
if (status < 0) {
- if (!use_no_irq) {
- mutex_lock(&data->pending_lock);
- list_del(&msg->list);
- mutex_unlock(&data->pending_lock);
- }
+ ssp_pending_del(data, msg);
goto _error_locked;
}
mutex_unlock(&data->comm_lock);
- if (!use_no_irq && done)
- if (wait_for_completion_timeout(done,
- msecs_to_jiffies(timeout)) ==
- 0) {
- mutex_lock(&data->pending_lock);
- list_del(&msg->list);
- mutex_unlock(&data->pending_lock);
+ if (msg->length && done &&
+ !wait_for_completion_timeout(done, msecs_to_jiffies(timeout))) {
+ ssp_pending_del(data, msg);
- data->timeout_cnt++;
- return -ETIMEDOUT;
- }
+ data->timeout_cnt++;
+ return -ETIMEDOUT;
+ }
return 0;
--
2.34.1
next prev parent reply other threads:[~2026-04-15 5:08 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-15 5:07 [PATCH v6 0/7] iio: ssp_sensors: improve resource cleanup Sanjay Chitroda
2026-04-15 5:07 ` [PATCH v6 1/7] iio: ssp_sensors: cleanup codestyle warning Sanjay Chitroda
2026-04-19 17:28 ` Jonathan Cameron
2026-04-20 4:28 ` Sanjay Chitroda
2026-04-15 5:07 ` [PATCH v6 2/7] iio: ssp_sensors: cleanup codestyle check Sanjay Chitroda
2026-04-15 9:14 ` Andy Shevchenko
2026-04-19 17:33 ` Jonathan Cameron
2026-04-20 4:29 ` Sanjay Chitroda
2026-04-15 5:07 ` Sanjay Chitroda [this message]
2026-04-15 9:22 ` [PATCH v6 3/7] iio: ssp_sensors: factor out pending list add/remove helper(s) Andy Shevchenko
2026-04-15 9:25 ` Andy Shevchenko
2026-04-15 5:07 ` [PATCH v6 4/7] iio: ssp_sensors: drop duplicated wdt timer and work cleanup Sanjay Chitroda
2026-04-15 9:29 ` Andy Shevchenko
2026-04-19 12:32 ` Sanjay Chitroda
2026-04-15 5:07 ` [PATCH v6 5/7] iio: ssp_sensors: convert probe and teardown to devm-managed resources Sanjay Chitroda
2026-04-15 9:33 ` Andy Shevchenko
2026-04-19 12:33 ` Sanjay Chitroda
2026-04-19 17:39 ` Jonathan Cameron
2026-04-25 11:05 ` Sanjay Chitroda
2026-04-15 5:07 ` [PATCH v6 6/7] iio: ssp_sensors: Use dev_err_probe Sanjay Chitroda
2026-04-15 9:39 ` Andy Shevchenko
2026-04-19 12:40 ` Sanjay Chitroda
2026-04-15 5:07 ` [PATCH v6 7/7] iio: ssp_sensors: reuse embedded RX buffer for SPI transfers Sanjay Chitroda
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=20260415050749.3858046-4-sanjayembedded@gmail.com \
--to=sanjayembeddedse@gmail.com \
--cc=andy@kernel.org \
--cc=christophe.jaillet@wanadoo.fr \
--cc=dlechner@baylibre.com \
--cc=jic23@kernel.org \
--cc=kees@kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=nabijaczleweli@nabijaczleweli.xyz \
--cc=nuno.sa@analog.com \
--cc=tglx@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.