From: Tony Lindgren <tony@atomide.com>
To: Kevin Hilman <khilman@deeprootsystems.com>
Cc: linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 1/3] OMAP: PM: formalize idle notifications
Date: Fri, 22 Oct 2010 11:05:53 -0700 [thread overview]
Message-ID: <20101022180553.GD17595@atomide.com> (raw)
In-Reply-To: <1287617483-24170-1-git-send-email-khilman@deeprootsystems.com>
* Kevin Hilman <khilman@deeprootsystems.com> [101020 16:22]:
> Currently in the idle path, we have custom function calls into device
> code to handle device specific actions that need to be coordinated CPU
> idle transitions. Rather than continue this ad-hoc method of calling
> device code from the PM core, create a formal way for device/driver
> code to register for idle notifications.
>
> Idle notifications are done late in the idle path when interrupts are
> disabled, hence use atomic notifier chains. These notifications will
> also be atomic with respect to CPU idle transitions.
...
> +EXPORT_SYMBOL_GPL(omap_idle_notifier_register);
> +EXPORT_SYMBOL_GPL(omap_idle_notifier_unregister);
Let's rather set this up as a generic framework to avoid adding
more omap specific frameworks to the drivers.
Regards,
Tony
WARNING: multiple messages have this Message-ID (diff)
From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/3] OMAP: PM: formalize idle notifications
Date: Fri, 22 Oct 2010 11:05:53 -0700 [thread overview]
Message-ID: <20101022180553.GD17595@atomide.com> (raw)
In-Reply-To: <1287617483-24170-1-git-send-email-khilman@deeprootsystems.com>
* Kevin Hilman <khilman@deeprootsystems.com> [101020 16:22]:
> Currently in the idle path, we have custom function calls into device
> code to handle device specific actions that need to be coordinated CPU
> idle transitions. Rather than continue this ad-hoc method of calling
> device code from the PM core, create a formal way for device/driver
> code to register for idle notifications.
>
> Idle notifications are done late in the idle path when interrupts are
> disabled, hence use atomic notifier chains. These notifications will
> also be atomic with respect to CPU idle transitions.
...
> +EXPORT_SYMBOL_GPL(omap_idle_notifier_register);
> +EXPORT_SYMBOL_GPL(omap_idle_notifier_unregister);
Let's rather set this up as a generic framework to avoid adding
more omap specific frameworks to the drivers.
Regards,
Tony
next prev parent reply other threads:[~2010-10-22 18:05 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-20 23:31 [PATCH 1/3] OMAP: PM: formalize idle notifications Kevin Hilman
2010-10-20 23:31 ` Kevin Hilman
2010-10-20 23:31 ` [PATCH 2/3] OMAP: INTC: use idle notifier for autoidle management Kevin Hilman
2010-10-20 23:31 ` Kevin Hilman
2010-10-20 23:31 ` [PATCH 3/3] OMAP: UART: use atomic idle notifiers Kevin Hilman
2010-10-20 23:31 ` Kevin Hilman
2010-10-22 12:54 ` Govindraj
2010-10-22 12:54 ` Govindraj
2010-10-22 16:11 ` Kevin Hilman
2010-10-22 16:11 ` Kevin Hilman
2010-10-22 18:05 ` Tony Lindgren [this message]
2010-10-22 18:05 ` [PATCH 1/3] OMAP: PM: formalize idle notifications Tony Lindgren
2010-10-22 22:00 ` Kevin Hilman
2010-10-22 22:00 ` Kevin Hilman
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=20101022180553.GD17595@atomide.com \
--to=tony@atomide.com \
--cc=khilman@deeprootsystems.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
/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.