From: balbi@ti.com (Felipe Balbi)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] backlight: add regulator support for platform_lcd driver
Date: Mon, 5 Dec 2011 10:52:28 +0200 [thread overview]
Message-ID: <20111205085228.GF9900@legolas.emea.dhcp.ti.com> (raw)
In-Reply-To: <1323074921-29291-1-git-send-email-thomas.abraham@linaro.org>
Hi,
On Mon, Dec 05, 2011 at 02:18:41PM +0530, Thomas Abraham wrote:
> The power source to the lcd panel or the lcd interface such as lvds
> transmitters could be controlled by a regulator supply. Add support
> for enabling/disabling the regulator when switching power to lcd.
>
> Two new elements 'min_uV' and 'max_uV' in the platform data are added
> to allow platform code to specifiy the desired output voltage from the
> regulator.
>
> Cc: Ben Dooks <ben-linux@fluff.org>
> Signed-off-by: Thomas Abraham <thomas.abraham@linaro.org>
> ---
> drivers/video/backlight/platform_lcd.c | 29 +++++++++++++++++++++++++++++
> include/video/platform_lcd.h | 7 +++++++
> 2 files changed, 36 insertions(+), 0 deletions(-)
>
> diff --git a/drivers/video/backlight/platform_lcd.c b/drivers/video/backlight/platform_lcd.c
> index 302330a..ffa8108 100644
> --- a/drivers/video/backlight/platform_lcd.c
> +++ b/drivers/video/backlight/platform_lcd.c
> @@ -17,6 +17,8 @@
> #include <linux/backlight.h>
> #include <linux/lcd.h>
> #include <linux/slab.h>
> +#include <linux/regulator/consumer.h>
> +#include <linux/regulator/machine.h>
>
> #include <video/platform_lcd.h>
>
> @@ -44,11 +46,38 @@ static int platform_lcd_get_power(struct lcd_device *lcd)
> static int platform_lcd_set_power(struct lcd_device *lcd, int power)
> {
> struct platform_lcd *plcd = to_our_lcd(lcd);
> + struct regulator *lcd_regulator;
> int lcd_power = 1;
>
> if (power == FB_BLANK_POWERDOWN || plcd->suspended)
> lcd_power = 0;
>
> + /*
> + * If power to lcd and/or lcd interface is controlled using a regulator,
> + * enable or disable the regulator based in the power setting.
> + */
> + lcd_regulator = regulator_get(plcd->us, "vcc_lcd");
> + if (IS_ERR(lcd_regulator)) {
> + dev_info(plcd->us, "could not get regulator\n");
> + goto set_power;
> + }
> +
> + if (lcd_power) {
> + if (plcd->pdata->min_uV || plcd->pdata->max_uV)
> + if (regulator_set_voltage(lcd_regulator,
> + plcd->pdata->min_uV, plcd->pdata->max_uV))
> + dev_info(plcd->us,
> + "regulator voltage set failed\n");
> +
> + if (regulator_enable(lcd_regulator))
> + dev_info(plcd->us, "failed to enable regulator\n");
> + } else {
> + regulator_disable(lcd_regulator);
> + }
> +
> + regulator_put(lcd_regulator);
I wonder why you ->get() and ->put() everytime here. Wouldn't it be
enough to ->get() on probe() and ->put() on remove() ??
--
balbi
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20111205/7fceaaed/attachment.sig>
next prev parent reply other threads:[~2011-12-05 8:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-05 8:48 [PATCH] backlight: add regulator support for platform_lcd driver Thomas Abraham
2011-12-05 8:52 ` Felipe Balbi [this message]
2011-12-05 9:14 ` Thomas Abraham
2011-12-05 10:10 ` Kyungmin Park
2011-12-05 10:33 ` Mark Brown
2011-12-05 10:36 ` Thomas Abraham
2011-12-05 10:52 ` Mark Brown
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20111205085228.GF9900@legolas.emea.dhcp.ti.com \
--to=balbi@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).