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
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, jonath4nns@gmail.com,
marcelo.schmitt1@gmail.com
Subject: Re: [PATCH RESEND v3 11/17] iio: adc: ad7768-1: add regulator to control VCM output
Date: Thu, 20 Feb 2025 16:20:51 -0600 [thread overview]
Message-ID: <2bc93cdf-e6d0-4879-a637-04db0bfe45aa@baylibre.com> (raw)
In-Reply-To: <3552833157f252f3b6813f0042059e858c90d53a.1739368121.git.Jonathan.Santos@analog.com>
On 2/12/25 12:17 PM, 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.
>
> Signed-off-by: Jonathan Santos <Jonathan.Santos@analog.com>
> ---
> v3 Changes:
> * Register VCM output via the regulator framework for improved flexibility
> and external integration.
>
> v2 Changes:
> * VCM output support is now defined by a devicetree property, instead of
> and IIO attribute.
> ---
> drivers/iio/adc/ad7768-1.c | 138 +++++++++++++++++++++++++++++++++++++
> 1 file changed, 138 insertions(+)
>
> diff --git a/drivers/iio/adc/ad7768-1.c b/drivers/iio/adc/ad7768-1.c
> index 378245bce199..a359cd8fceca 100644
> --- a/drivers/iio/adc/ad7768-1.c
> +++ b/drivers/iio/adc/ad7768-1.c
> @@ -12,8 +12,10 @@
> #include <linux/gpio/consumer.h>
> #include <linux/kernel.h>
> #include <linux/module.h>
> +#include <linux/of.h>
> #include <linux/regmap.h>
> #include <linux/regulator/consumer.h>
> +#include <linux/regulator/driver.h>
> #include <linux/sysfs.h>
> #include <linux/spi/spi.h>
>
> @@ -80,9 +82,15 @@
> #define AD7768_CONV_MODE_MSK GENMASK(2, 0)
> #define AD7768_CONV_MODE(x) FIELD_PREP(AD7768_CONV_MODE_MSK, x)
>
> +/* AD7768_REG_ANALOG2 */
> +#define AD7768_REG_ANALOG2_VCM_MSK GENMASK(2, 0)
> +#define AD7768_REG_ANALOG2_VCM(x) FIELD_PREP(AD7768_REG_ANALOG2_VCM_MSK, x)
> +
> #define AD7768_RD_FLAG_MSK(x) (BIT(6) | ((x) & 0x3F))
> #define AD7768_WR_FLAG_MSK(x) ((x) & 0x3F)
>
> +#define AD7768_VCM_OFF 0x08
> +
> enum ad7768_conv_mode {
> AD7768_CONTINUOUS,
> AD7768_ONE_SHOT,
> @@ -160,6 +168,7 @@ struct ad7768_state {
> struct regmap *regmap;
> struct regmap *regmap24;
> struct regulator *vref;
> + struct regulator_dev *vcm_rdev;
> struct clk *mclk;
> unsigned int mclk_freq;
> unsigned int samp_freq;
> @@ -643,6 +652,130 @@ static int ad7768_triggered_buffer_alloc(struct iio_dev *indio_dev)
> &ad7768_buffer_ops);
> }
>
> +static int ad7768_vcm_enable(struct regulator_dev *rdev)
> +{
> + struct ad7768_state *st = rdev_get_drvdata(rdev);
> + int ret, val;
> +
> + if (!st)
> + return -EINVAL;
Do we need iio_device_claim_direct_mode() here to prevent accessing
registers on the ADC during a buffered read?
Same applies to other functions too.
> +
> + ret = regmap_read(st->regmap, AD7768_REG_ANALOG2, &val);
> + if (ret)
> + return ret;
> +
> + /* if regulator is off, turn it on */
> + if (FIELD_GET(AD7768_REG_ANALOG2_VCM_MSK, val) == AD7768_VCM_OFF)
regmap_update_bits() already does this sort of check internally, so
open-coding it here is redundant.
> + return regmap_update_bits(st->regmap, AD7768_REG_ANALOG2,
> + AD7768_REG_ANALOG2_VCM_MSK, 0x00);
Can be simplified with regmap_clear_bits().
> +
> + return 0;
> +}
> +
> +static int ad7768_vcm_disable(struct regulator_dev *rdev)
> +{
> + struct ad7768_state *st = rdev_get_drvdata(rdev);
> +
> + if (!st)
> + return -EINVAL;
> +
> + return regmap_update_bits(st->regmap, AD7768_REG_ANALOG2,
> + AD7768_REG_ANALOG2_VCM_MSK, AD7768_VCM_OFF);
> +}
> +
> +static int ad7768_vcm_is_enabled(struct regulator_dev *rdev)
> +{
> + struct ad7768_state *st = rdev_get_drvdata(rdev);
> + int ret, val;
> +
> + if (!st)
> + return -EINVAL;
> +
> + ret = regmap_read(st->regmap, AD7768_REG_ANALOG2, &val);
> + if (ret)
> + return ret;
> +
> + if (FIELD_GET(AD7768_REG_ANALOG2_VCM_MSK, val) == AD7768_VCM_OFF)
> + return 0;
Could skip the if and just return directly.
> +
> + return 1;
> +}
> +
> +static int ad7768_set_voltage_sel(struct regulator_dev *rdev,
> + unsigned int selector)
> +{
> + unsigned int regval = AD7768_REG_ANALOG2_VCM(selector + 1);
> + struct ad7768_state *st = rdev_get_drvdata(rdev);
> +
> + if (!st)
> + return -EINVAL;
> +
> + return regmap_update_bits(st->regmap, AD7768_REG_ANALOG2,
> + AD7768_REG_ANALOG2_VCM_MSK, regval);
> +}
> +
> +static int ad7768_get_voltage_sel(struct regulator_dev *rdev)
> +{
> + struct ad7768_state *st = rdev_get_drvdata(rdev);
> + int ret, val;
> +
> + if (!st)
> + return -EINVAL;
> +
> + ret = regmap_read(st->regmap, AD7768_REG_ANALOG2, &val);
> + if (ret)
> + return ret;
> +
> + val = FIELD_GET(AD7768_REG_ANALOG2_VCM_MSK, val) - 1;
> + val = clamp(val, 0, 8);
> +
> + return val;
> +}
> +
> +static const struct regulator_ops vcm_regulator_ops = {
> + .enable = ad7768_vcm_enable,
> + .disable = ad7768_vcm_disable,
> + .is_enabled = ad7768_vcm_is_enabled,
> + .list_voltage = regulator_list_voltage_table,
> + .set_voltage_sel = ad7768_set_voltage_sel,
> + .get_voltage_sel = ad7768_get_voltage_sel,
> +};
> +
> +static const unsigned int vcm_voltage_table[] = {
> + 2500000,
> + 2050000,
> + 1650000,
> + 1900000,
> + 1100000,
> + 900000,
> +};
> +
> +static const struct regulator_desc vcm_desc = {
> + .name = "vcm_output",
It looks like this is typically a datasheet name, like
"AD7768-1 VCM"
> + .of_match = of_match_ptr("vcm_output"),
"vcm-output" as in DT bindings review.
> + .regulators_node = of_match_ptr("regulators"),
> + .n_voltages = ARRAY_SIZE(vcm_voltage_table),
> + .volt_table = vcm_voltage_table,
> + .ops = &vcm_regulator_ops,
> + .type = REGULATOR_VOLTAGE,
> + .owner = THIS_MODULE,
> +};
> +
> +static int ad7768_register_regulators(struct device *dev, struct ad7768_state *st)
> +{
> + struct regulator_config config = {
> + .dev = dev,
> + .driver_data = st,
> + };
> +
> + 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;
> +}
> +
> static int ad7768_probe(struct spi_device *spi)
> {
> struct ad7768_state *st;
> @@ -707,6 +840,11 @@ static int ad7768_probe(struct spi_device *spi)
> indio_dev->info = &ad7768_info;
> indio_dev->modes = INDIO_DIRECT_MODE;
>
> + /* Register VCM output regulator */
> + ret = ad7768_register_regulators(&spi->dev, st);
> + if (ret)
> + return ret;
> +
> ret = ad7768_setup(st);
> if (ret < 0) {
> dev_err(&spi->dev, "AD7768 setup failed\n");
next prev parent reply other threads:[~2025-02-20 22:20 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-12 18:15 [PATCH RESEND v3 00/17] iio: adc: ad7768-1: Add features, improvements, and fixes Jonathan Santos
2025-02-12 18:15 ` [PATCH RESEND v3 01/17] iio: adc: ad7768-1: Fix conversion result sign Jonathan Santos
2025-02-12 18:16 ` [PATCH RESEND v3 02/17] iio: adc: ad7768-1: set MOSI idle state to prevent accidental reset Jonathan Santos
2025-02-16 15:59 ` Jonathan Cameron
2025-02-12 18:16 ` [PATCH RESEND v3 03/17] dt-bindings: iio: adc: ad7768-1: add trigger-sources property Jonathan Santos
2025-02-13 20:24 ` Conor Dooley
2025-02-27 21:30 ` Jonathan Santos
2025-03-21 14:39 ` Rob Herring
2025-02-12 18:16 ` [PATCH RESEND v3 04/17] dt-bindings: iio: adc: ad7768-1: Document GPIO controller Jonathan Santos
2025-02-12 18:16 ` [PATCH RESEND v3 05/17] dt-bindings: iio: adc: ad7768-1: document regulator provider property Jonathan Santos
2025-02-13 20:25 ` Conor Dooley
2025-02-20 21:22 ` David Lechner
2025-02-12 18:16 ` [PATCH RESEND v3 06/17] Documentation: ABI: add wideband filter type to sysfs-bus-iio Jonathan Santos
2025-02-20 21:28 ` David Lechner
2025-02-22 11:51 ` Jonathan Cameron
2025-02-12 18:17 ` [PATCH RESEND v3 07/17] iio: adc: ad7768-1: remove unnecessary locking Jonathan Santos
2025-02-20 21:30 ` David Lechner
2025-02-12 18:17 ` [PATCH RESEND v3 08/17] iio: adc: ad7768-1: convert driver to use regmap Jonathan Santos
2025-02-16 16:06 ` Jonathan Cameron
2025-02-20 21:41 ` David Lechner
2025-02-12 18:17 ` [PATCH RESEND v3 09/17] iio: adc: ad7768-1: Add reset gpio Jonathan Santos
2025-02-12 18:17 ` [PATCH RESEND v3 10/17] iio: adc: ad7768-1: Move buffer allocation to a separate function Jonathan Santos
2025-02-20 21:43 ` David Lechner
2025-02-12 18:17 ` [PATCH RESEND v3 11/17] iio: adc: ad7768-1: add regulator to control VCM output Jonathan Santos
2025-02-13 22:57 ` kernel test robot
2025-02-16 16:11 ` Jonathan Cameron
2025-02-20 22:20 ` David Lechner [this message]
2025-02-12 18:18 ` [PATCH RESEND v3 12/17] iio: adc: ad7768-1: Add GPIO controller support Jonathan Santos
2025-02-16 16:14 ` Jonathan Cameron
2025-02-19 20:34 ` Linus Walleij
2025-02-20 22:27 ` David Lechner
2025-02-27 21:36 ` Jonathan Santos
2025-02-27 21:54 ` David Lechner
2025-02-28 8:52 ` Linus Walleij
2025-02-28 15:55 ` David Lechner
2025-03-04 8:03 ` Linus Walleij
2025-02-12 18:18 ` [PATCH RESEND v3 13/17] iio: adc: ad7768-1: add multiple scan types to support 16-bits mode Jonathan Santos
2025-02-20 22:38 ` David Lechner
2025-02-12 18:18 ` [PATCH RESEND v3 14/17] iio: adc: ad7768-1: add support for Synchronization over SPI Jonathan Santos
2025-02-12 18:18 ` [PATCH RESEND v3 15/17] iio: adc: ad7768-1: replace manual attribute declaration Jonathan Santos
2025-02-16 16:21 ` Jonathan Cameron
2025-02-12 18:18 ` [PATCH RESEND v3 16/17] iio: adc: ad7768-1: add filter type and oversampling ratio attributes Jonathan Santos
2025-02-16 16:31 ` Jonathan Cameron
2025-02-20 13:28 ` Jonathan Santos
2025-02-12 18:19 ` [PATCH RESEND v3 17/17] iio: adc: ad7768-1: add low pass -3dB cutoff attribute Jonathan Santos
2025-02-16 16:33 ` 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=2bc93cdf-e6d0-4879-a637-04db0bfe45aa@baylibre.com \
--to=dlechner@baylibre.com \
--cc=Jonathan.Santos@analog.com \
--cc=Michael.Hennerich@analog.com \
--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=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).