devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jon Hunter <jonathanh@nvidia.com>
To: Thierry Reding <thierry.reding@gmail.com>,
	Linus Walleij <linus.walleij@linaro.org>
Cc: Rob Herring <robh+dt@kernel.org>,
	linux-gpio@vger.kernel.org, devicetree@vger.kernel.org,
	linux-tegra@vger.kernel.org
Subject: Re: [PATCH] dt-bindings: tegra186-gpio: Add Tegra186 specific prefix
Date: Thu, 29 Nov 2018 13:25:57 +0000	[thread overview]
Message-ID: <07ba710c-719c-f3dc-2d39-8fdbf0e9f643@nvidia.com> (raw)
In-Reply-To: <20181123124341.21431-1-thierry.reding@gmail.com>


On 23/11/2018 12:43, Thierry Reding wrote:
> From: Thierry Reding <treding@nvidia.com>
> 
> Subsequent generations of Tegra, such as Tegra194, contain a completely
> different set of GPIOs. In order to clarify that the Tegra186 defines
> are indeed specific to Tegra186, change the prefix from TEGRA_ to
> TEGRA186_.
> 
> Note that for now we need to keep the old definitions in place to avoid
> breaking compilation in file that use this header. Once all users have
> been converted to use the new defines, the old ones can be removed.
> 
> Also note that this is only a naming change and doesn't affect device
> tree ABI.
> 
> Signed-off-by: Thierry Reding <treding@nvidia.com>
> ---
>  include/dt-bindings/gpio/tegra186-gpio.h | 41 ++++++++++++++++++++++++
>  1 file changed, 41 insertions(+)
> 
> diff --git a/include/dt-bindings/gpio/tegra186-gpio.h b/include/dt-bindings/gpio/tegra186-gpio.h
> index 463ad398fe3e..cabc5712e745 100644
> --- a/include/dt-bindings/gpio/tegra186-gpio.h
> +++ b/include/dt-bindings/gpio/tegra186-gpio.h
> @@ -14,6 +14,34 @@
>  #include <dt-bindings/gpio/gpio.h>
>  
>  /* GPIOs implemented by main GPIO controller */
> +#define TEGRA186_MAIN_GPIO_PORT_A 0
> +#define TEGRA186_MAIN_GPIO_PORT_B 1
> +#define TEGRA186_MAIN_GPIO_PORT_C 2
> +#define TEGRA186_MAIN_GPIO_PORT_D 3
> +#define TEGRA186_MAIN_GPIO_PORT_E 4
> +#define TEGRA186_MAIN_GPIO_PORT_F 5
> +#define TEGRA186_MAIN_GPIO_PORT_G 6
> +#define TEGRA186_MAIN_GPIO_PORT_H 7
> +#define TEGRA186_MAIN_GPIO_PORT_I 8
> +#define TEGRA186_MAIN_GPIO_PORT_J 9
> +#define TEGRA186_MAIN_GPIO_PORT_K 10
> +#define TEGRA186_MAIN_GPIO_PORT_L 11
> +#define TEGRA186_MAIN_GPIO_PORT_M 12
> +#define TEGRA186_MAIN_GPIO_PORT_N 13
> +#define TEGRA186_MAIN_GPIO_PORT_O 14
> +#define TEGRA186_MAIN_GPIO_PORT_P 15
> +#define TEGRA186_MAIN_GPIO_PORT_Q 16
> +#define TEGRA186_MAIN_GPIO_PORT_R 17
> +#define TEGRA186_MAIN_GPIO_PORT_T 18
> +#define TEGRA186_MAIN_GPIO_PORT_X 19
> +#define TEGRA186_MAIN_GPIO_PORT_Y 20
> +#define TEGRA186_MAIN_GPIO_PORT_BB 21
> +#define TEGRA186_MAIN_GPIO_PORT_CC 22
> +
> +#define TEGRA186_MAIN_GPIO(port, offset) \
> +	((TEGRA186_MAIN_GPIO_PORT_##port * 8) + offset)
> +
> +/* need to keep these for backwards-compatibility */
>  #define TEGRA_MAIN_GPIO_PORT_A 0
>  #define TEGRA_MAIN_GPIO_PORT_B 1
>  #define TEGRA_MAIN_GPIO_PORT_C 2
> @@ -42,6 +70,19 @@
>  	((TEGRA_MAIN_GPIO_PORT_##port * 8) + offset)
>  
>  /* GPIOs implemented by AON GPIO controller */
> +#define TEGRA186_AON_GPIO_PORT_S 0
> +#define TEGRA186_AON_GPIO_PORT_U 1
> +#define TEGRA186_AON_GPIO_PORT_V 2
> +#define TEGRA186_AON_GPIO_PORT_W 3
> +#define TEGRA186_AON_GPIO_PORT_Z 4
> +#define TEGRA186_AON_GPIO_PORT_AA 5
> +#define TEGRA186_AON_GPIO_PORT_EE 6
> +#define TEGRA186_AON_GPIO_PORT_FF 7
> +
> +#define TEGRA186_AON_GPIO(port, offset) \
> +	((TEGRA186_AON_GPIO_PORT_##port * 8) + offset)
> +
> +/* need to keep these for backwards-compatibility */
>  #define TEGRA_AON_GPIO_PORT_S 0
>  #define TEGRA_AON_GPIO_PORT_U 1
>  #define TEGRA_AON_GPIO_PORT_V 2

I guess this will make it more consistent with what we have for
Tegra194, so looks fine to me ...

Acked-by: Jon Hunter <jonathanh@nvidia.com>

Cheers
Jon

-- 
nvpublic

  reply	other threads:[~2018-11-29 13:25 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-23 12:43 [PATCH] dt-bindings: tegra186-gpio: Add Tegra186 specific prefix Thierry Reding
2018-11-29 13:25 ` Jon Hunter [this message]
2018-12-07 10:08 ` Linus Walleij
2018-12-10 10:56   ` Thierry Reding
  -- strict thread matches above, loose matches on Subject: below --
2018-11-28 16:41 Thierry Reding

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=07ba710c-719c-f3dc-2d39-8fdbf0e9f643@nvidia.com \
    --to=jonathanh@nvidia.com \
    --cc=devicetree@vger.kernel.org \
    --cc=linus.walleij@linaro.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-tegra@vger.kernel.org \
    --cc=robh+dt@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;
as well as URLs for NNTP newsgroup(s).