[PATCH V2 0/20] thermal: exynos: Add thermal driver for exynos5440
From: Amit Daniel Kachhap
Date: Fri Apr 26 2013 - 06:38:17 EST
Changes in V2:
* Separated SOC data from TMU driver. This is as per suggestion from Eduardo.
* Merged the new file created for exynos5440 TMU controller with the existing
TMU controller code.
* Removed the DT parsing code as now the SOC specific data are cleanly put
inside the data specific file.
* Even the register definations/bitfields are treated as data as there is
some variation across SOC's.
This patchset adds TMU(Thermal management Unit) driver support for
exynos5440 platform. There are 3 instances of the TMU controllers so
necessary cleanup is done to handle multiple thermal zone.
1 patch (exynos4: Add documentation for Exynos SoC thermal bindings) from
Lukasz Majewski is already posted to mainline. Adding it here for completeness.
(http://www.mail-archive.com/linux-samsung-soc@xxxxxxxxxxxxxxx/msg17817.html)
1 patch (thermal: exynos: Support thermal tripping ) from Jonghwan Choi is
added here with some changes.
(https://patchwork.kernel.org/patch/1668371/)
All these patches are based on thermal maintainers git tree,
git://git.kernel.org/pub/scm/linux/kernel/git/rzhang/linux.git next.
Amit Daniel Kachhap (19):
thermal: exynos: Moving exynos thermal files into samsung directory
thermal: exynos: Bifurcate exynos thermal common and tmu controller
code
thermal: exynos: Rename exynos_thermal.c to exynos_tmu.c
thermal: exynos: Move exynos_thermal.h from include/* to driver/*
folder
thermal: exynos: Bifurcate exynos tmu driver and configuration data
thermal: exynos: Add missing definations and code cleanup
thermal: exynos: Add extra entries in the tmu platform data
thermal: exynos: Support thermal tripping
thermal: exynos: Move register definitions from driver file to data
file
thermal: exynos: Fix to clear only the generated interrupts
thermal: exynos: Add support for instance based register/unregister
thermal: exynos: Modify private_data to appropriate name driver_data
thermal: exynos: Return success even if no cooling data supplied
thermal: exynos: Make the zone handling dependent on trip count
thermal: exynos: Add support to handle many instances of TMU
thermal: exynos: Add features to check instead of SOC type
thermal: exynos: Add support for exynos5440 TMU sensor.
Documentation: thermal: Explain the exynos thermal driver model
ARM: dts: Add device tree node for exynos5440 TMU controller
Lukasz Majewski (1):
ARM: dts: thermal: exynos4: Add documentation for Exynos SoC thermal
bindings
.../devicetree/bindings/thermal/exynos-thermal.txt | 49 +
Documentation/thermal/exynos_thermal | 43 +-
arch/arm/boot/dts/exynos5440.dtsi | 30 +
drivers/thermal/Kconfig | 13 +-
drivers/thermal/Makefile | 2 +-
drivers/thermal/exynos_thermal.c | 1066 --------------------
drivers/thermal/samsung/Kconfig | 21 +
drivers/thermal/samsung/Makefile | 7 +
drivers/thermal/samsung/exynos_thermal_common.c | 401 ++++++++
drivers/thermal/samsung/exynos_thermal_common.h | 85 ++
drivers/thermal/samsung/exynos_tmu.c | 719 +++++++++++++
drivers/thermal/samsung/exynos_tmu.h | 223 ++++
drivers/thermal/samsung/exynos_tmu_data.c | 224 ++++
drivers/thermal/samsung/exynos_tmu_data.h | 150 +++
include/linux/platform_data/exynos_thermal.h | 119 ---
15 files changed, 1949 insertions(+), 1203 deletions(-)
create mode 100644 Documentation/devicetree/bindings/thermal/exynos-thermal.txt
delete mode 100644 drivers/thermal/exynos_thermal.c
create mode 100644 drivers/thermal/samsung/Kconfig
create mode 100644 drivers/thermal/samsung/Makefile
create mode 100644 drivers/thermal/samsung/exynos_thermal_common.c
create mode 100644 drivers/thermal/samsung/exynos_thermal_common.h
create mode 100644 drivers/thermal/samsung/exynos_tmu.c
create mode 100644 drivers/thermal/samsung/exynos_tmu.h
create mode 100644 drivers/thermal/samsung/exynos_tmu_data.c
create mode 100644 drivers/thermal/samsung/exynos_tmu_data.h
delete mode 100644 include/linux/platform_data/exynos_thermal.h
--
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/