[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20250116084702.3473176-1-catalin.popescu@leica-geosystems.com>
Date: Thu, 16 Jan 2025 09:47:01 +0100
From: Catalin Popescu <catalin.popescu@...ca-geosystems.com>
To: andrew+netdev@...n.ch,
davem@...emloft.net,
edumazet@...gle.com,
kuba@...nel.org,
pabeni@...hat.com,
robh@...nel.org,
krzk+dt@...nel.org,
conor+dt@...nel.org,
johannes@...solutions.net,
p.zabel@...gutronix.de
Cc: netdev@...r.kernel.org,
devicetree@...r.kernel.org,
linux-kernel@...r.kernel.org,
linux-wireless@...r.kernel.org,
m.felsch@...gutronix.de,
bsp-development.geo@...ca-geosystems.com,
Catalin Popescu <catalin.popescu@...ca-geosystems.com>
Subject: [PATCH net-next v2 1/2] dt-bindings: net: rfkill-gpio: enable booting in blocked state
By default, rfkill state is set to unblocked. Sometimes, we want to boot
in blocked state and let the application unblock the rfkill.
Signed-off-by: Catalin Popescu <catalin.popescu@...ca-geosystems.com>
---
Changes in v2:
- change "default-blocked" type from boolean to flag
---
Documentation/devicetree/bindings/net/rfkill-gpio.yaml | 5 +++++
1 file changed, 5 insertions(+)
diff --git a/Documentation/devicetree/bindings/net/rfkill-gpio.yaml b/Documentation/devicetree/bindings/net/rfkill-gpio.yaml
index 9630c8466fac..4a706a41ab38 100644
--- a/Documentation/devicetree/bindings/net/rfkill-gpio.yaml
+++ b/Documentation/devicetree/bindings/net/rfkill-gpio.yaml
@@ -32,6 +32,10 @@ properties:
shutdown-gpios:
maxItems: 1
+ default-blocked:
+ $ref: /schemas/types.yaml#/definitions/flag
+ description: configure rfkill state as blocked at boot
+
required:
- compatible
- radio-type
@@ -48,4 +52,5 @@ examples:
label = "rfkill-pcie-wlan";
radio-type = "wlan";
shutdown-gpios = <&gpio2 25 GPIO_ACTIVE_HIGH>;
+ default-blocked;
};
base-commit: 25cc469d6d344f5772e9fb6a5cf9d82a690afe68
prerequisite-patch-id: 0000000000000000000000000000000000000000
--
2.34.1
Powered by blists - more mailing lists