GNUBoot
/
coreboot-kgpe-d16
2
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Documentation/drivers/dptf: Add oem variables support 

Add oem variables information with usage example.

BRANCH=None
BUG=b:187253038
TEST=Built and tested on dedede board

Change-Id: I45db17f6ee3328da28f985c6854d65a430c9c61b
Signed-off-by: Sumeet Pawnikar <sumeet.r.pawnikar@intel.com>
Reviewed-on: https://review.coreboot.org/c/coreboot/+/55846
Tested-by: build bot (Jenkins) <no-reply@coreboot.org>
Reviewed-by: Tim Wawrzynczak <twawrzynczak@chromium.org>
This commit is contained in:
Sumeet Pawnikar 2021-06-25 20:13:05 +05:30 committed by Felix Held
parent 681a59d5c3
commit 590eb2bb9c
1 changed files with 16 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

16
Documentation/drivers/dptf.md
View File

@ -311,3 +311,19 @@ table for a given temperature threshold.
1) Hysteresis - The amount of hysteresis implemented in either circuitry or 1) Hysteresis - The amount of hysteresis implemented in either circuitry or
the firmware that reads the temperature sensor (in degrees C). the firmware that reads the temperature sensor (in degrees C).
2) Name - This name is applied to the _STR property of the sensor 2) Name - This name is applied to the _STR property of the sensor
## OEM Variables
Platform vendors can define an array of OEM-specific values as OEM variables
to be used under DPTF policy. There are total six OEM variables available.
These can be used in AP policy for more specific actions. These OEM variables
can be defined as below mentioned example and can be used any variable between
[0], [1],...,[5]. Platform vendors can enable and use this for specific platform
by defining OEM variables macro under board variant.
Example:
```C
register "oem_data.oem_variables" = "{
[1] = 0x6,
[3] = 0x1
}"
```