From: Andy Shevchenko <andriy.shevchenko@intel.com>
To: Jorge Marques <jorge.marques@analog.com>
Cc: "Lars-Peter Clausen" <lars@metafoo.de>,
"Michael Hennerich" <Michael.Hennerich@analog.com>,
"Jonathan Cameron" <jic23@kernel.org>,
"David Lechner" <dlechner@baylibre.com>,
"Nuno Sá" <nuno.sa@analog.com>,
"Andy Shevchenko" <andy@kernel.org>,
"Rob Herring" <robh@kernel.org>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
"Conor Dooley" <conor+dt@kernel.org>,
"Jonathan Corbet" <corbet@lwn.net>,
"Linus Walleij" <linus.walleij@linaro.org>,
"Bartosz Golaszewski" <brgl@bgdev.pl>,
linux-iio@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org,
linux-gpio@vger.kernel.org
Subject: Re: [PATCH v2 9/9] iio: adc: ad4062: Add GPIO Controller support
Date: Mon, 24 Nov 2025 12:40:37 +0200 [thread overview]
Message-ID: <aSQ2JUN05vmMQC1I@smile.fi.intel.com> (raw)
In-Reply-To: <20251124-staging-ad4062-v2-9-a375609afbb7@analog.com>
On Mon, Nov 24, 2025 at 10:18:08AM +0100, Jorge Marques wrote:
> When gp0 or gp1 is not taken as an interrupt, expose them as gpo if
GPO
> gpio-contoller is set in the devicetree.
Why can't gpio-regmap be used?
...
> +static int ad4062_gpio_get(struct gpio_chip *gc, unsigned int offset)
> +{
> + struct ad4062_state *st = gpiochip_get_data(gc);
> + unsigned int reg_val;
> + int ret;
> +
> + ret = regmap_read(st->regmap, AD4062_REG_GP_CONF, ®_val);
> + if (ret)
> + return 0;
> + if (st->gpo_irq[offset])
> + return -ENODEV;
Consider using valid_mask instead (.init_valid_mask() callback).
Hmm... And it seems it's in place. I didn't get what is here then and
why we need to do it after accessing the HW? If there are side-effects
they must be described.
> + if (offset)
> + reg_val = FIELD_GET(AD4062_REG_GP_CONF_MODE_MSK_1, reg_val);
> + else
> + reg_val = FIELD_GET(AD4062_REG_GP_CONF_MODE_MSK_0, reg_val);
> +
> + return reg_val == AD4062_GP_STATIC_HIGH ? 1 : 0;
return !!(reg_val == AD4062_GP_STATIC_HIGH);
also will work.
> +}
> +static int ad4062_gpio_init_valid_mask(struct gpio_chip *gc,
> + unsigned long *valid_mask,
> + unsigned int ngpios)
> +{
> + struct ad4062_state *st = gpiochip_get_data(gc);
> +
> + bitmap_zero(valid_mask, ngpios);
> +
> + if (!st->gpo_irq[0])
> + set_bit(0, valid_mask);
> + if (!st->gpo_irq[1])
> + set_bit(1, valid_mask);
Why atomic bit set:s?
> + return 0;
> +}
> +
> +static int ad4062_gpio_init(struct ad4062_state *st)
> +{
> + struct device *dev = &st->i3cdev->dev;
> + struct gpio_chip *gc;
> + u8 val, mask;
> + int ret;
> + if ((st->gpo_irq[0] && st->gpo_irq[1]) ||
> + !device_property_read_bool(dev, "gpio-controller"))
> + return 0;
Do you need this? valid_mask should take care of this.
> + gc = devm_kzalloc(dev, sizeof(*gc), GFP_KERNEL);
> + if (!gc)
> + return -ENOMEM;
> +
> + val = 0;
> + mask = 0;
> + if (!st->gpo_irq[0]) {
> + mask |= AD4062_REG_GP_CONF_MODE_MSK_0;
> + val |= FIELD_PREP(AD4062_REG_GP_CONF_MODE_MSK_0, AD4062_GP_STATIC_LOW);
> + }
> + if (!st->gpo_irq[1]) {
> + mask |= AD4062_REG_GP_CONF_MODE_MSK_1;
> + val |= FIELD_PREP(AD4062_REG_GP_CONF_MODE_MSK_1, AD4062_GP_STATIC_LOW);
> + }
> +
> + ret = regmap_update_bits(st->regmap, AD4062_REG_GP_CONF,
> + mask, val);
> + if (ret)
> + return ret;
> +
> + ret = devm_add_action_or_reset(dev, ad4062_gpio_disable, st);
> + if (ret)
> + return ret;
> +
> + gc->parent = dev;
> + gc->label = st->chip->name;
> + gc->owner = THIS_MODULE;
> + gc->base = -1;
> + gc->ngpio = 2;
> + gc->init_valid_mask = ad4062_gpio_init_valid_mask;
> + gc->get_direction = ad4062_gpio_get_direction;
> + gc->set = ad4062_gpio_set;
> + gc->get = ad4062_gpio_get;
> + gc->can_sleep = true;
> +
> + ret = devm_gpiochip_add_data(dev, gc, st);
> + if (ret)
> + return dev_err_probe(dev, ret, "Unable to register GPIO chip\n");
> +
> + return 0;
> +}
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2025-11-24 10:40 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-24 9:17 [PATCH v2 0/9] Add support for AD4062 device family Jorge Marques
2025-11-24 9:18 ` [PATCH v2 1/9] dt-bindings: iio: adc: Add adi,ad4062 Jorge Marques
2025-11-25 9:50 ` Krzysztof Kozlowski
2025-11-26 16:14 ` Jorge Marques
2025-11-24 9:18 ` [PATCH v2 2/9] docs: iio: New docs for ad4062 driver Jorge Marques
2025-11-24 9:18 ` [PATCH v2 3/9] iio: adc: Add support for ad4062 Jorge Marques
2025-11-24 10:20 ` Andy Shevchenko
2025-11-26 11:40 ` Jorge Marques
2025-11-27 8:58 ` Andy Shevchenko
2025-11-28 18:50 ` Jorge Marques
2025-11-28 19:25 ` Andy Shevchenko
2025-12-04 21:37 ` Jorge Marques
2025-12-04 22:23 ` Andy Shevchenko
2025-12-06 16:39 ` Jonathan Cameron
2025-11-24 9:18 ` [PATCH v2 4/9] docs: iio: ad4062: Add IIO Trigger support Jorge Marques
2025-11-24 9:18 ` [PATCH v2 5/9] iio: adc: " Jorge Marques
2025-11-24 9:36 ` Andy Shevchenko
2025-11-26 14:03 ` Jorge Marques
2025-11-24 9:18 ` [PATCH v2 6/9] docs: iio: ad4062: Add IIO Events support Jorge Marques
2025-11-24 9:18 ` [PATCH v2 7/9] iio: adc: " Jorge Marques
2025-11-24 10:33 ` Andy Shevchenko
2025-11-26 15:00 ` Jorge Marques
2025-11-27 9:13 ` Andy Shevchenko
2025-12-04 21:37 ` Jorge Marques
2025-11-24 9:18 ` [PATCH v2 8/9] docs: iio: ad4062: Add GPIO Controller support Jorge Marques
2025-11-24 9:18 ` [PATCH v2 9/9] iio: adc: " Jorge Marques
2025-11-24 9:51 ` Linus Walleij
2025-11-24 10:40 ` Andy Shevchenko [this message]
2025-11-26 15:55 ` Jorge Marques
2025-11-27 9:20 ` Andy Shevchenko
2025-12-04 21:38 ` Jorge Marques
2025-12-04 22:21 ` Andy Shevchenko
2025-12-05 11:53 ` Jorge Marques
2025-12-05 12:02 ` Andy Shevchenko
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=aSQ2JUN05vmMQC1I@smile.fi.intel.com \
--to=andriy.shevchenko@intel.com \
--cc=Michael.Hennerich@analog.com \
--cc=andy@kernel.org \
--cc=brgl@bgdev.pl \
--cc=conor+dt@kernel.org \
--cc=corbet@lwn.net \
--cc=devicetree@vger.kernel.org \
--cc=dlechner@baylibre.com \
--cc=jic23@kernel.org \
--cc=jorge.marques@analog.com \
--cc=krzk+dt@kernel.org \
--cc=lars@metafoo.de \
--cc=linus.walleij@linaro.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nuno.sa@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).