From: Guenter Roeck <linux@roeck-us.net>
To: Alexandre Courbot <gnurou@gmail.com>
Cc: "linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linus Walleij <linus.walleij@linaro.org>,
Mika Westerberg <mika.westerberg@linux.intel.com>
Subject: Re: [PATCH] gpiolib: Export gpiochip_request_own_desc and gpiochip_free_own_desc
Date: Mon, 21 Jul 2014 22:03:02 -0700 [thread overview]
Message-ID: <53CDF086.6010705@roeck-us.net> (raw)
In-Reply-To: <CAAVeFu+9NTH8pbx-dvYD3xVpZ9Y5F0P9KNDQP1DMB6Qn0Sv8KQ@mail.gmail.com>
On 07/21/2014 09:42 PM, Alexandre Courbot wrote:
> On Tue, Jul 22, 2014 at 1:26 PM, Guenter Roeck <linux@roeck-us.net> 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.
>>
>> 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.
>>
>> Cc: Mika Westerberg <mika.westerberg@linux.intel.com>
>> Signed-off-by: Guenter Roeck <linux@roeck-us.net>
>> ---
>> drivers/gpio/gpiolib.c | 2 ++
>> drivers/gpio/gpiolib.h | 3 ---
>> include/linux/gpio/consumer.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);
>>
>> /**
>> * 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);
>>
>> /* 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/consumer.h b/include/linux/gpio/consumer.h
>> index 05e53cc..e85f7e6 100644
>> --- a/include/linux/gpio/consumer.h
>> +++ b/include/linux/gpio/consumer.h
>> @@ -32,6 +32,9 @@ struct gpio_desc *__must_check gpiod_get_index_optional(struct device *dev,
>>
>> void gpiod_put(struct gpio_desc *desc);
>>
>> +int gpiochip_request_own_desc(struct gpio_desc *desc, const char *label);
>> +void gpiochip_free_own_desc(struct gpio_desc *desc);
>
> I guess these functions should be made public in driver.h, not
> consumer.h. Users will be GPIO drivers and platform code, not device
> drivers which are the typical consumers of GPIOs.
>
No problem; I was not sure which include file would be appropriate,
and just picked one. I'll update the patch and resubmit.
Thanks,
Guenter
prev parent reply other threads:[~2014-07-22 5:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-22 4:26 [PATCH] gpiolib: Export gpiochip_request_own_desc and gpiochip_free_own_desc Guenter Roeck
2014-07-22 4:42 ` Alexandre Courbot
2014-07-22 5:03 ` Guenter Roeck [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=53CDF086.6010705@roeck-us.net \
--to=linux@roeck-us.net \
--cc=gnurou@gmail.com \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mika.westerberg@linux.intel.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;
as well as URLs for NNTP newsgroup(s).