From: Jonathan Cameron <jic23@kernel.org>
To: Olivier Moysan <olivier.moysan@foss.st.com>
Cc: Alexandre Torgue <alexandre.torgue@foss.st.com>,
Arnaud Pouliquen <arnaud.pouliquen@foss.st.com>,
Fabrice Gasnier <fabrice.gasnier@st.com>,
Lars-Peter Clausen <lars@metafoo.de>,
Maxime Coquelin <mcoquelin.stm32@gmail.com>,
Rob Herring <robh+dt@kernel.org>, <alsa-devel@alsa-project.org>,
<devicetree@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-iio@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<linux-stm32@st-md-mailman.stormreply.com>
Subject: Re: [PATCH 4/7] iio: adc: stm32-adc: add support of generic channels binding
Date: Sat, 11 Sep 2021 17:08:23 +0100 [thread overview]
Message-ID: <20210911170823.292aa672@jic23-huawei> (raw)
In-Reply-To: <20210908155452.25458-5-olivier.moysan@foss.st.com>
On Wed, 8 Sep 2021 17:54:49 +0200
Olivier Moysan <olivier.moysan@foss.st.com> wrote:
> Add support of generic IIO channel binding:
> ./devicetree/bindings/iio/adc/adc.yaml
> Keep support of st,adc-channels and st,adc-diff-channels
> for backward compatibility.
>
> Signed-off-by: Olivier Moysan <olivier.moysan@foss.st.com>
Hi Olivier,
A few minor things inline.
Thanks,
Jonathan
> ---
> drivers/iio/adc/stm32-adc.c | 99 +++++++++++++++++++++++++++++++++----
> 1 file changed, 90 insertions(+), 9 deletions(-)
>
> diff --git a/drivers/iio/adc/stm32-adc.c b/drivers/iio/adc/stm32-adc.c
> index 2f137d14f141..ae4a314854f7 100644
> --- a/drivers/iio/adc/stm32-adc.c
> +++ b/drivers/iio/adc/stm32-adc.c
> @@ -35,7 +35,7 @@
> #define STM32H7_BOOST_CLKRATE 20000000UL
>
> #define STM32_ADC_CH_MAX 20 /* max number of channels */
> -#define STM32_ADC_CH_SZ 10 /* max channel name size */
> +#define STM32_ADC_CH_SZ 16 /* max channel name size */
> #define STM32_ADC_MAX_SQ 16 /* SQ1..SQ16 */
> #define STM32_ADC_MAX_SMP 7 /* SMPx range is [0..7] */
> #define STM32_ADC_TIMEOUT_US 100000
> @@ -1732,6 +1732,11 @@ static int stm32_adc_get_legacy_chan_count(struct iio_dev *indio_dev, struct stm
> num_channels += ret;
> }
>
> + if (!num_channels) {
> + dev_err(indio_dev->dev.parent, "No channel found\n");
> + return -ENODATA;
I'd return 0 and handle this at the caller. Both because it makes this
patch more readable and because a count of 0 isn't an error of the function
reading how many they are, but rather at a higher level.
> + }
> +
> return num_channels;
> }
>
> @@ -1792,6 +1797,73 @@ static int stm32_adc_legacy_chan_init(struct iio_dev *indio_dev,
> return scan_index;
> }
>
> +static int stm32_adc_generic_chan_init(struct iio_dev *indio_dev,
> + struct stm32_adc *adc,
> + struct iio_chan_spec *channels)
> +{
> + struct device_node *node = indio_dev->dev.of_node;
> + const struct stm32_adc_info *adc_info = adc->cfg->adc_info;
> + struct device_node *child;
> + const char *name;
> + int val, scan_index = 0, ret;
> + bool differential;
> + u32 vin[2];
> +
> + for_each_available_child_of_node(node, child) {
> + ret = of_property_read_u32(child, "reg", &val);
> + if (ret) {
> + dev_err(&indio_dev->dev, "Missing channel index %d\n", ret);
> + goto err;
> + }
> +
> + ret = of_property_read_string(child, "label", &name);
> + /* label is optional */
> + if (!ret) {
> + if (strlen(name) >= STM32_ADC_CH_SZ) {
> + dev_err(&indio_dev->dev, "Label %s exceeds %d characters\n",
> + name, STM32_ADC_CH_SZ);
> + return -EINVAL;
> + }
> + strncpy(adc->chan_name[val], name, STM32_ADC_CH_SZ);
> + } else if (ret != -EINVAL) {
> + dev_err(&indio_dev->dev, "Invalid label %d\n", ret);
> + goto err;
> + }
> +
> + if (val >= adc_info->max_channels) {
> + dev_err(&indio_dev->dev, "Invalid channel %d\n", val);
> + ret = -EINVAL;
> + goto err;
> + }
> +
> + differential = false;
> + ret = of_property_read_u32_array(child, "diff-channels", vin, 2);
> + /* diff-channels is optional */
> + if (!ret) {
> + differential = true;
> + if (vin[0] != val || vin[1] >= adc_info->max_channels) {
> + dev_err(&indio_dev->dev, "Invalid channel in%d-in%d\n",
> + vin[0], vin[1]);
> + goto err;
> + }
> + } else if (ret != -EINVAL) {
> + dev_err(&indio_dev->dev, "Invalid diff-channels property %d\n", ret);
> + goto err;
> + }
> +
> + stm32_adc_chan_init_one(indio_dev, &channels[scan_index], val,
> + vin[1], scan_index, differential);
> + scan_index++;
> + }
> +
> + return scan_index;
> +
> +err:
> + of_node_put(child);
> +
> + return ret;
> +}
> +
> static int stm32_adc_chan_of_init(struct iio_dev *indio_dev, bool timestamping)
> {
> struct device_node *node = indio_dev->dev.of_node;
> @@ -1800,15 +1872,21 @@ static int stm32_adc_chan_of_init(struct iio_dev *indio_dev, bool timestamping)
> struct iio_chan_spec *channels;
> int scan_index = 0, num_channels = 0, ret, i;
> u32 smp = 0;
> + bool legacy = false;
>
> - ret = stm32_adc_get_legacy_chan_count(indio_dev, adc);
> - if (ret < 0)
> - return ret;
> - num_channels = ret;
> -
> + num_channels = of_get_available_child_count(node);
> + /*
> + * If no channels have been found, fallback to channels legacy properties.
> + * Legacy channel properties will be ignored, if some channels are
drop the ,
Legacy channel properties will be ignored if some channels...
> + * already defined using the standard binding.
> + */
> if (!num_channels) {
> - dev_err(&indio_dev->dev, "No channels configured\n");
> - return -ENODATA;
> + ret = stm32_adc_get_legacy_chan_count(indio_dev, adc);
> + if (ret < 0)
> + return ret;
> +
> + legacy = true;
Trivial but I would set legacy at top of this if block so it is nearer the comment.
> + num_channels = ret;
> }
>
> if (num_channels > adc_info->max_channels) {
> @@ -1832,7 +1910,10 @@ static int stm32_adc_chan_of_init(struct iio_dev *indio_dev, bool timestamping)
> if (!channels)
> return -ENOMEM;
>
> - ret = stm32_adc_legacy_chan_init(indio_dev, adc, channels);
> + if (legacy)
> + ret = stm32_adc_legacy_chan_init(indio_dev, adc, channels);
> + else
> + ret = stm32_adc_generic_chan_init(indio_dev, adc, channels);
> if (ret < 0)
> return ret;
> scan_index = ret;
next prev parent reply other threads:[~2021-09-11 16:04 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-08 15:54 [PATCH 0/7] add internal channels support Olivier Moysan
2021-09-08 15:54 ` [PATCH 1/7] dt-bindings: iio: adc: add generic channel binding Olivier Moysan
2021-09-11 15:51 ` Jonathan Cameron
2021-09-21 17:08 ` Rob Herring
2021-09-08 15:54 ` [PATCH 2/7] dt-bindings: iio: adc: add nvmem support for vrefint internal channel Olivier Moysan
2021-09-21 17:10 ` Rob Herring
2021-09-08 15:54 ` [PATCH 3/7] iio: adc stm32-adc: split channel init into several routines Olivier Moysan
2021-09-08 15:54 ` [PATCH 4/7] iio: adc: stm32-adc: add support of generic channels binding Olivier Moysan
2021-09-11 16:08 ` Jonathan Cameron [this message]
2021-09-08 15:54 ` [PATCH 5/7] iio: adc: stm32-adc: add support of internal channels Olivier Moysan
2021-09-11 16:17 ` Jonathan Cameron
2021-09-08 15:54 ` [PATCH 6/7] iio: adc: stm32-adc: add vrefint calibration support Olivier Moysan
2021-09-11 16:28 ` Jonathan Cameron
2021-09-15 10:02 ` Olivier MOYSAN
2021-09-18 18:42 ` Jonathan Cameron
2021-09-22 7:53 ` Olivier MOYSAN
2021-09-26 12:09 ` Jonathan Cameron
2021-09-08 15:54 ` [PATCH 7/7] iio: adc: stm32-adc: use generic binding for sample-time Olivier Moysan
2021-09-11 15:44 ` [PATCH 0/7] add internal channels support 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=20210911170823.292aa672@jic23-huawei \
--to=jic23@kernel.org \
--cc=alexandre.torgue@foss.st.com \
--cc=alsa-devel@alsa-project.org \
--cc=arnaud.pouliquen@foss.st.com \
--cc=devicetree@vger.kernel.org \
--cc=fabrice.gasnier@st.com \
--cc=lars@metafoo.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=mcoquelin.stm32@gmail.com \
--cc=olivier.moysan@foss.st.com \
--cc=robh+dt@kernel.org \
/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).