0001 What: /sys/bus/platform/devices/INTC1092:00/intc_reg
0002 Date: August 2021
0003 KernelVersion: 5.15
0004 Contact: Shravan S <s.shravan@intel.com>,
0005 An Sudhakar <sudhakar.an@intel.com>
0006 Description:
0007 Specific Absorption Rate (SAR) regulatory mode is typically
0008 derived based on information like mcc (Mobile Country Code) and
0009 mnc (Mobile Network Code) that is available for the currently
0010 attached LTE network. A userspace application is required to set
0011 the current SAR regulatory mode on the Dynamic SAR driver using
0012 this sysfs node. Such an application can also read back using
0013 this sysfs node, the currently configured regulatory mode value
0014 from the Dynamic SAR driver.
0015
0016 Acceptable regulatory modes are:
0017 == ====
0018 0 FCC
0019 1 CE
0020 2 ISED
0021 == ====
0022
0023 - The regulatory mode value has one of the above values.
0024 - The default regulatory mode used in the driver is 0.
0025
0026 What: /sys/bus/platform/devices/INTC1092:00/intc_data
0027 Date: August 2021
0028 KernelVersion: 5.15
0029 Contact: Shravan S <s.shravan@intel.com>,
0030 An Sudhakar <sudhakar.an@intel.com>
0031 Description:
0032 This sysfs entry is used to retrieve Dynamic SAR information
0033 emitted/maintained by a BIOS that supports Dynamic SAR.
0034
0035 The retrieved information is in the order given below:
0036 - device_mode
0037 - bandtable_index
0038 - antennatable_index
0039 - sartable_index
0040
0041 The above information is sent as integer values separated
0042 by a single space. This information can then be pushed to a
0043 WWAN modem that uses this to control the transmit signal
0044 level using the Band/Antenna/SAR table index information.
0045 These parameters are derived/decided by aggregating
0046 device-mode like laptop/tablet/clamshell etc. and the
0047 proximity-sensor data available to the embedded controller on
0048 given host. The regulatory mode configured on Dynamic SAR
0049 driver also influences these values.
0050
0051 The userspace applications can poll for changes to this file
0052 using POLLPRI event on file-descriptor (fd) obtained by opening
0053 this sysfs entry. Application can then read this information from
0054 the sysfs node and consume the given information.
