[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <8031c3ef-3b16-4200-83aa-0776bdfa8b45@denx.de>
Date: Fri, 23 Aug 2024 03:38:29 +0200
From: Marek Vasut <marex@...x.de>
To: Krzysztof Kozlowski <krzk@...nel.org>
Cc: linux-wireless@...r.kernel.org, "David S. Miller" <davem@...emloft.net>,
Adham Abozaeid <adham.abozaeid@...rochip.com>,
Ajay Singh <ajay.kathat@...rochip.com>,
Alexis Lothoré <alexis.lothore@...tlin.com>,
Claudiu Beznea <claudiu.beznea@...on.dev>, Conor Dooley
<conor+dt@...nel.org>, Eric Dumazet <edumazet@...gle.com>,
Jakub Kicinski <kuba@...nel.org>, Kalle Valo <kvalo@...nel.org>,
Krzysztof Kozlowski <krzk+dt@...nel.org>, Paolo Abeni <pabeni@...hat.com>,
Rob Herring <robh@...nel.org>, devicetree@...r.kernel.org,
netdev@...r.kernel.org
Subject: Re: [PATCH 1/2] dt-bindings: wireless: wilc1000: Document WILC3000
compatible string
On 8/22/24 10:07 AM, Krzysztof Kozlowski wrote:
Hi,
>> diff --git a/Documentation/devicetree/bindings/net/wireless/microchip,wilc1000.yaml b/Documentation/devicetree/bindings/net/wireless/microchip,wilc1000.yaml
>> index 2460ccc082371..1bf3496c21e64 100644
>> --- a/Documentation/devicetree/bindings/net/wireless/microchip,wilc1000.yaml
>> +++ b/Documentation/devicetree/bindings/net/wireless/microchip,wilc1000.yaml
>> @@ -16,7 +16,9 @@ description:
>>
>> properties:
>> compatible:
>> - const: microchip,wilc1000
>> + enum:
>> + - microchip,wilc1000
>> + - microchip,wilc3000
>
> Your driver change suggests device type is fully auto-detectable
It seems that way, yes.
>, thus
> they are compatible.
I _think_ the hardware is internally somewhat different, the WILC1000 is
WiFi-only device and the WILC3000 has some extra Bluetooth part (which
is currently not supported).
Maybe a fallback compatible string would be better here ?
Powered by blists - more mailing lists