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>
---
v1->v2: No change
---
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);
+ 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;
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;
--
2.47.3
On 2/2/26 1:40 PM, Harshit Mogalapalli 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. Even better would be to replace spi_get_device_id() with pi_get_device_match_data() and turn sca3000_spi_chip_info_tbl[] into individual structs that are used directly as the match data pointers. > > Reuse the local dev pointer for resource managed helpers. While at it, > reshuffle variable list in a reverse Christmas tree order. The dev cleanup sounds like a second unrelated change that can be split out from the spi_get_device_id() changes.
Hi David, On 03/02/26 04:31, David Lechner wrote: > On 2/2/26 1:40 PM, Harshit Mogalapalli 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. > > Even better would be to replace spi_get_device_id() with > pi_get_device_match_data() and turn sca3000_spi_chip_info_tbl[] > into individual structs that are used directly as the match > data pointers. > Thanks for the review. Jonathan also suggested this on v1, but thought of doing this item separate to this patch series(as its a functional change) , would you mind if I do it in a separate patch after this series ? >> >> Reuse the local dev pointer for resource managed helpers. While at it, >> reshuffle variable list in a reverse Christmas tree order. > > The dev cleanup sounds like a second unrelated change that can be split > out from the spi_get_device_id() changes. > Sure I will separate dev cleanup and device_id extraction into separate patches. Thanks for the suggestion. Regards, Harshit
On 2/3/26 4:24 AM, Harshit Mogalapalli wrote: > Hi David, > > On 03/02/26 04:31, David Lechner wrote: >> On 2/2/26 1:40 PM, Harshit Mogalapalli 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. >> >> Even better would be to replace spi_get_device_id() with >> pi_get_device_match_data() and turn sca3000_spi_chip_info_tbl[] >> into individual structs that are used directly as the match >> data pointers. >> > > Thanks for the review. > > Jonathan also suggested this on v1, but thought of doing this item separate to this patch series(as its a functional change) , would you mind if I do it in a separate patch after this series ? I'm not sure why it would be considered a functional change. If you want to save it for a separate series, that is fine. If we do that though, there is probably not much point in cleaning up spi_get_device_id() first since it will all be replaced anyway.
© 2016 - 2026 Red Hat, Inc.