[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAMZdPi8mS92ACrZOmfnni7bnCKkU5x-Z26QKcu_-J9xYuCjq1w@mail.gmail.com>
Date: Thu, 29 Mar 2018 09:40:33 +0200
From: Loic Poulain <loic.poulain@...aro.org>
To: Ramon Fried <rfried@...eaurora.org>
Cc: Kalle Valo <kvalo@...eaurora.org>, wcn36xx@...ts.infradead.org,
linux-wireless@...r.kernel.org, netdev@...r.kernel.org,
linux-kernel@...r.kernel.org,
devicetree <devicetree@...r.kernel.org>
Subject: Re: [PATCH v2] wcn36xx: Disable 5GHz for wcn3610
Hi Ramon,
On 29 March 2018 at 09:32, Ramon Fried <rfried@...eaurora.org> wrote:
>> Should we document qcom,wcn3610 just like wcn3620 is:
>>
>> Documentation/devicetree/bindings/remoteproc/qcom,wcnss-pil.txt: "qcom,wcn3620",
> IMHO the mentioned bindings is related to the PIL (peripheral image loaded) which is just the firmware part and has
> nothing to do with wifi frontend(IRIS).
>
It seems that the RF is a subnode of the PIL node:
"= SUBNODES
A required subnode of the WCNSS PIL is used to describe the attached rf module
and its resource dependencies. It is described by the following properties:"
So we should add qcom,wcn3610 to the exiting list of 'compatible' rf modules.
Regards,
Loic
Powered by blists - more mailing lists