From: Jonathan Cameron <jic23@kernel.org>
To: Harshit Mogalapalli <harshit.m.mogalapalli@oracle.com>
Cc: "David Lechner" <dlechner@baylibre.com>,
"Nuno Sá" <nuno.sa@analog.com>,
"Andy Shevchenko" <andy@kernel.org>,
"Andrew Ijano" <andrew.ijano@gmail.com>,
linux-iio@vger.kernel.org (open list:IIO SUBSYSTEM AND DRIVERS),
linux-kernel@vger.kernel.org (open list),
kernel-janitors@vger.kernel.org,
"Andy Shevchenko" <andriy.shevchenko@intel.com>
Subject: Re: [PATCH next 1/4] iio: sca3000: cache SPI device ID in probe
Date: Sat, 31 Jan 2026 16:28:07 +0000 [thread overview]
Message-ID: <20260131162807.137bb92a@jic23-huawei> (raw)
In-Reply-To: <20260130214323.236389-2-harshit.m.mogalapalli@oracle.com>
On Fri, 30 Jan 2026 13:43:08 -0800
Harshit Mogalapalli <harshit.m.mogalapalli@oracle.com> wrote:
> Store the spi_device_id at probe entry and reuse it for the name and
> chip info instead of calling spi_get_device_id() repeatedly.
>
> Reuse the local dev pointer for resource managed helpers. While at it,
> reshuffle variable list in a reverse Christmas tree order.
>
> No functional change intended.
>
> Suggested-by: Andy Shevchenko <andriy.shevchenko@intel.com>
> Signed-off-by: Harshit Mogalapalli <harshit.m.mogalapalli@oracle.com>
Hi Harshit,
A few comments inline but they are all about extra things to do rather
than really being comments on this patch which is fine as a starting point.
> ---
> drivers/iio/accel/sca3000.c | 13 +++++++------
> 1 file changed, 7 insertions(+), 6 deletions(-)
>
> diff --git a/drivers/iio/accel/sca3000.c b/drivers/iio/accel/sca3000.c
> index 9ef4d6e27466..afe6ef61a53b 100644
> --- a/drivers/iio/accel/sca3000.c
> +++ b/drivers/iio/accel/sca3000.c
> @@ -1439,11 +1439,13 @@ static const struct iio_info sca3000_info = {
>
> static int sca3000_probe(struct spi_device *spi)
> {
> - int ret;
> + const struct spi_device_id *id = spi_get_device_id(spi);
This is probably ok as an intermediate step, but ultimately we
shouldn't be using the spi_device_id at all.
id->driver_data should be a pointer to a named (not in array)
sca3000_chip_info structure and so should the data in the of_match_id
table etc.
Then we use spi_get_device_match_data() which prefers the of_device_id
table entry (which would needed adding).
> + struct device *dev = &spi->dev;
> struct sca3000_state *st;
> struct iio_dev *indio_dev;
> + int ret;
>
> - indio_dev = devm_iio_device_alloc(&spi->dev, sizeof(*st));
> + indio_dev = devm_iio_device_alloc(dev, sizeof(*st));
> if (!indio_dev)
> return -ENOMEM;
>
> @@ -1451,10 +1453,9 @@ static int sca3000_probe(struct spi_device *spi)
> spi_set_drvdata(spi, indio_dev);
> st->us = spi;
> mutex_init(&st->lock);
> - st->info = &sca3000_spi_chip_info_tbl[spi_get_device_id(spi)
> - ->driver_data];
> + st->info = &sca3000_spi_chip_info_tbl[id->driver_data];
>
> - indio_dev->name = spi_get_device_id(spi)->name;
> + indio_dev->name = id->name;
This also needs an update to make it get the name from within the
chip_info structure. Whilst this works today it can be fragile
if we have dt compatibles that don't match exactly with the spi_device_id
table entries.
> indio_dev->info = &sca3000_info;
> if (st->info->temp_output) {
> indio_dev->channels = sca3000_channels_with_temp;
> @@ -1466,7 +1467,7 @@ static int sca3000_probe(struct spi_device *spi)
> }
> indio_dev->modes = INDIO_DIRECT_MODE;
>
> - ret = devm_iio_kfifo_buffer_setup(&spi->dev, indio_dev,
> + ret = devm_iio_kfifo_buffer_setup(dev, indio_dev,
> &sca3000_ring_setup_ops);
> if (ret)
> return ret;
next prev parent reply other threads:[~2026-01-31 16:28 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-30 21:43 [PATCH next 0/4] IIO: sca3000: devm resource management Harshit Mogalapalli
2026-01-30 21:43 ` [PATCH next 1/4] iio: sca3000: cache SPI device ID in probe Harshit Mogalapalli
2026-01-31 16:28 ` Jonathan Cameron [this message]
2026-01-31 17:32 ` Harshit Mogalapalli
2026-01-30 21:43 ` [PATCH next 2/4] iio: sca3000: switch IRQ handling to devm helpers Harshit Mogalapalli
2026-01-31 16:30 ` Jonathan Cameron
2026-01-31 17:34 ` Harshit Mogalapalli
2026-01-31 19:21 ` David Lechner
2026-01-31 19:28 ` Harshit Mogalapalli
2026-01-30 21:43 ` [PATCH next 3/4] iio: sca3000: manage device registration with devm helper Harshit Mogalapalli
2026-01-31 16:32 ` Jonathan Cameron
2026-01-30 21:43 ` [PATCH next 4/4] iio: sca3000: stop interrupts via devm_add_action_or_reset() Harshit Mogalapalli
2026-01-31 16:39 ` Jonathan Cameron
2026-01-31 17:52 ` Harshit Mogalapalli
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=20260131162807.137bb92a@jic23-huawei \
--to=jic23@kernel.org \
--cc=andrew.ijano@gmail.com \
--cc=andriy.shevchenko@intel.com \
--cc=andy@kernel.org \
--cc=dlechner@baylibre.com \
--cc=harshit.m.mogalapalli@oracle.com \
--cc=kernel-janitors@vger.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 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®