Lines Matching refs:EM
10 The Energy Model (EM) framework serves as an interface between drivers knowing
19 possible source of information on its own, the EM framework intervenes as an
24 Multiple subsystems might use the EM and it is up to the system integrator to
33 Kernel subsystems might implement automatic detection to check whether EM
34 registered devices have inconsistent scale (based on EM internal flag).
39 approach is applicable to any architecture) providing power costs to the EM
67 In case of CPU devices the EM framework manages power cost tables per
81 CONFIG_ENERGY_MODEL must be enabled to use the EM framework.
87 Registration of 'advanced' EM
90 The 'advanced' EM gets it's name due to the fact that the driver is allowed
92 formula in the framework (like it's in 'simple' EM case). It can better reflect
94 registration method should be preferred in case considering EM static power
97 Drivers are expected to register performance domains into the EM framework by
110 subsystems which use EM might rely on this flag to check if all EM devices use
116 Registration of EM using DT
119 The EM can also be registered using OPP framework and information in DT
122 allows a platform to register EM power values which are reflecting total power
126 Registration of 'artificial' EM
138 has different relation than what would be forced by the EM internal
139 formulas calculating 'cost' values. To register an EM for such platform, the
141 and provide .get_cost() callback. The EM framework would handle such platform
143 platform. Special care should be taken by other frameworks which are using EM
146 Registration of 'simple' EM
149 The 'simple' EM is registered using the framework helper function
155 The EM which is registered using this method might not reflect correctly the
194 the EM for a given CPU(s) 'policy' object: cpufreq_driver::register_em().
200 EM framework::
219 16 /* Return the values to the EM framework */