Changes in Kconfig

b9962b69 - ACPI: DPTF: Drop stale link from Kconfig help

Tue, 27 Sep 2022 14:10:31 +0000

ACPI: DPTF: Drop stale link from Kconfig helpThe web site pointed to from the DPTF Kconfig help is not accessibleany more, so drop the link to it from there.Signed-off-by: Rafael J. Wysocki List of files: /linux-6.15/drivers/acpi/dptf/Kconfig

d7a4a85c - ACPI: DPTF: Add ACPI_DPTF Kconfig menu

Thu, 15 Oct 2020 16:59:52 +0000

ACPI: DPTF: Add ACPI_DPTF Kconfig menuAdd a Kconfig menu for Intel DPTF (Dynamic Platform and ThermalFramework), put both the existing participant drivers in it and setthem to be built as modules by default.While at it, do a few assorted cleanups for a good measure.Signed-off-by: Rafael J. Wysocki Reviewed-by: Srinivas Pandruvada Acked-by: Borislav Petkov List of files: /linux-6.15/drivers/acpi/dptf/Kconfig

2ce6324e - ACPI: DPTF: Add PCH FIVR participant driver

Tue, 15 Sep 2020 23:18:14 +0000

ACPI: DPTF: Add PCH FIVR participant driverThis driver adds support for Dynamic Platform and Thermal Framework(DPTF) PCH (Platform Controller Hub) FIVR (Fully Integrated VoltageRegulator) participant support.This participant is responsible for exposing platform telemetry andcontrol for: freq_mhz_high_clock freq_mhz_low_clockThese attributes are used to get and set PCH FIVR switching frequencyfor thermal and radio frequency interference mitigation.Refer to Documentation/ABI/testing/sysfs-platform-dptf for ABI details.ACPI methods description used in this driver:RFC0: This ACPI method to set PCH FIVR switching frequency when FIVRclock is 19.2MHz or 24MHz. The ACPI method takes a DWORD value.GFC0: This ACPI method to get PCH FIVR switching frequency when FIVRclock is 19.2MHz or 24MHz.RFC1: This ACPI method to set PCH FIVR switching frequency when FIVRclock is 38.4MHz. The ACPI method takes a DWORD value.GFC1: This ACPI method to get PCH FIVR switching frequency when FIVRclock is 38.4MHz.Signed-off-by: Srinivas Pandruvada Signed-off-by: Rafael J. Wysocki List of files: /linux-6.15/drivers/acpi/dptf/Kconfig

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/acpi/dptf/Kconfig

6256ebd5 - ACPI / DPTF: Add DPTF power participant driver

Sun, 17 Jul 2016 20:45:32 +0000

ACPI / DPTF: Add DPTF power participant driverThis driver adds support for Dynamic Platform and Thermal Framework(DPTF) Platform Power Participant device (INT3407) support.This participant is responsible for exposing platform telemetry such as: max_platform_power platform_power_source adapter_rating battery_steady_power charger_typeThese attributes are presented via sysfs interface under the INT3407platform device:$ls /sys/bus/platform/devices/INT3407\:00/dptf_power/ adapter_rating_mw battery_steady_power_mw charger_type max_platform_power_mw platform_power_source `ACPI methods description used in this driver: PMAX: Maximum platform power that can be supported by the battery in mW. PSRC: System charge source, 0x00 = DC 0x01 = AC 0x02 = USB 0x03 = Wireless Charger ARTG: Adapter rating in mW (Maximum Adapter power) Must be 0 if no AC adapter is plugged in. CTYP: Charger Type, Traditional : 0x01 Hybrid: 0x02 NVDC: 0x03 PBSS: Returns max sustained power for battery in milliWatts.The INT3407 also contains _BTS and _BIX objects, which are compliant toACPI 5.0, specification. Those objects are already used by ACPI battery(PNP0C0A) driver and information about them is exported via Linux powersupply class registration.Signed-off-by: Srinivas Pandruvada Signed-off-by: Rafael J. Wysocki List of files: /linux-6.15/drivers/acpi/dptf/Kconfig