linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Hui Wang <jason77.wang@gmail.com>
To: gaowanlong@cn.fujitsu.com
Cc: Hui Wang <jason77.wang@gmail.com>,
	dmitry.torokhov@gmail.com, s.hauer@pengutronix.de,
	maramaopercheseimorto@gmail.com, linux-input@vger.kernel.org
Subject: Re: [PATCH] input/imx_keypad: add pm suspend and resume functions
Date: Fri, 30 Sep 2011 16:59:53 +0800	[thread overview]
Message-ID: <4E858509.80303@gmail.com> (raw)
In-Reply-To: <4E857E25.4040503@cn.fujitsu.com>

Wanlong Gao wrote:
> On 09/30/2011 03:54 PM, Hui Wang wrote:
>
>   
>> The imx_keypad driver is set wake capable in the imx_keypad_probe(),
>> but it doesn't implement suspend and reusme callback interface.
>>
>> >From the i.MX series MCU Reference Manual, the kpp (keypad port) is
>> a major wake up source which can detect any key press even in low
>> power modes and even when there is no clock.
>>
>> Now add suspend and resume callback functions for this driver.
>>
>> Signed-off-by: Hui Wang <jason77.wang@gmail.com>
>> ---
>> Validated this patch both on i.MX51 PDK and i.MX31 PDK
>>
>>  drivers/input/keyboard/imx_keypad.c |   42 +++++++++++++++++++++++++++++++++++
>>  1 files changed, 42 insertions(+), 0 deletions(-)
>>
>> diff --git a/drivers/input/keyboard/imx_keypad.c b/drivers/input/keyboard/imx_keypad.c
>> index d92c15c..9992617 100644
>> --- a/drivers/input/keyboard/imx_keypad.c
>> +++ b/drivers/input/keyboard/imx_keypad.c
>> @@ -567,10 +567,52 @@ static int __devexit imx_keypad_remove(struct platform_device *pdev)
>>  	return 0;
>>  }
>>  
>> +#ifdef CONFIG_PM
>> +static int imx_kbd_suspend(struct device *dev)
>> +{
>> +	struct platform_device *pdev = to_platform_device(dev);
>> +	struct imx_keypad *kbd = platform_get_drvdata(pdev);
>> +
>> +	clk_disable(kbd->clk);
>> +
>> +	if (device_may_wakeup(&pdev->dev))
>> +		enable_irq_wake(kbd->irq);
>> +
>> +	return 0;
>> +}
>>     
>
> 	struct input_dev *input_dev = kbd->input_dev;
> 	if (device_may_wakeup(dev)) {
> 		enable_irq_wake(kdb->irq);
> 	} else {
> 		mutex_lock(&input_dev->mutex);
>
> 		if (input_dev->users)
> 			clk_disable(kbd->clk);
>
> 		mutex_unlock(&input_dev->mutex);
> 	}
>
> right?
>
>   
The i.MX series kpp is not like other normal kpps on other platforms, 
the kpp on the i.MX can detect key event and wake up system from low 
power mode even we disable kpp clock. So i choose to unconditionally 
disable its clock. I have explain it the commit header.

"From the i.MX series MCU Reference Manual, the kpp (keypad port) is

a major wake up source which can detect any key press even in low
power modes and even when there is no clock.
"

>> +
>> +static int imx_kbd_resume(struct device *dev)
>> +{
>> +	struct platform_device *pdev = to_platform_device(dev);
>> +	struct imx_keypad *kbd = platform_get_drvdata(pdev);
>> +	struct input_dev *input_dev = kbd->input_dev;
>> +
>> +	mutex_lock(&input_dev->mutex);
>> +
>> +	if (device_may_wakeup(&pdev->dev))
>> +		disable_irq_wake(kbd->irq);
>> +
>> +	if (input_dev->users)
>> +		clk_enable(kbd->clk);
>> +
>> +	mutex_unlock(&input_dev->mutex);
>> +
>> +	return 0;
>> +}
>>     
>
> 	struct input_dev *input_dev = kbd->input_dev;
> 	if (device_may_wakeup(dev)) {
> 		disable_irq_wake(kdb->irq);
> 	} else {
> 		mutex_lock(&input_dev->mutex);
>
> 		if (input_dev->users)
> 			clk_enable(kbd->clk);
>
> 		mutex_unlock(&input_dev->mutex);
> 	}
>
>   
So, if we unconditionally disable kpp clock in the suspend, we don't 
need above logic as well in the resume.
>> +
>> +static const struct dev_pm_ops imx_kbd_pm_ops = {
>>     
>
>
> SIMPLE_DEV_PM_OPS?
>   
Correct, i will use SIMPLE_DEV_PM_OPS in V2.

>
> Thanks
> -Wanlong Gao
>
>   


  reply	other threads:[~2011-09-30  9:00 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-30  7:54 [PATCH] input/imx_keypad: add pm suspend and resume functions Hui Wang
2011-09-30  8:30 ` Wanlong Gao
2011-09-30  8:59   ` Hui Wang [this message]
2011-09-30  9:05     ` Wanlong Gao
2011-10-09  9:47       ` Hui Wang
2011-09-30  9:12     ` Dmitry Torokhov
2011-10-09  9:49       ` Hui Wang

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=4E858509.80303@gmail.com \
    --to=jason77.wang@gmail.com \
    --cc=dmitry.torokhov@gmail.com \
    --cc=gaowanlong@cn.fujitsu.com \
    --cc=linux-input@vger.kernel.org \
    --cc=maramaopercheseimorto@gmail.com \
    --cc=s.hauer@pengutronix.de \
    /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).