From: andy.shevchenko@gmail.com
To: Herve Codina <herve.codina@bootlin.com>
Cc: Liam Girdwood <lgirdwood@gmail.com>,
Mark Brown <broonie@kernel.org>, Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>,
Jonathan Cameron <jic23@kernel.org>,
Lars-Peter Clausen <lars@metafoo.de>,
Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.com>,
Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>,
alsa-devel@alsa-project.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-iio@vger.kernel.org,
Christophe Leroy <christophe.leroy@csgroup.eu>,
Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Subject: Re: [PATCH v2 7/9] ASoC: codecs: Add support for the generic IIO auxiliary devices
Date: Sat, 3 Jun 2023 21:26:19 +0300 [thread overview]
Message-ID: <ZHuFywIrTnEFpX6e@surfacebook> (raw)
In-Reply-To: <20230523151223.109551-8-herve.codina@bootlin.com>
Tue, May 23, 2023 at 05:12:21PM +0200, Herve Codina kirjoitti:
> Industrial I/O devices can be present in the audio path.
> These devices needs to be used as audio components in order to be fully
> integrated in the audio path.
>
> This support allows to consider these Industrial I/O devices as auxliary
> audio devices and allows to control them using mixer controls.
...
> +// audio-iio-aux.c -- ALSA SoC glue to use IIO devices as audio components
Putting file name into file is not a good idea in case the file will be renamed
in the future.
...
> +struct audio_iio_aux_chan {
> + struct iio_channel *iio_chan;
> + const char *name;
> + bool is_invert_range;
If you put bool after int:s it may save a few bytes in some cases.
> + int max;
> + int min;
Wondering if there is already a data type for the ranges (like linear_range.h,
but not sure it's applicable here).
> +};
...
> + if (val < 0)
> + return -EINVAL;
> + if (val > max - min)
Btw, who will validate that max > min?
> + return -EINVAL;
...
> + return 1; /* The value changed */
Perhaps this 1 needs a definition?
...
> +static struct snd_soc_dapm_widget widgets[3] = {0};
> +static struct snd_soc_dapm_route routes[2] = {0};
0:s are not needed. Moreover, the entire assingments are redundant
as this is guaranteed by the C standard.
...
> + char *input_name = NULL;
> + char *output_name = NULL;
> + char *pga_name = NULL;
Redundant assignments if you properly label the freeing.
...
> + BUILD_BUG_ON(ARRAY_SIZE(widgets) < 3);
Use static_assert() at the place where the array is defined.
...
> + BUILD_BUG_ON(ARRAY_SIZE(routes) < 2);
Ditto.
...
> +end:
out_free:
> + /* Allocated names are no more needed (duplicated in ASoC internals) */
> + kfree(pga_name);
> + kfree(output_name);
> + kfree(input_name);
> +
> + return ret;
...
> + for (i = 0; i < iio_aux->num_chans; i++) {
> + chan = iio_aux->chans + i;
> +
> + ret = iio_read_max_channel_raw(chan->iio_chan, &chan->max);
> + if (ret) {
> + dev_err(component->dev, "chan[%d] %s: Cannot get max raw value (%d)\n",
> + i, chan->name, ret);
> + return ret;
It sounds like a part of ->probe() flow, correct?
Can dev_err_probe() be used here?
> + }
> +
> + ret = iio_read_min_channel_raw(chan->iio_chan, &chan->min);
> + if (ret) {
> + dev_err(component->dev, "chan[%d] %s: Cannot get min raw value (%d)\n",
> + i, chan->name, ret);
> + return ret;
Ditto.
> + }
> +
> + /* Set initial value */
> + ret = iio_write_channel_raw(chan->iio_chan,
> + chan->is_invert_range ? chan->max : chan->min);
> + if (ret) {
> + dev_err(component->dev, "chan[%d] %s: Cannot set initial value (%d)\n",
> + i, chan->name, ret);
> + return ret;
Ditto.
> + }
...
> + dev_dbg(component->dev, "chan[%d]: Added %s (min=%d, max=%d, invert=%s)\n",
> + i, chan->name, chan->min, chan->max,
> + chan->is_invert_range ? "on" : "off");
str_on_off()
> + }
...
> + count = of_property_count_strings(np, "io-channel-names");
> + if (count < 0) {
> + dev_err(iio_aux->dev, "%pOF: failed to read io-channel-names\n", np);
> + return count;
return dev_err_probe();
> + }
...
> + for (i = 0; i < iio_aux->num_chans; i++) {
> + iio_aux_chan = iio_aux->chans + i;
> +
> + ret = of_property_read_string_index(np, "io-channel-names", i,
> + &iio_aux_chan->name);
> + if (ret < 0) {
> + dev_err(iio_aux->dev, "%pOF: failed to read io-channel-names[%d]\n", np, i);
> + return ret;
Ditto.
> + }
> + tmp = 0;
> + of_property_read_u32_index(np, "snd-control-invert-range", i, &tmp);
> + iio_aux_chan->is_invert_range = tmp;
You can use this variable directly.
> + }
Btw, can you avoid using OF APIs? It's better to have device property/fwnode
API to be used from day 1.
...
> + platform_set_drvdata(pdev, iio_aux);
Which callback is using this driver data?
...
> +static const struct of_device_id audio_iio_aux_ids[] = {
> + { .compatible = "audio-iio-aux", },
Inner comma is not needed.
> + { }
> +};
...
> +static struct platform_driver audio_iio_aux_driver = {
> + .driver = {
> + .name = "audio-iio-aux",
> + .of_match_table = audio_iio_aux_ids,
> + },
> + .probe = audio_iio_aux_probe,
> +};
> +
Redundant blank line
> +module_platform_driver(audio_iio_aux_driver);
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2023-06-03 18:26 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-23 15:12 [PATCH v2 0/9] Add support for IIO devices in ASoC Herve Codina
2023-05-23 15:12 ` [PATCH v2 1/9] ASoC: dt-bindings: Add audio-iio-aux Herve Codina
2023-05-23 15:12 ` [PATCH v2 2/9] ASoC: dt-bindings: simple-card: Add additional-devs subnode Herve Codina
2023-05-23 15:12 ` [PATCH v2 3/9] iio: inkern: Check error explicitly in iio_channel_read_max() Herve Codina
2023-05-28 17:32 ` Jonathan Cameron
2023-05-23 15:12 ` [PATCH v2 4/9] iio: consumer.h: Fix raw values documentation notes Herve Codina
2023-05-28 17:29 ` Jonathan Cameron
2023-05-23 15:12 ` [PATCH v2 5/9] iio: inkern: Add a helper to query an available minimum raw value Herve Codina
2023-05-28 17:33 ` Jonathan Cameron
2023-06-03 14:04 ` andy.shevchenko
2023-06-05 7:46 ` Herve Codina
2023-06-05 9:45 ` Andy Shevchenko
2023-06-05 14:11 ` Herve Codina
2023-06-05 17:05 ` Jonathan Cameron
2023-06-05 17:36 ` Herve Codina
2023-05-23 15:12 ` [PATCH v2 6/9] ASoC: soc-dapm.h: Add a helper to build a DAPM widget dynamically Herve Codina
2023-06-03 14:07 ` andy.shevchenko
2023-06-05 8:54 ` Herve Codina
2023-06-05 12:35 ` Herve Codina
2023-05-23 15:12 ` [PATCH v2 7/9] ASoC: codecs: Add support for the generic IIO auxiliary devices Herve Codina
2023-05-28 17:38 ` Jonathan Cameron
2023-06-05 17:22 ` Herve Codina
2023-06-03 18:26 ` andy.shevchenko [this message]
2023-06-06 13:54 ` Herve Codina
2023-06-06 14:34 ` Andy Shevchenko
2023-06-07 14:56 ` Herve Codina
2023-06-07 13:23 ` Herve Codina
2023-05-23 15:12 ` [PATCH v2 8/9] ASoC: simple-card: Add missing of_node_put() in case of error Herve Codina
2023-05-23 23:24 ` Kuninori Morimoto
2023-05-23 15:12 ` [PATCH v2 9/9] ASoC: simple-card: Handle additional devices Herve Codina
2023-05-24 0:08 ` Kuninori Morimoto
2023-05-24 0:36 ` Kuninori Morimoto
2023-05-24 12:14 ` Herve Codina
2023-05-25 0:01 ` Kuninori Morimoto
2023-05-26 13:07 ` Herve Codina
2023-05-29 0:18 ` Kuninori Morimoto
2023-06-03 18:27 ` andy.shevchenko
2023-05-26 16:31 ` (subset) [PATCH v2 0/9] Add support for IIO devices in ASoC Mark Brown
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=ZHuFywIrTnEFpX6e@surfacebook \
--to=andy.shevchenko@gmail.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=christophe.leroy@csgroup.eu \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=herve.codina@bootlin.com \
--cc=jic23@kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=kuninori.morimoto.gx@renesas.com \
--cc=lars@metafoo.de \
--cc=lgirdwood@gmail.com \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=perex@perex.cz \
--cc=robh+dt@kernel.org \
--cc=thomas.petazzoni@bootlin.com \
--cc=tiwai@suse.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).