From: "Rob Herring (Arm)" <robh@kernel.org>
To: Aaron Kling <webgeek1234@gmail.com>
Cc: linux-kernel@vger.kernel.org, linux-tegra@vger.kernel.org,
linux-gpio@vger.kernel.org, devicetree@vger.kernel.org,
Linus Walleij <linus.walleij@linaro.org>,
Jonathan Hunter <jonathanh@nvidia.com>,
Bartosz Golaszewski <brgl@bgdev.pl>,
Conor Dooley <conor+dt@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Thierry Reding <thierry.reding@gmail.com>
Subject: Re: [PATCH v2 1/3] dt-bindings: pinctrl: Document Tegra186 pin controllers
Date: Wed, 25 Jun 2025 14:38:21 -0500 [thread overview]
Message-ID: <175088030096.2091553.3144090820246144987.robh@kernel.org> (raw)
In-Reply-To: <20250608-tegra186-pinctrl-v2-1-502d41f3eedd@gmail.com>
On Sun, 08 Jun 2025 21:13:13 -0500, Aaron Kling wrote:
> Tegra186 contains two pin controllers. Document their compatible strings
> and describe the list of pins and functions that they provide.
>
> Signed-off-by: Aaron Kling <webgeek1234@gmail.com>
> ---
> .../bindings/pinctrl/nvidia,tegra186-pinmux.yaml | 285 +++++++++++++++++++++
> 1 file changed, 285 insertions(+)
>
Reviewed-by: Rob Herring (Arm) <robh@kernel.org>
next prev parent reply other threads:[~2025-06-25 19:38 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-09 2:13 [PATCH v2 0/3] pinctrl: tegra: Add Tegra186 pinmux driver Aaron Kling via B4 Relay
2025-06-09 2:13 ` [PATCH v2 1/3] dt-bindings: pinctrl: Document Tegra186 pin controllers Aaron Kling via B4 Relay
2025-06-25 19:38 ` Rob Herring (Arm) [this message]
2025-06-09 2:13 ` [PATCH v2 2/3] pinctrl: tegra: Add Tegra186 pinmux driver Aaron Kling via B4 Relay
2025-06-10 9:40 ` Thierry Reding
2025-06-10 15:34 ` Aaron Kling
2025-06-11 6:58 ` Linus Walleij
2025-06-11 15:23 ` Thierry Reding
2025-06-30 19:23 ` Aaron Kling
2025-07-03 7:08 ` Thierry Reding
2025-07-14 5:45 ` Aaron Kling
2025-07-23 11:08 ` Linus Walleij
2025-08-01 6:33 ` Aaron Kling
2025-08-01 9:35 ` Thierry Reding
2025-06-09 2:13 ` [PATCH v2 3/3] arm64: tegra: Add Tegra186 pin controllers Aaron Kling via B4 Relay
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=175088030096.2091553.3144090820246144987.robh@kernel.org \
--to=robh@kernel.org \
--cc=brgl@bgdev.pl \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jonathanh@nvidia.com \
--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=thierry.reding@gmail.com \
--cc=webgeek1234@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
all inboxes | Powered by JetHome®