From: Harshit Mogalapalli <harshit.m.mogalapalli@oracle.com>
To: Jonathan Cameron <jic23@kernel.org>
Cc: "David Lechner" <dlechner@baylibre.com>,
"Nuno Sá" <nuno.sa@analog.com>,
"Andy Shevchenko" <andy@kernel.org>,
"Andrew Ijano" <andrew.ijano@gmail.com>,
"open list:IIO SUBSYSTEM AND DRIVERS" <linux-iio@vger.kernel.org>,
"open list" <linux-kernel@vger.kernel.org>,
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 23:02:15 +0530 [thread overview]
Message-ID: <fdb53b50-e0b4-4337-bf73-e138a0cfdea5@oracle.com> (raw)
In-Reply-To: <20260131162807.137bb92a@jic23-huawei>
Hi Jonathan,
> 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.
>
....
>> 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).
>
>
...
>> - 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.
>
Thanks a lot for the review, will try to make this change on top of
these refactors.
Regards,
Harshit
next prev parent reply other threads:[~2026-01-31 17:32 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
2026-01-31 17:32 ` Harshit Mogalapalli [this message]
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=fdb53b50-e0b4-4337-bf73-e138a0cfdea5@oracle.com \
--to=harshit.m.mogalapalli@oracle.com \
--cc=andrew.ijano@gmail.com \
--cc=andriy.shevchenko@intel.com \
--cc=andy@kernel.org \
--cc=dlechner@baylibre.com \
--cc=jic23@kernel.org \
--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