Lines Matching refs:throttle

35 - throttle-cfgs: A sub-node which is a container of configuration for each
36     hardware throttle events. These events can be set as cooling devices.
37   * throttle events: Sub-nodes must be named as "light" or "heavy".
39       - nvidia,priority: Each throttles has its own throttle settings, so the
40         SW need to set priorities for various throttle, the HW arbiter can select
41         the final throttle settings.
51         level of pulse skippers, which used to throttle clock frequencies. It
57         It is the level of pulse skippers, which used to throttle clock
70       valid only for OCx throttle events.
79       - nvidia,throttle-period-us: Specifies the number of uSec for which
98 - the "hot" type trip points will be set to SOC_THERM hardware as the throttle
100 than it, it will trigger the HW throttle event.
121 		throttle-cfgs {
149 			 * If these two devices are triggered in same time, the HW throttle
150 			 * arbiter will select the highest priority as the final throttle
159 				nvidia,throttle-period-us = <0>;
167 Example: referring to Tegra132's "reg", "reg-names" and "throttle-cfgs" :
175 		throttle-cfgs {
199 			 * If these two devices are triggered in same time, the HW throttle
200 			 * arbiter will select the highest priority as the final throttle
224 				cpu_throttle_trip: throttle-trip {