[RFC PATCH 0/5] ACPI: thermal: Migrate cpufreq cooling to generic cpu_cooling layer

[Amit Daniel Kachhap]

This patch adds notification support for those clients of cpu_cooling
APIs which may want to do something extra after receiving these
cpu_cooling events shown below. The notifier structure passed is of both Set/Get type.
The notfications events can be of the following type,

1. CPU_COOLING_SET_STATE_PRE
2. CPU_COOLING_SET_STATE_POST
3. CPU_COOLING_GET_CUR_STATE
4. CPU_COOLING_GET_MAX_STATE

The advantages of these notfications is to differentiate between different
P states in the cpufreq table and the cooling states. The clients of these
events may group few P states into 1 cooling states as done by ACPI .
Also some more cooling states can be enabled when the maximum of P state is
reached. In case of ACPI processor throttling are enabled when minimum
P-state is reached. Post notification events can be used for those cases.

Amit Daniel Kachhap (5):
  thermal: cpu_cooling: Support passing driver private data.
  thermal: cpu_cooling: Add notifications support for the clients
  thermal: cpu_cooling: Add support to find nearby frequency levels.
  thermal: cpu_cooling: Release the upper cooling limit checks
  ACPI: thermal: processor: Use the generic cpufreq infrastructure

 drivers/acpi/processor_driver.c                    |    6 +-
 drivers/acpi/processor_thermal.c                   |  210 +++++++++----------
 drivers/thermal/cpu_cooling.c                      |  220 +++++++++++++++++---
 drivers/thermal/db8500_cpufreq_cooling.c           |    2 +-
 drivers/thermal/samsung/exynos_thermal_common.c    |    5 +-
 drivers/thermal/step_wise.c                        |    2 +-
 drivers/thermal/thermal_core.c                     |    9 +-
 drivers/thermal/ti-soc-thermal/ti-thermal-common.c |    2 +-
 include/linux/cpu_cooling.h                        |   83 +++++++-
 include/linux/thermal.h                            |    1 +
 10 files changed, 378 insertions(+), 162 deletions(-)

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/