From: Jon Hunter <jonathanh@nvidia.com>
To: Thierry Reding <thierry.reding@gmail.com>
Cc: Prathamesh Shete <pshete@nvidia.com>,
linux-tegra@vger.kernel.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v3] dt-bindings: gpio: Remove FSI domain ports on Tegra234
Date: Tue, 30 May 2023 12:19:10 +0100 [thread overview]
Message-ID: <00382245-5bb4-6fd7-0654-da3e39b7e9a3@nvidia.com> (raw)
In-Reply-To: <20230530105108.1292681-1-thierry.reding@gmail.com>
On 30/05/2023 11:51, Thierry Reding wrote:
> From: Prathamesh Shete <pshete@nvidia.com>
>
> Ports S, T, U and V are in a separate controller that is part of the FSI
> domain. Remove their definitions from the MAIN controller definitions to
> get rid of the confusion.
>
> This technically breaks ABI compatibility with old device trees. However
> it doesn't cause issues in practice. The GPIO pins impacted by this are
> used for non-critical functionality.
>
> Fixes: a8b10f3d12cfc ("dt-bindings: gpio: Add Tegra234 support")
> Signed-off-by: Prathamesh Shete <pshete@nvidia.com>
> [treding@nvidia.com: rewrite commit message]
> Signed-off-by: Thierry Reding <treding@nvidia.com>
> ---
> Changes in v3:
> - rewrite commit message to provide a bit more background
I believe that this is actually V1 in case anyone is confused. I know
that we had kicked this around off-list before sending out and this is
why is appears as V3, but should be V1.
>
> include/dt-bindings/gpio/tegra234-gpio.h | 20 ++++++++------------
> 1 file changed, 8 insertions(+), 12 deletions(-)
>
> diff --git a/include/dt-bindings/gpio/tegra234-gpio.h b/include/dt-bindings/gpio/tegra234-gpio.h
> index d7a1f2e298e8..784673c2c752 100644
> --- a/include/dt-bindings/gpio/tegra234-gpio.h
> +++ b/include/dt-bindings/gpio/tegra234-gpio.h
> @@ -33,18 +33,14 @@
> #define TEGRA234_MAIN_GPIO_PORT_P 14
> #define TEGRA234_MAIN_GPIO_PORT_Q 15
> #define TEGRA234_MAIN_GPIO_PORT_R 16
> -#define TEGRA234_MAIN_GPIO_PORT_S 17
> -#define TEGRA234_MAIN_GPIO_PORT_T 18
> -#define TEGRA234_MAIN_GPIO_PORT_U 19
> -#define TEGRA234_MAIN_GPIO_PORT_V 20
> -#define TEGRA234_MAIN_GPIO_PORT_X 21
> -#define TEGRA234_MAIN_GPIO_PORT_Y 22
> -#define TEGRA234_MAIN_GPIO_PORT_Z 23
> -#define TEGRA234_MAIN_GPIO_PORT_AC 24
> -#define TEGRA234_MAIN_GPIO_PORT_AD 25
> -#define TEGRA234_MAIN_GPIO_PORT_AE 26
> -#define TEGRA234_MAIN_GPIO_PORT_AF 27
> -#define TEGRA234_MAIN_GPIO_PORT_AG 28
> +#define TEGRA234_MAIN_GPIO_PORT_X 17
> +#define TEGRA234_MAIN_GPIO_PORT_Y 18
> +#define TEGRA234_MAIN_GPIO_PORT_Z 19
> +#define TEGRA234_MAIN_GPIO_PORT_AC 20
> +#define TEGRA234_MAIN_GPIO_PORT_AD 21
> +#define TEGRA234_MAIN_GPIO_PORT_AE 22
> +#define TEGRA234_MAIN_GPIO_PORT_AF 23
> +#define TEGRA234_MAIN_GPIO_PORT_AG 24
>
> #define TEGRA234_MAIN_GPIO(port, offset) \
> ((TEGRA234_MAIN_GPIO_PORT_##port * 8) + offset)
Otherwise ...
Reviewed-by: Jon Hunter <jonathanh@nvidia.com>
Thanks!
Jon
--
nvpublic
next prev parent reply other threads:[~2023-05-30 11:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-30 10:51 [PATCH v3] dt-bindings: gpio: Remove FSI domain ports on Tegra234 Thierry Reding
2023-05-30 11:19 ` Jon Hunter [this message]
2023-06-06 13:03 ` 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=00382245-5bb4-6fd7-0654-da3e39b7e9a3@nvidia.com \
--to=jonathanh@nvidia.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.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