linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Shubhrajyoti <shubhrajyoti@ti.com>
To: Viresh Kumar <viresh.kumar@st.com>
Cc: dmitry.torokhov@gmail.com, linux-input@vger.kernel.org,
	armando.visconti@st.com, shiraz.hashim@st.com,
	vipin.kumar@st.com, rajeev-dlh.kumar@st.com, deepak.sikri@st.com,
	vipulkumar.samar@st.com, amit.virdi@st.com,
	pratyush.anand@st.com, bhupesh.sharma@st.com,
	viresh.linux@gmail.com, bhavna.yadav@st.com,
	vincenzo.frascino@st.com, mirko.gardi@st.com
Subject: Re: [PATCH 2/2] Input/spear-keyboard: Provide thaw and poweroff routines
Date: Thu, 23 Feb 2012 16:59:29 +0530	[thread overview]
Message-ID: <4F462319.9010602@ti.com> (raw)
In-Reply-To: <94d1fcbd230297361d8137e06fdb5d4e2b741529.1329990021.git.viresh.kumar@st.com>

On Thursday 23 February 2012 03:10 PM, Viresh Kumar wrote:
> Thaw and poweroff routines are missing for spear-keyboard. They are required for:
> - Error case scenarios during freeze
> - Using test features, of hibernate.
Not a comment doubt

When is thaw called and when is power off called?
> Signed-off-by: Viresh Kumar <viresh.kumar@st.com>
> Signed-off-by: Viresh Kumar <viresh.kumar@st.com>
> ---
>  drivers/input/keyboard/spear-keyboard.c |    5 +----
>  1 files changed, 1 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/input/keyboard/spear-keyboard.c b/drivers/input/keyboard/spear-keyboard.c
> index 6eb2dd8..6e83828 100644
> --- a/drivers/input/keyboard/spear-keyboard.c
> +++ b/drivers/input/keyboard/spear-keyboard.c
> @@ -321,10 +321,7 @@ static int spear_kbd_resume(struct device *dev)
>  	return 0;
>  }
>  
> -static const struct dev_pm_ops spear_kbd_pm_ops = {
> -	.suspend	= spear_kbd_suspend,
> -	.resume		= spear_kbd_resume,
> -};
Now that you have converted to simple dev pm can you remove the #ifdef
from pm.

> +static SIMPLE_DEV_PM_OPS(spear_kbd_pm_ops, spear_kbd_suspend, spear_kbd_resume);
>  #endif
>  
>  static struct platform_driver spear_kbd_driver = {


  parent reply	other threads:[~2012-02-23 11:29 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-23  9:40 [PATCH 1/2] Input/spear-keyboard: Fix for balancing the enable_irq_wake in Power Mgmt Viresh Kumar
2012-02-23  9:40 ` [PATCH 2/2] Input/spear-keyboard: Provide thaw and poweroff routines Viresh Kumar
2012-02-23 10:35   ` Viresh Kumar
2012-02-23 11:29   ` Shubhrajyoti [this message]
2012-02-23 11:56     ` Viresh Kumar
2012-02-23 11:59       ` Viresh Kumar
2012-02-23 12:11       ` Shubhrajyoti
2012-02-24  5:29   ` [PATCH V2] " Viresh Kumar
2012-02-24  8:34 ` [PATCH 1/2] Input/spear-keyboard: Fix for balancing the enable_irq_wake in Power Mgmt Dmitry Torokhov
2012-02-24  8:58   ` deepaksi
2012-02-24  9:02     ` Dmitry Torokhov
2012-02-24  9:12       ` deepaksi

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=4F462319.9010602@ti.com \
    --to=shubhrajyoti@ti.com \
    --cc=amit.virdi@st.com \
    --cc=armando.visconti@st.com \
    --cc=bhavna.yadav@st.com \
    --cc=bhupesh.sharma@st.com \
    --cc=deepak.sikri@st.com \
    --cc=dmitry.torokhov@gmail.com \
    --cc=linux-input@vger.kernel.org \
    --cc=mirko.gardi@st.com \
    --cc=pratyush.anand@st.com \
    --cc=rajeev-dlh.kumar@st.com \
    --cc=shiraz.hashim@st.com \
    --cc=vincenzo.frascino@st.com \
    --cc=vipin.kumar@st.com \
    --cc=vipulkumar.samar@st.com \
    --cc=viresh.kumar@st.com \
    --cc=viresh.linux@gmail.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).