ath9k driver for PCI-e wifi card on TX2

I’m trying to bring up an Atheros PCI-e Wifi card on a TX2 based board with ath9k driver that comes with TX2 kernel, and seeing constant memory controller errors:

[ 15.170663] arm-smmu 12000000.iommu: Unhandled context fault: iova=0x80029000, fsynr=0x100003, cb=22, sid=17(0x11 - AFI), pgd=264033003, pud=264033003, pmd=264032003, pte=0
[ 15.186052] unknown mcerr fault, int_status=0x00001040, ch_int_status=0x00000000, hubc_int_status=0x00000000
[ 15.195883] unknown mcerr fault, int_status=0x00001040, ch_int_status=0x00000000, hubc_int_status=0x00000000
[ 15.205709] unknown mcerr fault, int_status=0x00001040, ch_int_status=0x00000000, hubc_int_status=0x00000000
[ 15.215539] unknown mcerr fault, int_status=0x00001040, ch_int_status=0x00000000, hubc_int_status=0x00000000
[ 15.225361] mc-err: Too many MC errors; throttling prints

It all works fine on TX1. There were some issues discussed previously here https://devtalk.nvidia.com/default/topic/940077/

However, applying the patch to the device tree mentioned in the discussion above doesn’t help, but seems the error becomes more explicit:

[ 362.908106] arm-smmu 12000000.iommu: Unhandled context fault: iova=0x80043000, fsynr=0x10003, cb=22, sid=17(0x11 - AFI), pgd=2652d6003, pud=2652d6003, pmd=2652d7003, pte=0
[ 362.923477] (255) csw_afiw: MC request violates VPR requirements
[ 362.929500] status = 0x00377031; addr = 0x3ffffffc0
[ 362.934560] secure: yes, access-type: write
[ 362.938932] unknown mcerr fault, int_status=0x00000000, ch_int_status=0x00000000, hubc_int_status=0x00000000
[ 362.948763] unknown mcerr fault, int_status=0x00000000, ch_int_status=0x00000000, hubc_int_status=0x00000000
[ 362.958588] unknown mcerr fault, int_status=0x00000000, ch_int_status=0x00000000, hubc_int_status=0x00000000

So something tries to access an address that is not valid.

Did anyone have success in bringing up ath9k for PCIe devices? Any potential clues? All help is appreciated