From: Santosh Shilimkar <santosh.shilimkar@ti.com>
To: Rajendra Nayak <rnayak@ti.com>
Cc: linux-omap@vger.kernel.org, paul@pwsan.com, khilman@ti.com,
b-cousson@ti.com, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 1/4] OMAP2+: clockdomain: Add an api to read idle mode
Date: Tue, 05 Apr 2011 19:09:56 +0530 [thread overview]
Message-ID: <4D9B1BAC.3090700@ti.com> (raw)
In-Reply-To: <1302007497-10525-2-git-send-email-rnayak@ti.com>
On 4/5/2011 6:14 PM, Rajendra Nayak wrote:
> Add a clockdomain api to check if hardware supervised
> idle transitions are enabled on a clockdomain.
>
> Signed-off-by: Rajendra Nayak<rnayak@ti.com>
> ---
> arch/arm/mach-omap2/clockdomain.c | 21 +++++++++++++++++++++
> arch/arm/mach-omap2/clockdomain.h | 3 +++
> 2 files changed, 24 insertions(+), 0 deletions(-)
>
> diff --git a/arch/arm/mach-omap2/clockdomain.c b/arch/arm/mach-omap2/clockdomain.c
> index ab87854..1de6def 100644
> --- a/arch/arm/mach-omap2/clockdomain.c
> +++ b/arch/arm/mach-omap2/clockdomain.c
> @@ -795,6 +795,27 @@ void clkdm_deny_idle(struct clockdomain *clkdm)
> arch_clkdm->clkdm_deny_idle(clkdm);
> }
>
> +/**
> + * clkdm_is_idle - Check if the clkdm hwsup/autoidle is enabled
> + * @clkdm: struct clockdomain *
> + *
> + * Returns true if the clockdomain is in hardware-supervised
> + * idle mode, or 0 otherwise.
> + *
> + */
> +int clkdm_is_idle(struct clockdomain *clkdm)
>
Name of the API not seems to fit correctly.
Shoule it be something like "clkdm_is_in_hwsup"?
WARNING: multiple messages have this Message-ID (diff)
From: santosh.shilimkar@ti.com (Santosh Shilimkar)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/4] OMAP2+: clockdomain: Add an api to read idle mode
Date: Tue, 05 Apr 2011 19:09:56 +0530 [thread overview]
Message-ID: <4D9B1BAC.3090700@ti.com> (raw)
In-Reply-To: <1302007497-10525-2-git-send-email-rnayak@ti.com>
On 4/5/2011 6:14 PM, Rajendra Nayak wrote:
> Add a clockdomain api to check if hardware supervised
> idle transitions are enabled on a clockdomain.
>
> Signed-off-by: Rajendra Nayak<rnayak@ti.com>
> ---
> arch/arm/mach-omap2/clockdomain.c | 21 +++++++++++++++++++++
> arch/arm/mach-omap2/clockdomain.h | 3 +++
> 2 files changed, 24 insertions(+), 0 deletions(-)
>
> diff --git a/arch/arm/mach-omap2/clockdomain.c b/arch/arm/mach-omap2/clockdomain.c
> index ab87854..1de6def 100644
> --- a/arch/arm/mach-omap2/clockdomain.c
> +++ b/arch/arm/mach-omap2/clockdomain.c
> @@ -795,6 +795,27 @@ void clkdm_deny_idle(struct clockdomain *clkdm)
> arch_clkdm->clkdm_deny_idle(clkdm);
> }
>
> +/**
> + * clkdm_is_idle - Check if the clkdm hwsup/autoidle is enabled
> + * @clkdm: struct clockdomain *
> + *
> + * Returns true if the clockdomain is in hardware-supervised
> + * idle mode, or 0 otherwise.
> + *
> + */
> +int clkdm_is_idle(struct clockdomain *clkdm)
>
Name of the API not seems to fit correctly.
Shoule it be something like "clkdm_is_in_hwsup"?
next prev parent reply other threads:[~2011-04-05 13:40 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-05 12:44 [PATCH 0/4] OMAP2+: Fix clockdomain state programming Rajendra Nayak
2011-04-05 12:44 ` Rajendra Nayak
2011-04-05 12:44 ` [PATCH 1/4] OMAP2+: clockdomain: Add an api to read idle mode Rajendra Nayak
2011-04-05 12:44 ` Rajendra Nayak
2011-04-05 12:44 ` [PATCH 2/4] OMAP2+: clockdomain: Add SoC support for clkdm_is_idle Rajendra Nayak
2011-04-05 12:44 ` Rajendra Nayak
2011-04-05 12:44 ` [PATCH 3/4] OMAP2+: PM: Initialise sleep_switch to a non-valid value Rajendra Nayak
2011-04-05 12:44 ` Rajendra Nayak
2011-04-05 12:44 ` [PATCH 4/4] OMAP2+: PM: idle clkdms only if already in idle Rajendra Nayak
2011-04-05 12:44 ` Rajendra Nayak
2011-04-05 13:39 ` Santosh Shilimkar [this message]
2011-04-05 13:39 ` [PATCH 1/4] OMAP2+: clockdomain: Add an api to read idle mode Santosh Shilimkar
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=4D9B1BAC.3090700@ti.com \
--to=santosh.shilimkar@ti.com \
--cc=b-cousson@ti.com \
--cc=khilman@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=paul@pwsan.com \
--cc=rnayak@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.