From: Andreas Klinger <ak@it-klinger.de>
To: David Lechner <dlechner@baylibre.com>
Cc: "Jonathan Cameron" <jic23@kernel.org>,
"Nuno Sá" <nuno.sa@analog.com>,
"Andy Shevchenko" <andy@kernel.org>,
linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] iio: proximity: srf08: use stack allocated scan buffer
Date: Sun, 13 Jul 2025 14:17:11 +0200 [thread overview]
Message-ID: <aHOjxzNqW8Yf2kR7@mail.your-server.de> (raw)
In-Reply-To: <20250711-iio-use-more-iio_declare_buffer_with_ts-6-v1-1-25c70b990d6c@baylibre.com>
[-- Attachment #1: Type: text/plain, Size: 2281 bytes --]
Reviewed-by: Andreas Klinger <ak@it-klinger.de>
David Lechner <dlechner@baylibre.com> schrieb am Fr, 11. Jul 11:07:
> Use a stack allocated scan struct in srf08_trigger_handler(). Since the
> scan buffer isn't used outside of this function and doesn't need to be
> DMA-safe, it doesn't need to be in struct srf08_data. We can also
> eliminate an extra local variable for the return value of
> srf08_read_ranging() by using scan.chan directly.
>
> Signed-off-by: David Lechner <dlechner@baylibre.com>
> ---
> drivers/iio/proximity/srf08.c | 18 +++++++-----------
> 1 file changed, 7 insertions(+), 11 deletions(-)
>
> diff --git a/drivers/iio/proximity/srf08.c b/drivers/iio/proximity/srf08.c
> index 6e32fdfd161b93a5624f757d5b7de579415b1055..a28efcf324a844a6dca43dff69e71ca38a2ccc68 100644
> --- a/drivers/iio/proximity/srf08.c
> +++ b/drivers/iio/proximity/srf08.c
> @@ -63,12 +63,6 @@ struct srf08_data {
> int range_mm;
> struct mutex lock;
>
> - /* Ensure timestamp is naturally aligned */
> - struct {
> - s16 chan;
> - aligned_s64 timestamp;
> - } scan;
> -
> /* Sensor-Type */
> enum srf08_sensor_type sensor_type;
>
> @@ -182,16 +176,18 @@ static irqreturn_t srf08_trigger_handler(int irq, void *p)
> struct iio_poll_func *pf = p;
> struct iio_dev *indio_dev = pf->indio_dev;
> struct srf08_data *data = iio_priv(indio_dev);
> - s16 sensor_data;
> + struct {
> + s16 chan;
> + aligned_s64 timestamp;
> + } scan;
>
> - sensor_data = srf08_read_ranging(data);
> - if (sensor_data < 0)
> + scan.chan = srf08_read_ranging(data);
> + if (scan.chan < 0)
> goto err;
>
> mutex_lock(&data->lock);
>
> - data->scan.chan = sensor_data;
> - iio_push_to_buffers_with_ts(indio_dev, &data->scan, sizeof(data->scan),
> + iio_push_to_buffers_with_ts(indio_dev, &scan, sizeof(scan),
> pf->timestamp);
>
> mutex_unlock(&data->lock);
>
> ---
> base-commit: f8f559752d573a051a984adda8d2d1464f92f954
> change-id: 20250711-iio-use-more-iio_declare_buffer_with_ts-6-6ffc8e99552d
>
> Best regards,
> --
> David Lechner <dlechner@baylibre.com>
>
--
Andreas Klinger
Grabenreith 27
84508 Burgkirchen
+49 8623 373
ak@it-klinger.de
www.it-klinger.de
www.grabenreith.de
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]
prev parent reply other threads:[~2025-07-13 12:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-11 16:07 [PATCH] iio: proximity: srf08: use stack allocated scan buffer David Lechner
2025-07-11 16:44 ` Andy Shevchenko
2025-07-11 17:07 ` David Lechner
2025-07-13 14:01 ` Jonathan Cameron
2025-07-13 12:17 ` Andreas Klinger [this message]
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=aHOjxzNqW8Yf2kR7@mail.your-server.de \
--to=ak@it-klinger.de \
--cc=andy@kernel.org \
--cc=dlechner@baylibre.com \
--cc=jic23@kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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.