From: Jonathan Cameron <jic23@kernel.org>
To: Arnd Bergmann <arnd@kernel.org>
Cc: "Linus Walleij" <linusw@kernel.org>,
"Bartosz Golaszewski" <brgl@kernel.org>,
"Jorge Marques" <jorge.marques@analog.com>,
"Arnd Bergmann" <arnd@arndb.de>,
"David Lechner" <dlechner@baylibre.com>,
"Nuno Sá" <nuno.sa@analog.com>,
"Andy Shevchenko" <andy@kernel.org>,
"Marcelo Schmitt" <marcelo.schmitt@analog.com>,
"Jonathan Santos" <Jonathan.Santos@analog.com>,
"Radu Sabau" <radu.sabau@analog.com>,
linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-gpio@vger.kernel.org
Subject: Re: [PATCH] iio: adc: ad4062: add GPIOLIB dependency
Date: Fri, 15 May 2026 14:19:21 +0100 [thread overview]
Message-ID: <20260515141921.72242ab7@jic23-huawei> (raw)
In-Reply-To: <20260515090814.437092-1-arnd@kernel.org>
On Fri, 15 May 2026 11:07:53 +0200
Arnd Bergmann <arnd@kernel.org> wrote:
> From: Arnd Bergmann <arnd@arndb.de>
>
> The ad4062 driver gained support for the gpiochip and now fails
> to build when GPIOLIB is disabled:
>
> 390-linux-ld: drivers/iio/adc/ad4062.o: in function `ad4062_gpio_get':
> drivers/iio/adc/ad4062.c:1383:(.text+0x3dc): undefined reference to `gpiochip_get_data`
>
> Add a Kconfig dependency for this.
>
> Fixes: da1d3596b1e4 ("iio: adc: ad4062: Add GPIO Controller support")
> Signed-off-by: Arnd Bergmann <arnd@arndb.de>
Applied and marked for stable. thanks,
J
> ---
> drivers/iio/adc/Kconfig | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/drivers/iio/adc/Kconfig b/drivers/iio/adc/Kconfig
> index 8550917226a1..2c96e500c684 100644
> --- a/drivers/iio/adc/Kconfig
> +++ b/drivers/iio/adc/Kconfig
> @@ -78,6 +78,7 @@ config AD4030
> config AD4062
> tristate "Analog Devices AD4062 Driver"
> depends on I3C
> + depends on GPIOLIB
> select REGMAP_I3C
> select IIO_BUFFER
> select IIO_TRIGGERED_BUFFER
prev parent reply other threads:[~2026-05-15 13:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-15 9:07 [PATCH] iio: adc: ad4062: add GPIOLIB dependency Arnd Bergmann
2026-05-15 13:19 ` Jonathan Cameron [this message]
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=20260515141921.72242ab7@jic23-huawei \
--to=jic23@kernel.org \
--cc=Jonathan.Santos@analog.com \
--cc=andy@kernel.org \
--cc=arnd@arndb.de \
--cc=arnd@kernel.org \
--cc=brgl@kernel.org \
--cc=dlechner@baylibre.com \
--cc=jorge.marques@analog.com \
--cc=linusw@kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo.schmitt@analog.com \
--cc=nuno.sa@analog.com \
--cc=radu.sabau@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