| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
| |
SMP systems. It appears all drivers except ichss should attach to each
CPU and that settings should be performed on each CPU. Add comments about
this. Also, add a guard for p4tcc's identify method being called more than
once.
|
|
|
|
| |
hint.ichss.0.disabled="1"
|
|
|
|
| |
the multi-setting EST is preferable.
|
|
|
|
|
|
|
|
|
|
|
| |
driver. This used to be handled by cpufreq_drv_settings() but it's
useful to get the type/flags separately from getting the settings.
(For example, you don't have to pass an array of cf_setting just to find
the driver type.)
Use this new method in our in-tree drivers to detect reliably if acpi_perf
is present and owns the hardware. This simplifies logic in drivers as well
as fixing a bug introduced in my last commit where too many drivers attached.
|
|
|
|
|
|
|
|
|
| |
or just offering info. In the former case, we don't probe/attach to allow
the ACPI driver precedence. A refinement of this would be to actually
use the info provided by acpi_perf(4) to get the real CPU clock rates
instead of estimating them but since all systems that support both
acpi_perf(4) and ichss(4) export the control registers to acpi_perf(4),
it can just handle the registers on its own.
|
|
|
|
| |
not MI. This should fix build on non i386 platforms.
|
|
|
|
|
|
| |
bus_space_{read,write}_* routines. This doesn't matter in the current
tree, but will matter soon (the rest of the tree appears to already be
clean).
|
|
driver offers two settings. Information for this driver was obtained from
the Intel datasheets and by reviewing the Linux driver.
|