linux-gpio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Aaron Kling via B4 Relay <devnull+webgeek1234.gmail.com@kernel.org>
To: Linus Walleij <linus.walleij@linaro.org>,
	Rob Herring <robh@kernel.org>,
	 Krzysztof Kozlowski <krzk+dt@kernel.org>,
	 Conor Dooley <conor+dt@kernel.org>,
	 Thierry Reding <thierry.reding@gmail.com>,
	 Jonathan Hunter <jonathanh@nvidia.com>,
	Bartosz Golaszewski <brgl@bgdev.pl>
Cc: linux-gpio@vger.kernel.org, devicetree@vger.kernel.org,
	 linux-tegra@vger.kernel.org, linux-kernel@vger.kernel.org,
	 Aaron Kling <webgeek1234@gmail.com>
Subject: [PATCH 2/4] dt-bindings: gpio: tegra186: Add gpio-ranges
Date: Tue, 29 Apr 2025 16:33:31 -0500	[thread overview]
Message-ID: <20250429-tegra186-pinctrl-v1-2-722c7c42394e@gmail.com> (raw)
In-Reply-To: <20250429-tegra186-pinctrl-v1-0-722c7c42394e@gmail.com>

From: Aaron Kling <webgeek1234@gmail.com>

Add optional gpio-ranges property.

Signed-off-by: Aaron Kling <webgeek1234@gmail.com>
---
 Documentation/devicetree/bindings/gpio/nvidia,tegra186-gpio.yaml | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/Documentation/devicetree/bindings/gpio/nvidia,tegra186-gpio.yaml b/Documentation/devicetree/bindings/gpio/nvidia,tegra186-gpio.yaml
index 4ef06b2ff1ff04c38801b621b8e9be2ed749861f..065f5761a93f61d6b2c501102eadd492026a64d0 100644
--- a/Documentation/devicetree/bindings/gpio/nvidia,tegra186-gpio.yaml
+++ b/Documentation/devicetree/bindings/gpio/nvidia,tegra186-gpio.yaml
@@ -111,6 +111,9 @@ properties:
 
   gpio-controller: true
 
+  gpio-ranges:
+    maxItems: 1
+
   "#gpio-cells":
     description: |
       Indicates how many cells are used in a consumer's GPIO specifier. In the

-- 
2.48.1



  parent reply	other threads:[~2025-04-29 21:33 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-29 21:33 [PATCH 0/4] pinctrl: tegra: Add Tegra186 pinmux driver Aaron Kling via B4 Relay
2025-04-29 21:33 ` [PATCH 1/4] dt-bindings: pinctrl: Document Tegra186 pin controllers Aaron Kling via B4 Relay
2025-05-09 19:22   ` Rob Herring
2025-05-09 19:46     ` Aaron Kling
2025-04-29 21:33 ` Aaron Kling via B4 Relay [this message]
2025-05-09 19:33   ` [PATCH 2/4] dt-bindings: gpio: tegra186: Add gpio-ranges Rob Herring (Arm)
2025-05-13 13:25   ` Linus Walleij
2025-04-29 21:33 ` [PATCH 3/4] pinctrl: tegra: Add Tegra186 pinmux driver Aaron Kling via B4 Relay
2025-04-29 21:33 ` [PATCH 4/4] arm64: tegra: Add Tegra186 pin controllers Aaron Kling via B4 Relay
2025-04-29 21:38 ` [PATCH 0/4] pinctrl: tegra: Add Tegra186 pinmux driver Aaron Kling
2025-05-28 17:37   ` Aaron Kling
2025-06-05 13:19     ` Linus Walleij
2025-05-14 15:31 ` (subset) " Bartosz Golaszewski

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=20250429-tegra186-pinctrl-v1-2-722c7c42394e@gmail.com \
    --to=devnull+webgeek1234.gmail.com@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=robh@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;
as well as URLs for NNTP newsgroup(s).