-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge tag 'platform-drivers-x86-v5.15-1' of git://git.kernel.org/pub/…
…scm/linux/kernel/git/pdx86/platform-drivers-x86 Pull x86 platform driver updates from Hans de Goede: "Highlights: - Move all the Intel drivers into their own subdir(s) (mostly Kate's work) - New meraki-mx100 platform driver - Asus WMI driver enhancements, including support for /sys/firmware/acpi/platform_profile - New BIOS SAR driver for Intel M.2 WWAM modems - Alder Lake support for the Intel PMC driver - A whole bunch of cleanups + fixes all over the place" * tag 'platform-drivers-x86-v5.15-1' of git://git.kernel.org/pub/scm/linux/kernel/git/pdx86/platform-drivers-x86: (65 commits) platform/x86: dell-smbios-wmi: Add missing kfree in error-exit from run_smbios_call platform/x86: dell-smbios-wmi: Avoid false-positive memcpy() warning platform/x86: ISST: use semi-colons instead of commas platform/x86: asus-wmi: Fix "unsigned 'retval' is never less than zero" smatch warning platform/x86: asus-wmi: Delete impossible condition platform/x86: hp_accel: Convert to be a platform driver platform/x86: hp_accel: Remove _INI method call platform/mellanox: mlxbf-pmc: fix kernel-doc notation platform/x86/intel: pmc/core: Add GBE Package C10 fix for Alder Lake PCH platform/x86/intel: pmc/core: Add Alder Lake low power mode support for pmc core platform/x86/intel: pmc/core: Add Latency Tolerance Reporting (LTR) support to Alder Lake platform/x86/intel: pmc/core: Add Alderlake support to pmc core driver platform/x86: intel-wmi-thunderbolt: Move to intel sub-directory platform/x86: intel-wmi-sbl-fw-update: Move to intel sub-directory platform/x86: intel-vbtn: Move to intel sub-directory platform/x86: intel_oaktrail: Move to intel sub-directory platform/x86: intel_int0002_vgpio: Move to intel sub-directory platform/x86: intel-hid: Move to intel sub-directory platform/x86: intel_atomisp2: Move to intel sub-directory platform/x86: intel_speed_select_if: Move to intel sub-directory ...
- Loading branch information
Showing
89 changed files
with
2,429 additions
and
636 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,54 @@ | ||
What: /sys/bus/platform/devices/INTC1092:00/intc_reg | ||
Date: August 2021 | ||
KernelVersion: 5.15 | ||
Contact: Shravan S <s.shravan@intel.com>, | ||
An Sudhakar <sudhakar.an@intel.com> | ||
Description: | ||
Specific Absorption Rate (SAR) regulatory mode is typically | ||
derived based on information like mcc (Mobile Country Code) and | ||
mnc (Mobile Network Code) that is available for the currently | ||
attached LTE network. A userspace application is required to set | ||
the current SAR regulatory mode on the Dynamic SAR driver using | ||
this sysfs node. Such an application can also read back using | ||
this sysfs node, the currently configured regulatory mode value | ||
from the Dynamic SAR driver. | ||
|
||
Acceptable regulatory modes are: | ||
== ==== | ||
0 FCC | ||
1 CE | ||
2 ISED | ||
== ==== | ||
|
||
- The regulatory mode value has one of the above values. | ||
- The default regulatory mode used in the driver is 0. | ||
|
||
What: /sys/bus/platform/devices/INTC1092:00/intc_data | ||
Date: August 2021 | ||
KernelVersion: 5.15 | ||
Contact: Shravan S <s.shravan@intel.com>, | ||
An Sudhakar <sudhakar.an@intel.com> | ||
Description: | ||
This sysfs entry is used to retrieve Dynamic SAR information | ||
emitted/maintained by a BIOS that supports Dynamic SAR. | ||
|
||
The retrieved information is in the order given below: | ||
- device_mode | ||
- bandtable_index | ||
- antennatable_index | ||
- sartable_index | ||
|
||
The above information is sent as integer values separated | ||
by a single space. This information can then be pushed to a | ||
WWAN modem that uses this to control the transmit signal | ||
level using the Band/Antenna/SAR table index information. | ||
These parameters are derived/decided by aggregating | ||
device-mode like laptop/tablet/clamshell etc. and the | ||
proximity-sensor data available to the embedded controller on | ||
given host. The regulatory mode configured on Dynamic SAR | ||
driver also influences these values. | ||
|
||
The userspace applications can poll for changes to this file | ||
using POLLPRI event on file-descriptor (fd) obtained by opening | ||
this sysfs entry. Application can then read this information from | ||
the sysfs node and consume the given information. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.