From: Jonathan Cameron <jic23@kernel.org>
To: David Lechner <dlechner@baylibre.com>
Cc: "Andreas Klinger" <ak@it-klinger.de>,
"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: mb1232: use stack allocated scan struct
Date: Thu, 24 Jul 2025 11:26:28 +0100 [thread overview]
Message-ID: <20250724112628.565aac47@jic23-huawei> (raw)
In-Reply-To: <20250722-iio-proximity-mb1232-use-stack-allocated-scan-struct-v1-1-b4ef77e9ddea@baylibre.com>
On Tue, 22 Jul 2025 17:39:17 -0500
David Lechner <dlechner@baylibre.com> wrote:
> Use a stack allocated struct for the scan data instead of using the
> driver state to store the struct. The scan data is not used outside of
> the interrupt handler function so the struct does not need to exist
> outside of that scope.
>
> Signed-off-by: David Lechner <dlechner@baylibre.com>
Hi David,
Applied to the testing branch of iio.git.
I don't suppose you fancy a follow up to take that irqnr local to probe?
If not I'll get to it at some point maybe.
Thanks,
Jonathan
> ---
> drivers/iio/proximity/mb1232.c | 15 +++++++--------
> 1 file changed, 7 insertions(+), 8 deletions(-)
>
> diff --git a/drivers/iio/proximity/mb1232.c b/drivers/iio/proximity/mb1232.c
> index 01783486bc7df34ec3b38b1d0ad5f52e3eae6c92..34b49c54e68b0a11bac0287c65cb368c9e956da4 100644
> --- a/drivers/iio/proximity/mb1232.c
> +++ b/drivers/iio/proximity/mb1232.c
> @@ -42,11 +42,6 @@ struct mb1232_data {
> */
> struct completion ranging;
> int irqnr;
> - /* Ensure correct alignment of data to push to IIO buffer */
> - struct {
> - s16 distance;
> - aligned_s64 ts;
> - } scan;
> };
>
> static irqreturn_t mb1232_handle_irq(int irq, void *dev_id)
> @@ -120,12 +115,16 @@ static irqreturn_t mb1232_trigger_handler(int irq, void *p)
> struct iio_poll_func *pf = p;
> struct iio_dev *indio_dev = pf->indio_dev;
> struct mb1232_data *data = iio_priv(indio_dev);
> + struct {
> + s16 distance;
> + aligned_s64 ts;
> + } scan = { };
>
> - data->scan.distance = mb1232_read_distance(data);
> - if (data->scan.distance < 0)
> + scan.distance = mb1232_read_distance(data);
> + if (scan.distance < 0)
> goto err;
>
> - 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);
>
> err:
>
> ---
> base-commit: cd2731444ee4e35db76f4fb587f12d327eec5446
> change-id: 20250722-iio-proximity-mb1232-use-stack-allocated-scan-struct-e0f051595dfe
>
> Best regards,
next prev parent reply other threads:[~2025-07-24 10:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-22 22:39 [PATCH] iio: proximity: mb1232: use stack allocated scan struct David Lechner
2025-07-24 10:26 ` Jonathan Cameron [this message]
2025-09-05 19:12 ` David Lechner
2025-09-07 13:29 ` Jonathan Cameron
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=20250724112628.565aac47@jic23-huawei \
--to=jic23@kernel.org \
--cc=ak@it-klinger.de \
--cc=andy@kernel.org \
--cc=dlechner@baylibre.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox