Changes in Makefile

b1992c37 - kbuild: use $(src) instead of $(srctree)/$(src) for source directory

Sat, 27 Apr 2024 14:55:02 +0000

kbuild: use $(src) instead of $(srctree)/$(src) for source directoryKbuild conventionally uses $(obj)/ for generated files, and $(src)/ forchecked-in source files. It is merely a convention without any functionaldifference. In fact, $(obj) and $(src) are exactly the same, as definedin scripts/Makefile.build: src := $(obj)When the kernel is built in a separate output directory, $(src) doesnot accurately reflect the source directory location. While Kbuildresolves this discrepancy by specifying VPATH=$(srctree) to search forsource files, it does not cover all cases. For example, when adding aheader search path for local headers, -I$(srctree)/$(src) is typicallypassed to the compiler.This introduces inconsistency between upstream and downstream Makefilesbecause $(src) is used instead of $(srctree)/$(src) for the latter.To address this inconsistency, this commit changes the semantics of$(src) so that it always points to the directory in the source tree.Going forward, the variables used in Makefiles will have the followingmeanings: $(obj) - directory in the object tree $(src) - directory in the source tree (changed by this commit) $(objtree) - the top of the kernel object tree $(srctree) - the top of the kernel source treeConsequently, $(srctree)/$(src) in upstream Makefiles need to be replacedwith $(src).Signed-off-by: Masahiro Yamada Reviewed-by: Nicolas Schier List of files: /linux-6.15/drivers/hid/intel-ish-hid/Makefile

579a267e - HID: intel-ish-hid: Implement loading firmware from host feature

Mon, 06 May 2024 01:30:39 +0000

HID: intel-ish-hid: Implement loading firmware from host featureStarting from the Lunar Lake generation, the ISH firmware has beendivided into two components for better space optimization and increasedflexibility. These components include a bootloader that is integratedinto the BIOS, and a main firmware that is stored within the operatingsystem's file system.Introduce support for loading ISH main firmware from host. This feature isapplicable for Lunar Lake and later generation.Current intel-ishtp-loader, is designed for Chrome OS based systems whichuses core boot and has different firmware loading method. For non chromesystems the ISH firmware loading uses different method.Key differences include:1. The new method utilizes ISHTP capability/fixed client to enumerate thefirmware loader function. It does not require a connection or flow control,unlike the method used in Chrome OS, which is enumerated as an ISHTPdynamic client driver, necessitating connect/disconnect operations and flowcontrol.2. The new method employs a table to describe firmware fragments, which aresent to ISH in a single operation. Conversely, the Chrome OS method sendsfirmware fragments in multiple operations within a loop, sending only onefragment at a time.Additionally, address potential error scenarios to ensure graceful failurehandling.- Firmware Not Found: Triggers if request_firmware() fails, leaving ISH in a waiting state. Recovery: Re-insmod the ISH drivers to retry.- DMA Buffer Allocation Failure: Occurs during prepare_dma_bufs(), leading to ISH waiting state. Allocated resources are released. Recovery: Re-insmod the ISH drivers to retry.- Incorrect Firmware Image: Causes ISH to refuse loading after three failed attempts. Recovery: A platform reset is required.Please refer to the [Documentation](Documentation/hid/intel-ish-hid.rst)for the details on flows.Signed-off-by: Zhang Lixu Acked-by: Srinivas Pandruvada Signed-off-by: Jiri Kosina List of files: /linux-6.15/drivers/hid/intel-ish-hid/Makefile

9cc342f6 - treewide: prefix header search paths with $(srctree)/

Mon, 13 May 2019 06:22:16 +0000

treewide: prefix header search paths with $(srctree)/Currently, the Kbuild core manipulates header search paths in a crazyway [1].To fix this mess, I want all Makefiles to add explicit $(srctree)/ tothe search paths in the srctree. Some Makefiles are already written inthat way, but not all. The goal of this work is to make the notationconsistent, and finally get rid of the gross hacks.Having whitespaces after -I does not matter since commit 48f6e3cf5bc6("kbuild: do not drop -I without parameter").[1]: https://patchwork.kernel.org/patch/9632347/Signed-off-by: Masahiro Yamada List of files: /linux-6.15/drivers/hid/intel-ish-hid/Makefile

91b22810 - HID: intel-ish-hid: ISH firmware loader client driver

Tue, 02 Apr 2019 05:47:41 +0000

HID: intel-ish-hid: ISH firmware loader client driverThis driver adds support for loading Intel Integrated Sensor Hub (ISH) firmwarefrom host file system to ISH SRAM and start execution.At power-on, the ISH subsystem shall boot to an interim Shim loader-firmware,which shall expose an ISHTP loader device.The driver implements an ISHTP client that communicates with the Shim ISHTPloader device over the intel-ish-hid stack, to download the main ISH firmware.Signed-off-by: Rushikesh S Kadam Acked-by: Srinivas Pandruvada Acked-by: Nick Crews Tested-by: Jett Rink Signed-off-by: Jiri Kosina List of files: /linux-6.15/drivers/hid/intel-ish-hid/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/hid/intel-ish-hid/Makefile

0b28cb4b - HID: intel-ish-hid: ISH HID client driver

Sun, 07 Aug 2016 09:25:36 +0000

HID: intel-ish-hid: ISH HID client driverThis driver is responsible for implementing ISH HID client, whichgets HID description and report. Once it has completely getsreport descriptors, it registers as a HID LL drivers. This implementsnecessary callbacks so that it can be used by HID sensor hub driver.Original-author: Daniel Drubin Reviewed-and-tested-by: Ooi, Joyce Tested-by: Grant Likely Tested-by: Rann Bar-On Tested-by: Atri Bhattacharya Signed-off-by: Srinivas Pandruvada Signed-off-by: Jiri Kosina List of files: /linux-6.15/drivers/hid/intel-ish-hid/Makefile

ae02e5d4 - HID: intel-ish-hid: ipc layer

Sun, 07 Aug 2016 09:25:35 +0000

HID: intel-ish-hid: ipc layerThis layer is responsible for- Enumerating over PCI bus- Inform FW about host readiness- Provide HW interface to transport layer for control and messages- Interrupt handling and routingOriginal-author: Daniel Drubin Reviewed-and-tested-by: Ooi, Joyce Tested-by: Grant Likely Tested-by: Rann Bar-On Tested-by: Atri Bhattacharya Signed-off-by: Srinivas Pandruvada Signed-off-by: Jiri Kosina List of files: /linux-6.15/drivers/hid/intel-ish-hid/Makefile

3703f53b - HID: intel_ish-hid: ISH Transport layer

Sun, 07 Aug 2016 09:25:34 +0000

HID: intel_ish-hid: ISH Transport layerThe ISH transport layer (ishtp) is a bi-directional protocol implementedon the top of PCI based inter processor communication layer. This layeroffers:- Connection management- Flow control with the firmware- Multiple client sessions- Client message transfer- Client message reception- DMA for RX and TX for fast data transferRefer to Documentation/hid/intel-ish-hid.txt foroverview of the functionality implemented in this layer.Original-author: Daniel Drubin Reviewed-and-tested-by: Ooi, Joyce Tested-by: Grant Likely Tested-by: Rann Bar-On Tested-by: Atri Bhattacharya Signed-off-by: Srinivas Pandruvada Signed-off-by: Jiri Kosina List of files: /linux-6.15/drivers/hid/intel-ish-hid/Makefile