<?xml version="1.0"?>
<?xml-stylesheet type="text/xsl" href="/rss.xsl.xml"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/">
<channel>
    <title>Changes in Makefile</title>
    <description></description>
    <language>en</language>
    <copyright>Copyright 2015</copyright>
    <generator>Java</generator><item>
        <title>787c80cc - optee: separate notification functions</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/tee/optee/Makefile#787c80cc</link>
        <description>optee: separate notification functionsRenames struct optee_wait_queue to struct optee_notif and all relatedfunctions to optee_notif_*().The implementation is changed to allow sending a notification from anatomic state, that is from the top half of an interrupt handler.Waiting for keys is currently only used when secure world is waiting fora mutex or condition variable. The old implementation could handle any32-bit key while this new implementation is restricted to only 8 bits orthe maximum value 255. A upper value is needed since a bitmap isallocated to allow an interrupt handler to only set a bit in case thewaiter hasn&apos;t had the time yet to allocate and register a completion.The keys are currently only representing secure world threads whichnumber usually are never even close to 255 so it should be safe for now.In future ABI updates the maximum value of the key will be communicatedwhile the driver is initializing.Reviewed-by: Sumit Garg &lt;sumit.garg@linaro.org&gt;Signed-off-by: Jens Wiklander &lt;jens.wiklander@linaro.org&gt;

            List of files:
            /linux-6.15/drivers/tee/optee/Makefile</description>
        <pubDate>Tue, 15 Jun 2021 20:23:53 +0000</pubDate>
        <dc:creator>Jens Wiklander &lt;jens.wiklander@linaro.org&gt;</dc:creator>
    </item>
<item>
        <title>4615e5a3 - optee: add FF-A support</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/tee/optee/Makefile#4615e5a3</link>
        <description>optee: add FF-A supportAdds support for using FF-A [1] as transport to the OP-TEE driver.Introduces struct optee_msg_param_fmem which carries all informationneeded when OP-TEE is calling FFA_MEM_RETRIEVE_REQ to get the sharedmemory reference mapped by the hypervisor in S-EL2. Register usage isalso updated to include the information needed.The FF-A part of this driver is enabled if CONFIG_ARM_FFA_TRANSPORT isenabled.[1] https://developer.arm.com/documentation/den0077/latestAcked-by: Sumit Garg &lt;sumit.garg@linaro.org&gt;Signed-off-by: Jens Wiklander &lt;jens.wiklander@linaro.org&gt;

            List of files:
            /linux-6.15/drivers/tee/optee/Makefile</description>
        <pubDate>Wed, 21 Jul 2021 15:45:21 +0000</pubDate>
        <dc:creator>Jens Wiklander &lt;jens.wiklander@linaro.org&gt;</dc:creator>
    </item>
<item>
        <title>c51a564a - optee: isolate smc abi</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/tee/optee/Makefile#c51a564a</link>
        <description>optee: isolate smc abiIsolate the ABI based on raw SMCs. Code specific to the raw SMC ABI ismoved into smc_abi.c. This makes room for other ABIs with a clearseparation.The driver changes to use module_init()/module_exit() instead ofmodule_platform_driver(). The platform_driver_register() andplatform_driver_unregister() functions called directly to keep the samebehavior. This is needed because module_platform_driver() is based onmodule_driver() which can only be used once in a module.A function optee_rpc_cmd() is factored out from the functionhandle_rpc_func_cmd() to handle the ABI independent part of RPCprocessing.This patch is not supposed to change the driver behavior, it&apos;s only amatter of reorganizing the code.Reviewed-by: Sumit Garg &lt;sumit.garg@linaro.org&gt;Signed-off-by: Jens Wiklander &lt;jens.wiklander@linaro.org&gt;

            List of files:
            /linux-6.15/drivers/tee/optee/Makefile</description>
        <pubDate>Wed, 21 Jul 2021 14:30:28 +0000</pubDate>
        <dc:creator>Jens Wiklander &lt;jens.wiklander@linaro.org&gt;</dc:creator>
    </item>
<item>
        <title>7ccdcaac - tee: optee: fix build error caused by recent optee tracepoints feature</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/tee/optee/Makefile#7ccdcaac</link>
        <description>tee: optee: fix build error caused by recent optee tracepoints featureIf build kernel without &quot;O=dir&quot;, below error will be seen:In file included from drivers/tee/optee/optee_trace.h:67,                 from drivers/tee/optee/call.c:18:./include/trace/define_trace.h:95:42: fatal error: ./optee_trace.h: No such file or directory   95 | #include TRACE_INCLUDE(TRACE_INCLUDE_FILE)      |                                          ^compilation terminated.Fix it by adding below line to Makefile:CFLAGS_call.o := -I$(src)Tested with and without &quot;O=dir&quot;, both can build successfully.Fixes: 0101947dbcc3 (&quot;tee: optee: add invoke_fn tracepoints&quot;)Tested-by: Heiko Thiery &lt;heiko.thiery@gmail.com&gt;Tested-by: Guenter Roeck &lt;linux@roeck-us.net&gt;Reported-by: Guenter Roeck &lt;linux@roeck-us.net&gt;Suggested-by: Steven Rostedt &lt;rostedt@goodmis.org&gt;Signed-off-by: Jisheng Zhang &lt;Jisheng.Zhang@synaptics.com&gt;Signed-off-by: Jens Wiklander &lt;jens.wiklander@linaro.org&gt;

            List of files:
            /linux-6.15/drivers/tee/optee/Makefile</description>
        <pubDate>Thu, 25 Mar 2021 04:06:01 +0000</pubDate>
        <dc:creator>Jisheng Zhang &lt;Jisheng.Zhang@synaptics.com&gt;</dc:creator>
    </item>
<item>
        <title>c3fa24af - tee: optee: add TEE bus device enumeration support</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/tee/optee/Makefile#c3fa24af</link>
        <description>tee: optee: add TEE bus device enumeration supportOP-TEE provides a pseudo TA to enumerate TAs which can act as devices/services for TEE bus. So implement device enumeration using invokefunction: PTA_CMD_GET_DEVICES provided by pseudo TA to fetch array ofdevice UUIDs. Also register these enumerated devices with TEE bus as&quot;optee-clntX&quot; device.Signed-off-by: Sumit Garg &lt;sumit.garg@linaro.org&gt;Reviewed-by: Daniel Thompson &lt;daniel.thompson@linaro.org&gt;[jw: fix optee_enumerate_devices() with no devices found]Signed-off-by: Jens Wiklander &lt;jens.wiklander@linaro.org&gt;

            List of files:
            /linux-6.15/drivers/tee/optee/Makefile</description>
        <pubDate>Tue, 29 Jan 2019 05:49:37 +0000</pubDate>
        <dc:creator>Sumit Garg &lt;sumit.garg@linaro.org&gt;</dc:creator>
    </item>
<item>
        <title>abd135ba - tee: optee: add optee-specific shared pool implementation</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/tee/optee/Makefile#abd135ba</link>
        <description>tee: optee: add optee-specific shared pool implementationThis is simple pool that uses kernel page allocator. This pool can beused in case OP-TEE supports dynamic shared memory.Signed-off-by: Volodymyr Babchuk &lt;vlad.babchuk@gmail.com&gt;Signed-off-by: Jens Wiklander &lt;jens.wiklander@linaro.org&gt;

            List of files:
            /linux-6.15/drivers/tee/optee/Makefile</description>
        <pubDate>Wed, 29 Nov 2017 12:48:35 +0000</pubDate>
        <dc:creator>Volodymyr Babchuk &lt;vlad.babchuk@gmail.com&gt;</dc:creator>
    </item>
<item>
        <title>b2441318 - License cleanup: add SPDX GPL-2.0 license identifier to files with no license</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/tee/optee/Makefile#b2441318</link>
        <description>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 &apos;GPL-2.0&apos;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 &amp; 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 &gt;5   lines of source - File already had some variant of a license header in it (even if &lt;5   lines).All documentation files were explicitly excluded.The following heuristics were used to determine which SPDX licenseidentifiers to apply. - when both scanners couldn&apos;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 &quot;GPL-2.0 WITH   Linux-syscall-note&quot; otherwise it was &quot;GPL-2.0&quot;.  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&apos;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 &lt;kstewart@linuxfoundation.org&gt;Reviewed-by: Philippe Ombredanne &lt;pombredanne@nexb.com&gt;Reviewed-by: Thomas Gleixner &lt;tglx@linutronix.de&gt;Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

            List of files:
            /linux-6.15/drivers/tee/optee/Makefile</description>
        <pubDate>Wed, 01 Nov 2017 14:07:57 +0000</pubDate>
        <dc:creator>Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;</dc:creator>
    </item>
<item>
        <title>4fb0a5eb - tee: add OP-TEE driver</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/tee/optee/Makefile#4fb0a5eb</link>
        <description>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 &lt;dannenberg@ti.com&gt;Tested-by: Jerome Forissier &lt;jerome.forissier@linaro.org&gt; (HiKey)Tested-by: Volodymyr Babchuk &lt;vlad.babchuk@gmail.com&gt; (RCAR H3)Tested-by: Scott Branden &lt;scott.branden@broadcom.com&gt;Reviewed-by: Javier Gonz&#225;lez &lt;javier@javigon.com&gt;Signed-off-by: Jens Wiklander &lt;jens.wiklander@linaro.org&gt;

            List of files:
            /linux-6.15/drivers/tee/optee/Makefile</description>
        <pubDate>Tue, 14 Apr 2015 12:33:20 +0000</pubDate>
        <dc:creator>Jens Wiklander &lt;jens.wiklander@linaro.org&gt;</dc:creator>
    </item>
</channel>
</rss>
