From: Dmitry Yashin <dmt.yashin@gmail.com>
To: Andrew Lunn <andrew+netdev@lunn.ch>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>,
Paolo Abeni <pabeni@redhat.com>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Johannes Berg <johannes@sipsolutions.net>,
Philipp Zabel <p.zabel@pengutronix.de>,
Heiko Stuebner <heiko@sntech.de>
Cc: netdev@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org,
Dmitry Yashin <dmt.yashin@gmail.com>
Subject: [PATCH v2 1/5] dt-bindings: net: rfkill-gpio: document reset-gpios property
Date: Fri, 16 Oct 2026 15:29:33 +0500 [thread overview]
Message-ID: <20261016-ok3568-c-v2-1-068d68430e6d@gmail.com> (raw)
In-Reply-To: <20261016-ok3568-c-v2-0-068d68430e6d@gmail.com>
rfkill-gpio driver requiers at-least one of the gpios to be defined:
shutdown-gpios or reset-gpios. Document missing reset-gpios property.
Also add example for wwan with both gpios.
Signed-off-by: Dmitry Yashin <dmt.yashin@gmail.com>
---
.../devicetree/bindings/net/rfkill-gpio.yaml | 23 +++++++++++++++++++++-
1 file changed, 22 insertions(+), 1 deletion(-)
diff --git a/Documentation/devicetree/bindings/net/rfkill-gpio.yaml b/Documentation/devicetree/bindings/net/rfkill-gpio.yaml
index 4a706a41ab38..66f6ad2872ff 100644
--- a/Documentation/devicetree/bindings/net/rfkill-gpio.yaml
+++ b/Documentation/devicetree/bindings/net/rfkill-gpio.yaml
@@ -29,7 +29,12 @@ properties:
- wlan
- wwan
+ reset-gpios:
+ description: GPIO connected to device's reset pin (RESET#)
+ maxItems: 1
+
shutdown-gpios:
+ description: GPIO connected to device's shutdown pin (W_DISABLE1#, etc.)
maxItems: 1
default-blocked:
@@ -39,7 +44,12 @@ properties:
required:
- compatible
- radio-type
- - shutdown-gpios
+
+anyOf:
+ - required:
+ - reset-gpios
+ - required:
+ - shutdown-gpios
additionalProperties: false
@@ -54,3 +64,14 @@ examples:
shutdown-gpios = <&gpio2 25 GPIO_ACTIVE_HIGH>;
default-blocked;
};
+
+ - |
+ #include <dt-bindings/gpio/gpio.h>
+
+ rfkill-wwan {
+ compatible = "rfkill-gpio";
+ label = "m2 usb wwan";
+ radio-type = "wwan";
+ reset-gpios = <&gpio2 23 GPIO_ACTIVE_HIGH>;
+ shutdown-gpios = <&gpio2 25 GPIO_ACTIVE_HIGH>;
+ };
--
2.56.0
next prev parent reply other threads:[~2026-10-16 10:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-16 10:29 [PATCH v2 0/5] arm64: dts: rockchip: add Forlinx OK3568-C Dmitry Yashin
2026-10-16 10:29 ` Dmitry Yashin [this message]
2026-10-16 10:29 ` [PATCH v2 2/5] dt-bindings: arm: rockchip: add Forlinx FET3568-C Dmitry Yashin
2026-10-16 10:29 ` [PATCH v2 3/5] arm64: dts: " Dmitry Yashin
2026-10-16 10:29 ` [PATCH v2 4/5] arm64: dts: rockchip: add Forlinx OK3568-C Dmitry Yashin
2026-10-16 10:29 ` [PATCH v2 5/5] arm64: dts: rockchip: add FIT-PCIE-SATA overlay Dmitry Yashin
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=20261016-ok3568-c-v2-1-068d68430e6d@gmail.com \
--to=dmt.yashin@gmail.com \
--cc=andrew+netdev@lunn.ch \
--cc=conor+dt@kernel.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=edumazet@google.com \
--cc=heiko@sntech.de \
--cc=johannes@sipsolutions.net \
--cc=krzk+dt@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=netdev@vger.kernel.org \
--cc=p.zabel@pengutronix.de \
--cc=pabeni@redhat.com \
--cc=robh@kernel.org \
/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