From: David Lechner <dlechner@baylibre.com>
To: Jonathan Santos <Jonathan.Santos@analog.com>,
linux-iio@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-gpio@vger.kernel.org
Cc: lars@metafoo.de, Michael.Hennerich@analog.com,
marcelo.schmitt@analog.com, jic23@kernel.org, robh@kernel.org,
krzk+dt@kernel.org, conor+dt@kernel.org,
marcelo.schmitt1@gmail.com, linus.walleij@linaro.org,
brgl@bgdev.pl, lgirdwood@gmail.com, broonie@kernel.org,
jonath4nns@gmail.com
Subject: Re: [PATCH v5 08/14] iio: adc: ad7768-1: add regulator to control VCM output
Date: Fri, 11 Apr 2025 16:44:55 -0500 [thread overview]
Message-ID: <bbdbf4ff-662e-459b-a31f-bc58e738a51f@baylibre.com> (raw)
In-Reply-To: <7753dcd690f07f855100fc28e7b8ae746082de1c.1744325346.git.Jonathan.Santos@analog.com>
On 4/11/25 10:57 AM, Jonathan Santos wrote:
> The VCM output voltage can be used as a common-mode voltage within the
> amplifier preconditioning circuits external to the AD7768-1.
>
> This change allows the user to configure VCM output using the regulator
> framework.
>
> Acked-by: Marcelo Schmitt <marcelo.schmitt@analog.com>
> Signed-off-by: Jonathan Santos <Jonathan.Santos@analog.com>
> ---
...
> +static int ad7768_vcm_is_enabled(struct regulator_dev *rdev)
> +{
> + struct iio_dev *indio_dev = rdev_get_drvdata(rdev);
> + struct ad7768_state *st = iio_priv(indio_dev);
> + int ret, val;
> +
> + if (!indio_dev)
> + return -EINVAL;
> +
> + if (!iio_device_claim_direct(indio_dev))
> + return -EBUSY;
> +
> + ret = regmap_read(st->regmap, AD7768_REG_ANALOG2, &val);
If we put iio_device_release_direct(indio_dev); here, we can avoid
the goto.
> + if (ret)
> + goto err_release;
> +
> + ret = FIELD_GET(AD7768_REG_ANALOG2_VCM_MSK, val) != AD7768_VCM_OFF;
> +err_release:
> + iio_device_release_direct(indio_dev);
> +
> + return ret;
> +}
> +
> +static int ad7768_set_voltage_sel(struct regulator_dev *rdev,
> + unsigned int selector)
> +{
> + unsigned int regval = AD7768_REG_ANALOG2_VCM(selector + 1);
> + struct iio_dev *indio_dev = rdev_get_drvdata(rdev);
> + struct ad7768_state *st = iio_priv(indio_dev);
> + int ret;
> +
> + if (!indio_dev)
> + return -EINVAL;
> +
> + if (!iio_device_claim_direct(indio_dev))
> + return -EBUSY;
> +
> + ret = regmap_update_bits(st->regmap, AD7768_REG_ANALOG2,
> + AD7768_REG_ANALOG2_VCM_MSK, regval);
> + iio_device_release_direct(indio_dev);
> + st->vcm_output_sel = selector;
Do we still want to make this assignment if there is an error?
> +
> + return ret;
> +}
> +
> +static int ad7768_get_voltage_sel(struct regulator_dev *rdev)
> +{
> + struct iio_dev *indio_dev = rdev_get_drvdata(rdev);
> + struct ad7768_state *st = iio_priv(indio_dev);
> + int ret, val;
> +
> + if (!indio_dev)
> + return -EINVAL;
> +
> + if (!iio_device_claim_direct(indio_dev))
> + return -EBUSY;
> +
> + ret = regmap_read(st->regmap, AD7768_REG_ANALOG2, &val);
> + if (ret)
> + goto err_release;
Can rearrange to avoid goto here too.
> +
> + val = FIELD_GET(AD7768_REG_ANALOG2_VCM_MSK, val);
> + ret = clamp(val, 1, (int)rdev->desc->n_voltages) - 1;
> +err_release:
> + iio_device_release_direct(indio_dev);
> +
> + return ret;
> +}
> +
...
> +static int ad7768_register_regulators(struct device *dev, struct ad7768_state *st,
> + struct iio_dev *indio_dev)
> +{
> + struct regulator_config config = {
> + .dev = dev,
> + .driver_data = indio_dev,
> + };
> + int ret;
> +
> + /* Disable the regulator before registering it */
> + ret = regmap_update_bits(st->regmap, AD7768_REG_ANALOG2,
> + AD7768_REG_ANALOG2_VCM_MSK, AD7768_VCM_OFF);
> + if (ret)
> + return -EINVAL;
Why not return ret; ?
> +
> + st->vcm_rdev = devm_regulator_register(dev, &vcm_desc, &config);
> + if (IS_ERR(st->vcm_rdev))
> + return dev_err_probe(dev, PTR_ERR(st->vcm_rdev),
> + "failed to register VCM regulator\n");
> +
> + return 0;
> +}
> +
next prev parent reply other threads:[~2025-04-11 21:44 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-11 15:55 [PATCH v5 00/14] iio: adc: ad7768-1: Add features, improvements, and fixes Jonathan Santos
2025-04-11 15:56 ` [PATCH v5 01/14] dt-bindings: trigger-source: add generic GPIO trigger source Jonathan Santos
2025-04-11 16:41 ` Conor Dooley
2025-04-11 21:49 ` David Lechner
2025-04-16 7:43 ` Linus Walleij
2025-04-16 18:38 ` David Lechner
2025-04-11 15:56 ` [PATCH v5 02/14] dt-bindings: iio: adc: ad7768-1: add trigger-sources property Jonathan Santos
2025-04-11 16:30 ` Conor Dooley
2025-04-11 21:27 ` David Lechner
2025-04-17 0:08 ` Jonathan Santos
2025-04-17 15:11 ` David Lechner
2025-04-11 21:57 ` David Lechner
2025-04-17 0:22 ` Jonathan Santos
2025-04-17 15:07 ` David Lechner
2025-04-11 15:56 ` [PATCH v5 03/14] dt-bindings: iio: adc: ad7768-1: Document GPIO controller Jonathan Santos
2025-04-11 15:56 ` [PATCH v5 04/14] dt-bindings: iio: adc: ad7768-1: document regulator provider property Jonathan Santos
2025-04-11 15:56 ` [PATCH v5 05/14] iio: adc: ad7768-1: convert driver to use regmap Jonathan Santos
2025-04-12 17:51 ` Jonathan Cameron
2025-04-11 15:57 ` [PATCH v5 06/14] iio: adc: ad7768-1: Add reset gpio Jonathan Santos
2025-04-12 17:52 ` Jonathan Cameron
2025-04-11 15:57 ` [PATCH v5 07/14] iio: adc: ad7768-1: Move buffer allocation to a separate function Jonathan Santos
2025-04-12 17:54 ` Jonathan Cameron
2025-04-11 15:57 ` [PATCH v5 08/14] iio: adc: ad7768-1: add regulator to control VCM output Jonathan Santos
2025-04-11 21:44 ` David Lechner [this message]
2025-04-12 18:02 ` Jonathan Cameron
2025-04-11 15:57 ` [PATCH v5 09/14] iio: adc: ad7768-1: Add GPIO controller support Jonathan Santos
2025-04-16 7:35 ` Linus Walleij
2025-04-11 15:58 ` [PATCH v5 10/14] iio: adc: ad7768-1: add multiple scan types to support 16-bits mode Jonathan Santos
2025-04-11 15:58 ` [PATCH v5 11/14] iio: adc: ad7768-1: add support for Synchronization over SPI Jonathan Santos
2025-04-11 22:48 ` David Lechner
2025-04-11 15:58 ` [PATCH v5 12/14] iio: adc: ad7768-1: replace manual attribute declaration Jonathan Santos
2025-04-11 15:58 ` [PATCH v5 13/14] iio: adc: ad7768-1: add filter type and oversampling ratio attributes Jonathan Santos
2025-04-11 23:26 ` David Lechner
2025-04-12 18:11 ` Jonathan Cameron
2025-04-11 15:59 ` [PATCH v5 14/14] iio: adc: ad7768-1: add low pass -3dB cutoff attribute Jonathan Santos
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=bbdbf4ff-662e-459b-a31f-bc58e738a51f@baylibre.com \
--to=dlechner@baylibre.com \
--cc=Jonathan.Santos@analog.com \
--cc=Michael.Hennerich@analog.com \
--cc=brgl@bgdev.pl \
--cc=broonie@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jic23@kernel.org \
--cc=jonath4nns@gmail.com \
--cc=krzk+dt@kernel.org \
--cc=lars@metafoo.de \
--cc=lgirdwood@gmail.com \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo.schmitt1@gmail.com \
--cc=marcelo.schmitt@analog.com \
--cc=robh@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).