qiurui
/
Centos-kernel-stream-9
mirror of https://gitlab.com/redhat/centos-stream/src/kernel/centos-stream-9.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
Centos-kernel-stream-9/drivers/platform/x86/intel/Makefile

26 lines
741 B
Makefile
Raw Normal View History

platform/x86: intel_skl_int3472: Move to intel/ subfolder Start collecting Intel x86 related drivers in its own subfolder. Move intel_skl_int3472 first. Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com> Link: https://lore.kernel.org/r/20210618125516.53510-7-andriy.shevchenko@linux.intel.com Signed-off-by: Hans de Goede <hdegoede@redhat.com>
2021-06-18 12:55:15 +00:00
# SPDX-License-Identifier: GPL-2.0
#
# Makefile for drivers/platform/x86/intel
# Intel x86 Platform-Specific Drivers
#
platform/x86/intel/ifs: Add stub driver for In-Field Scan Bugzilla: https://bugzilla.redhat.com/1971938 commit 67896ef13c4db88082a914e96d958044cd3392e8 Author: Tony Luck <tony.luck@intel.com> Date: Fri May 6 15:54:02 2022 -0700 platform/x86/intel/ifs: Add stub driver for In-Field Scan Cloud Service Providers that operate fleets of servers have reported [1] occasions where they can detect that a CPU has gone bad due to effects like electromigration, or isolated manufacturing defects. However, that detection method is A/B testing seemingly random application failures looking for a pattern. In-Field Scan (IFS) is a driver for a platform capability to load a crafted 'scan image' to run targeted low level diagnostics outside of the CPU's architectural error detection capabilities. Stub version of driver just does initial part of check for the IFS feature. MSR_IA32_CORE_CAPS must enumerate the presence of the MSR_INTEGRITY_CAPS MSR. [1]: https://www.youtube.com/watch?v=QMF3rqhjYuM Reviewed-by: Dan Williams <dan.j.williams@intel.com> Signed-off-by: Tony Luck <tony.luck@intel.com> Acked-by: Hans de Goede <hdegoede@redhat.com> Reviewed-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org> Reviewed-by: Thomas Gleixner <tglx@linutronix.de> Link: https://lore.kernel.org/r/20220506225410.1652287-5-tony.luck@intel.com Signed-off-by: Hans de Goede <hdegoede@redhat.com> Signed-off-by: David Arcari <darcari@redhat.com>
2022-08-10 17:50:59 +00:00
obj-$(CONFIG_INTEL_IFS) += ifs/
platform/x86: BIOS SAR driver for Intel M.2 Modem Bugzilla: https://bugzilla.redhat.com/2123542 Conflicts: - drivers/platform/x86/intel/Kconfig - drivers/platform/x86/intel/Makefile context diff because 67896ef13c4db was already applied commit dcfbd31ef4bcf6ceb373911faa4a5299e0547702 Author: Shravan S <s.shravan@intel.com> Date: Sat Jul 24 02:44:52 2021 +0530 platform/x86: BIOS SAR driver for Intel M.2 Modem Dynamic BIOS SAR driver exposing dynamic SAR information from BIOS The Dynamic SAR (Specific Absorption Rate) driver uses ACPI DSM (Device Specific Method) to communicate with BIOS and retrieve dynamic SAR information and change notifications. The driver uses sysfs to expose this data to userspace via read and notify. Sysfs interface is documented in detail under: Documentation/ABI/testing/sysfs-driver-intc_sar Signed-off-by: Shravan S <s.shravan@intel.com> Link: https://lore.kernel.org/r/20210723211452.27995-2-s.shravan@intel.com Reviewed-by: Hans de Goede <hdegoede@redhat.com> Signed-off-by: Hans de Goede <hdegoede@redhat.com> Signed-off-by: Jose Ignacio Tornos Martinez <jtornosm@redhat.com>
2023-07-10 15:56:00 +00:00
obj-$(CONFIG_INTEL_SAR_INT1092) += int1092/
platform/x86: intel_cht_int33fe: Move to its own subfolder Since we have started collecting Intel x86 specific drivers in their own folder, move intel_cht_int33fe to its own subfolder there. Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com> Link: https://lore.kernel.org/r/20210618125516.53510-8-andriy.shevchenko@linux.intel.com Signed-off-by: Hans de Goede <hdegoede@redhat.com>
2021-06-18 12:55:16 +00:00
obj-$(CONFIG_INTEL_CHT_INT33FE) += int33fe/
platform/x86: intel_skl_int3472: Move to intel/ subfolder Start collecting Intel x86 related drivers in its own subfolder. Move intel_skl_int3472 first. Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com> Link: https://lore.kernel.org/r/20210618125516.53510-7-andriy.shevchenko@linux.intel.com Signed-off-by: Hans de Goede <hdegoede@redhat.com>
2021-06-18 12:55:15 +00:00
obj-$(CONFIG_INTEL_SKL_INT3472) += int3472/
platform/x86: intel_pmc_core: Move to intel sub-directory Bugzilla: http://bugzilla.redhat.com/2007707 commit fa082a7cf5a66a42a06da048afd972e2cc1b67ea Author: Kate Hsuan <hpa@redhat.com> Date: Fri Aug 20 14:04:44 2021 +0300 platform/x86: intel_pmc_core: Move to intel sub-directory Move Intel PMC core driver to intel sub-directory to improve readability. Signed-off-by: Kate Hsuan <hpa@redhat.com> Reviewed-by: Hans de Goede <hdegoede@redhat.com> Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com> Reviewed-by: Rajneesh Bhardwaj <irenic.rajneesh@gmail.com> Link: https://lore.kernel.org/r/20210820110458.73018-7-andriy.shevchenko@linux.intel.com Signed-off-by: Hans de Goede <hdegoede@redhat.com> Signed-off-by: David Arcari <darcari@redhat.com>
2021-09-24 14:15:42 +00:00
obj-$(CONFIG_INTEL_PMC_CORE) += pmc/
platform/x86/intel: Move Intel PMT drivers to new subfolder Bugzilla: https://bugzilla.redhat.com/2058806 commit e184b1e589a7fbb80bfdd0364c11422999a17a26 Author: David E. Box <david.e.box@linux.intel.com> Date: Tue Jul 27 09:49:28 2021 -0700 platform/x86/intel: Move Intel PMT drivers to new subfolder Move all Intel Platform Monitoring Technology drivers to drivers/platform/x86/intel/pmt. Signed-off-by: David E. Box <david.e.box@linux.intel.com> Reviewed-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com> Link: https://lore.kernel.org/r/20210727164928.3171521-1-david.e.box@linux.intel.com Signed-off-by: Hans de Goede <hdegoede@redhat.com> Signed-off-by: David Arcari <darcari@redhat.com>
2022-03-15 14:57:45 +00:00
obj-$(CONFIG_INTEL_PMT_CLASS) += pmt/
platform/x86: intel_speed_select_if: Move to intel sub-directory Bugzilla: https://bugzilla.redhat.com/2040063 commit 6b1e482898e841b577d1d22b97fb65ac8ffacd9a Author: Kate Hsuan <hpa@redhat.com> Date: Fri Aug 20 14:04:51 2021 +0300 platform/x86: intel_speed_select_if: Move to intel sub-directory Move Intel Speed Select interface driver to intel sub-directory to improve readability and rename it from intel_speed_select_if to speed_select_if. Signed-off-by: Kate Hsuan <hpa@redhat.com> Reviewed-by: Hans de Goede <hdegoede@redhat.com> Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com> Link: https://lore.kernel.org/r/20210820110458.73018-14-andriy.shevchenko@linux.intel.com Signed-off-by: Hans de Goede <hdegoede@redhat.com> Signed-off-by: David Arcari <darcari@redhat.com> v2: rebase due to conflicts
2022-03-25 19:53:16 +00:00
obj-$(CONFIG_INTEL_SPEED_SELECT_INTERFACE) += speed_select_if/
platform/x86: Add Intel Software Defined Silicon driver Bugzilla: https://bugzilla.redhat.com/1971952 commit 2546c60004309ede8e2d1d5341e0decd90e057bf Author: David E. Box <david.e.box@linux.intel.com> Date: Fri Feb 11 17:32:50 2022 -0800 platform/x86: Add Intel Software Defined Silicon driver Intel Software Defined Silicon (SDSi) is a post manufacturing mechanism for activating additional silicon features. Features are enabled through a license activation process. The SDSi driver provides a per socket, sysfs attribute interface for applications to perform 3 main provisioning functions: 1. Provision an Authentication Key Certificate (AKC), a key written to internal NVRAM that is used to authenticate a capability specific activation payload. 2. Provision a Capability Activation Payload (CAP), a token authenticated using the AKC and applied to the CPU configuration to activate a new feature. 3. Read the SDSi State Certificate, containing the CPU configuration state. The operations perform function specific mailbox commands that forward the requests to SDSi hardware to perform authentication of the payloads and enable the silicon configuration (to be made available after power cycling). The SDSi device itself is enumerated as an auxiliary device from the intel_vsec driver and as such has a build dependency on CONFIG_INTEL_VSEC. Link: https://github.com/intel/intel-sdsi Signed-off-by: David E. Box <david.e.box@linux.intel.com> Reviewed-by: Mark Gross <markgross@kernel.org> Link: https://lore.kernel.org/r/20220212013252.1293396-2-david.e.box@linux.intel.com Reviewed-by: Hans de Goede <hdegoede@redhat.com> Signed-off-by: Hans de Goede <hdegoede@redhat.com> Signed-off-by: David Arcari <darcari@redhat.com>
2022-04-05 13:39:19 +00:00
intel_sdsi-y := sdsi.o
obj-$(CONFIG_INTEL_SDSI) += intel_sdsi.o
platform/x86/intel: Move intel_pmt from MFD to Auxiliary Bus Bugzilla: https://bugzilla.redhat.com/2058806 commit a3c8f906ed5fc1d4895b5e1a5c6ad6e942d6c0ca Author: David E. Box <david.e.box@linux.intel.com> Date: Tue Dec 7 17:50:12 2021 -0800 platform/x86/intel: Move intel_pmt from MFD to Auxiliary Bus Intel Platform Monitoring Technology (PMT) support is indicated by presence of an Intel defined PCIe Designated Vendor Specific Extended Capabilities (DVSEC) structure with a PMT specific ID. The current MFD implementation creates child devices for each PMT feature, currently telemetry, watcher, and crashlog. However DVSEC structures may also be used by Intel to indicate support for other features. The Out Of Band Management Services Module (OOBMSM) uses DVSEC to enumerate several features, including PMT. In order to support them it is necessary to modify the intel_pmt driver to handle the creation of the child devices more generically. To that end, modify the driver to create child devices for any VSEC/DVSEC features on supported devices (indicated by PCI ID). Additionally, move the implementation from MFD to the Auxiliary bus. VSEC/DVSEC features are really multifunctional PCI devices, not platform devices as MFD was designed for. Auxiliary bus gives more flexibility by allowing the definition of custom structures that can be shared between associated auxiliary devices and the parent device. Also, rename the driver from intel_pmt to intel_vsec to better reflect the purpose. This series also removes the current runtime pm support which was not complete to begin with. None of the current devices require runtime pm. However the support will be replaced when a device is added that requires it. Reviewed-by: Mark Gross <markgross@kernel.org> Acked-by: Hans de Goede <hdegoede@redhat.com> Signed-off-by: David E. Box <david.e.box@linux.intel.com> Link: https://lore.kernel.org/r/20211208015015.891275-4-david.e.box@linux.intel.com Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org> Signed-off-by: David Arcari <darcari@redhat.com>
2022-03-15 15:01:15 +00:00
intel_vsec-y := vsec.o
obj-$(CONFIG_INTEL_VSEC) += intel_vsec.o
platform/x86: Add Intel ishtp eclite driver ``` Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1921376 Brew: https://brewweb.engineering.redhat.com/brew/taskinfo?taskID=45226519 Upstream status: v5.18-rc6 Conflicts: . Partical backport, only those hunks needed to support ishtp_eclite, ergo the diffs in drivers/platform/x86/intel/Kconfig. . This commit is the initial commit of ishtp_eclite.c, so later commits in this series will update it to look like the current upstream commit bf9167a8b40c9. commit 7b6bf51de9746b43ec56567a0297378cd0172946 Author: K Naduvalath, Sumesh <sumesh.k.naduvalath@intel.com> Date: Mon Sep 13 10:40:56 2021 +0530 platform/x86: Add Intel ishtp eclite driver This driver is for accessing the PSE (Programmable Service Engine) - an Embedded Controller like IP - using ISHTP (Integratd Sensor Hub Transport Protocol) to get battery, thermal and UCSI (USB Type-C Connector System Software Interface) related data from the platform. Signed-off-by: K Naduvalath, Sumesh <sumesh.k.naduvalath@intel.com> Reviewed-by: Mark Gross <mgross@linux.intel.com> Link: https://lore.kernel.org/r/20210913051056.28736-1-sumesh.k.naduvalath@intel.com Reviewed-by: Hans de Goede <hdegoede@redhat.com> Signed-off-by: Hans de Goede <hdegoede@redhat.com> Signed-off-by: Tony Camuso <tcamuso@redhat.com>
2022-05-11 14:00:55 +00:00
platform/x86/intel: Intel TPMI enumeration driver Bugzilla: https://bugzilla.redhat.com/2177011 commit 47731fd2865fcbcd0b9cdbe90fcd6583c9559631 Author: Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com> Date: Wed Feb 1 17:07:35 2023 -0800 platform/x86/intel: Intel TPMI enumeration driver The TPMI (Topology Aware Register and PM Capsule Interface) provides a flexible, extendable and PCIe enumerable MMIO interface for PM features. For example Intel RAPL (Running Average Power Limit) provides a MMIO interface using TPMI. This has advantage over traditional MSR (Model Specific Register) interface, where a thread needs to be scheduled on the target CPU to read or write. Also the RAPL features vary between CPU models, and hence lot of model specific code. Here TPMI provides an architectural interface by providing hierarchical tables and fields, which will not need any model specific implementation. The TPMI interface uses a PCI VSEC structure to expose the location of MMIO region. This VSEC structure is present in the PCI configuration space of the Intel Out-of-Band (OOB) device, which is handled by the Intel VSEC driver. The Intel VSEC driver parses VSEC structures present in the PCI configuration space of the given device and creates an auxiliary device object for each of them. In particular, it creates an auxiliary device object representing TPMI that can be bound by an auxiliary driver. Introduce a TPMI driver that will bind to the TPMI auxiliary device object created by the Intel VSEC driver. The TPMI specification defines a PFS (PM Feature Structure) table. This table is present in the TPMI MMIO region. The starting address of PFS is derived from the tBIR (Bar Indicator Register) and "Address" field from the VSEC header. Each TPMI PM feature has one entry in the PFS with a unique TPMI ID and its access details. The TPMI driver creates device nodes for the supported PM features. The names of the devices created by the TPMI driver start with the "intel_vsec.tpmi-" prefix which is followed by a specific name of the given PM feature (for example, "intel_vsec.tpmi-rapl.0"). The device nodes are create by using interface "intel_vsec_add_aux()" provided by the Intel VSEC driver. Signed-off-by: Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com> Reviewed-by: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com> Acked-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com> Link: https://lore.kernel.org/r/20230202010738.2186174-5-srinivas.pandruvada@linux.intel.com Reviewed-by: Hans de Goede <hdegoede@redhat.com> Signed-off-by: Hans de Goede <hdegoede@redhat.com> Signed-off-by: David Arcari <darcari@redhat.com>
2023-09-05 17:46:41 +00:00
# TPMI drivers
intel_vsec_tpmi-y := tpmi.o
obj-$(CONFIG_INTEL_TPMI) += intel_vsec_tpmi.o
platform/x86: Add Intel ishtp eclite driver ``` Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1921376 Brew: https://brewweb.engineering.redhat.com/brew/taskinfo?taskID=45226519 Upstream status: v5.18-rc6 Conflicts: . Partical backport, only those hunks needed to support ishtp_eclite, ergo the diffs in drivers/platform/x86/intel/Kconfig. . This commit is the initial commit of ishtp_eclite.c, so later commits in this series will update it to look like the current upstream commit bf9167a8b40c9. commit 7b6bf51de9746b43ec56567a0297378cd0172946 Author: K Naduvalath, Sumesh <sumesh.k.naduvalath@intel.com> Date: Mon Sep 13 10:40:56 2021 +0530 platform/x86: Add Intel ishtp eclite driver This driver is for accessing the PSE (Programmable Service Engine) - an Embedded Controller like IP - using ISHTP (Integratd Sensor Hub Transport Protocol) to get battery, thermal and UCSI (USB Type-C Connector System Software Interface) related data from the platform. Signed-off-by: K Naduvalath, Sumesh <sumesh.k.naduvalath@intel.com> Reviewed-by: Mark Gross <mgross@linux.intel.com> Link: https://lore.kernel.org/r/20210913051056.28736-1-sumesh.k.naduvalath@intel.com Reviewed-by: Hans de Goede <hdegoede@redhat.com> Signed-off-by: Hans de Goede <hdegoede@redhat.com> Signed-off-by: Tony Camuso <tcamuso@redhat.com>
2022-05-11 14:00:55 +00:00
# Intel miscellaneous drivers
obj-$(CONFIG_INTEL_ISHTP_ECLITE) += ishtp_eclite.o