On Friday, 19 April 2019 20:11:35 CEST Rajkumar Manoharan wrote:
> Hi,
> 
> Posting initial patches to bring Mesh support to ath11k. There are known
> issues which is also captured in first patch.

What else is required to get this working? I used ath11k-bringup (which 
included these patches) and wanted to implement the HE registration part for 
it. But it turns out that it doesn't event work here with VHT. This is what I 
did on two HK01 rev B:

    iw phy phy2 interface add mesh2 type mp
    ip link set up dev mesh2
    iw dev mesh2 mesh join testmesh freq 5180 80MHz

But the firmware just crashes somewhere around the association phase:

    [   59.458342] ath11k c000000.wifi1: Added peer: 00:03:7f:12:82:a3 for VDEV: 0
    [   59.566646] qcom-q6v5-wcss-pil cd00000.qcom_q6v5_wcss: fatal error received:
    [   59.566646] QC Image Version: QC_IMAGE_VERSION_STRING=WLAN.HK.2.1.0.1-00410-QCAHKSWPL_SILICONZ-2
    [   59.566646] Image Variant : IMAGE_VARIANT_STRING=8074.wlanfw.eval_v2Q
    [   59.566646]
    [   59.566646] wlan_peer.c:2486 Assertion (vdev->bss->ni_chan.phy_mode >= peer_ratectrl_params.phymode) failedparam0 :zero, param1 :zero, param2 :zero.
    [   59.566646] Thread ID      : 0x0000005d  Thread name    : WLAN RT2  Process ID     : 0
    [   59.566646] Register:
    [   59.566646] SP : 0x4c1921f0
    [   59.566646] FP : 0x4c1921f8
    [   59.566646] PC : 0x4b1c8850
    [   59.566646] SSR : 0x00000008
    [   59.566646] BADVA : 0x00020000
    [   59.566646] LR : 0x4b1c7c68
    [   59.566646]
    [   59.566646] Stack Dump
    [   59.566646] from : 0x4c1921f0
    [   59.566646] to   : 0x4c192860
    [   59.566646]
    [   59.618939] remoteproc remoteproc0: crash detected in cd00000.qcom_q6v5_wcss: type fatal error
    [   59.641203] remoteproc remoteproc0: handling crash #1 in cd00000.qcom_q6v5_wcss
    [   59.649605] Kernel panic - not syncing: remoteproc remoteproc0: Resetting the SoC - cd00000.qcom_q6v5_wcss crashed

The whole device goes down after that.

Kind regards,
	Sven