This is a RFC since this patch largely drifted beyond its original goal of supporting one GPIO and one regulator for the pwm_backlight driver. The issue to address is that backlight power sequences, which were implemented using board-specific callbacks so far, could not be used with the device tree. This series of patches adds a small power sequence interpreter that allows to acquire and control regulators, GPIOs, and PWMs during sequences defined in the device tree. It is easy to use, low-footprint, and takes care of managing the resources that it acquires. The implementation is working and should be complete, but documentation is lacking. Also since the interpreter could be used by other drivers (which ones?), it may make sense to have it in a better place than drivers/video/backlight/. The tegra device tree nodes are just here as an example usage. Alexandre Courbot (3): Power sequences interpreter for device tree pwm-backlight: use power sequences tegra: add pwm backlight device tree nodes .../bindings/video/backlight/pwm-backlight.txt | 28 +- arch/arm/boot/dts/tegra20-ventana.dts | 31 +++ arch/arm/boot/dts/tegra20.dtsi | 2 +- drivers/video/backlight/Makefile | 2 +- drivers/video/backlight/power_seq.c | 298 +++++++++++++++++++++ drivers/video/backlight/pwm_bl.c | 212 +++++++++++---- include/linux/power_seq.h | 96 +++++++ include/linux/pwm_backlight.h | 37 ++- 8 files changed, 645 insertions(+), 61 deletions(-) create mode 100644 drivers/video/backlight/power_seq.c create mode 100644 include/linux/power_seq.h -- 1.7.11.1 -- To unsubscribe from this list: send the line "unsubscribe linux-tegra" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
