[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20250113-skater-surrogate-4c72df770dbf@spud>
Date: Mon, 13 Jan 2025 18:32:06 +0000
From: Conor Dooley <conor@...nel.org>
To: Catalin Popescu <catalin.popescu@...ca-geosystems.com>
Cc: andrew+netdev@...n.ch, davem@...emloft.net, edumazet@...gle.com,
kuba@...nel.org, pabeni@...hat.com, robh@...nel.org,
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
Subject: Re: [PATCH net-next 1/2] dt-bindings: net: rfkill-gpio: enable
booting in blocked state
On Fri, Jan 10, 2025 at 09:19:01AM +0100, 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@...ca-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
type here should be flag, not 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
> --
> 2.34.1
>
>
Download attachment "signature.asc" of type "application/pgp-signature" (229 bytes)
Powered by blists - more mailing lists