Changes in Makefile

8e1debd8 - wifi: ath10k: add LED and GPIO controlling support for various chipsets

Mon, 13 May 2024 14:22:25 +0000

wifi: ath10k: add LED and GPIO controlling support for various chipsetsAdds LED and GPIO Control support for 988x, 9887, 9888, 99x0, 9984based chipsets with on chipset connected led's using WMI Firmware API.The LED device will get available named as "ath10k-phyX" at sysfs andcan be controlled with various triggers.Adds also debugfs interface for gpio control.Signed-off-by: Sebastian Gottschall Reviewed-by: Steve deRosier [kvalo: major reorg and cleanup]Signed-off-by: Kalle Valo [ansuel: rebase and small cleanup]Signed-off-by: Christian Marangi Tested-by: Stefan Lippers-Hollmann Signed-off-by: Kalle Valo Link: https://msgid.link/20230611080505.17393-1-ansuelsmth@gmail.com List of files: /linux-6.15/drivers/net/wireless/ath/ath10k/Makefile

f0553ca9 - ath10k: switch to use SPDX license identifiers

Tue, 19 Feb 2019 17:45:26 +0000

ath10k: switch to use SPDX license identifiersUse SPDX identifiers everywhere in ath10k.Makefile was incorrectly marked in commit b24413180f56 ("License cleanup: addSPDX GPL-2.0 license identifier to files with no license"), fix that as well.Signed-off-by: Kalle Valo List of files: /linux-6.15/drivers/net/wireless/ath/ath10k/Makefile

ba94c753 - ath10k: add QMI message handshake for wcn3990 client

Thu, 11 Oct 2018 10:16:26 +0000

ath10k: add QMI message handshake for wcn3990 clientAdd WCN3990 QMI client handshakes for Q6 integrated WLAN connectivitysubsystem. This layer is responsible for communicating qmi controlmessages to wifi fw QMI service using QMI messaging protocol.Qualcomm MSM Interface(QMI) is a messaging format used to communicatebetween components running between remote processors with underlyingtransport layer based on integrated chipset(shared memory) ordiscrete chipset(PCI/USB/SDIO/UART).Signed-off-by: Govind Singh Reviewed-by: Bjorn Andersson Acked-by: Niklas Cassel Reviewed-by: Brian Norris Signed-off-by: Kalle Valo List of files: /linux-6.15/drivers/net/wireless/ath/ath10k/Makefile

17f5559e - ath10k: platform driver for WCN3990 SNOC WLAN module

Tue, 10 Apr 2018 15:01:14 +0000

ath10k: platform driver for WCN3990 SNOC WLAN moduleWCN3990 is integrated 802.11ac chipset with SNOCbus interface. Add snoc layer driver registrationand associated ops.WCN3990 support is not yet complete as cold-boothandshake is done using qmi(Qualcomm-MSM-Interface)and qmi client support will be added once qmi frameworkis available.Signed-off-by: Govind Singh Signed-off-by: Kalle Valo List of files: /linux-6.15/drivers/net/wireless/ath/ath10k/Makefile

a0aedd6e - ath10k: build ce layer in ath10k core module

Tue, 10 Apr 2018 15:01:11 +0000

ath10k: build ce layer in ath10k core moduleCE layer is shared between pci and snoc target and resultsin duplicate object inclusion if both modules are compiledtogether statically and undefined KBUILD_MODNAME ifcompiled as module.Fix this by building ce layer in ath10k core module byadding ce object inclusion with ATH10K_CE boolean CONFIG.Signed-off-by: Govind Singh Signed-off-by: Kalle Valo List of files: /linux-6.15/drivers/net/wireless/ath/ath10k/Makefile

e2fcf60c - ath10k: detach coredump.c from debug.c

Fri, 22 Dec 2017 13:38:59 +0000

ath10k: detach coredump.c from debug.cNow coredump is totally separate from debug.c and doesn't depend onCONFIG_ATH10K_DEBUGFS anymore, only on CONFIG_DEV_COREDUMP. Also removeleftovers from the removed debugfs file support.Signed-off-by: Kalle Valo List of files: /linux-6.15/drivers/net/wireless/ath/ath10k/Makefile

f25b9f28 - ath10k: refactor firmware crashdump code to coredump.c

Fri, 22 Dec 2017 13:38:43 +0000

ath10k: refactor firmware crashdump code to coredump.cIn preparation to add RAM dump support. No functional changes, only moving codeand renaming function names.Signed-off-by: Kalle Valo List of files: /linux-6.15/drivers/net/wireless/ath/ath10k/Makefile

42e01cb9 - ath10k: move spectral scan support under a separate config symbol

Mon, 27 Nov 2017 17:56:23 +0000

ath10k: move spectral scan support under a separate config symbolAt the moment, spectral scan support, and with it RELAY, is always enabledwith ATH10K_DEBUGFS. Spectral scan support is currently the only user ofRELAY in ath10k, and it unconditionally reserves a relay channel.Having debugfs support in ath10k is often useful even on very smallembedded routers, where we'd rather like to avoid the code size and RAMusage of the relay support. While ath10k-based devices usually have moreresources than ath9k-based ones, it makes sense to keep the configurationsymmetric to ath9k, so the same base kernel without RELAY can be used forboth ath9k and ath10k hardware.Signed-off-by: Matthias Schiffer Signed-off-by: Kalle Valo List of files: /linux-6.15/drivers/net/wireless/ath/ath10k/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/ath/ath10k/Makefile

4db66499 - ath10k: add initial USB support

Fri, 28 Jul 2017 12:15:39 +0000

ath10k: add initial USB supportChipsets like QCA9377 have support for USB so add initial USB bussupport to ath10k. With this patch we have the low level HIF andHTC protocol working and it's possible to boot the firmware,but it's still not possible to connect or anything like.More changes are needed for full functionality. For that reasonwe print during initialisation:WARNING: ath10k USB support is incomplete, don't expect anything to work!Signed-off-by: Erik Stromdahl Signed-off-by: Kalle Valo List of files: /linux-6.15/drivers/net/wireless/ath/ath10k/Makefile

d96db25d - ath10k: add initial SDIO support

Wed, 26 Apr 2017 09:18:00 +0000

ath10k: add initial SDIO supportChipsets like QCA6584 have support for SDIO so add initial SDIO bus support toath10k. With this patch we have the low level HTC protocol working and it'spossible to boot the firmware, but it's still not possible to connect oranything like. More changes are needed for full functionality. For that reasonwe print during initialisation:WARNING: ath10k SDIO support is incomplete, don't expect anything to work!Signed-off-by: Erik Stromdahl [kvalo@qca.qualcomm.com: refactoring, cleanup, commit log]Signed-off-by: Kalle Valo List of files: /linux-6.15/drivers/net/wireless/ath/ath10k/Makefile

0b523ced - ath10k: add basic skeleton to support ahb

Wed, 27 Jan 2016 09:54:25 +0000

ath10k: add basic skeleton to support ahbqca4019 uses ahb instead of pci where it slightly differs in deviceenumeration, clock control, reset control, etc. Good thing is thatahb also uses copy engine for the data transaction. So, the most ofthe stuff implemented in pci.c/ce.c are reusable in ahb case too.Device enumeration in ahb case comes through platform driver/devicemodel. All resource details like irq, memory map, clocks, etc forqca4019 can be fetched from of_node of platform device.Simply flow would look like, device tree => platform device (kernel) => platform driver (ath10k)Device tree entry will have all qca4019 resource details and the sameinfo will be passed to kernel. Kernel will prepare new platform devicefor that entry and expose DT info to of_node in platform device.Later, ath10k would register platform driver with unique compatible nameand then kernels binds to corresponding compatible entry & calls ath10kahb probe functions. From there onwards, ath10k will take control of itand move forward.New bool flag CONFIG_ATH10K_AHB is added in Kconfig to conditionallyenable ahb support in ath10k. On enabling this flag, ath10k_pci.kowill have ahb support. This patch adds only basic skeleton and fewmacros to support ahb in the context of qca4019.Signed-off-by: Raja Mani Signed-off-by: Kalle Valo List of files: /linux-6.15/drivers/net/wireless/ath/ath10k/Makefile

dcb02db1 - ath10k: Add support for code swap

Thu, 18 Jun 2015 07:01:09 +0000

ath10k: Add support for code swapCode swap is a mechanism to use host memory to storesome fw binary code segment. Ath10k host driver allocatesand loads the code swap binary into the host memory andconfigures the target with the host allocated memoryinformation at the address taken from code swap binary.This patch adds code swap support for firmware binary.Code swap binary for firmware bin is available inATH10K_FW_IE_FW_CODE_SWAP_IMAGE.Signed-off-by: Vasanthakumar Thiagarajan Signed-off-by: Kalle Valo List of files: /linux-6.15/drivers/net/wireless/ath/ath10k/Makefile

5fd3ac3c - ath10k: add WOW disconnect/magic-packet support

Mon, 23 Mar 2015 15:32:53 +0000

ath10k: add WOW disconnect/magic-packet supportAdd support for WOW disconnect and magic-packet.Signed-off-by: Janusz Dziedzic Signed-off-by: Kalle Valo List of files: /linux-6.15/drivers/net/wireless/ath/ath10k/Makefile

6a94888f - ath10k: refactor p2p noa code

Thu, 26 Feb 2015 12:23:17 +0000

ath10k: refactor p2p noa codeSome files are getting bloated and it makes senseto split some of the code into separate files. Doso with the P2P NoA code and prepare it for reuse.Signed-off-by: Michal Kazior Signed-off-by: Kalle Valo List of files: /linux-6.15/drivers/net/wireless/ath/ath10k/Makefile

d63955b3 - ath10k: add support for qca6174

Sat, 24 Jan 2015 10:14:49 +0000

ath10k: add support for qca6174The QCA6174 in combination with new wmi-tlv firmware is capable ofmulti-channel, beamforming, tdls and other features.This patch just makes it possible to boot these devices and do some basic stufflike connect to an AP without encryption. Some things may not work or may beunreliable. New features will be implemented later. This will be addressedeventually with future patches.Signed-off-by: Michal Kazior Signed-off-by: Kalle Valo List of files: /linux-6.15/drivers/net/wireless/ath/ath10k/Makefile

f5045988 - ath10k: Implement sta_add_debugfs

Mon, 12 Jan 2015 12:07:27 +0000

ath10k: Implement sta_add_debugfsAdd per station debugfs files when a station is added to mac80211'sstation list. This helps to group peer specific debugfs entriesaltogether. Right now this callback adds support to test aggregationprocedures (addba/addba_resp/delba) manually.To enable automatic aggregation in target,echo 0 >/sys/kernel/debug/ieee80211/phyX/netdev:wlanX/ stations/XX:XX:XX:XX:XX:XX/aggr_modeFor manual mode,echo 1 >/sys/kernel/debug/ieee80211/phyX/netdev:wlanX/ stations/XX:XX:XX:XX:XX:XX/aggr_modeSigned-off-by: Rajkumar Manoharan Signed-off-by: Kalle Valo List of files: /linux-6.15/drivers/net/wireless/ath/ath10k/Makefile

fe6f36d6 - ath10k: add thermal cooling device support

Wed, 17 Dec 2014 10:22:07 +0000

ath10k: add thermal cooling device supportThermal cooling device support is added to control the temperatureby throttling the data transmission for the given duration. Throttlingis done using hw MAC quiet time setting. Period, duration and offsetfrom TBTT can be set up to quiet the MAC transmits for the required dutycycle (% of quiet duration). The thermal device allows user to configureduty cycle.The quiet params are derived as follows. period = max(25TU, beacon interval / number of bss) duration = period * duty cycle / 100Quiet mode can be disabled by setting the duty cycle to 0. The coolingdevice can be found under /sys/class/thermal/cooling_deviceX/.Corresponding soft link to this device can be found under phy folder./sys/class/ieee80211/phy*/device/cooling_device.To set duty cycle as 40%,echo 40 >/sys/class/ieee80211/phy*/device/cooling_device/cur_stateSigned-off-by: Rajkumar Manoharan Signed-off-by: Kalle Valo List of files: /linux-6.15/drivers/net/wireless/ath/ath10k/Makefile

ca996ec5 - ath10k: implement wmi-tlv backend

Wed, 03 Dec 2014 08:11:32 +0000

ath10k: implement wmi-tlv backendLatest main firmware branch introduced a new WMIABI called wmi-tlv. It is not a tlv strictlyspeaking but something that resembles it becauseit is ordered and may have duplicate id entries.This prepares ath10k to support new hw.Signed-off-by: Michal Kazior Signed-off-by: Kalle Valo List of files: /linux-6.15/drivers/net/wireless/ath/ath10k/Makefile

43d2a30f - ath10k: add testmode

Wed, 10 Sep 2014 15:23:30 +0000

ath10k: add testmodeAdd testmode interface for starting and using UTF firmware which is used to runfactory tests. This is implemented by adding new state ATH10K_STATE_UTF and userspace can enable this state with ATH10K_TM_CMD_UTF_START command. To go back tonormal mode user space can send ATH10K_TM_CMD_UTF_STOP.Signed-off-by: Kalle Valo List of files: /linux-6.15/drivers/net/wireless/ath/ath10k/Makefile