[PATCH v3 3/3] wifi: ath10k: only load compatible DT cal data

2023-02-01 Thread equu
From: Edward Chow ath10k might also be sensitive to the issue reported on https://github.com/openwrt/openwrt/pull/11345 , loading calibration data from a device tree node declared incompatible. ath10k will first check whether the device tree node is compatible with it, using the functionality

[PATCH v3 2/3] wifi: ath9k: stop loading incompatible DT cal data

2023-02-01 Thread equu
From: Edward Chow As reported in https://github.com/openwrt/openwrt/pull/11345 , ath9k would load calibration data from a device tree node declared incompatible. Now, ath9k will first check whether the device tree node is compatible with it, using the functionality introduced with the first

[PATCH v3 1/3] PCI: of: Match pci devices or drivers against OF DT nodes

2023-02-01 Thread equu
From: Edward Chow Currently, whether a compatibility string within an OF DT node for a PCI device (whose spec is at https://www.devicetree.org/open-firmware/bindings/pci/ ) matches the vendor and device id of either the PCI device installed on the corresponding location or the driver suggested

[PATCH v3 0/3] PCI: of: Load extra data only from compatible DT nodes

2023-02-01 Thread equu
From: Edward Chow In order to solve the issue reported in https://github.com/openwrt/openwrt/pull/11345 , this patchset attempt to add mechanisms to ckeck whether an OF DT node is compatible to the PCI device installed on the corresponding location or the driver for it, and make ath9k and ath10k

Re: [PATCH v2 3/3] wifi: ath10k: only load compatible DT cal data

2023-02-01 Thread kernel test robot
Hi, Thank you for the patch! Perhaps something to improve: [auto build test WARNING on helgaas-pci/next] [also build test WARNING on helgaas-pci/for-linus wireless-next/main wireless/main linus/master v6.2-rc6 next-20230202] [If your patch is applied to the wrong git tree, kindly drop us a

[PATCH v2 3/3] wifi: ath10k: only load compatible DT cal data

2023-02-01 Thread equu
From: Edward Chow ath10k might also be sensitive to the issue reported on https://github.com/openwrt/openwrt/pull/11345 , loading calibration data from a device tree node declared incompatible. ath10k will first check whether the device tree node is compatible with it, using the functionality

[PATCH v2 0/3] PCI: of: Load extra data only from compatible DT nodes

2023-02-01 Thread equu
From: Edward Chow In order to solve the issue reported in https://github.com/openwrt/openwrt/pull/11345 , this patchset attempt to add mechanisms to ckeck whether an OF DT node is compatible to the PCI device installed on the corresponding location or the driver for it, and make ath9k and ath10k

[PATCH v2 1/3] PCI: of: Match pci devices or drivers against OF DT nodes

2023-02-01 Thread equu
From: Edward Chow Currently, whether a compatibility string within an OF DT node for a PCI device (whose spec is at https://www.devicetree.org/open-firmware/bindings/pci/ ) matches the vendor and device id of either the PCI device installed on the corresponding location or the driver suggested

[PATCH v2 2/3] wifi: ath9k: stop loading incompatible DT cal data

2023-02-01 Thread equu
From: Edward Chow As reported in https://github.com/openwrt/openwrt/pull/11345 , ath9k would load calibration data from a device tree node declared incompatible. Now, ath9k will first check whether the device tree node is compatible with it, using the functionality introduced with the first