From: Grygorii Strashko <grygorii.strashko@ti.com>
To: Alexander Sverdlin <alexander.sverdlin@gmail.com>,
<linux-omap@vger.kernel.org>
Cc: Santosh Shilimkar <ssantosh@kernel.org>,
Kevin Hilman <khilman@kernel.org>,
Linus Walleij <linus.walleij@linaro.org>,
Bartosz Golaszewski <bgolaszewski@baylibre.com>,
Rob Herring <robh+dt@kernel.org>, <linux-gpio@vger.kernel.org>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] gpio: omap: Honor "aliases" node
Date: Tue, 2 Mar 2021 11:27:25 +0200 [thread overview]
Message-ID: <eb34f303-4d05-4fcd-fb18-e304d06e6e2d@ti.com> (raw)
In-Reply-To: <20210302011813.2331879-1-alexander.sverdlin@gmail.com>
On 02/03/2021 03:18, Alexander Sverdlin wrote:
> Currently the naming of the GPIO chips depends on their order in the DT,
> but also on the kernel version (I've noticed the change from v5.10.x to
> v5.11). Honor the persistent enumeration in the "aliases" node like other
> GPIO drivers do.
>
> Signed-off-by: Alexander Sverdlin <alexander.sverdlin@gmail.com>
> ---
> Yes, I noticed checkpatch "WARNING: DT binding docs and includes should be
> a separate patch."
> However, the parts below are tiny and barely make sense separately.
>
> Documentation/devicetree/bindings/gpio/gpio-omap.txt | 6 ++++++
> drivers/gpio/gpio-omap.c | 5 +++++
> 2 files changed, 11 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/gpio/gpio-omap.txt b/Documentation/devicetree/bindings/gpio/gpio-omap.txt
> index e57b2cb28f6c..6050db3fd84e 100644
> --- a/Documentation/devicetree/bindings/gpio/gpio-omap.txt
> +++ b/Documentation/devicetree/bindings/gpio/gpio-omap.txt
> @@ -30,9 +30,15 @@ OMAP specific properties:
> - ti,gpio-always-on: Indicates if a GPIO bank is always powered and
> so will never lose its logic state.
>
> +Note: GPIO ports can have an alias correctly numbered in "aliases" node for
> +persistent enumeration.
>
> Example:
>
> +aliases {
> + gpio0 = &gpio0;
> +};
> +
> gpio0: gpio@44e07000 {
> compatible = "ti,omap4-gpio";
> reg = <0x44e07000 0x1000>;
> diff --git a/drivers/gpio/gpio-omap.c b/drivers/gpio/gpio-omap.c
> index 41952bb818ad..dd2a8f6d920f 100644
> --- a/drivers/gpio/gpio-omap.c
> +++ b/drivers/gpio/gpio-omap.c
> @@ -1014,6 +1014,11 @@ 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 {
> +#ifdef CONFIG_OF_GPIO
> + ret = of_alias_get_id(bank->chip.of_node, "gpio");
> + if (ret >= 0)
> + gpio = ret * bank->width;
> +#endif
> label = devm_kasprintf(bank->chip.parent, GFP_KERNEL, "gpio-%d-%d",
> gpio, gpio + bank->width - 1);
> if (!label)
>
You're not the first one, this was not accepted. See [1]
[1] https://patchwork.kernel.org/project/linux-omap/patch/1465898604-16294-1-git-send-email-u.kleine-koenig@pengutronix.de/
--
Best regards,
grygorii
next prev parent reply other threads:[~2021-03-02 9:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-02 1:18 [PATCH] gpio: omap: Honor "aliases" node Alexander Sverdlin
2021-03-02 9:27 ` Grygorii Strashko [this message]
2021-03-02 16:21 ` Linus Walleij
2021-03-08 18:37 ` Rob Herring
2021-03-09 13:40 ` 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=eb34f303-4d05-4fcd-fb18-e304d06e6e2d@ti.com \
--to=grygorii.strashko@ti.com \
--cc=alexander.sverdlin@gmail.com \
--cc=bgolaszewski@baylibre.com \
--cc=devicetree@vger.kernel.org \
--cc=khilman@kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=ssantosh@kernel.org \
/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