From: Ceclan Dumitru <mitrutzceclan@gmail.com>
To: Jonathan Cameron <Jonathan.Cameron@Huawei.com>
Cc: linus.walleij@linaro.org, brgl@bgdev.pl, andy@kernel.org,
linux-gpio@vger.kernel.org,
"Lars-Peter Clausen" <lars@metafoo.de>,
"Jonathan Cameron" <jic23@kernel.org>,
"Rob Herring" <robh+dt@kernel.org>,
"Krzysztof Kozlowski" <krzysztof.kozlowski+dt@linaro.org>,
"Conor Dooley" <conor+dt@kernel.org>,
"Michael Walle" <michael@walle.cc>,
"Andy Shevchenko" <andy.shevchenko@gmail.com>,
"Arnd Bergmann" <arnd@arndb.de>,
"ChiaEn Wu" <chiaen_wu@richtek.com>,
"Niklas Schnelle" <schnelle@linux.ibm.com>,
"Leonard Göhrs" <l.goehrs@pengutronix.de>,
"Mike Looijmans" <mike.looijmans@topic.nl>,
"Haibo Chen" <haibo.chen@nxp.com>,
"Hugo Villeneuve" <hvilleneuve@dimonoff.com>,
"Ceclan Dumitru" <dumitru.ceclan@analog.com>,
linux-iio@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v8 2/2] iio: adc: ad7173: add AD7173 driver
Date: Thu, 14 Dec 2023 14:57:35 +0200 [thread overview]
Message-ID: <375bf803-a5d5-4778-938a-b8218b116375@gmail.com> (raw)
In-Reply-To: <20231214123029.000002f1@Huawei.com>
On 12/14/23 14:30, Jonathan Cameron wrote:
> On Tue, 12 Dec 2023 12:44:36 +0200
> Dumitru Ceclan <mitrutzceclan@gmail.com> wrote:
>
>> The AD7173 family offer a complete integrated Sigma-Delta ADC solution
>> which can be used in high precision, low noise single channel
>> applications or higher speed multiplexed applications. The Sigma-Delta
>> ADC is intended primarily for measurement of signals close to DC but also
>> delivers outstanding performance with input bandwidths out to ~10kHz.
>>
>> Reviewed-by: Michael Walle <michael@walle.cc> # for gpio-regmap
>> Signed-off-by: Dumitru Ceclan <mitrutzceclan@gmail.com>
> Hi
>
> Given it seems like you'll be doing a v9, one quick comment from me below.
>
> Jonathan
>
>> diff --git a/drivers/iio/adc/ad7173.c b/drivers/iio/adc/ad7173.c
>> new file mode 100644
>> index 000000000000..96918b24a10a
>> --- /dev/null
>> +++ b/drivers/iio/adc/ad7173.c
>> @@ -0,0 +1,964 @@
> ...
>
>> +static int ad7173_fw_parse_channel_config(struct iio_dev *indio_dev)
>> +{
>
> ...
>
>> +
>> + if (st->info->has_temp) {
>> + chan_arr[chan_index] = ad7173_temp_iio_channel_template;
>> + chan_st_priv = &channels_st_priv_arr[chan_index];
>> + chan_st_priv->ain =
>> + AD7173_CH_ADDRESS(chan_arr[chan_index].channel, chan_arr[chan_index].channel2);
>> + chan_st_priv->cfg.bipolar = false;
>> + chan_st_priv->cfg.input_buf = true;
>> + chan_st_priv->cfg.ref_sel = AD7173_SETUP_REF_SEL_INT_REF;
>> + st->adc_mode |= AD7173_ADC_MODE_REF_EN;
>> +
>> + chan_index++;
>> + }
>> +
>> + device_for_each_child_node(dev, child) {
>> + chan = &chan_arr[chan_index];
>> + chan_st_priv = &channels_st_priv_arr[chan_index];
>> + ret = fwnode_property_read_u32_array(child, "diff-channels",
>> + ain, ARRAY_SIZE(ain));
>> + if (ret) {
>> + fwnode_handle_put(child);
>> + return ret;
>> + }
>> +
>> + if (ain[0] >= st->info->num_inputs ||
>> + ain[1] >= st->info->num_inputs) {
>> + fwnode_handle_put(child);
>> + return dev_err_probe(dev, -EINVAL,
>> + "Input pin number out of range for pair (%d %d).\n",
>> + ain[0], ain[1]);
>> + }
>> +
>> + ret = fwnode_property_match_property_string(child,
>> + "adi,reference-select",
>> + ad7173_ref_sel_str,
>> + ARRAY_SIZE(ad7173_ref_sel_str));
>> +
>> + if (ret < 0)
>> + ref_sel = AD7173_SETUP_REF_SEL_INT_REF;
>> + else
>> + ref_sel = ret;
> Simpler pattern for properties with a default is not to check the error code.
>
> ref_sel = AD7173_SETUP_REF_SEL_INT_REF;
>
> fwnode_property_match_property_String(child, ...
>
> so only if it succeeds is the value overridden.
Where exactly would the value be overridden, the function does not have
an argument passed for the found index. The function is written to
return either the found index or a negative error.
The proposed pattern would just ignore the returned index and would
always leave ref_sel to default. Am I missing something?
I can see in the thread where it was introduced that you proposed:
"Looking at the usecases I wonder if it would be better to pass in
an unsigned int *ret which is only updated on a match?"
But on the iio togreg branch that was suggested I could the function on,
it does not have that parameter.
next prev parent reply other threads:[~2023-12-14 12:57 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-12 10:44 [PATCH v8 1/2] dt-bindings: adc: add AD7173 Dumitru Ceclan
2023-12-12 10:44 ` [PATCH v8 2/2] iio: adc: ad7173: add AD7173 driver Dumitru Ceclan
2023-12-13 14:24 ` Andy Shevchenko
2023-12-14 11:02 ` Ceclan Dumitru
2023-12-14 12:30 ` Jonathan Cameron
2023-12-14 12:57 ` Ceclan Dumitru [this message]
2023-12-14 14:47 ` Andy Shevchenko
2023-12-17 13:31 ` Jonathan Cameron
2023-12-12 15:09 ` [PATCH v8 1/2] dt-bindings: adc: add AD7173 David Lechner
2023-12-14 12:43 ` Ceclan Dumitru
2023-12-14 16:12 ` David Lechner
2023-12-14 17:03 ` Ceclan Dumitru
2023-12-17 13:50 ` Jonathan Cameron
2023-12-18 1:00 ` David Lechner
2023-12-20 12:38 ` Jonathan Cameron
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=375bf803-a5d5-4778-938a-b8218b116375@gmail.com \
--to=mitrutzceclan@gmail.com \
--cc=Jonathan.Cameron@Huawei.com \
--cc=andy.shevchenko@gmail.com \
--cc=andy@kernel.org \
--cc=arnd@arndb.de \
--cc=brgl@bgdev.pl \
--cc=chiaen_wu@richtek.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dumitru.ceclan@analog.com \
--cc=haibo.chen@nxp.com \
--cc=hvilleneuve@dimonoff.com \
--cc=jic23@kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=l.goehrs@pengutronix.de \
--cc=lars@metafoo.de \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michael@walle.cc \
--cc=mike.looijmans@topic.nl \
--cc=robh+dt@kernel.org \
--cc=schnelle@linux.ibm.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;
as well as URLs for NNTP newsgroup(s).