From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Pierluigi Passaro <pierluigi.p@variscite.com>
Cc: linus.walleij@linaro.org, brgl@bgdev.pl,
yamada.masahiro@socionext.com, linux-gpio@vger.kernel.org,
linux-kernel@vger.kernel.org, sfr@canb.auug.org.au,
eran.m@variscite.com, nate.d@variscite.com,
francesco.f@variscite.com, pierluigi.passaro@gmail.com,
kernel test robot <lkp@intel.com>
Subject: Re: [PATCH v3] gpiolib: fix linker errors when GPIOLIB is disabled
Date: Wed, 25 Jan 2023 20:59:00 +0200 [thread overview]
Message-ID: <Y9F79GvU1a+CjmLr@smile.fi.intel.com> (raw)
In-Reply-To: <20230124013138.358595-1-pierluigi.p@variscite.com>
On Tue, Jan 24, 2023 at 02:31:38AM +0100, Pierluigi Passaro wrote:
> Both the functions gpiochip_request_own_desc and
> gpiochip_free_own_desc are exported from
> drivers/gpio/gpiolib.c
> but this file is compiled only when CONFIG_GPIOLIB is enabled.
> Move the prototypes under "#ifdef CONFIG_GPIOLIB" and provide
> reasonable definitions and includes in the "#else" branch.
So far as a quick fix I can agree on the change with a caveat that inclusion
hell should be untangled in the future.
Reviewed-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
P.S. The root cause of this problem is that some drivers without being GPIO chips
abuse this API. Better fix can be to go through each of such drivers and add ugly
ifdeffery with a FIXME comment that this shouldn't be actually used to begin with.
> Fixes: 9091373ab7ea ("gpio: remove less important #ifdef around declarations")
> Signed-off-by: Pierluigi Passaro <pierluigi.p@variscite.com>
> Reported-by: kernel test robot <lkp@intel.com>
> ---
> Changes in v2:
> - add Fixes tag
> Changes in v3:
> - add includes to fix builds against x86_64-defconfig
>
> include/linux/gpio/driver.h | 23 +++++++++++++++++++++--
> 1 file changed, 21 insertions(+), 2 deletions(-)
>
> diff --git a/include/linux/gpio/driver.h b/include/linux/gpio/driver.h
> index 44783fc16125..e00eaba724dc 100644
> --- a/include/linux/gpio/driver.h
> +++ b/include/linux/gpio/driver.h
> @@ -758,6 +758,8 @@ gpiochip_remove_pin_ranges(struct gpio_chip *gc)
>
> #endif /* CONFIG_PINCTRL */
>
> +#ifdef CONFIG_GPIOLIB
> +
> struct gpio_desc *gpiochip_request_own_desc(struct gpio_chip *gc,
> unsigned int hwnum,
> const char *label,
> @@ -765,8 +767,6 @@ struct gpio_desc *gpiochip_request_own_desc(struct gpio_chip *gc,
> enum gpiod_flags dflags);
> void gpiochip_free_own_desc(struct gpio_desc *desc);
>
> -#ifdef CONFIG_GPIOLIB
> -
> /* lock/unlock as IRQ */
> int gpiochip_lock_as_irq(struct gpio_chip *gc, unsigned int offset);
> void gpiochip_unlock_as_irq(struct gpio_chip *gc, unsigned int offset);
> @@ -776,6 +776,25 @@ struct gpio_chip *gpiod_to_chip(const struct gpio_desc *desc);
>
> #else /* CONFIG_GPIOLIB */
>
> +#include <linux/gpio/machine.h>
> +#include <linux/gpio/consumer.h>
> +
> +static inline struct gpio_desc *gpiochip_request_own_desc(struct gpio_chip *gc,
> + unsigned int hwnum,
> + const char *label,
> + enum gpio_lookup_flags lflags,
> + enum gpiod_flags dflags)
> +{
> + /* GPIO can never have been requested */
> + WARN_ON(1);
> + return ERR_PTR(-ENODEV);
> +}
> +
> +static inline void gpiochip_free_own_desc(struct gpio_desc *desc)
> +{
> + WARN_ON(1);
> +}
> +
> static inline struct gpio_chip *gpiod_to_chip(const struct gpio_desc *desc)
> {
> /* GPIO can never have been requested */
> --
> 2.34.1
>
>
--
With Best Regards,
Andy Shevchenko
prev parent reply other threads:[~2023-01-25 18:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-24 1:31 [PATCH v3] gpiolib: fix linker errors when GPIOLIB is disabled Pierluigi Passaro
2023-01-24 8:54 ` Bartosz Golaszewski
2023-01-25 18:22 ` Andy Shevchenko
2023-01-25 18:59 ` Andy Shevchenko [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=Y9F79GvU1a+CjmLr@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=brgl@bgdev.pl \
--cc=eran.m@variscite.com \
--cc=francesco.f@variscite.com \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=nate.d@variscite.com \
--cc=pierluigi.p@variscite.com \
--cc=pierluigi.passaro@gmail.com \
--cc=sfr@canb.auug.org.au \
--cc=yamada.masahiro@socionext.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