e401fa25 - qtnfmac: add support for Topaz chipsets

Tue, 16 Oct 2018 10:23:58 +0000

qtnfmac: add support for Topaz chipsetsThis patch adds support for QSR1000/QSR2000 family of chipsetsto qtnfmac_pcie platform driver.QSR1000/QSR2000 (aka Topaz) is a family of 80MHz, 11ac Wave2,4x4/2x4/2x2 chips, including single and dual band devices.Depending on specific chip model and firmware in use, eitherSTA or both STA and AP modes are supported.Patch adds Topaz support to qtnfmac_pcie driver. Proper platformbus will be selected on probing based on chip ID.Signed-off-by: Igor Mitsyanko Signed-off-by: Sergey Matyukevich Signed-off-by: Andrey Shevchenko Signed-off-by: Kalle Valo List of files: /linux-6.15/drivers/net/wireless/quantenna/qtnfmac/Makefile

b7da53cd - qtnfmac_pcie: use single PCIe driver for all platforms

Tue, 16 Oct 2018 10:23:56 +0000

qtnfmac_pcie: use single PCIe driver for all platformsSingle PCIe driver can identify hardware type by reading CHIP ID atprobe time and invoking a correct initialization sequence.Signed-off-by: Igor Mitsyanko Signed-off-by: Kalle Valo List of files: /linux-6.15/drivers/net/wireless/quantenna/qtnfmac/Makefile

addc7540 - qtnfmac_pcie: extract platform-independent PCIe code

Mon, 24 Sep 2018 22:15:12 +0000

qtnfmac_pcie: extract platform-independent PCIe codeExtract platform-independent PCIe driver code into a separate file, anduse it from platform-specific modules.Signed-off-by: Igor Mitsyanko Signed-off-by: Kalle Valo List of files: /linux-6.15/drivers/net/wireless/quantenna/qtnfmac/Makefile

2ef0ecd7 - qtnfmac_pcie: move Pearl pcie sources to pcie-specific directory

Mon, 24 Sep 2018 22:15:05 +0000

qtnfmac_pcie: move Pearl pcie sources to pcie-specific directoryIn preparation to extract common qtnfmac PCIe driver sources into aseparate file, move existing Pearl-specific pcie driver sources to pcie/directory.Signed-off-by: Igor Mitsyanko Signed-off-by: Kalle Valo List of files: /linux-6.15/drivers/net/wireless/quantenna/qtnfmac/Makefile

b2441318 - License cleanup: add SPDX GPL-2.0 license identifier to files with no license

Wed, 01 Nov 2017 14:07:57 +0000

License cleanup: add SPDX GPL-2.0 license identifier to files with no licenseMany source files in the tree are missing licensing information, whichmakes it harder for compliance tools to determine the correct license.By default all files without license information are under the defaultlicense of the kernel, which is GPL version 2.Update the files which contain no license information with the 'GPL-2.0'SPDX license identifier. The SPDX identifier is a legally bindingshorthand, which can be used instead of the full boiler plate text.This patch is based on work done by Thomas Gleixner and Kate Stewart andPhilippe Ombredanne.How this work was done:Patches were generated and checked against linux-4.14-rc6 for a subset ofthe use cases: - file had no licensing information it it. - file was a */uapi/* one with no licensing information in it, - file was a */uapi/* one with existing licensing information,Further patches will be generated in subsequent months to fix up caseswhere non-standard license headers were used, and references to licensehad to be inferred by heuristics based on keywords.The analysis to determine which SPDX License Identifier to be applied toa file was done in a spreadsheet of side by side results from of theoutput of two independent scanners (ScanCode & Windriver) producing SPDXtag:value files created by Philippe Ombredanne. Philippe prepared thebase worksheet, and did an initial spot review of a few 1000 files.The 4.13 kernel was the starting point of the analysis with 60,537 filesassessed. Kate Stewart did a file by file comparison of the scannerresults in the spreadsheet to determine which SPDX license identifier(s)to be applied to the file. She confirmed any determination that was notimmediately clear with lawyers working with the Linux Foundation.Criteria used to select files for SPDX license identifier tagging was: - Files considered eligible had to be source code files. - Make and config files were included as candidates if they contained >5 lines of source - File already had some variant of a license header in it (even if <5 lines).All documentation files were explicitly excluded.The following heuristics were used to determine which SPDX licenseidentifiers to apply. - when both scanners couldn't find any license traces, file was considered to have no license information in it, and the top level COPYING file license applied. For non */uapi/* files that summary was: SPDX license identifier # files ---------------------------------------------------|------- GPL-2.0 11139 and resulted in the first patch in this series. If that file was a */uapi/* path one, it was "GPL-2.0 WITH Linux-syscall-note" otherwise it was "GPL-2.0". Results of that was: SPDX license identifier # files ---------------------------------------------------|------- GPL-2.0 WITH Linux-syscall-note 930 and resulted in the second patch in this series. - if a file had some form of licensing information in it, and was one of the */uapi/* ones, it was denoted with the Linux-syscall-note if any GPL family license was found in the file or had no licensing in it (per prior point). Results summary: SPDX license identifier # files ---------------------------------------------------|------ GPL-2.0 WITH Linux-syscall-note 270 GPL-2.0+ WITH Linux-syscall-note 169 ((GPL-2.0 WITH Linux-syscall-note) OR BSD-2-Clause) 21 ((GPL-2.0 WITH Linux-syscall-note) OR BSD-3-Clause) 17 LGPL-2.1+ WITH Linux-syscall-note 15 GPL-1.0+ WITH Linux-syscall-note 14 ((GPL-2.0+ WITH Linux-syscall-note) OR BSD-3-Clause) 5 LGPL-2.0+ WITH Linux-syscall-note 4 LGPL-2.1 WITH Linux-syscall-note 3 ((GPL-2.0 WITH Linux-syscall-note) OR MIT) 3 ((GPL-2.0 WITH Linux-syscall-note) AND MIT) 1 and that resulted in the third patch in this series. - when the two scanners agreed on the detected license(s), that became the concluded license(s). - when there was disagreement between the two scanners (one detected a license but the other didn't, or they both detected different licenses) a manual inspection of the file occurred. - In most cases a manual inspection of the information in the file resulted in a clear resolution of the license that should apply (and which scanner probably needed to revisit its heuristics). - When it was not immediately clear, the license identifier was confirmed with lawyers working with the Linux Foundation. - If there was any question as to the appropriate license identifier, the file was flagged for further research and to be revisited later in time.In total, over 70 hours of logged manual review was done on thespreadsheet to determine the SPDX license identifiers to apply to thesource files by Kate, Philippe, Thomas and, in some cases, confirmationby lawyers working with the Linux Foundation.Kate also obtained a third independent scan of the 4.13 code base fromFOSSology, and compared selected files where the other two scannersdisagreed against that SPDX file, to see if there was new insights. TheWindriver scanner is based on an older version of FOSSology in part, sothey are related.Thomas did random spot checks in about 500 files from the spreadsheetsfor the uapi headers and agreed with SPDX license identifier in thefiles he inspected. For the non-uapi files Thomas did random spot checksin about 15000 files.In initial set of patches against 4.14-rc6, 3 files were found to havecopy/paste license identifier errors, and have been fixed to reflect thecorrect identifier.Additionally Philippe spent 10 hours this week doing a detailed manualinspection and review of the 12,461 patched files from the initial patchversion early this week with: - a full scancode scan run, collecting the matched texts, detected license ids and scores - reviewing anything where there was a license detected (about 500+ files) to ensure that the applied SPDX license was correct - reviewing anything where there was no detection but the patch license was not GPL-2.0 WITH Linux-syscall-note to ensure that the applied SPDX license was correctThis produced a worksheet with 20 files needing minor correction. Thisworksheet was then exported into 3 different .csv files for thedifferent types of files to be modified.These .csv files were then reviewed by Greg. Thomas wrote a script toparse the csv files and add the proper SPDX tag to the file, in theformat that the file expected. This script was further refined by Gregbased on the output to detect more types of files automatically and todistinguish between header and source .c files (which need differentcomment types.) Finally Greg ran the script using the .csv files togenerate the patches.Reviewed-by: Kate Stewart Reviewed-by: Philippe Ombredanne Reviewed-by: Thomas Gleixner Signed-off-by: Greg Kroah-Hartman List of files: /linux-6.15/drivers/net/wireless/quantenna/qtnfmac/Makefile

57b18a75 - qtnfmac: drop -D__CHECK_ENDIAN from cflags

Tue, 29 Aug 2017 12:16:19 +0000

qtnfmac: drop -D__CHECK_ENDIAN from cflagsFlag -D__CHECK_ENDIAN was wrong: it should be -D__CHECK_ENDIAN__ instead.However now this flag is enabled by default, so it can be removed.Signed-off-by: Sergey Matyukevich Signed-off-by: Kalle Valo List of files: /linux-6.15/drivers/net/wireless/quantenna/qtnfmac/Makefile

98f44cb0 - qtnfmac: introduce new FullMAC driver for Quantenna chipsets

Thu, 11 May 2017 21:51:01 +0000

qtnfmac: introduce new FullMAC driver for Quantenna chipsetsThis patch adds support for new FullMAC WiFi driver for QuantennaQSR10G chipsets.QSR10G (aka Pearl) is Quantenna's 8x8, 160M, 11ac offering.QSR10G supports 2 simultaneous WMACs - one 5G and one 2G.5G WMAC supports 160M, 8x8 configuration. FW supportsup to 8 concurrent virtual interfaces on each WMAC.Patch introduces 2 new drivers:- qtnfmac.ko for interfacing with kernel wireless core- qtnfmac_pearl_pcie.ko for interfacing with hardware over PCIe interfaceSigned-off-by: Dmitrii Lebed Signed-off-by: Sergei Maksimenko Signed-off-by: Sergey Matyukevich Signed-off-by: Bindu Therthala Signed-off-by: Huizhao Wang Signed-off-by: Kamlesh Rath Signed-off-by: Avinash Patil Signed-off-by: Igor Mitsyanko Signed-off-by: Kalle Valo List of files: /linux-6.15/drivers/net/wireless/quantenna/qtnfmac/Makefile