Message ID | 20250110081902.1846296-1-catalin.popescu@leica-geosystems.com (mailing list archive) |
---|---|
State | New |
Delegated to: | Johannes Berg |
Headers | show |
Series | [net-next,1/2] dt-bindings: net: rfkill-gpio: enable booting in blocked state | expand |
Due to typo in my send-email command, some recipients were truncated. Adding them here. BR, Catalin On 10/01/2025 09:19, Catalin Popescu wrote: > 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@leica-geosystems.com> > --- > 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..22f26f1a3856 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: > + description: configure rfkill state as blocked at boot > + type: boolean > + > 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
Catalin Popescu <catalin.popescu@leica-geosystems.com> writes: > 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@leica-geosystems.com> Don't rfkill patches go via wireless-next, not net-next?
diff --git a/Documentation/devicetree/bindings/net/rfkill-gpio.yaml b/Documentation/devicetree/bindings/net/rfkill-gpio.yaml index 9630c8466fac..22f26f1a3856 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: + description: configure rfkill state as blocked at boot + type: boolean + 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; };
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@leica-geosystems.com> --- Documentation/devicetree/bindings/net/rfkill-gpio.yaml | 5 +++++ 1 file changed, 5 insertions(+) base-commit: 25cc469d6d344f5772e9fb6a5cf9d82a690afe68 prerequisite-patch-id: 0000000000000000000000000000000000000000