Changes in Makefile

d33dbddf - ARM: keystone: Merge PM function into main support file

Wed, 26 Jul 2023 16:04:41 +0000

ARM: keystone: Merge PM function into main support fileThe one function left in this file does not justify a whole extrafile nor the keystone.h support file used to forward declare thatfunction. Merge this into the main keystone.c file.Signed-off-by: Andrew Davis Link: https://lore.kernel.org/r/20230726160441.101566-2-afd@ti.comSigned-off-by: Nishanth Menon List of files: /linux-6.15/arch/arm/mach-keystone/Makefile

7e8edf55 - ARM: keystone: Replace platform SMP with PSCI

Wed, 26 Oct 2022 14:50:33 +0000

ARM: keystone: Replace platform SMP with PSCIThe KS2 boot monitor supports PSCI commands. These are already definedin DT for KS2. We can drop this platform override and remove relatedcode without changing SMP. Do this here.Signed-off-by: Andrew Davis Signed-off-by: Nishanth Menon Link: https://lore.kernel.org/r/20221026145033.17905-1-afd@ti.com List of files: /linux-6.15/arch/arm/mach-keystone/Makefile

3fe1ee40 - ARM: use arch_extension directive instead of arch argument

Mon, 27 May 2019 22:40:50 +0000

ARM: use arch_extension directive instead of arch argumentThe LLVM Target parser currently does not allow to specify the securityextension as part of -march (see also LLVM Bug 40186 [0]). When tryingto use Clang with LLVM's integrated assembler, this leads to builderrors such as this: clang-8: error: the clang compiler does not support '-Wa,-march=armv7-a+sec'Use ".arch_extension sec" to enable the security extension in a moreportable fasion. Also make sure to use ".arch armv7-a" in case a v6/v7multi-platform kernel is being built.Note that this is technically not exactly the same as the old codechecked for availabilty of the security extension by calling as-instr.However, there are already other sites which use ".arch_extension sec"unconditionally, hence de-facto we need an assembler capable of".arch_extension sec" already today (arch/arm/mm/proc-v7.S). Thearch extension "sec" is available since binutils 2.21 according toits documentation [1].[0] https://bugs.llvm.org/show_bug.cgi?id=40186[1] https://sourceware.org/binutils/docs-2.21/as/ARM-Options.htmlSigned-off-by: Stefan Agner Acked-by: Mans Rullgard Acked-by: Arnd Bergmann Acked-by: Krzysztof Kozlowski Signed-off-by: Olof Johansson List of files: /linux-6.15/arch/arm/mach-keystone/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/arch/arm/mach-keystone/Makefile

fc20ffe1 - ARM: keystone: add PM domain support for clock management

Sun, 14 Jul 2013 21:17:39 +0000

ARM: keystone: add PM domain support for clock managementAdd runtime PM core support to Keystone SOCs by using the pm_clkinfrastructure of the PM core. Patch is based on Kevin's pm_domainwork on DaVinci SOCs.Keystone SOC doesn't have depedency to enable clocks in earlyin the boot and hence the clock and PM domain initialisation is doneat subsys_init() level.Cc: Kevin Hilman Signed-off-by: Santosh Shilimkar List of files: /linux-6.15/arch/arm/mach-keystone/Makefile

3aae7ab0 - ARM: keystone: Move CPU bringup code to dedicated asm file

Fri, 21 Jun 2013 22:54:47 +0000

ARM: keystone: Move CPU bringup code to dedicated asm fileBecause of inline asm usage in platsmp.c, smc instructioncreates build failure for ARM V6+V7 build where as using instructionencoding for smc breaks the thumb2 build.So move the code snippet to separate asm file and markit with 'armv7-a$(plus_sec)' to avoid any build issues.Signed-off-by: Santosh Shilimkar Signed-off-by: Arnd Bergmann List of files: /linux-6.15/arch/arm/mach-keystone/Makefile

f07cb6a0 - ARM: keystone: Enable SMP support on Keystone machines

Mon, 10 Jun 2013 16:20:17 +0000

ARM: keystone: Enable SMP support on Keystone machinesAdd basic SMP support for Keystone machines. This does notinclude support for CPU hotplug for now.Cc: Arnd Bergmann Cc: arm@kernel.orgAcked-by: Olof Johansson Signed-off-by: Santosh Shilimkar List of files: /linux-6.15/arch/arm/mach-keystone/Makefile

828989ad - ARM: keystone: Add minimal TI Keystone platform support

Mon, 10 Jun 2013 15:27:13 +0000

ARM: keystone: Add minimal TI Keystone platform supportTexas Instruments Keystone family of multi-core devices arebased on ARM Cortex A15. Patch adds basic definitions for anew Keystone sub-architecture in ARM.The TCI66xxK2H Communications Infrastructure Keystone SoCsare member of the C66x family based on TI's new KeyStone 2multi-core SoC Architecture designed specifically for highperformance wireless and networking infrastructure applications.The SOCs contains many subsystems like Cortex A15 ARM CorePacs,C66XX DSP CorePacs, MSMC memory controller, Tera Net bus,IP Network, Navigator, Hyperlink, 1G/10G Ethernet, Radio layersand queue based communication systems.Cc: Arnd Bergmann Cc: arm@kernel.orgAcked-by: Olof Johansson Signed-off-by: Santosh Shilimkar List of files: /linux-6.15/arch/arm/mach-keystone/Makefile