Linux Tegra architecture development
 help / color / mirror / Atom feed
From: Jon Hunter <jonathanh@nvidia.com>
To: Prathamesh Shete <pshete@nvidia.com>,
	linus.walleij@linaro.org, brgl@bgdev.pl,
	thierry.reding@gmail.com, robh@kernel.org, krzk+dt@kernel.org,
	conor+dt@kernel.org, devicetree@vger.kernel.org,
	linux-gpio@vger.kernel.org, linux-tegra@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] gpio: tegra186: Add support for Tegra256
Date: Fri, 21 Nov 2025 14:25:36 +0000	[thread overview]
Message-ID: <b67b887d-541c-43a6-85fb-3fe7ac490d26@nvidia.com> (raw)
In-Reply-To: <20250823055420.24664-2-pshete@nvidia.com>


On 23/08/2025 06:54, Prathamesh Shete wrote:
> Extend the existing Tegra186 GPIO controller driver with support for the
> GPIO controller found on Tegra256. While the programming model remains
> the same, the number of pins has slightly changed.
> 
> Signed-off-by: Prathamesh Shete <pshete@nvidia.com>
> ---
>   drivers/gpio/gpio-tegra186.c | 28 ++++++++++++++++++++++++++++
>   1 file changed, 28 insertions(+)
> 
> diff --git a/drivers/gpio/gpio-tegra186.c b/drivers/gpio/gpio-tegra186.c
> index d27bfac6c9f5..c9f1441a7b30 100644
> --- a/drivers/gpio/gpio-tegra186.c
> +++ b/drivers/gpio/gpio-tegra186.c
> @@ -20,6 +20,7 @@
>   #include <dt-bindings/gpio/tegra194-gpio.h>
>   #include <dt-bindings/gpio/tegra234-gpio.h>
>   #include <dt-bindings/gpio/tegra241-gpio.h>
> +#include <dt-bindings/gpio/tegra256-gpio.h>
>   
>   /* security registers */
>   #define TEGRA186_GPIO_CTL_SCR 0x0c
> @@ -1274,6 +1275,30 @@ static const struct tegra_gpio_soc tegra241_aon_soc = {
>   	.has_vm_support = false,
>   };
>   
> +#define TEGRA256_MAIN_GPIO_PORT(_name, _bank, _port, _pins)	\
> +	[TEGRA256_MAIN_GPIO_PORT_##_name] = {			\
> +		.name = #_name,					\
> +		.bank = _bank,					\
> +		.port = _port,					\
> +		.pins = _pins,					\
> +	}
> +
> +static const struct tegra_gpio_port tegra256_main_ports[] = {
> +	TEGRA256_MAIN_GPIO_PORT(A, 0, 0, 8),
> +	TEGRA256_MAIN_GPIO_PORT(B, 0, 1, 8),
> +	TEGRA256_MAIN_GPIO_PORT(C, 0, 2, 8),
> +	TEGRA256_MAIN_GPIO_PORT(D, 0, 3, 8),
> +};
> +
> +static const struct tegra_gpio_soc tegra256_main_soc = {
> +	.num_ports = ARRAY_SIZE(tegra256_main_ports),
> +	.ports = tegra256_main_ports,
> +	.name = "tegra256-gpio-main",
> +	.instance = 1,

Shouldn't this be 0?

Jon

-- 
nvpublic


  reply	other threads:[~2025-11-21 14:25 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-23  5:54 [PATCH 1/2] dt-bindings: gpio: Add Tegra256 support Prathamesh Shete
2025-08-23  5:54 ` [PATCH 2/2] gpio: tegra186: Add support for Tegra256 Prathamesh Shete
2025-11-21 14:25   ` Jon Hunter [this message]
2025-08-23 13:52 ` [PATCH 1/2] dt-bindings: gpio: Add Tegra256 support Conor Dooley
2025-09-01  8:20 ` Bartosz Golaszewski
  -- strict thread matches above, loose matches on Subject: below --
2025-08-04  4:16 Prathamesh Shete
2025-08-04  4:16 ` [PATCH 2/2] gpio: tegra186: Add support for Tegra256 Prathamesh Shete

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=b67b887d-541c-43a6-85fb-3fe7ac490d26@nvidia.com \
    --to=jonathanh@nvidia.com \
    --cc=brgl@bgdev.pl \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=linus.walleij@linaro.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-tegra@vger.kernel.org \
    --cc=pshete@nvidia.com \
    --cc=robh@kernel.org \
    --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