Lines Matching refs:intel_idle

5 ``intel_idle`` CPU Idle Time Management Driver
16 ``intel_idle`` is a part of the
22 firmware.  [To understand ``intel_idle`` it is necessary to know how ``CPUIdle``
26 ``intel_idle`` uses the ``MWAIT`` instruction to inform the processor that the
32 Manual [1]_).  Accordingly, ``intel_idle`` refuses to work with processors in
37 ``intel_idle`` is not modular, so it cannot be unloaded, which means that the
58 ``intel_idle`` can use two sources of information: static tables of idle states
61 recognized by ``intel_idle`` and the latter are used if that is required for
63 recognized by ``intel_idle``) or if the processor model is not recognized.
69 states, ``intel_idle`` first looks for a ``_CST`` object under one of the ACPI
73 driver will be suitable for all of the CPUs handled by it and ``intel_idle`` is
82 coming from the ACPI tables.  [This step is skipped if ``intel_idle`` is
90 If the processor model at hand is recognized by ``intel_idle``, there is a
107 If the given processor model is not recognized by ``intel_idle``, but it
119 various processor models recognized by ``intel_idle``) and for the other idle
122 in the majority of cases for the processor models recognized by ``intel_idle``).
131 The initialization of ``intel_idle`` starts with checking if the kernel command
151 Finally, ``intel_idle`` is registered with the help of cpuidle_register_driver()
171 ``intel_idle`` will fail.
173 Apart from that there are four module parameters recognized by ``intel_idle``
180 can be used by ``intel_idle``, so the enumeration of idle states is terminated
184 ``intel_idle`` from exposing idle states that are regarded as "too deep" for
193 Setting ``max_cstate`` to 0 causes the ``intel_idle`` initialization to fail.
195 The ``no_acpi`` and ``use_acpi`` module parameters (recognized by ``intel_idle``
257 tables of idle states in ``intel_idle`` reflect the properties of package
260 ``intel_idle`` described `above <intel-idle-parameters_>`_ must be used to