linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: sebastian.capella@linaro.org
To: tomi.valkeinen@ti.com, shuah.kh@samsung.com, rpurdie@rpsys.net,
	rafael.j.wysocki@intel.com, plagnioj@jcrosoft.com,
	FlorianSchandinat@gmx.de
Cc: shuahkhan@gmail.com, linux-kernel@vger.kernel.org,
	linux-fbdev@vger.kernel.org
Subject: Re: [v2] backlight: Convert from Legacy pm ops to dev_pm_ops
Date: Tue, 18 Feb 2014 22:20:42 +0000	[thread overview]
Message-ID: <5303dcb6.2587440a.3f18.fffff1ba@mx.google.com> (raw)
In-Reply-To: <2236505237-3336-1-git-send-email-shuah.kh@samsung.com>

Shuah Khan <shuah.kh@samsung.com> wrote:

> Convert drivers/video/backlight/class to use dev_pm_ops for power
> management and remove Legacy PM ops hooks. With this change, rtc class
> registers suspend/resume callbacks via class->pm (dev_pm_ops) instead of
> Legacy class->suspend/resume. When __device_suspend() runs call-backs,
> it will find class->pm ops for the backlight class.
>
> Signed-off-by: Shuah Khan <shuah.kh@samsung.com>
> Cc: Shuah Khan <shuahkhan@gmail.com>
>
> ---
> v2: Updated changelog to correct device class.
>
>  drivers/video/backlight/backlight.c |    8 +++++---
>  1 file changed, 5 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/video/backlight/backlight.c b/drivers/video/backlight/backlight.c
> index c74e7aa..0ffb251 100644
> --- a/drivers/video/backlight/backlight.c
> +++ b/drivers/video/backlight/backlight.c
> @@ -208,7 +208,7 @@ static ssize_t backlight_show_actual_brightness(struct device *dev,
>  
>  static struct class *backlight_class;
>  
> -static int backlight_suspend(struct device *dev, pm_message_t state)
> +static int backlight_suspend(struct device *dev)
>  {
>  	struct backlight_device *bd = to_backlight_device(dev);
>  
> @@ -236,6 +236,9 @@ static int backlight_resume(struct device *dev)
>  	return 0;
>  }
>  
> +static SIMPLE_DEV_PM_OPS(backlight_class_dev_pm_ops, backlight_suspend,
> +			 backlight_resume);
> +
>  static void bl_device_release(struct device *dev)
>  {
>  	struct backlight_device *bd = to_backlight_device(dev);
> @@ -414,8 +417,7 @@ static int __init backlight_class_init(void)
>  	}
>  
>  	backlight_class->dev_attrs = bl_device_attributes;
> -	backlight_class->suspend = backlight_suspend;
> -	backlight_class->resume = backlight_resume;
> +	backlight_class->pm = &backlight_class_dev_pm_ops;
>  	return 0;
>  }
>  

      parent reply	other threads:[~2014-02-18 22:20 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-01  3:59 [PATCH v2] backlight: Convert from Legacy pm ops to dev_pm_ops Shuah Khan
2013-06-01  4:13 ` Jingoo Han
2013-08-09 21:28 ` David Brown
2013-08-09 21:33   ` Shuah Khan
2014-01-19 15:37 ` Rafael J. Wysocki
2014-01-20  1:34   ` Jingoo Han
2014-01-20 15:27     ` Shuah Khan
2014-02-04 17:55       ` Shuah Khan
2014-02-05  0:17         ` Jingoo Han
2014-01-21 15:29   ` Shuah Khan
2014-02-18 22:20 ` sebastian.capella [this message]

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=5303dcb6.2587440a.3f18.fffff1ba@mx.google.com \
    --to=sebastian.capella@linaro.org \
    --cc=FlorianSchandinat@gmx.de \
    --cc=linux-fbdev@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=plagnioj@jcrosoft.com \
    --cc=rafael.j.wysocki@intel.com \
    --cc=rpurdie@rpsys.net \
    --cc=shuah.kh@samsung.com \
    --cc=shuahkhan@gmail.com \
    --cc=tomi.valkeinen@ti.com \
    /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).