Changes in Makefile

936daee9 - Bluetooth: Remove hci_request.{c,h}

Mon, 01 Jul 2024 21:10:41 +0000

Bluetooth: Remove hci_request.{c,h}This removes hci_request.{c,h} since it shall no longer be used.Signed-off-by: Luiz Augusto von Dentz List of files: /linux-6.15/net/bluetooth/Makefile

e7b02296 - Bluetooth: Remove BT_HS

Thu, 01 Feb 2024 16:18:58 +0000

Bluetooth: Remove BT_HSHigh Speed, Alternate MAC and PHY (AMP) extension, has been removed fromBluetooth Core specification on 5.3:https://www.bluetooth.com/blog/new-core-specification-v5-3-feature-enhancements/Fixes: 244bc377591c ("Bluetooth: Add BT_HS config option")Signed-off-by: Luiz Augusto von Dentz List of files: /linux-6.15/net/bluetooth/Makefile

9695ef87 - Bluetooth: Add support for hci devcoredump

Thu, 30 Mar 2023 16:58:23 +0000

Bluetooth: Add support for hci devcoredumpAdd devcoredump APIs to hci core so that drivers only have to providethe dump skbs instead of managing the synchronization and timeouts.The devcoredump APIs should be used in the following manner: - hci_devcoredump_init is called to allocate the dump. - hci_devcoredump_append is called to append any skbs with dump data OR hci_devcoredump_append_pattern is called to insert a pattern. - hci_devcoredump_complete is called when all dump packets have been sent OR hci_devcoredump_abort is called to indicate an error and cancel an ongoing dump collection.The high level APIs just prepare some skbs with the appropriate data andqueue it for the dump to process. Packets part of the crashdump can beintercepted in the driver in interrupt context and forwarded directly tothe devcoredump APIs.Internally, there are 5 states for the dump: idle, active, complete,abort and timeout. A devcoredump will only be in active state after ithas been initialized. Once active, it accepts data to be appended,patterns to be inserted (i.e. memset) and a completion event or an abortevent to generate a devcoredump. The timeout is initialized at the sametime the dump is initialized (defaulting to 10s) and will be clearedeither when the timeout occurs or the dump is complete or aborted.Signed-off-by: Abhishek Pandit-Subedi Signed-off-by: Manish Mandlik Reviewed-by: Abhishek Pandit-Subedi Signed-off-by: Luiz Augusto von Dentz List of files: /linux-6.15/net/bluetooth/Makefile

ccf74f23 - Bluetooth: Add BTPROTO_ISO socket type

Thu, 16 Jan 2020 23:55:57 +0000

Bluetooth: Add BTPROTO_ISO socket typeThis introduces a new socket type BTPROTO_ISO which can be enabled withuse of ISO Socket experiemental UUID, it can used to initiate/acceptconnections and transfer packets between userspace and kernel similarlyto how BTPROTO_SCO works:Central -> uses connect with address set to destination bdaddr:> tools/isotest -s 00:AA:01:00:00:00Peripheral -> uses listen:> tools/isotest -dSigned-off-by: Luiz Augusto von Dentz List of files: /linux-6.15/net/bluetooth/Makefile

6a98e383 - Bluetooth: Add helper for serialized HCI command execution

Wed, 27 Oct 2021 23:58:38 +0000

Bluetooth: Add helper for serialized HCI command executionThe usage of __hci_cmd_sync() within the hdev->setup() callback allows fora nice and simple serialized execution of HCI commands. More importantlyit allows for result processing before issueing the next command.With the current usage of hci_req_run() it is possible to batch upcommands and execute them, but it is impossible to react to theirresults or errors.This is an attempt to generalize the hdev->setup() handling and providea simple way of running multiple HCI commands from a single functioncontext.There are multiple struct work that are decdicated to certain tasksalready used right now. It is add a lot of bloat to hci_dev struct andextra handling code. So it might be possible to put all of these behinda common HCI command infrastructure and just execute the HCI commandsfrom the same work context in a serialized fashion.For example updating the white list and resolving list can be done nowwithout having to know the list size ahead of time. Also preparing forsuspend or resume shouldn't require a state machine anymore. There areother tasks that should be simplified as well.Signed-off-by: Marcel Holtmann Signed-off-by: Luiz Augusto von Dentz Signed-off-by: Marcel Holtmann List of files: /linux-6.15/net/bluetooth/Makefile

01ce70b0 - Bluetooth: eir: Move EIR/Adv Data functions to its own file

Mon, 20 Sep 2021 22:59:37 +0000

Bluetooth: eir: Move EIR/Adv Data functions to its own fileThis moves functions manipulating EIR/Adv Data to its own file so itcan be reused by other files.Signed-off-by: Luiz Augusto von Dentz Signed-off-by: Marcel Holtmann List of files: /linux-6.15/net/bluetooth/Makefile

8961987f - Bluetooth: Enumerate local supported codec and cache details

Tue, 07 Sep 2021 10:12:37 +0000

Bluetooth: Enumerate local supported codec and cache detailsMove reading of supported local codecs into a separate init function,query codecs capabilities and cache the dataSigned-off-by: Kiran K Signed-off-by: Chethan T N Signed-off-by: Srivatsa Ravishankar Signed-off-by: Luiz Augusto von Dentz List of files: /linux-6.15/net/bluetooth/Makefile

f67743f9 - Bluetooth: Add support for reading AOSP vendor capabilities

Tue, 06 Apr 2021 19:55:52 +0000

Bluetooth: Add support for reading AOSP vendor capabilitiesWhen drivers indicate support for AOSP vendor extension, initialize themand read its capabilities.Signed-off-by: Marcel Holtmann Signed-off-by: Luiz Augusto von Dentz List of files: /linux-6.15/net/bluetooth/Makefile

17896406 - Bluetooth: implement read/set default system parameters mgmt

Thu, 11 Jun 2020 02:01:57 +0000

Bluetooth: implement read/set default system parameters mgmtThis patch implements the read default system parameters and the setdefault system parameters mgmt commands.Signed-off-by: Alain Michaud Reviewed-by: Abhishek Pandit-Subedi Signed-off-by: Marcel Holtmann List of files: /linux-6.15/net/bluetooth/Makefile

145373cb - Bluetooth: Add framework for Microsoft vendor extension

Fri, 03 Apr 2020 19:44:01 +0000

Bluetooth: Add framework for Microsoft vendor extensionMicrsoft defined a set for HCI vendor extensions. Check the followinglink for details:https://docs.microsoft.com/en-us/windows-hardware/drivers/bluetooth/microsoft-defined-bluetooth-hci-commands-and-eventsThis provides the basic framework to enable the extension and read itssupported features. Drivers still have to declare support for thisextension before it can be utilized by the host stack.Signed-off-by: Miao-chen Chou Signed-off-by: Marcel Holtmann Signed-off-by: Johan Hedberg List of files: /linux-6.15/net/bluetooth/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/net/bluetooth/Makefile

58771c1c - Bluetooth: convert smp and selftest to crypto kpp API

Mon, 24 Apr 2017 12:13:20 +0000

Bluetooth: convert smp and selftest to crypto kpp API* Convert both smp and selftest to crypto kpp API* Remove module ecc as no more required* Add ecdh_helper functions for wrapping kpp async callsThis patch has been tested *only* with selftest, which is called onmodule loading.Signed-off-by: Salvatore Benedetto Signed-off-by: Marcel Holtmann List of files: /linux-6.15/net/bluetooth/Makefile

6bdf1e0e - Makefile: drop -D__CHECK_ENDIAN__ from cflags

Thu, 15 Dec 2016 02:07:46 +0000

Makefile: drop -D__CHECK_ENDIAN__ from cflagsThat's the default now, no need for makefiles to set it.Signed-off-by: Michael S. Tsirkin Acked-by: Kalle Valo Acked-by: Marcel Holtmann Acked-by: Marc Kleine-Budde Acked-by: Greg Kroah-Hartman Acked-by: Arend van Spriel List of files: /linux-6.15/net/bluetooth/Makefile

6d5d2ee6 - Bluetooth: add LED trigger for indicating HCI is powered up

Fri, 08 Jan 2016 18:28:58 +0000

Bluetooth: add LED trigger for indicating HCI is powered upAdd support for LED triggers to the Bluetooth subsystem and add kernelconfig symbol BT_LEDS for it.For now one trigger for indicating "HCI is powered up" is supported.Signed-off-by: Heiner Kallweit Signed-off-by: Marcel Holtmann List of files: /linux-6.15/net/bluetooth/Makefile

244bc377 - Bluetooth: Add BT_HS config option

Fri, 24 Jul 2015 09:12:55 +0000

Bluetooth: Add BT_HS config optionMove A2MP Module under BT_HS config option and allowthe user have flexible option to choose the feature onlythey needa2mp_discover_amp() & a2mp_channel_create() are a2mp moduleentry point for master and slave, and this is dynamicinvoked depends on the userspace or remote request, thenwe defined their implementation depends on BT_HS configSigned-off-by: Arron Wang Signed-off-by: Marcel Holtmann List of files: /linux-6.15/net/bluetooth/Makefile

ff50e8af - Bluetooth: Move SCO support under BT_BREDR config option

Tue, 09 Jun 2015 09:47:23 +0000

Bluetooth: Move SCO support under BT_BREDR config optionSCO/eSCO link is supported by BR/EDR controller, it issuitable to move them under BT_BREDR config optionSigned-off-by: Arron Wang Signed-off-by: Marcel Holtmann List of files: /linux-6.15/net/bluetooth/Makefile

a380b6cf - Bluetooth: Add generic mgmt helper API

Tue, 17 Mar 2015 11:48:48 +0000

Bluetooth: Add generic mgmt helper APIThere are several mgmt protocol features that will be needed by morethan just the current HCI_CHANNEL_CONTROL. These include sending genericevents as well as handling pending commands. This patch moves thesefunctions out from mgmt.c to a new mgmt_util.c file.Signed-off-by: Johan Hedberg Signed-off-by: Marcel Holtmann List of files: /linux-6.15/net/bluetooth/Makefile

035a07d5 - Bluetooth: Provide option to enable/disable debugfs information

Sat, 14 Feb 2015 21:40:06 +0000

Bluetooth: Provide option to enable/disable debugfs informationThe Bluetooth controllers can export extensive information aboutinternal states via debugfs. This patch provides an option tochoose if these information are provided or not.For backwards compatibility with existing kernel configuration,this option defaults to yes.Signed-off-by: Marcel Holtmann Signed-off-by: Johan Hedberg List of files: /linux-6.15/net/bluetooth/Makefile

ee485290 - Bluetooth: Add support for self testing framework

Tue, 30 Dec 2014 04:48:35 +0000

Bluetooth: Add support for self testing frameworkThis add support for the Bluetooth self testing framework that allowsrunning certain test cases of sample data to ensure correctness of itsbasic functionality.With this patch only the basic framework will be added. It containsthe build magic that allows running this at module loading time orat late_initcall stage when built into the kernel image.Signed-off-by: Marcel Holtmann Signed-off-by: Johan Hedberg List of files: /linux-6.15/net/bluetooth/Makefile

60c5f5fb - Bluetooth: Add skeleton functions for debugfs creation

Sat, 20 Dec 2014 15:05:13 +0000

Bluetooth: Add skeleton functions for debugfs creationThe debugfs file creation has been part of the core initializationhandling of controllers. With the introduction of Bluetooth 4.2 corespecification, the number of debugfs files is increasing even further.To avoid cluttering the core controller handling, create a separatefile hci_debugfs.c to centralize all debugfs file creation. For nowleave the current files in the core, but in the future all debugfsfile creation will be moved.Signed-off-by: Marcel Holtmann Signed-off-by: Johan Hedberg List of files: /linux-6.15/net/bluetooth/Makefile