From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Magnus Damm <magnus.damm@gmail.com>
Cc: linux-sh@vger.kernel.org, linus.walleij@linaro.org,
linux-kernel@vger.kernel.org, horms@verge.net.au,
grant.likely@linaro.org
Subject: Re: [PATCH] gpio: em: Add pinctrl support
Date: Wed, 03 Jul 2013 20:59:39 +0200 [thread overview]
Message-ID: <2134291.KQ1KkPOaiZ@avalon> (raw)
In-Reply-To: <20130703041432.7351.45970.sendpatchset@w520>
Hi Magnus,
Thank you for the patch.
On Wednesday 03 July 2013 13:14:32 Magnus Damm wrote:
> From: Magnus Damm <damm@opensource.se>
>
> Register the GPIO pin range, and request and free GPIO pins using the
> pinctrl API. The pctl_name platform data member should be used by
> platform devices to point out which pinctrl device to use.
>
> Follows same style as "dc3465a gpio-rcar: Add pinctrl support",
> by Laurent Pinchart, thanks to him.
>
> Signed-off-by: Magnus Damm <damm@opensource.se>
Acked-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Linus, now that the v3.12 development cycle will begin, would you like to take
the patch through your tree ? If so, how should we handle cross-dependencies
between the pinctrl/gpio tree and the Renesas ARM tree ?
> ---
>
> drivers/gpio/gpio-em.c | 25 +++++++++++++++++++++++++
> include/linux/platform_data/gpio-em.h | 1 +
> 2 files changed, 26 insertions(+)
>
> --- 0001/drivers/gpio/gpio-em.c
> +++ work/drivers/gpio/gpio-em.c 2013-07-03 12:49:55.000000000 +0900
> @@ -30,6 +30,7 @@
> #include <linux/gpio.h>
> #include <linux/slab.h>
> #include <linux/module.h>
> +#include <linux/pinctrl/consumer.h>
> #include <linux/platform_data/gpio-em.h>
>
> struct em_gio_priv {
> @@ -216,6 +217,21 @@ static int em_gio_to_irq(struct gpio_chi
> return irq_create_mapping(gpio_to_priv(chip)->irq_domain, offset);
> }
>
> +static int em_gio_request(struct gpio_chip *chip, unsigned offset)
> +{
> + return pinctrl_request_gpio(chip->base + offset);
> +}
> +
> +static void em_gio_free(struct gpio_chip *chip, unsigned offset)
> +{
> + pinctrl_free_gpio(chip->base + offset);
> +
> + /* Set the GPIO as an input to ensure that the next GPIO request won't
> + * drive the GPIO pin as an output.
> + */
> + em_gio_direction_input(chip, offset);
> +}
> +
> static int em_gio_irq_domain_map(struct irq_domain *h, unsigned int virq,
> irq_hw_number_t hw)
> {
> @@ -308,6 +324,8 @@ static int em_gio_probe(struct platform_
> gpio_chip->direction_output = em_gio_direction_output;
> gpio_chip->set = em_gio_set;
> gpio_chip->to_irq = em_gio_to_irq;
> + gpio_chip->request = em_gio_request;
> + gpio_chip->free = em_gio_free;
> gpio_chip->label = name;
> gpio_chip->owner = THIS_MODULE;
> gpio_chip->base = pdata->gpio_base;
> @@ -351,6 +369,13 @@ static int em_gio_probe(struct platform_
> dev_err(&pdev->dev, "failed to add GPIO controller\n");
> goto err1;
> }
> +
> + if (pdata->pctl_name) {
> + ret = gpiochip_add_pin_range(gpio_chip, pdata->pctl_name, 0,
> + gpio_chip->base, gpio_chip->ngpio);
> + if (ret < 0)
> + dev_warn(&pdev->dev, "failed to add pin range\n");
> + }
> return 0;
>
> err1:
> --- 0001/include/linux/platform_data/gpio-em.h
> +++ work/include/linux/platform_data/gpio-em.h 2013-07-03
12:45:27.000000000
> +0900 @@ -5,6 +5,7 @@ struct gpio_em_config {
> unsigned int gpio_base;
> unsigned int irq_base;
> unsigned int number_of_pins;
> + const char *pctl_name;
> };
>
> #endif /* __GPIO_EM_H__ */
--
Regards,
Laurent Pinchart
next prev parent reply other threads:[~2013-07-03 18:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-03 4:14 [PATCH] gpio: em: Add pinctrl support Magnus Damm
2013-07-03 18:59 ` Laurent Pinchart [this message]
2013-07-04 1:16 ` Simon Horman
2013-07-04 21:23 ` Laurent Pinchart
2013-07-05 0:01 ` Simon Horman
2013-07-21 15:26 ` Linus Walleij
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=2134291.KQ1KkPOaiZ@avalon \
--to=laurent.pinchart@ideasonboard.com \
--cc=grant.likely@linaro.org \
--cc=horms@verge.net.au \
--cc=linus.walleij@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=magnus.damm@gmail.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