From: Shubhrajyoti <shubhrajyoti@ti.com>
To: linux-input@vger.kernel.org
Cc: shubhrajyoti@ti.com, Abraham Arce <x0066660@ti.com>,
Kevin Hilman <khilman@deeprootsystems.com>
Subject: Re: [PATCH v8 3/3] OMAP4:keypad: PM runtime
Date: Tue, 08 Feb 2011 14:00:58 +0530 [thread overview]
Message-ID: <4D50FF42.1070401@ti.com> (raw)
In-Reply-To: <1293429106-16543-4-git-send-email-shubhrajyoti@ti.com>
Hello,
Any comments/suggestions.
Thanks,
On Monday 27 December 2010 11:21 AM, shubhrajyoti@ti.com wrote:
> From: Abraham Arce<x0066660@ti.com>
>
> Enable Runtime PM functionality in OMAP4 driver based on the following assumptions
>
> A minimal pm runtime get/put approach is implemented in probe/remove calls
> respectively.
>
> - Keyboard controller in wakeup domain so it is always on and
> power impact may be minimal
> - In OMAP4 the device control is at module/device level and ick/fclk level control is
> difficult so cutting of clocks will prevent interrupts.
>
> Signed-off-by: Abraham Arce<x0066660@ti.com>
> Cc: Kevin Hilman<khilman@deeprootsystems.com>
> Signed-off-by: Shubhrajyoti D<shubhrajyoti@ti.com>
> ---
> drivers/input/keyboard/omap4-keypad.c | 8 ++++++++
> 1 files changed, 8 insertions(+), 0 deletions(-)
>
> diff --git a/drivers/input/keyboard/omap4-keypad.c b/drivers/input/keyboard/omap4-keypad.c
> index 45bd097..fcfbb9b 100644
> --- a/drivers/input/keyboard/omap4-keypad.c
> +++ b/drivers/input/keyboard/omap4-keypad.c
> @@ -29,6 +29,7 @@
> #include<linux/io.h>
> #include<linux/input.h>
> #include<linux/slab.h>
> +#include<linux/pm_runtime.h>
>
> #include<plat/omap4-keypad.h>
>
> @@ -239,6 +240,9 @@ static int __devinit omap4_keypad_probe(struct platform_device *pdev)
> matrix_keypad_build_keymap(pdata->keymap_data, row_shift,
> input_dev->keycode, input_dev->keybit);
>
> + pm_runtime_enable(&pdev->dev);
> + pm_runtime_get_sync(&pdev->dev);
> +
> omap4_keypad_config(keypad_data);
>
> error = request_irq(keypad_data->irq, omap4_keypad_interrupt,
> @@ -278,6 +282,10 @@ static int __devexit omap4_keypad_remove(struct platform_device *pdev)
> struct resource *res;
>
> free_irq(keypad_data->irq, keypad_data);
> +
> + pm_runtime_put_sync(&pdev->dev);
> + pm_runtime_disable(&pdev->dev);
> +
> input_unregister_device(keypad_data->input);
>
> iounmap(keypad_data->base);
next prev parent reply other threads:[~2011-02-08 8:31 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-27 5:51 [PATCH 0/3]OMAP4: Keypad support shubhrajyoti
2010-12-27 5:51 ` [PATCH v8 1/3] OMAP4: hwmod data: Add keypad in the hwmod database shubhrajyoti
2010-12-27 5:51 ` [PATCH v8 2/3] OMAP4: keypad: Add the board support shubhrajyoti
2010-12-27 5:51 ` [PATCH v8 3/3] OMAP4:keypad: PM runtime shubhrajyoti
2011-02-08 8:30 ` Shubhrajyoti [this message]
2011-02-11 17:18 ` Shubhrajyoti
2011-02-19 3:07 ` Shubhrajyoti
2011-02-19 5:31 ` Dmitry Torokhov
[not found] ` <AANLkTikCmiSrOZb3WvMZHcxRsSRxd1zUsWE59aexHdeF@mail.gmail.com>
2011-02-23 6:29 ` Dmitry Torokhov
2011-02-23 14:19 ` Shubhrajyoti
2011-02-23 22:58 ` Tony Lindgren
2011-02-23 23:12 ` Dmitry Torokhov
2011-02-15 9:41 ` [PATCH 0/3]OMAP4: Keypad support Shubhrajyoti Datta
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=4D50FF42.1070401@ti.com \
--to=shubhrajyoti@ti.com \
--cc=khilman@deeprootsystems.com \
--cc=linux-input@vger.kernel.org \
--cc=x0066660@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.