[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <1432128046-12921-1-git-send-email-s.hauer@pengutronix.de>
Date: Wed, 20 May 2015 15:20:30 +0200
From: Sascha Hauer <s.hauer@...gutronix.de>
To: linux-pm@...r.kernel.org
Cc: Zhang Rui <rui.zhang@...el.com>,
Eduardo Valentin <edubezval@...il.com>,
linux-kernel@...r.kernel.org,
Stephen Warren <swarren@...dotorg.org>,
Mikko Perttunen <mikko.perttunen@...si.fi>,
kernel@...gutronix.de, linux-mediatek@...ts.infradead.org,
linux-arm-kernel@...ts.infradead.org,
Brian Norris <computersforpeace@...il.com>
Subject: [PATCH v4] Thermal cleanups and hardware trip points
This series adds support for hardware trip points. It picks up earlier
work from Mikko Perttunen. Mikko implemented hardware trip points as part
of the device tree support. It was suggested back then to move the
functionality to the thermal core instead of putting more code into the
device tree support. This series does exactly that.
The majority of the patches are cleanups and fixes. Patch 11 introduces
hardware tracked trip points and finally a driver for the Mediatek
thermal controller is introduced as the first user.
All comments welcome
Changes since v3:
- Fix some missing function type changes in int3400_thermal.c,
processor_thermal_device.c, kirkwood_thermal.c and exynos_tmu.c
- Add better description for set_trips callback
- update the interrupt triggers also when the trip points change
- Add missing MODULE_* tags
- Broaden temperature range in the Mediatek driver so that we can be sure
the measured temperatures are really out of the desired range
Changes since v2:
- Add Mediatek thermal controller driver as first user for hardware trip
points
Changes since v1:
- Use int instead of unsigned long consistently for temperatures
- Instead of misfixing the emulation code add a comment how the
code is meant
- Add doc entry for .set_trips callback
- initialize prev_low_trip/prev_high_trip properly
- get tz->lock before calling thermal_zone_set_trips()
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists