From: Jonathan Santos <jonath4nns@gmail.com>
To: Andy Shevchenko <andy.shevchenko@gmail.com>
Cc: 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,
Sergiu Cuciurean <sergiu.cuciurean@analog.com>,
andy@kernel.org, nuno.sa@analog.com,
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, dlechner@baylibre.com,
Bartosz Golaszewski <bartosz.golaszewski@linaro.org>
Subject: Re: [PATCH v6 06/11] iio: adc: ad7768-1: Add GPIO controller support
Date: Wed, 30 Apr 2025 20:37:11 -0300 [thread overview]
Message-ID: <aBK0J8yriQy3BcN5@JSANTO12-L01.ad.analog.com> (raw)
In-Reply-To: <CAHp75VdbD4HTonEZT8O-3bsqQ70_XRnZd7vS7gdyrG2gKYBHPA@mail.gmail.com>
On 04/28, Andy Shevchenko wrote:
> On Mon, Apr 28, 2025 at 3:13 AM Jonathan Santos
> <Jonathan.Santos@analog.com> wrote:
> >
> > The AD7768-1 has the ability to control other local hardware (such as gain
> > stages),to power down other blocks in the signal chain, or read local
> > status signals over the SPI interface.
> >
> > Add direct mode conditional locks in the gpio callbacks to prevent register
> > access when the device is in buffered mode.
> >
> > This change exports the AD7768-1's four gpios and makes them accessible
> > at an upper layer.
>
> ...
>
> > +#include <linux/gpio.h>
>
> No way. This header must not be in any of the code. (Yes, there are
> leftovers in the kernel, but work is ongoing to clean that up)
>
Sorry about that, will fix it.
> > +#include <linux/gpio/driver.h>
> > #include <linux/gpio/consumer.h>
>
> > #include <linux/kernel.h>
>
> And since you are doing the big series for the driver, please drop
> this header and replace it (if required) with what is used. No driver
> code should use kernel.h.
>
Sure, noted.
> > #include <linux/module.h>
>
> ...
>
> > struct ad7768_state {
>
> > struct regulator_dev *vcm_rdev;
> > unsigned int vcm_output_sel;
> > struct clk *mclk;
> > + struct gpio_chip gpiochip;
> > unsigned int mclk_freq;
> > unsigned int samp_freq;
> > struct completion completion;
>
> Btw, have you run `pahole`? Is this the best place for a new field in
> accordance with its output?
>
I didn't, but I am going to use it.
> ...
>
> > +static int ad7768_gpio_set(struct gpio_chip *chip, unsigned int offset, int value)
> > +{
> > + struct iio_dev *indio_dev = gpiochip_get_data(chip);
> > + struct ad7768_state *st = iio_priv(indio_dev);
> > + unsigned int val;
> > + int ret;
> > +
> > + if (!iio_device_claim_direct(indio_dev))
> > + return -EBUSY;
> > +
> > + ret = regmap_read(st->regmap, AD7768_REG_GPIO_CONTROL, &val);
> > + if (ret)
> > + goto err_release;
> > +
> > + if (val & BIT(offset))
> > + ret = regmap_update_bits(st->regmap, AD7768_REG_GPIO_WRITE,
> > + BIT(offset), value << offset);
>
> And if value happens to be > 1?
> Also consider the use of regmap_assign_bits().
>
ok!
> > +err_release:
> > + iio_device_release_direct(indio_dev);
> > +
> > + return ret;
> > +}
>
> ...
>
> > +static int ad7768_gpio_init(struct iio_dev *indio_dev)
> > +{
> > + struct ad7768_state *st = iio_priv(indio_dev);
> > + int ret;
> > +
> > + ret = regmap_write(st->regmap, AD7768_REG_GPIO_CONTROL,
> > + AD7768_GPIO_UNIVERSAL_EN);
> > + if (ret)
> > + return ret;
> > +
> > + st->gpiochip = (struct gpio_chip) {
>
> > + .label = "ad7768_1_gpios",
>
> What is '_1' for?
> Also, what will happen if the device has two or more such ADCs
> installed? Will they all provide _the same_ label?!
>
the '_1' is because the part name is 'ad7768-1'.
Most of similar devices only define a static name, but I could use the
reg field, if you beleive it is better.
> > + .base = -1,
> > + .ngpio = 4,
> > + .parent = &st->spi->dev,
> > + .can_sleep = true,
> > + .direction_input = ad7768_gpio_direction_input,
> > + .direction_output = ad7768_gpio_direction_output,
> > + .get = ad7768_gpio_get,
> > + .set_rv = ad7768_gpio_set,
> > + .owner = THIS_MODULE,
> > + };
> > +
> > + return devm_gpiochip_add_data(&st->spi->dev, &st->gpiochip, indio_dev);
> > +}
>
> ...
>
> > + /* Only create a Chip GPIO if flagged for it */
> > + if (device_property_read_bool(&st->spi->dev, "gpio-controller")) {
> > + ret = ad7768_gpio_init(indio_dev);
> > + if (ret < 0)
>
> Why ' < 0'?
>
> > + return ret;
> > + }
>
> --
> With Best Regards,
> Andy Shevchenko
next prev parent reply other threads:[~2025-04-30 23:37 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-28 0:11 [PATCH v6 00/11] iio: adc: ad7768-1: Add features, improvements, and fixes Jonathan Santos
2025-04-28 0:12 ` [PATCH v6 01/11] dt-bindings: trigger-source: add generic GPIO trigger source Jonathan Santos
2025-05-05 15:44 ` Jonathan Cameron
2025-05-05 15:56 ` David Lechner
2025-05-13 9:32 ` Linus Walleij
2025-04-28 0:12 ` [PATCH v6 02/11] dt-bindings: iio: adc: ad7768-1: add trigger-sources property Jonathan Santos
2025-04-30 18:46 ` David Lechner
2025-05-05 15:39 ` Jonathan Cameron
2025-05-06 19:16 ` Jonathan Santos
2025-05-07 19:50 ` Jonathan Cameron
2025-04-28 0:12 ` [PATCH v6 03/11] dt-bindings: iio: adc: ad7768-1: Document GPIO controller Jonathan Santos
2025-04-28 0:12 ` [PATCH v6 04/11] dt-bindings: iio: adc: ad7768-1: document regulator provider property Jonathan Santos
2025-04-28 0:13 ` [PATCH v6 05/11] iio: adc: ad7768-1: add regulator to control VCM output Jonathan Santos
2025-04-28 6:42 ` Andy Shevchenko
2025-04-30 23:24 ` Jonathan Santos
2025-04-30 18:43 ` David Lechner
2025-04-28 0:13 ` [PATCH v6 06/11] iio: adc: ad7768-1: Add GPIO controller support Jonathan Santos
2025-04-28 6:50 ` Andy Shevchenko
2025-04-30 23:37 ` Jonathan Santos [this message]
2025-04-28 0:13 ` [PATCH v6 07/11] iio: adc: ad7768-1: add multiple scan types to support 16-bits mode Jonathan Santos
2025-04-28 6:55 ` Andy Shevchenko
2025-05-05 15:52 ` Jonathan Cameron
2025-05-02 14:30 ` Marcelo Schmitt
2025-04-28 0:13 ` [PATCH v6 08/11] iio: adc: ad7768-1: add support for Synchronization over SPI Jonathan Santos
2025-04-28 7:04 ` Andy Shevchenko
2025-05-01 0:03 ` Jonathan Santos
2025-04-30 19:07 ` David Lechner
2025-05-05 15:59 ` Jonathan Cameron
2025-04-28 0:14 ` [PATCH v6 09/11] iio: adc: ad7768-1: replace manual attribute declaration Jonathan Santos
2025-04-28 7:10 ` Andy Shevchenko
2025-04-28 0:14 ` [PATCH v6 10/11] iio: adc: ad7768-1: add filter type and oversampling ratio attributes Jonathan Santos
2025-04-29 22:40 ` Andy Shevchenko
2025-05-05 16:09 ` Jonathan Cameron
2025-05-06 19:03 ` Jonathan Santos
2025-05-06 19:10 ` David Lechner
2025-04-28 0:14 ` [PATCH v6 11/11] 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=aBK0J8yriQy3BcN5@JSANTO12-L01.ad.analog.com \
--to=jonath4nns@gmail.com \
--cc=CAHp75VdbD4HTonEZT8O-3bsqQ70_XRnZd7vS7gdyrG2gKYBHPA@mail.gmail.com \
--cc=Jonathan.Santos@analog.com \
--cc=Michael.Hennerich@analog.com \
--cc=andy.shevchenko@gmail.com \
--cc=andy@kernel.org \
--cc=bartosz.golaszewski@linaro.org \
--cc=brgl@bgdev.pl \
--cc=broonie@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dlechner@baylibre.com \
--cc=jic23@kernel.org \
--cc=krzk+dt@kernel.org \
--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=nuno.sa@analog.com \
--cc=robh@kernel.org \
--cc=sergiu.cuciurean@analog.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
all inboxes | Powered by JetHome®