From: David Lechner <dlechner@baylibre.com>
To: Daniel Lezcano <daniel.lezcano@linaro.org>,
Jonathan Cameron <jic23@kernel.org>
Cc: nuno.sa@analog.com, andy@kernel.org, robh@kernel.org,
conor+dt@kernel.org, krzk+dt@kernel.org,
linux-iio@vger.kernel.org, s32@nxp.com,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
chester62515@gmail.com, mbrugger@suse.com,
ghennadi.procopciuc@oss.nxp.com
Subject: Re: [PATCH v2 2/2] iio: adc: Add the NXP SAR ADC support for the s32g2/3 platforms
Date: Thu, 11 Sep 2025 08:26:06 -0500 [thread overview]
Message-ID: <c746e72c-dbd9-4afb-9da4-5d13733fd561@baylibre.com> (raw)
In-Reply-To: <b4d2ad54-54d5-4c26-be49-b6ac671683d2@linaro.org>
On 9/11/25 7:55 AM, Daniel Lezcano wrote:
>
> Hi Jonathan,
>
> thanks for the review
>
> On 10/09/2025 19:32, Jonathan Cameron wrote:
>> On Wed, 10 Sep 2025 17:57:56 +0200
>> Daniel Lezcano <daniel.lezcano@linaro.org> wrote:
>
> [ ... ]
>
...
>
>>> + indio_dev->name = dev_name(dev);
>>
>> This should be the 'part number'. That is a little ill defined
>> for a SoC integrated ADC, but generally not what we get from dev_name()
>> on the platform_device.
>
> Sorry, I don't get the comment. If I refer to the different drivers there is not consistency with the iio_dev->name.
dev_name() will be something like adc@12345678 from the devicetree,
so not the "part number".
>
> rtq6056.c: indio_dev->name = "rtq6056";
This style is preferred if there is only one supported part.
> rzg2l_adc.c: indio_dev->name = DRIVER_NAME;
We try to avoid using a macro for the driver name like this.
> sc27xx_adc.c: indio_dev->name = dev_name(dev);
Looks like we missed catching this one in review.
> mt6359-auxadc.c: indio_dev->name = adc_dev->chip_info->model_name;
This is preferred if there is more than one part supported in the driver.
> mcp3911.c: indio_dev->name = spi_get_device_id(spi)->name;
This is fine too in cases where there isn't chip_info.
>
> Are you suggesting to use the compatible part number ?
>
> indio->name = "s32g2-sar-adc";
>
That works.
next prev parent reply other threads:[~2025-09-11 13:26 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-10 15:57 [PATCH v2 0/2] NXP SAR ADC IIO driver for s32g2/3 platforms Daniel Lezcano
2025-09-10 15:57 ` [PATCH v2 1/2] dt-bindings: iio: adc: Add the NXP SAR ADC " Daniel Lezcano
2025-09-10 15:57 ` [PATCH v2 2/2] iio: adc: Add the NXP SAR ADC support for the " Daniel Lezcano
2025-09-10 17:32 ` Jonathan Cameron
2025-09-11 12:55 ` Daniel Lezcano
2025-09-11 13:26 ` David Lechner [this message]
2025-09-12 14:17 ` Jonathan Cameron
2025-09-12 15:10 ` Nuno Sá
2025-09-12 14:18 ` Jonathan Cameron
2025-09-11 20:10 ` David Lechner
2025-09-11 23:03 ` Daniel Lezcano
2025-09-12 5:38 ` Andy Shevchenko
2025-09-12 8:19 ` Nuno Sá
2025-09-12 14:21 ` Jonathan Cameron
2025-09-12 6:00 ` Andy Shevchenko
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=c746e72c-dbd9-4afb-9da4-5d13733fd561@baylibre.com \
--to=dlechner@baylibre.com \
--cc=andy@kernel.org \
--cc=chester62515@gmail.com \
--cc=conor+dt@kernel.org \
--cc=daniel.lezcano@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=ghennadi.procopciuc@oss.nxp.com \
--cc=jic23@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mbrugger@suse.com \
--cc=nuno.sa@analog.com \
--cc=robh@kernel.org \
--cc=s32@nxp.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