Changes in Makefile

386a766c - mei: Add MEI hardware support for IVSC device

Mon, 04 Dec 2023 00:55:44 +0000

mei: Add MEI hardware support for IVSC deviceThe protocol used for the IVSC device to communicate with HOST is MEI.The MEI hardware interfaces for the IVSC device are implemented.The APIs are exposed by MEI framework to mei clients, e.g. mei_csi andmei_ace.Signed-off-by: Wentong Wu Reviewed-by: Alexander Usyskin Reviewed-by: Sakari Ailus Tested-by: Hao Yao Acked-by: Tomas Winkler Link: https://lore.kernel.org/r/1701651344-20723-3-git-send-email-wentong.wu@intel.comSigned-off-by: Greg Kroah-Hartman List of files: /linux-6.15/drivers/misc/mei/Makefile

566f5ca9 - mei: Add transport driver for IVSC device

Mon, 04 Dec 2023 00:55:43 +0000

mei: Add transport driver for IVSC deviceThe Intel visual sensing controller (IVSC) device is designed to controlthe camera sharing between host IPU for media usage and IVSC for contextsensing (face detection).IVSC is exposed to HOST as an SPI device and the message protocol overthe SPI BUS for communicating with the IVSC device is implemented. Thisis the backend of mei framework for IVSC device, which usually handlesthe hardware data transfer. The mei_csi and mei_ace are the clients ofIVSC mei framework.The firmware downloading for the IVSC device is implemented as well.Signed-off-by: Wentong Wu Reviewed-by: Sakari Ailus Tested-by: Hao Yao Acked-by: Tomas Winkler Link: https://lore.kernel.org/r/1701651344-20723-2-git-send-email-wentong.wu@intel.comSigned-off-by: Greg Kroah-Hartman List of files: /linux-6.15/drivers/misc/mei/Makefile

1dd924f6 - mei: gsc_proxy: add gsc proxy driver

Tue, 02 May 2023 16:38:52 +0000

mei: gsc_proxy: add gsc proxy driverAdd GSC proxy driver. It to allows messaging between GSC componenton Intel graphics card and CSE device.Cc: Alan Previn Signed-off-by: Alexander Usyskin Signed-off-by: Tomas Winkler Signed-off-by: Daniele Ceraolo Spurio Acked-by: Greg Kroah-Hartman Reviewed-by: Alan Previn Link: https://patchwork.freedesktop.org/patch/msgid/20230502163854.317653-3-daniele.ceraolospurio@intel.com List of files: /linux-6.15/drivers/misc/mei/Makefile

a98c30fd - mei: add support for graphics system controller (gsc) devices

Tue, 19 Apr 2022 19:33:09 +0000

mei: add support for graphics system controller (gsc) devicesGSC is a graphics system controller, based on CSE, it providesa chassis controller for graphics discrete cards, as well as itsupports media protection on selected devices.mei_gsc binds to a auxiliary devices exposed by Intel discretedriver i915.v2: fix error check in mei_gsc_probev3: update MODULE_LICENSE ("GPL" is preferred over "GPL v2" and they both map to GPL version 2)Signed-off-by: Alexander Usyskin Signed-off-by: Tomas Winkler Reviewed-by: Daniele Ceraolo Spurio Signed-off-by: Daniele Ceraolo Spurio Acked-by: Rodrigo Vivi #v3Link: https://patchwork.freedesktop.org/patch/msgid/20220419193314.526966-3-daniele.ceraolospurio@intel.com List of files: /linux-6.15/drivers/misc/mei/Makefile

c2004ce9 - mei: pxp: export pavp client to me client bus

Fri, 24 Sep 2021 19:14:37 +0000

mei: pxp: export pavp client to me client busExport PAVP client to work with i915 driver,for binding it uses kernel component framework.v2:drop debug prints, refactor match code to match mei_hdcp (Tomas)Signed-off-by: Vitaly Lubart Signed-off-by: Tomas Winkler Signed-off-by: Daniele Ceraolo Spurio Reviewed-by: Rodrigo Vivi Signed-off-by: Rodrigo Vivi Link: https://patchwork.freedesktop.org/patch/msgid/20210924191452.1539378-3-alan.previn.teres.alexis@intel.com List of files: /linux-6.15/drivers/misc/mei/Makefile

264f53b4 - Revert "mei: virtio: virtualization frontend driver"

Sat, 05 Dec 2020 19:38:46 +0000

Revert "mei: virtio: virtualization frontend driver"This reverts commit d162219c655c8cf8003128a13840d6c1e183fb80.The device uses a VIRTIO device ID out of a not-for-production range.Releasing Linux using an ID out of this range will make it conflict withdevelopment setups. An official request to reserve an ID for an MEIdevice is yet to be submitted to the virtio TC, thus there's no chanceit will be reserved and fixed in time before the next release.Once requested it usually takes 2-3 weeks to land in the spec, whichmeans the device can be supported with the official ID in the next Linuxversion if contributors act quickly.Signed-off-by: Michael S. Tsirkin Cc: Tomas Winkler Cc: Alexander Usyskin Cc: Wang Yu Cc: Liu Shuo Link: https://lore.kernel.org/r/20201205193625.469773-1-mst@redhat.comSigned-off-by: Greg Kroah-Hartman List of files: /linux-6.15/drivers/misc/mei/Makefile

d162219c - mei: virtio: virtualization frontend driver

Tue, 18 Aug 2020 11:51:47 +0000

mei: virtio: virtualization frontend driverThis frontend driver implements MEI hw interface based on virtioframework to let MEI driver work without changes under virtualization.It requires a backend service in the ACRN device-model on the serviceOS side to make it work. The backend service will emulate mei routingand assign vtags for each mei vritio device.The backend service is available in ACRN device-model at github.For more information, please refer to https://projectacrn.orgThe ACRN virtio sub device id for MEI is is 0x8602.Signed-off-by: Tomas Winkler Signed-off-by: Alexander Usyskin Signed-off-by: Wang Yu Signed-off-by: Liu Shuo Link: https://lore.kernel.org/r/20200818115147.2567012-14-tomas.winkler@intel.comSigned-off-by: Greg Kroah-Hartman List of files: /linux-6.15/drivers/misc/mei/Makefile

1e55b609 - mei: adjust the copyright notice in the files.

Mon, 11 Mar 2019 22:10:44 +0000

mei: adjust the copyright notice in the files.Use unified version of the copyright notice in the filesUpdate copyright years according the year the fileswere touched, except this patch and SPDX conversions.Signed-off-by: Tomas Winkler Signed-off-by: Greg Kroah-Hartman List of files: /linux-6.15/drivers/misc/mei/Makefile

64e9bbdd - misc/mei/hdcp: Client driver for HDCP application

Thu, 21 Feb 2019 18:11:56 +0000

misc/mei/hdcp: Client driver for HDCP applicationME FW contributes a vital role in HDCP2.2 authentication.HDCP2.2 driver needs to communicate to ME FW for each step of theHDCP2.2 authentication.ME FW prepare and HDCP2.2 authentication parameters and encrypt themas per spec. With such parameter Driver prepares HDCP2.2 auth messagesand communicate with HDCP2.2 sink.Similarly HDCP2.2 sink's response is shared with ME FW for decrypt andverification.Once All the steps of HDCP2.2 authentications are complete on driver'srequest ME FW will configure the port as authenticated and supply theHDCP keys to the Gen HW for encryption.Only after this stage HDCP2.2 driver can start the HDCP2.2 encryptionfor a port.ME FW is interfaced to kernel through MEI Bus Driver. To obtain theHDCP2.2 services from the ME FW through MEI Bus driver MEI ClientDriver is developed.v2: hdcp files are moved to drivers/misc/mei/hdcp/ [Tomas]v3: Squashed the Kbuild support [Tomas] UUID renamed and Module License is modified [Tomas] drv_data is set to null at remove [Tomas]v4: Module name is changed to "MEI HDCP" I915 Selects the MEI_HDCPv5: Remove redundant text from the License header Fix malformed licence Removed the drv_data resetting.v6: K-Doc addition. [Tomas]v7: %s/UUID_LE/GUID_INIT [Tomas] GPL Ver is 2.0 than 2.0+ [Tomas]v8: Added more info into Kconfig addition [Tomas]Signed-off-by: Ramalingam C Signed-off-by: Tomas Winkler Acked-by: Tomas Winkler Signed-off-by: Daniel Vetter Link: https://patchwork.freedesktop.org/patch/msgid/1550772730-23280-3-git-send-email-ramalingam.c@intel.com List of files: /linux-6.15/drivers/misc/mei/Makefile

ce0925e8 - mei: dma ring buffers allocation

Thu, 22 Nov 2018 11:11:36 +0000

mei: dma ring buffers allocationAllocate DMA ring buffers from managed coherent memory.Signed-off-by: Tomas Winkler Signed-off-by: Alexander Usyskin Signed-off-by: Greg Kroah-Hartman List of files: /linux-6.15/drivers/misc/mei/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/misc/mei/Makefile

394a77d0 - mei: drop amthif internal client

Mon, 20 Mar 2017 13:04:03 +0000

mei: drop amthif internal clientAMTHIF has special support in the mei drive, it handles multiplexingmultiple user space connection above single me client connection.Since there is no additional addressing information there is a strictrequirement on the traffic order on each connection and on the "readafter write" order within the connection. This creates a lot ofcomplexity mostly because the other client types do not necessarily fallunder the same restriction. After carefully studying the use of theAMTHIF client, we came to conclusion that the multiplexing is not reallyutilized by any application and we may safely remove that support andsignificantly simplify the driver.Signed-off-by: Alexander Usyskin Signed-off-by: Tomas Winkler Signed-off-by: Greg Kroah-Hartman List of files: /linux-6.15/drivers/misc/mei/Makefile

fdd9b865 - mei: wd: drop the watchdog code from the core mei driver

Thu, 07 Jan 2016 22:49:21 +0000

mei: wd: drop the watchdog code from the core mei driverInstead of integrating the iAMT watchdog in the mei core driverwe will create a watchdog device on the mei client bus andcreate a driver for it.This patch removes the watchdog code from the mei core driver.Signed-off-by: Alexander Usyskin Signed-off-by: Tomas Winkler Signed-off-by: Greg Kroah-Hartman List of files: /linux-6.15/drivers/misc/mei/Makefile

a0a785c4 - mei: bus: rename nfc.c to bus-fixup.c

Thu, 23 Jul 2015 12:08:34 +0000

mei: bus: rename nfc.c to bus-fixup.cThe bus-fixup.c will be a place for fixups and quirksfor all types of me client devices.As for now it contians only the fixup for settingthe nfc device name on the me client bus.Signed-off-by: Tomas Winkler Signed-off-by: Greg Kroah-Hartman List of files: /linux-6.15/drivers/misc/mei/Makefile

a0a927d0 - mei: me: add io register tracing

Tue, 10 Feb 2015 08:39:33 +0000

mei: me: add io register tracingTo make debugging a bit easier we add me registeraccess tracing/tracing/events/mei/mei_reg_{read,write}Signed-off-by: Tomas Winkler Signed-off-by: Greg Kroah-Hartman List of files: /linux-6.15/drivers/misc/mei/Makefile

92ab5130 - mei: txe: add Kbuild for TXE device

Wed, 15 Jan 2014 22:58:36 +0000

mei: txe: add Kbuild for TXE deviceSigned-off-by: Tomas Winkler Signed-off-by: Greg Kroah-Hartman List of files: /linux-6.15/drivers/misc/mei/Makefile

59fcd7c6 - mei: nfc: Initial nfc implementation

Thu, 11 Apr 2013 01:03:29 +0000

mei: nfc: Initial nfc implementationNFC ME device is exported through the MEI bus to be consumed by theNFC subsystem.NFC is represented by two mei clients: An info one and the actualNFC one. In order to properly build the ME id we first need to retrievethe firmware information from the info client and then disconnect from it.Signed-off-by: Samuel Ortiz Signed-off-by: Tomas Winkler Signed-off-by: Greg Kroah-Hartman List of files: /linux-6.15/drivers/misc/mei/Makefile

30e53bb8 - mei: add debugfs hooks

Fri, 05 Apr 2013 19:10:34 +0000

mei: add debugfs hooksdebugfs exposes device state and list of me clients and theirpropertiesSigned-off-by: Tomas Winkler Signed-off-by: Greg Kroah-Hartman List of files: /linux-6.15/drivers/misc/mei/Makefile

e5354107 - mei: bus: Initial MEI Client bus type implementation

Wed, 27 Mar 2013 15:29:53 +0000

mei: bus: Initial MEI Client bus type implementationmei client bus will present some of the mei clientsas devices for other standard subsystemsImplement the probe, remove, match, device addtion routines, along withthe sysfs and uevent ones. mei_cl_device_id is also added tomod_devicetable.hA mei-cleint-bus.txt document describing the rationale and the API usageis also added while ABI/testing/sysfs-bus-mei describeis the modalias ABI.Signed-off-by: Samuel Ortiz Signed-off-by: Tomas Winkler Signed-off-by: Greg Kroah-Hartman List of files: /linux-6.15/drivers/misc/mei/Makefile

40e0b67b - mei: move mei-me to separate module

Wed, 27 Mar 2013 14:58:30 +0000

mei: move mei-me to separate modulemei layer provides host bus message layer, client management,and os interfacemei-me - provides access to ME hardware throughthe pci busSigned-off-by: Tomas Winkler Signed-off-by: Greg Kroah-Hartman List of files: /linux-6.15/drivers/misc/mei/Makefile