Failing to load wcn36xx firmware on db410c with mainline

[Riku Voipio]

On 11 January 2017 at 21:48, Bjorn Andersson <bjorn.andersson at linaro.org> wrote:
> On Wed 11 Jan 00:00 PST 2017, Riku Voipio wrote:
>
>> Hi,
>>
>> I'm triying wifi on Dragonboard 410c with mainline 4.10-rc3 + wcn36xxx
>> patches from: https://git.kernel.org/cgit/linux/kernel/git/kvalo/ath.git/log/?h=pending
>>
>> For device tree, the following was applied:
>> https://patches.linaro.org/patch/83059/
>>
>> Mainline:
>>
>> [    7.858517] a204000.wcnss supply vddcx not found, using dummy regulator
>> [    7.868858] remoteproc remoteproc0: a204000.wcnss is available
>> [    7.872690] remoteproc remoteproc0: powering up a204000.wcnss
>> [    7.874077] remoteproc remoteproc0: Booting fw image wcnss.mdt, size 7260
>> [    7.882642] remoteproc remoteproc0: invalid firmware metadata
>> [    7.886649] remoteproc remoteproc0: Failed to load program segments: 130
>>
>
> It looks like you're running into an issue with how we interface with
> TrustZone to authenticate the firmware on recent kernels.

> The fix for this is under review, you can pick the latest patches here:
> https://patchwork.kernel.org/patch/9491673/
> https://patchwork.kernel.org/patch/9491677/

Thanks, with these patches wireless works!

 For future improvement, it seems a module dependency should be added.
Until I modprobe wcn36xx, there is a stream of reboot messages every
40 sec:

[   48.577262] remoteproc remoteproc0: crash detected in
a204000.wcnss: type fatal error
[   48.585161] remoteproc remoteproc0: handling crash #1 in a204000.wcnss
[   48.593098] remoteproc remoteproc0: recovering a204000.wcnss
[   48.608660] remoteproc remoteproc0: stopped remote processor a204000.wcnss
[   48.608848] remoteproc remoteproc0: powering up a204000.wcnss
[   48.614636] remoteproc remoteproc0: Booting fw image wcnss.mdt, size 7260
[   48.620864] alloc_contig_range: [b9864, b9866) PFNs busy
[   49.049980] remoteproc remoteproc0: remote processor a204000.wcnss is now up


Riku