From: Joshua Crofts <joshua.crofts1@gmail.com>
To: Abdelnasser Hussein <abdelnasserhussein11@gmail.com>
Cc: gregkh@linuxfoundation.org, jic23@kernel.org, nuno.sa@analog.com,
Michael.Hennerich@analog.com, dlechner@baylibre.com,
andy@kernel.org, linux@analog.com, linux-iio@vger.kernel.org,
linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 1/2] staging: iio: adc: ad7816: Serialize SPI read operations
Date: Sun, 6 Sep 2026 16:06:15 +0200 [thread overview]
Message-ID: <20260906160615.2fb5555d@systembl0wer> (raw)
In-Reply-To: <20260906114049.32912-2-abdelnasserhussein11@gmail.com>
On Sun, 6 Sep 2026 14:40:48 +0300
Abdelnasser Hussein <abdelnasserhussein11@gmail.com> wrote:
> Add a mutex to serialize SPI read operations and prevent data corruption. Used guard(mutex) and devm_mutex_init() for safer and automatic cleanup.
Please wrap your commit message to ~75 characters per line.
> Signed-off-by: Abdelnasser Hussein <abdelnasserhussein11@gmail.com>
> ---
> drivers/staging/iio/adc/ad7816.c | 9 ++++++++-
> 1 file changed, 8 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/staging/iio/adc/ad7816.c b/drivers/staging/iio/adc/ad7816.c
> index 0e32a2295990..ab80b3a889bb 100644
> --- a/drivers/staging/iio/adc/ad7816.c
> +++ b/drivers/staging/iio/adc/ad7816.c
> @@ -14,6 +14,8 @@
> #include <linux/list.h>
> #include <linux/spi/spi.h>
> #include <linux/module.h>
> +#include <linux/mutex.h>
> +#include <linux/cleanup.h>
Even if the header list isn't sorted, try to add the headers
in the approximate location if the list were sorted. Better yet,
you could send a patch that orders and cleans up the include list.
>
> #include <linux/iio/iio.h>
> #include <linux/iio/sysfs.h>
> @@ -65,7 +67,8 @@ static int ad7816_spi_read(struct ad7816_chip_info *chip, u16 *data)
> {
> struct spi_device *spi_dev = chip->spi_dev;
> int ret;
> - __be16 buf;
Stray change? I believe this goes into patch 2.
> +
> + guard(mutex)(&chip->lock);
> gpiod_set_value(chip->rdwr_pin, 1);
> gpiod_set_value(chip->rdwr_pin, 0);
> @@ -360,6 +363,10 @@ static int ad7816_probe(struct spi_device *spi_dev)
> return -ENOMEM;
> chip = iio_priv(indio_dev);
>
> + ret = devm_mutex_init(&spi_dev->dev, &chip->lock);
> + if (ret)
> + return ret;
> +
> chip->spi_dev = spi_dev;
> for (i = 0; i <= AD7816_CS_MAX; i++)
> chip->oti_data[i] = 203;
--
Kind regards,
Joshua Crofts
next prev parent reply other threads:[~2026-09-06 14:06 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-06 11:40 [PATCH v4 0/2] staging: iio: adc: ad7816: Fix SPI read operations and VMAP_STACK issue Abdelnasser Hussein
2026-09-06 11:40 ` [PATCH v4 1/2] staging: iio: adc: ad7816: Serialize SPI read operations Abdelnasser Hussein
2026-09-06 14:06 ` Joshua Crofts [this message]
2026-09-06 14:11 ` Joshua Crofts
2026-09-06 17:47 ` Jonathan Cameron
2026-09-06 11:40 ` [PATCH v4 2/2] staging: iio: adc: ad7816: Use DMA-safe buffer for SPI read Abdelnasser Hussein
2026-09-06 14:15 ` Joshua Crofts
2026-09-06 17:50 ` Jonathan Cameron
2026-09-07 6:08 ` nasser
2026-09-06 14:20 ` [PATCH v4 0/2] staging: iio: adc: ad7816: Fix SPI read operations and VMAP_STACK issue Joshua Crofts
2026-09-06 16:25 ` nasser
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=20260906160615.2fb5555d@systembl0wer \
--to=joshua.crofts1@gmail.com \
--cc=Michael.Hennerich@analog.com \
--cc=abdelnasserhussein11@gmail.com \
--cc=andy@kernel.org \
--cc=dlechner@baylibre.com \
--cc=gregkh@linuxfoundation.org \
--cc=jic23@kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=linux@analog.com \
--cc=nuno.sa@analog.com \
/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.