From: Jonathan Cameron <jic23@kernel.org>
To: Sanjay Chitroda <sanjayembeddedse@gmail.com>
Cc: dlechner@baylibre.com, nuno.sa@analog.com, andy@kernel.org,
kees@kernel.org, linux-iio@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] iio: st_sensors: drop temporary kmalloc buffer and reuse buffer_data
Date: Sun, 15 Mar 2026 18:46:27 +0000 [thread overview]
Message-ID: <20260315184627.5bca7f73@jic23-huawei> (raw)
In-Reply-To: <20260311182050.3467471-1-sanjayembedded@gmail.com>
On Wed, 11 Mar 2026 23:50:50 +0530
Sanjay Chitroda <sanjayembeddedse@gmail.com> wrote:
> From: Sanjay Chitroda <sanjayembeddedse@gmail.com>
>
> Replace the per-call kmalloc() scratch buffer with the statically allocated
> buffer_data[] field present in struct st_sensor_data. The existing buffer
> is DMA-aligned and sufficiently sized for all channel widths, so using it
> avoids unnecessary dynamic memory allocation on each read.
>
> This simplifies the code, removes redundent code and allocation.
> No functional change intended.
>
> Signed-off-by: Sanjay Chitroda <sanjayembeddedse@gmail.com>
> ---
> Changes in v2:
> - split series to individual patch
> - address review comment from David Lechner and reuse exising buffer instead of allocation
> - Link to v1 https://lore.kernel.org/all/20260310200513.2162018-4-sanjayembedded@gmail.com/
> ---
> drivers/iio/common/st_sensors/st_sensors_core.c | 12 +++---------
> 1 file changed, 3 insertions(+), 9 deletions(-)
>
> diff --git a/drivers/iio/common/st_sensors/st_sensors_core.c b/drivers/iio/common/st_sensors/st_sensors_core.c
> index dac593be5695..488e2bf6d117 100644
> --- a/drivers/iio/common/st_sensors/st_sensors_core.c
> +++ b/drivers/iio/common/st_sensors/st_sensors_core.c
> @@ -495,20 +495,17 @@ static int st_sensors_read_axis_data(struct iio_dev *indio_dev,
> struct iio_chan_spec const *ch, int *data)
> {
> int err;
> - u8 *outdata;
> struct st_sensor_data *sdata = iio_priv(indio_dev);
> unsigned int byte_for_channel;
>
> byte_for_channel = DIV_ROUND_UP(ch->scan_type.realbits +
> ch->scan_type.shift, 8);
> - outdata = kmalloc(byte_for_channel, GFP_DMA | GFP_KERNEL);
> - if (!outdata)
> - return -ENOMEM;
> + u8 *outdata = (u8 *)sdata->buffer_data;
Why is buffer_data a char array? It's already implicitly cast to a u8
in one place. I'd see if it actually wants to be a char anywhere in the driver.
If not fix that as a precursor patch to this one.
I'm not sure I'd bother having a local variable for outdata given
it is only used a few times but I don't mind it much (beyond what Andy
pointed out about declaring it here).
Jonathan
>
> err = regmap_bulk_read(sdata->regmap, ch->address,
> outdata, byte_for_channel);
> if (err < 0)
> - goto st_sensors_free_memory;
> + return err;
>
> if (byte_for_channel == 1)
> *data = (s8)*outdata;
> @@ -517,10 +514,7 @@ static int st_sensors_read_axis_data(struct iio_dev *indio_dev,
> else if (byte_for_channel == 3)
> *data = (s32)sign_extend32(get_unaligned_le24(outdata), 23);
>
> -st_sensors_free_memory:
> - kfree(outdata);
> -
> - return err;
> + return 0;
> }
>
> int st_sensors_read_info_raw(struct iio_dev *indio_dev,
prev parent reply other threads:[~2026-03-15 18:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-11 18:20 Sanjay Chitroda
2026-03-11 20:21 ` Andy Shevchenko
2026-03-15 18:46 ` Jonathan Cameron [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=20260315184627.5bca7f73@jic23-huawei \
--to=jic23@kernel.org \
--cc=andy@kernel.org \
--cc=dlechner@baylibre.com \
--cc=kees@kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nuno.sa@analog.com \
--cc=sanjayembeddedse@gmail.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
all inboxes | Powered by JetHome®