Searched hist:e94a0c1a18e6974bd6467d32a0f0fec8bffe5307 (Results 1 – 5 of 5) sorted by relevance
/freebsd/sys/kern/ |
H A D | cpufreq_if.m | diff e94a0c1a18e6974bd6467d32a0f0fec8bffe5307 Fri Feb 18 01:23:36 CET 2005 Nate Lawson <njl@FreeBSD.org> Introduce a new method, cpufreq_drv_type(), that returns the type of the 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. diff e94a0c1a18e6974bd6467d32a0f0fec8bffe5307 Fri Feb 18 01:23:36 CET 2005 Nate Lawson <njl@FreeBSD.org> Introduce a new method, cpufreq_drv_type(), that returns the type of the 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.
|
H A D | kern_cpu.c | diff e94a0c1a18e6974bd6467d32a0f0fec8bffe5307 Fri Feb 18 01:23:36 CET 2005 Nate Lawson <njl@FreeBSD.org> Introduce a new method, cpufreq_drv_type(), that returns the type of the 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. diff e94a0c1a18e6974bd6467d32a0f0fec8bffe5307 Fri Feb 18 01:23:36 CET 2005 Nate Lawson <njl@FreeBSD.org> Introduce a new method, cpufreq_drv_type(), that returns the type of the 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.
|
/freebsd/sys/dev/acpica/ |
H A D | acpi_throttle.c | diff e94a0c1a18e6974bd6467d32a0f0fec8bffe5307 Fri Feb 18 01:23:36 CET 2005 Nate Lawson <njl@FreeBSD.org> Introduce a new method, cpufreq_drv_type(), that returns the type of the 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. diff e94a0c1a18e6974bd6467d32a0f0fec8bffe5307 Fri Feb 18 01:23:36 CET 2005 Nate Lawson <njl@FreeBSD.org> Introduce a new method, cpufreq_drv_type(), that returns the type of the 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.
|
H A D | acpi_perf.c | diff e94a0c1a18e6974bd6467d32a0f0fec8bffe5307 Fri Feb 18 01:23:36 CET 2005 Nate Lawson <njl@FreeBSD.org> Introduce a new method, cpufreq_drv_type(), that returns the type of the 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. diff e94a0c1a18e6974bd6467d32a0f0fec8bffe5307 Fri Feb 18 01:23:36 CET 2005 Nate Lawson <njl@FreeBSD.org> Introduce a new method, cpufreq_drv_type(), that returns the type of the 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.
|
/freebsd/sys/dev/cpufreq/ |
H A D | ichss.c | diff e94a0c1a18e6974bd6467d32a0f0fec8bffe5307 Fri Feb 18 01:23:36 CET 2005 Nate Lawson <njl@FreeBSD.org> Introduce a new method, cpufreq_drv_type(), that returns the type of the 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. diff e94a0c1a18e6974bd6467d32a0f0fec8bffe5307 Fri Feb 18 01:23:36 CET 2005 Nate Lawson <njl@FreeBSD.org> Introduce a new method, cpufreq_drv_type(), that returns the type of the 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.
|