From: Grygorii Strashko <grygorii.strashko@ti.com>
To: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>,
"Santosh Shilimkar" <ssantosh@kernel.org>,
"Kevin Hilman" <khilman@kernel.org>,
"Linus Walleij" <linus.walleij@linaro.org>,
"Alexandre Courbot" <gnurou@gmail.com>
Cc: linux-gpio@vger.kernel.org, linux-omap@vger.kernel.org,
kernel@pengutronix.de, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 1/2 v2] gpio: omap: make gpio numbering deterministical by using of aliases
Date: Tue, 21 Jun 2016 20:01:36 +0300 [thread overview]
Message-ID: <576972F0.7090207@ti.com> (raw)
In-Reply-To: <1465930632-18941-2-git-send-email-u.kleine-koenig@pengutronix.de>
On 06/14/2016 09:57 PM, Uwe Kleine-König wrote:
> Traditionally the n-th gpio device probed by the omap gpio driver got
> the gpio number range [n*32 .. n*32+31].
> When order of the devices probed by the driver changes (which can happen
> already now when some devices have a pinctrl and so the first probe
> attempt returns -ENODEV) the numbering changes.
>
> To ensure a deterministical numbering use of_alias_get_id to determine
> the base for a given device. If no respective alias exists fall back to
> the traditional numbering.
>
> For the unusual case where only a part of the gpio devices have a
> matching alias some of them might fail to probe. But if none of them has
> an alias or all, there is no conflict which should be good enough to
> maintain backward compatibility.
>
> Signed-off-by: Uwe Kleine-König <u.kleine-koenig@pengutronix.de>
> ---
> drivers/gpio/gpio-omap.c | 19 ++++++++++++++++++-
> 1 file changed, 18 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/gpio/gpio-omap.c b/drivers/gpio/gpio-omap.c
> index b98ede78c9d8..4d91792e7266 100644
> --- a/drivers/gpio/gpio-omap.c
> +++ b/drivers/gpio/gpio-omap.c
> @@ -1053,9 +1053,26 @@ static int omap_gpio_chip_init(struct gpio_bank *bank, struct irq_chip *irqc)
> bank->chip.parent = &omap_mpuio_device.dev;
> bank->chip.base = OMAP_MPUIO(0);
> } else {
> + int gpio_alias_id __maybe_unused;
> +
> bank->chip.label = "gpio";
> - bank->chip.base = gpio;
> +
> +#if defined(CONFIG_OF_GPIO)
> + /*
> + * Traditionally the base is given out in first-come-first-serve
> + * order. This might shuffle the numbering of gpios if the
> + * probe order changes. So make the base deterministical if the
> + * device tree specifies alias ids.
> + */
> + gpio_alias_id = of_alias_get_id(bank->chip.of_node, "gpio");
> + if (gpio_alias_id >= 0)
> + bank->chip.base = bank->width * gpio_alias_id;
> + else
> +#endif
> + bank->chip.base = gpio;
> }
> +
> +
> bank->chip.ngpio = bank->width;
>
> ret = gpiochip_add_data(&bank->chip, bank);
>
Reviewed-by: Grygorii Strashko <grygorii.strashko@ti.com>
--
regards,
-grygorii
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
WARNING: multiple messages have this Message-ID (diff)
From: grygorii.strashko@ti.com (Grygorii Strashko)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/2 v2] gpio: omap: make gpio numbering deterministical by using of aliases
Date: Tue, 21 Jun 2016 20:01:36 +0300 [thread overview]
Message-ID: <576972F0.7090207@ti.com> (raw)
In-Reply-To: <1465930632-18941-2-git-send-email-u.kleine-koenig@pengutronix.de>
On 06/14/2016 09:57 PM, Uwe Kleine-K?nig wrote:
> Traditionally the n-th gpio device probed by the omap gpio driver got
> the gpio number range [n*32 .. n*32+31].
> When order of the devices probed by the driver changes (which can happen
> already now when some devices have a pinctrl and so the first probe
> attempt returns -ENODEV) the numbering changes.
>
> To ensure a deterministical numbering use of_alias_get_id to determine
> the base for a given device. If no respective alias exists fall back to
> the traditional numbering.
>
> For the unusual case where only a part of the gpio devices have a
> matching alias some of them might fail to probe. But if none of them has
> an alias or all, there is no conflict which should be good enough to
> maintain backward compatibility.
>
> Signed-off-by: Uwe Kleine-K?nig <u.kleine-koenig@pengutronix.de>
> ---
> drivers/gpio/gpio-omap.c | 19 ++++++++++++++++++-
> 1 file changed, 18 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/gpio/gpio-omap.c b/drivers/gpio/gpio-omap.c
> index b98ede78c9d8..4d91792e7266 100644
> --- a/drivers/gpio/gpio-omap.c
> +++ b/drivers/gpio/gpio-omap.c
> @@ -1053,9 +1053,26 @@ static int omap_gpio_chip_init(struct gpio_bank *bank, struct irq_chip *irqc)
> bank->chip.parent = &omap_mpuio_device.dev;
> bank->chip.base = OMAP_MPUIO(0);
> } else {
> + int gpio_alias_id __maybe_unused;
> +
> bank->chip.label = "gpio";
> - bank->chip.base = gpio;
> +
> +#if defined(CONFIG_OF_GPIO)
> + /*
> + * Traditionally the base is given out in first-come-first-serve
> + * order. This might shuffle the numbering of gpios if the
> + * probe order changes. So make the base deterministical if the
> + * device tree specifies alias ids.
> + */
> + gpio_alias_id = of_alias_get_id(bank->chip.of_node, "gpio");
> + if (gpio_alias_id >= 0)
> + bank->chip.base = bank->width * gpio_alias_id;
> + else
> +#endif
> + bank->chip.base = gpio;
> }
> +
> +
> bank->chip.ngpio = bank->width;
>
> ret = gpiochip_add_data(&bank->chip, bank);
>
Reviewed-by: Grygorii Strashko <grygorii.strashko@ti.com>
--
regards,
-grygorii
next prev parent reply other threads:[~2016-06-21 17:01 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-14 18:57 [PATCH 0/2 v2] gpio-omap: ensure a stable gpio numbering Uwe Kleine-König
2016-06-14 18:57 ` Uwe Kleine-König
2016-06-14 18:57 ` [PATCH 1/2 v2] gpio: omap: make gpio numbering deterministical by using of aliases Uwe Kleine-König
2016-06-14 18:57 ` Uwe Kleine-König
2016-06-21 11:28 ` Tony Lindgren
2016-06-21 11:28 ` Tony Lindgren
2016-06-21 17:01 ` Grygorii Strashko [this message]
2016-06-21 17:01 ` Grygorii Strashko
2016-06-23 8:54 ` Linus Walleij
2016-06-23 8:54 ` Linus Walleij
2016-06-14 18:57 ` [PATCH 2/2 v2] ARM: dts: add aliases for ti,omap[234]-gpio devices Uwe Kleine-König
2016-06-14 18:57 ` Uwe Kleine-König
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=576972F0.7090207@ti.com \
--to=grygorii.strashko@ti.com \
--cc=gnurou@gmail.com \
--cc=kernel@pengutronix.de \
--cc=khilman@kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=ssantosh@kernel.org \
--cc=u.kleine-koenig@pengutronix.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.