Re: [PATCH v2 6/8] dt-bindings: wireless: ath12k: Add disable-rfkill property
From: Krzysztof Kozlowski
Date: Sun Dec 07 2025 - 21:20:47 EST
On 07/12/2025 20:28, Jérôme de Bretagne wrote:
> Le lun. 1 déc. 2025 à 08:34, Krzysztof Kozlowski <krzk@xxxxxxxxxx> a écrit :
>>
>> On 01/12/2025 02:14, Dale Whinham wrote:
>>> From: Jérôme de Bretagne <jerome.debretagne@xxxxxxxxx>
>>>
>>> rfkill should be disabled according to the Surface Pro 11's DSDT.
>>>
>>> https://lore.kernel.org/all/20250113074810.29729-3-quic_lingbok@xxxxxxxxxxx/
>>> has added support to read the ACPI bitflag when ACPI is supported.
>>
>> It wasn't merged. If it was, reference commits, not random emails.
>
> Good catch, It was merged in commit c6a7c0b09d5f, we will reference
> this commit instead.
>
>>> Document the disable-rfkill property to expose one specific feature
>>> (DISABLE_RFKILL_BIT) for devices described with a DT, so that the
>>> feature can be disabled.
>>
>> This is just a circular logic. Add property to have property in DT so
>> that you can use feature.
>>
>> No, describe the hardware or actual problem instead.
>
> Point taken. Would something like the following be better?
>
> "For some devices, Wi-Fi is entirely hard blocked by default making
> the Wi-Fi radio unusable, except if rfkill is disabled as described
> by an ACPI bitflag on those models. Add the disable-rfkill property
> to expose the DISABLE_RFKILL_BIT feature for devices described
> by a devicetree."
>
>> You still need to answer Rob's questions.
>
> Indeed, we didn't answer another question, sorry. Here it is for
> reference:
>
>> [Rob] Assuming it belongs in DT, why is this ath12k specific? Could be
>> for any wireless chip...
>
> Agree, it could be applicable to any wireless chip, it should be moved
> somewhere else. Would ieee80211.yaml be the right target file for
> this property? Or any other file suggestion instead? Thank you.
Yes, then place it please in above iee80211.yaml common file, with some
sort of bigger picture explanation.
Best regards,
Krzysztof