Changes in Makefile

c835e5a3 - tee: tstee: Add Trusted Services TEE driver

Mon, 25 Mar 2024 15:11:03 +0000

tee: tstee: Add Trusted Services TEE driverThe Trusted Services project provides a framework for developing anddeploying device Root of Trust services in FF-A Secure Partitions. TheFF-A SPs are accessible through the FF-A driver, but this doesn'tprovide a user space interface. The goal of this TEE driver is to makeTrusted Services SPs accessible for user space clients.All TS SPs have the same FF-A UUID, it identifies the RPC protocol usedby TS. A TS SP can host one or more services, a service is identified byits service UUID. The same type of service cannot be present twice inthe same SP. During SP boot each service in an SP is assigned aninterface ID, this is just a short ID to simplify message addressing.There is 1:1 mapping between TS SPs and TEE devices, i.e. a separate TEEdevice is registered for each TS SP. This is required since contrary tothe generic TEE design where memory is shared with the whole TEEimplementation, in case of FF-A, memory is shared with a specific SP. Auser space client has to be able to separately share memory with each SPbased on its endpoint ID.Acked-by: Sumit Garg Signed-off-by: Balint Dobszay Signed-off-by: Jens Wiklander List of files: /linux-6.15/drivers/tee/Makefile

757cc3e9 - tee: add AMD-TEE driver

Fri, 27 Dec 2019 05:24:01 +0000

tee: add AMD-TEE driverAdds AMD-TEE driver.* targets AMD APUs which has AMD Secure Processor with software-based Trusted Execution Environment (TEE) support* registers with TEE subsystem* defines tee_driver_ops function callbacks* kernel allocated memory is used as shared memory between normal world and secure world.* acts as REE (Rich Execution Environment) communication agent, which uses the services of AMD Secure Processor driver to submit commands for processing in TEE environmentCc: Ard Biesheuvel Cc: Tom Lendacky Acked-by: Jens Wiklander Co-developed-by: Devaraj Rangasamy Signed-off-by: Devaraj Rangasamy Signed-off-by: Rijo Thomas Reviewed-by: Gary R Hook Signed-off-by: Herbert Xu List of files: /linux-6.15/drivers/tee/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/tee/Makefile

4fb0a5eb - tee: add OP-TEE driver

Tue, 14 Apr 2015 12:33:20 +0000

tee: add OP-TEE driverAdds a OP-TEE driver which also can be compiled as a loadable module.* Targets ARM and ARM64* Supports using reserved memory from OP-TEE as shared memory* Probes OP-TEE version using SMCs* Accepts requests on privileged and unprivileged device* Uses OPTEE message protocol version 2 to communicate with secure worldAcked-by: Andreas Dannenberg Tested-by: Jerome Forissier (HiKey)Tested-by: Volodymyr Babchuk (RCAR H3)Tested-by: Scott Branden Reviewed-by: Javier González Signed-off-by: Jens Wiklander List of files: /linux-6.15/drivers/tee/Makefile

967c9cca - tee: generic TEE subsystem

Wed, 11 Mar 2015 13:39:39 +0000

tee: generic TEE subsystemInitial patch for generic TEE subsystem.This subsystem provides:* Registration/un-registration of TEE drivers.* Shared memory between normal world and secure world.* Ioctl interface for interaction with user space.* Sysfs implementation_id of TEE driverA TEE (Trusted Execution Environment) driver is a driver that interfaceswith a trusted OS running in some secure environment, for example,TrustZone on ARM cpus, or a separate secure co-processor etc.The TEE subsystem can serve a TEE driver for a Global Platform compliantTEE, but it's not limited to only Global Platform TEEs.This patch builds on other similar implementations trying to solvethe same problem:* "optee_linuxdriver" by among others Jean-michel DELORME and Emmanuel MICHEL * "Generic TrustZone Driver" by Javier González Acked-by: Andreas Dannenberg Tested-by: Jerome Forissier (HiKey)Tested-by: Volodymyr Babchuk (RCAR H3)Tested-by: Scott Branden Reviewed-by: Javier González Signed-off-by: Jens Wiklander List of files: /linux-6.15/drivers/tee/Makefile