From: Jon Hunter <jonathanh@nvidia.com>
To: Prathamesh Shete <pshete@nvidia.com>,
linusw@kernel.org, brgl@kernel.org, thierry.reding@gmail.com,
linux-gpio@vger.kernel.org, linux-tegra@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 2/2] gpio: tegra186: Support multi-socket devices
Date: Tue, 17 Feb 2026 09:34:57 +0000 [thread overview]
Message-ID: <547eb829-bee1-4178-bd2a-6edca9ce82ac@nvidia.com> (raw)
In-Reply-To: <20260217081431.1208351-2-pshete@nvidia.com>
On 17/02/2026 08:14, Prathamesh Shete wrote:
> On Tegra platforms, multiple SoC instances may be present with each
> defining the same GPIO name. For such devices, this results in
> duplicate GPIO names.
>
> When the device has a valid NUMA node, prepend the NUMA node ID
> to the GPIO name prefix. The node ID identifies each socket,
> ensuring GPIO line names remain distinct across multiple sockets.
>
> Signed-off-by: Prathamesh Shete <pshete@nvidia.com>
> ---
> Changes in v2:
> * Split the v1 patch into two; this one to support multi-socket devices.
> ---
> drivers/gpio/gpio-tegra186.c | 16 +++++++++++++---
> 1 file changed, 13 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/gpio/gpio-tegra186.c b/drivers/gpio/gpio-tegra186.c
> index f04cc240b5ec..fb26402b6c47 100644
> --- a/drivers/gpio/gpio-tegra186.c
> +++ b/drivers/gpio/gpio-tegra186.c
> @@ -857,7 +857,7 @@ static int tegra186_gpio_probe(struct platform_device *pdev)
> struct device_node *np;
> struct resource *res;
> char **names;
> - int err;
> + int node, err;
>
> gpio = devm_kzalloc(&pdev->dev, sizeof(*gpio), GFP_KERNEL);
> if (!gpio)
> @@ -937,13 +937,23 @@ static int tegra186_gpio_probe(struct platform_device *pdev)
> if (!names)
> return -ENOMEM;
>
> + node = dev_to_node(&pdev->dev);
> +
> for (i = 0, offset = 0; i < gpio->soc->num_ports; i++) {
> const struct tegra_gpio_port *port = &gpio->soc->ports[i];
> char *name;
>
> for (j = 0; j < port->pins; j++) {
> - name = devm_kasprintf(gpio->gpio.parent, GFP_KERNEL, "%sP%s.%02x",
> - gpio->soc->prefix ?: "", port->name, j);
> + if (node >= 0)
> + name = devm_kasprintf(gpio->gpio.parent, GFP_KERNEL,
> + "%d-%sP%s.%02x", node,
> + gpio->soc->prefix ?: "",
> + port->name, j);
> + else
> + name = devm_kasprintf(gpio->gpio.parent, GFP_KERNEL,
> + "%sP%s.%02x",
> + gpio->soc->prefix ?: "",
> + port->name, j);
> if (!name)
> return -ENOMEM;
>
Reviewed-by: Jon Hunter <jonathanh@nvidia.com>
Thanks!
Jon
--
nvpublic
next prev parent reply other threads:[~2026-02-17 9:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-17 8:14 [PATCH v2 1/2] gpio: tegra186: Simplify GPIO line name prefix handling Prathamesh Shete
2026-02-17 8:14 ` [PATCH v2 2/2] gpio: tegra186: Support multi-socket devices Prathamesh Shete
2026-02-17 9:34 ` Jon Hunter [this message]
2026-02-17 10:06 ` Thierry Reding
2026-02-17 9:34 ` [PATCH v2 1/2] gpio: tegra186: Simplify GPIO line name prefix handling Jon Hunter
2026-02-17 10:04 ` Thierry Reding
2026-02-17 12:17 ` Bartosz Golaszewski
2026-02-17 13:29 ` Jon Hunter
2026-02-17 14:06 ` Bartosz Golaszewski
2026-02-23 9:57 ` Bartosz Golaszewski
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=547eb829-bee1-4178-bd2a-6edca9ce82ac@nvidia.com \
--to=jonathanh@nvidia.com \
--cc=brgl@kernel.org \
--cc=linusw@kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=pshete@nvidia.com \
--cc=thierry.reding@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