On 17/01/2025 09:56, Krzysztof Kozlowski wrote: > This email is not from Hexagon’s Office 365 instance. Please be careful while clicking links, opening attachments, or replying to this email. > > > On Thu, Jan 16, 2025 at 09:47: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@xxxxxxxxxxxxxxxxxxxx> >> --- >> 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 > I am assuming rfkill does not have third state possible, so it is only > off or on. Indeed, only on/off. > Reviewed-by: Krzysztof Kozlowski <krzysztof.kozlowski@xxxxxxxxxx> Thanks! BR, Catalin > > Best regards, > Krzysztof >
