From: Rob Herring <robh@kernel.org>
To: Thierry Reding <thierry.reding@gmail.com>
Cc: linux-tegra@vger.kernel.org,
Linus Walleij <linus.walleij@linaro.org>,
Prathamesh Shete <pshete@nvidia.com>,
Bartosz Golaszewski <brgl@bgdev.pl>,
devicetree@vger.kernel.org, linux-gpio@vger.kernel.org,
Rob Herring <robh+dt@kernel.org>,
Jon Hunter <jonathanh@nvidia.com>
Subject: Re: [PATCH v3 3/6] dt-bindings: gpio: Add Tegra234 support
Date: Wed, 8 Dec 2021 13:22:56 -0600 [thread overview]
Message-ID: <YbEGENBN3fCj5KUJ@robh.at.kernel.org> (raw)
In-Reply-To: <20211208173047.558108-3-thierry.reding@gmail.com>
On Wed, 08 Dec 2021 18:30:44 +0100, Thierry Reding wrote:
> From: Prathamesh Shete <pshete@nvidia.com>
>
> Extend the existing Tegra186 GPIO controller device tree bindings with
> support for the GPIO controller found on Tegra234. The number of pins is
> slightly different, but the programming model remains the same.
>
> Signed-off-by: Prathamesh Shete <pshete@nvidia.com>
> [treding@nvidia.com: update device tree bindings]
> Signed-off-by: Thierry Reding <treding@nvidia.com>
> ---
> .../bindings/gpio/nvidia,tegra186-gpio.yaml | 4 ++
> include/dt-bindings/gpio/tegra234-gpio.h | 63 +++++++++++++++++++
> 2 files changed, 67 insertions(+)
> create mode 100644 include/dt-bindings/gpio/tegra234-gpio.h
>
Reviewed-by: Rob Herring <robh@kernel.org>
next prev parent reply other threads:[~2021-12-08 19:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-08 17:30 [PATCH v3 1/6] dt-bindings: gpio: tegra: Convert to json-schema Thierry Reding
2021-12-08 17:30 ` [PATCH v3 2/6] dt-bindings: gpio: tegra186: " Thierry Reding
2021-12-08 19:21 ` Rob Herring
2021-12-10 1:47 ` Linus Walleij
2021-12-08 17:30 ` [PATCH v3 3/6] dt-bindings: gpio: Add Tegra234 support Thierry Reding
2021-12-08 19:22 ` Rob Herring [this message]
2021-12-10 1:48 ` Linus Walleij
2021-12-08 19:01 ` [PATCH v3 1/6] dt-bindings: gpio: tegra: Convert to json-schema Rob Herring
2021-12-10 1:47 ` 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=YbEGENBN3fCj5KUJ@robh.at.kernel.org \
--to=robh@kernel.org \
--cc=brgl@bgdev.pl \
--cc=devicetree@vger.kernel.org \
--cc=jonathanh@nvidia.com \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=pshete@nvidia.com \
--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).