[PATCH RFC 0/7] ARM: bcm283x: Raspberry Pi Zero W support

[Stefan Wahren]

Am 19.07.2017 um 22:46 schrieb Eric Anholt:
> Stefan Wahren <stefan.wahren at i2se.com> writes:
>
>>> Stefan Wahren <stefan.wahren at i2se.com> hat am 9. Juli 2017 um 15:10 geschrieben:
>>>
>>>
>>> Hi,
>>>
>>>> Stefan Wahren <stefan.wahren at i2se.com> hat am 23. Juni 2017 um 22:27 geschrieben:
>>>>
>>>> ...
>>>>
>>>> Known issues:
>>>>
>>>> The Wifi chip is present in DT and detected during boot, but doesn't work
>>>> properly. I assume i need to apply some of Gerd's patches:
>>>>
>>>>     brcmfmac: brcmf_c_preinit_dcmds: Firmware version = wl0: May 27 2016 ...
>>>>     brcmfmac: brcmf_sdio_hostmail: Unknown mailbox data content: 0x40012
>>>>     brcmfmac: brcmf_sdio_bus_rxctl: reproto_bcdc_msg failed w/status -110
>>>>     brcmfmac: brcmf_cfg80211_attach: Failed to get D11 version (-110)
>>>>     brcmfmac: brcmf_bus_started: failed: -12
>>>>     brcmfmac: brcmf_sdio_firmware_callback: dongle is not responding
>>>>
>>> i figured out this is a regression in linux-next. So i rebased my changes on a clean 4.12:
>>>
>>> https://github.com/lategoodbye/rpi-zero/tree/rpi-zero-w-v2
>>>
>>> After that the wifi interface comes up.
>> I prepared a branch based on 4.13-rc1, which contains a workaround for the issue above:
>>
>> https://github.com/lategoodbye/rpi-zero/commits/rpi-zero-w-v3
> I've sent out a patch today that introduces a slight conflict for this,
> but would allow squashing patch 1+2 together so they make more sense
> (and avoid a possible need for a cross-merge from arm32 to arm64 for
> patch 2).
>
> I've merged the defconfig stuff to for-next, as we don't need any other
> acks for that.  Want to send your DT stuff as non-RFC, and Cc the DT
> maintainers so we can get the binding doc acked and start merging it?

Yes, i've made some longterm tests with my RPi Zero W in AP mode and it
looks very promising. Currently i can't see any need of those RPi
specific downstream patches on brcmfmac. So the final patch series would
be very small.