A-Team_Digital_Solutions/android_kernel_motorola_sm6375
Watch
2
0
Fork
You've already forked android_kernel_motorola_sm6375
 0
mirror of https://github.com/BobTheBlinker/android_kernel_motorola_sm6375.git synced 2026-10-28 02:32:09 -04:00
Code Issues Projects Releases Packages Wiki Activity

dt-bindings: devfreq: add support for memory latency QoS voting

Browse source 
Add documentation for the new memory latency QoS voting device
which is supported on some chipsets.

Change-Id: I89b4242b4fd91923031447338e379d2add162038
This commit is contained in:
Amir Vajid 2019-06-24 13:00:02 -07:00 • committed by Gerrit - the friendly Code Review server
commit 8fe9599836
1 changed files with 37 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

37
bindings/devfreq/devfreq-qcom-qoslat.txt Normal file
View file

@ -0,0 +1,37 @@
QCOM Devfreq memory latency QoS voting device
Some Qualcomm Technologies, Inc. (QTI) chipsets have an interface to vote for
a memory latency QoS level. The qcom,devfreq-qoslat represents a device that
votes on this interface to request a particular memory latency QoS level.
Required properties:
- compatible: Must be "qcom,devfreq-qoslat"
- operating-points-v2: A phandle to the OPP v2 table that holds the supported
QoS levels for the particular chipset. Currently, only
OPP values of 0 and 1 are supported.
- mboxes: A phandle to the mailbox used by this device to send
requests to adjust the memory latency QoS level.
Optional properties:
- governor: Initial governor to use for the device.
Default: "powersave"
Example:
qoslat_opp_table: qoslat-opp-table {
compatible = "operating-points-v2";
opp-0 {
opp-hz = /bits/ 64 < 0 >;
};
opp-1 {
opp-hz = /bits/ 64 < 1 >;
};
};
qcom,devfreq-qoslat {
compatible = "qcom,devfreq-qoslat";
governor = "powersave";
operating-points-v2 = <&qoslat_opp_table>;
mboxes = <&qmp_aop 0>;
};