|From:||Alexandre Courbot <email@example.com>|
|To:||Stephen Warren <firstname.lastname@example.org>, Thierry Reding <email@example.com>, Simon Glass <firstname.lastname@example.org>, Grant Likely <email@example.com>, Rob Herring <firstname.lastname@example.org>, Mark Brown <email@example.com>, Anton Vorontsov <firstname.lastname@example.org>, David Woodhouse <email@example.com>, Arnd Bergmann <firstname.lastname@example.org>|
|Subject:||[PATCH v5 0/4] Runtime Interpreted Power Sequences|
|Date:||Fri, 31 Aug 2012 20:34:02 +0900|
|Cc:||Leela Krishna Amudala <email@example.com>, <firstname.lastname@example.org>, <email@example.com>, <firstname.lastname@example.org>, <email@example.com>, <firstname.lastname@example.org>, <email@example.com>, Alexandre Courbot <firstname.lastname@example.org>|
New revision taking (hopefully) all the feedback received from the previous version into account. It's funny how a 30 lines patch to switch my backlight turned into a 1500 lines patchset introducing a new framework. And in the end my backlight switches just the same. So anyway, the main updates are: * Types of DT steps are now determined by a "type" property and not by the presence of a specific property. * Power sequences and their resources are now encapsulated into a "set" structure. I was reluctant to this idea but have to admit now that it is way cleaner. * GPIO steps now refer the GPIO phandle directly in the DT instead of by name. The GPIO framework does not work like regulator or PWM in that GPIOs cannot be accessed by name, so it did not make sense anyway. And thanks to that we now have perfect matching between the platform data members and the DT properties, which makes everything more consistent. * Moved the implementations of resources into their own file (directly included from the main file) and added an "ops" structure to abstract them. This clearly separates the framework from the resources implementations and should make it easier to add new resources types. Alexandre Courbot (4): Runtime Interpreted Power Sequences pwm_backlight: use power sequences tegra: dt: add label to tegra20's PWM tegra: ventana: add pwm backlight DT nodes .../devicetree/bindings/power_seq/power_seq.txt | 117 ++++++ .../bindings/video/backlight/pwm-backlight.txt | 67 +++- Documentation/power/power_seq.txt | 225 +++++++++++ arch/arm/boot/dts/tegra20-ventana.dts | 59 ++- arch/arm/boot/dts/tegra20.dtsi | 2 +- drivers/power/Kconfig | 1 + drivers/power/Makefile | 1 + drivers/power/power_seq/Kconfig | 2 + drivers/power/power_seq/Makefile | 1 + drivers/power/power_seq/power_seq.c | 446 +++++++++++++++++++++ drivers/power/power_seq/power_seq_delay.c | 51 +++ drivers/power/power_seq/power_seq_gpio.c | 81 ++++ drivers/power/power_seq/power_seq_pwm.c | 85 ++++ drivers/power/power_seq/power_seq_regulator.c | 86 ++++ drivers/video/backlight/Kconfig | 1 + drivers/video/backlight/pwm_bl.c | 179 ++++++--- include/linux/power_seq.h | 174 ++++++++ include/linux/pwm_backlight.h | 15 +- 18 files changed, 1537 insertions(+), 56 deletions(-) create mode 100644 Documentation/devicetree/bindings/power_seq/power_seq.txt create mode 100644 Documentation/power/power_seq.txt create mode 100644 drivers/power/power_seq/Kconfig create mode 100644 drivers/power/power_seq/Makefile create mode 100644 drivers/power/power_seq/power_seq.c create mode 100644 drivers/power/power_seq/power_seq_delay.c create mode 100644 drivers/power/power_seq/power_seq_gpio.c create mode 100644 drivers/power/power_seq/power_seq_pwm.c create mode 100644 drivers/power/power_seq/power_seq_regulator.c create mode 100644 include/linux/power_seq.h -- 1.7.12 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to email@example.com More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Copyright © 2012, Eklektix, Inc.
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds