linux-omap.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kevin Hilman <khilman@deeprootsystems.com>
To: Shubhrajyoti D <a0393217@india.ti.com>
Cc: linux-input@vger.kernel.org, linux-omap@vger.kernel.org,
	Abraham Arce <x0066660@ti.com>
Subject: Re: [PATCH v7] OMAP4:keypad: PM runtime
Date: Tue, 14 Dec 2010 09:25:43 -0800	[thread overview]
Message-ID: <8739q0w9k8.fsf@deeprootsystems.com> (raw)
In-Reply-To: <1292341137-14783-1-git-send-email-a0393217@india.ti.com> (Shubhrajyoti D.'s message of "Tue, 14 Dec 2010 21:08:57 +0530")

Shubhrajyoti D <a0393217@india.ti.com> writes:

> From: Abraham Arce <x0066660@ti.com>
>
> Enable Runtime PM functionality in OMAP4 driver based on the following assumptions
> - Runtime PM selected by ARCH_OMAP2PLUS_TYPICAL && ARCH_OMAP2PLUS,
>   which is the default OMAP2+ defconfig including OMAP4

this does not need to be stated in the changelog

> - Runtime PM APIs handles Clock Framework APIs

OMAP Runtime PM does much more than handle clocks.

> - Do not do the keypadconfig if the irq request fails

This is a separate fix, unrelated to enabling runtime PM.

> A minimal pm runtime get/put approach is implemented in probe/remove calls
> respectively based on:
>
> - Keyboard controller in wakeup domain so it is always on and
>   power impact may be minimal
> - Cutting of clocks will prevent interrupts

Again, please describe in more detail why preventing interrupts causes a
problem.    I understand it may seem obvious right now, but these
changelogs  need to be understandable many months/years down the road.

Kevin

> Signed-off-by: Abraham Arce <x0066660@ti.com>
> Cc: Kevin Hilman <khilman@deeprootsystems.com>
> ---
> Updating the changelogs as per Kevin's suggestion
>
>  drivers/input/keyboard/omap4-keypad.c |   11 +++++++++--
>  1 files changed, 9 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/input/keyboard/omap4-keypad.c b/drivers/input/keyboard/omap4-keypad.c
> index 45bd097..36239e2 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,7 +240,8 @@ 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);
>  
> -	omap4_keypad_config(keypad_data);
> +	pm_runtime_enable(&pdev->dev);
> +	pm_runtime_get_sync(&pdev->dev);
>  
>  	error = request_irq(keypad_data->irq, omap4_keypad_interrupt,
>  			     IRQF_TRIGGER_RISING,
> @@ -255,8 +257,9 @@ static int __devinit omap4_keypad_probe(struct platform_device *pdev)
>  		goto err_free_irq;
>  	}
>  
> -
> +	omap4_keypad_config(keypad_data);
>  	platform_set_drvdata(pdev, keypad_data);
> +
>  	return 0;
>  
>  err_free_irq:
> @@ -278,6 +281,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);

  reply	other threads:[~2010-12-14 17:25 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-14 15:38 [PATCH v7] OMAP4:keypad: PM runtime Shubhrajyoti D
2010-12-14 17:25 ` Kevin Hilman [this message]
  -- strict thread matches above, loose matches on Subject: below --
2010-12-15  4:09 Shubhrajyoti D
2010-12-15  5:31 ` Varadarajan, Charulatha
2010-12-15  7:54   ` Datta, Shubhrajyoti
2010-12-15  8:58     ` Varadarajan, Charulatha
2010-12-15 14:03       ` Datta, Shubhrajyoti

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=8739q0w9k8.fsf@deeprootsystems.com \
    --to=khilman@deeprootsystems.com \
    --cc=a0393217@india.ti.com \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-omap@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 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).