From: Mika Westerberg <mika.westerberg@linux.intel.com>
To: Guenter Roeck <linux@roeck-us.net>
Cc: linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org,
Linus Walleij <linus.walleij@linaro.org>,
Alexandre Courbot <gnurou@gmail.com>
Subject: Re: [PATCH v2] gpiolib: Export gpiochip_request_own_desc and gpiochip_free_own_desc
Date: Tue, 22 Jul 2014 09:43:48 +0300 [thread overview]
Message-ID: <20140722064348.GG1655@lahna.fi.intel.com> (raw)
In-Reply-To: <1406006305-22694-1-git-send-email-linux@roeck-us.net>
On Mon, Jul 21, 2014 at 10:18:25PM -0700, Guenter Roeck wrote:
> Both functions were introduced to let gpio drivers request their own
> gpio pins. Without exporting the functions, this can however only be
> used by gpio drivers built into the kernel.
The reason why these are private to drivers is that those are dangerous
if used blindly.
> Secondary impact is that the functions can not currently be used by
> platform initialization code associated with the gpio-pca953x driver.
> This code permits auto-export of gpio pins through platform data, but
> if this functionality is used, the module can no longer be unloaded due
> to the problem solved with the introduction of gpiochip_request_own_desc
> and gpiochip_free_own_desc.
>
> Export both function so they can be used from modules and from
> platform initialization code.
However, you have valid reason above. I wonder if this requires
some documentation in Documentation/gpio/driver.txt?
> Cc: Mika Westerberg <mika.westerberg@linux.intel.com>
> Signed-off-by: Guenter Roeck <linux@roeck-us.net>
> ---
> v2: Move function declarations from consumer.h to driver.h.
>
> drivers/gpio/gpiolib.c | 2 ++
> drivers/gpio/gpiolib.h | 3 ---
> include/linux/gpio/driver.h | 3 +++
> 3 files changed, 5 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/gpio/gpiolib.c b/drivers/gpio/gpiolib.c
> index 43d9e34..04c647e 100644
> --- a/drivers/gpio/gpiolib.c
> +++ b/drivers/gpio/gpiolib.c
> @@ -1953,6 +1953,7 @@ int gpiochip_request_own_desc(struct gpio_desc *desc, const char *label)
>
> return __gpiod_request(desc, label);
> }
> +EXPORT_SYMBOL(gpiochip_request_own_desc);
EXPORT_SYMBOL_GPL?
>
> /**
> * gpiochip_free_own_desc - Free GPIO requested by the chip driver
> @@ -1966,6 +1967,7 @@ void gpiochip_free_own_desc(struct gpio_desc *desc)
> if (desc)
> __gpiod_free(desc);
> }
> +EXPORT_SYMBOL(gpiochip_free_own_desc);
ditto.
> /* Drivers MUST set GPIO direction before making get/set calls. In
> * some cases this is done in early boot, before IRQs are enabled.
> diff --git a/drivers/gpio/gpiolib.h b/drivers/gpio/gpiolib.h
> index 1a4103d..2bdb69d 100644
> --- a/drivers/gpio/gpiolib.h
> +++ b/drivers/gpio/gpiolib.h
> @@ -45,9 +45,6 @@ acpi_get_gpiod_by_index(struct device *dev, int index,
> }
> #endif
>
> -int gpiochip_request_own_desc(struct gpio_desc *desc, const char *label);
> -void gpiochip_free_own_desc(struct gpio_desc *desc);
> -
> struct gpio_desc *of_get_named_gpiod_flags(struct device_node *np,
> const char *list_name, int index, enum of_gpio_flags *flags);
>
> diff --git a/include/linux/gpio/driver.h b/include/linux/gpio/driver.h
> index 573e4f3..8e07d58 100644
> --- a/include/linux/gpio/driver.h
> +++ b/include/linux/gpio/driver.h
> @@ -223,6 +223,9 @@ int gpiochip_irqchip_add(struct gpio_chip *gpiochip,
>
> #endif /* CONFIG_GPIO_IRQCHIP */
>
> +int gpiochip_request_own_desc(struct gpio_desc *desc, const char *label);
> +void gpiochip_free_own_desc(struct gpio_desc *desc);
> +
> #else /* CONFIG_GPIOLIB */
>
> static inline struct gpio_chip *gpiod_to_chip(const struct gpio_desc *desc)
> --
> 1.9.1
next prev parent reply other threads:[~2014-07-22 6:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-22 5:18 [PATCH v2] gpiolib: Export gpiochip_request_own_desc and gpiochip_free_own_desc Guenter Roeck
2014-07-22 6:43 ` Mika Westerberg [this message]
2014-07-22 6:47 ` Alexandre Courbot
2014-07-22 6:53 ` Guenter Roeck
2014-07-22 6:59 ` Mika Westerberg
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=20140722064348.GG1655@lahna.fi.intel.com \
--to=mika.westerberg@linux.intel.com \
--cc=gnurou@gmail.com \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
/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