From: Sergei Shtylyov <sshtylyov@mvista.com>
To: jean.pihet@newoldbits.com
Cc: linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
Kevin Hilman <khilman@ti.com>,
paul@pwsan.com, Jean Pihet <j-pihet@ti.com>
Subject: Re: [PATCH 4/8] OMAP2+: omap_hwmod: manage the omap_devices the wake-up latency constraints
Date: Thu, 31 Mar 2011 15:20:06 +0400 [thread overview]
Message-ID: <4D946366.4000805@ru.mvista.com> (raw)
In-Reply-To: <1301498364-726-5-git-send-email-j-pihet@ti.com>
Hello.
On 30-03-2011 19:19, jean.pihet@newoldbits.com wrote:
> From: Jean Pihet<j-pihet@ti.com>
> Hwmod is queried from the omap device layer to manage the power domains
> wake-up latency constraints. Hwmod retrieves the correct power domain
> and if it exists it calls the corresponding power domain function.
> Tested on OMAP3 Beagleboard in RET/OFF using wake-up latency constraints
> on MPU, CORE and PER.
> Signed-off-by: Jean Pihet<j-pihet@ti.com>
[...]
> diff --git a/arch/arm/mach-omap2/omap_hwmod.c b/arch/arm/mach-omap2/omap_hwmod.c
> index e034294..62de888 100644
> --- a/arch/arm/mach-omap2/omap_hwmod.c
> +++ b/arch/arm/mach-omap2/omap_hwmod.c
[...]
> @@ -2322,11 +2323,34 @@ ohsps_unlock:
> return ret;
> }
>
> +/*
> + * omap_hwmod_set_wkup_constraint- set/release a wake-up latency constraint
> + *
> + * @oh: struct omap_hwmod* to which the target device belongs to.
> + * @cookie: identifier of the constraints list for @oh.
> + * @min_latency: the minimum allowed wake-up latency for @oh.
> + *
> + * Returns 0 upon success.
> + */
> +int omap_hwmod_set_wkup_lat_constraint(struct omap_hwmod *oh,
> + void *cookie, long min_latency)
> +{
> + struct powerdomain *pwrdm = omap_hwmod_get_pwrdm(oh);
> +
> + if (!PTR_ERR(pwrdm)) {
What's the point of calling PTR_ERR() at all, if just '!pwrdm' will give
the same result?
WBR, Sergei
WARNING: multiple messages have this Message-ID (diff)
From: sshtylyov@mvista.com (Sergei Shtylyov)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 4/8] OMAP2+: omap_hwmod: manage the omap_devices the wake-up latency constraints
Date: Thu, 31 Mar 2011 15:20:06 +0400 [thread overview]
Message-ID: <4D946366.4000805@ru.mvista.com> (raw)
In-Reply-To: <1301498364-726-5-git-send-email-j-pihet@ti.com>
Hello.
On 30-03-2011 19:19, jean.pihet at newoldbits.com wrote:
> From: Jean Pihet<j-pihet@ti.com>
> Hwmod is queried from the omap device layer to manage the power domains
> wake-up latency constraints. Hwmod retrieves the correct power domain
> and if it exists it calls the corresponding power domain function.
> Tested on OMAP3 Beagleboard in RET/OFF using wake-up latency constraints
> on MPU, CORE and PER.
> Signed-off-by: Jean Pihet<j-pihet@ti.com>
[...]
> diff --git a/arch/arm/mach-omap2/omap_hwmod.c b/arch/arm/mach-omap2/omap_hwmod.c
> index e034294..62de888 100644
> --- a/arch/arm/mach-omap2/omap_hwmod.c
> +++ b/arch/arm/mach-omap2/omap_hwmod.c
[...]
> @@ -2322,11 +2323,34 @@ ohsps_unlock:
> return ret;
> }
>
> +/*
> + * omap_hwmod_set_wkup_constraint- set/release a wake-up latency constraint
> + *
> + * @oh: struct omap_hwmod* to which the target device belongs to.
> + * @cookie: identifier of the constraints list for @oh.
> + * @min_latency: the minimum allowed wake-up latency for @oh.
> + *
> + * Returns 0 upon success.
> + */
> +int omap_hwmod_set_wkup_lat_constraint(struct omap_hwmod *oh,
> + void *cookie, long min_latency)
> +{
> + struct powerdomain *pwrdm = omap_hwmod_get_pwrdm(oh);
> +
> + if (!PTR_ERR(pwrdm)) {
What's the point of calling PTR_ERR() at all, if just '!pwrdm' will give
the same result?
WBR, Sergei
next prev parent reply other threads:[~2011-03-31 11:21 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-30 15:19 [PATCH v3 0/8] OMAP: add PM CONSTRAINTS framework jean.pihet
2011-03-30 15:19 ` jean.pihet at newoldbits.com
2011-03-30 15:19 ` [PATCH 1/8] OMAP PM: create a PM layer plugin for per-device constraints jean.pihet
2011-03-30 15:19 ` jean.pihet at newoldbits.com
2011-03-30 15:19 ` [PATCH 2/8] OMAP2+: powerdomain: control power domains next state jean.pihet
2011-03-30 15:19 ` jean.pihet at newoldbits.com
2011-03-30 15:19 ` [PATCH 3/8] OMAP3: powerdomain data: add wake-up latency figures jean.pihet
2011-03-30 15:19 ` jean.pihet at newoldbits.com
2011-03-30 15:19 ` [PATCH 4/8] OMAP2+: omap_hwmod: manage the omap_devices the wake-up latency constraints jean.pihet
2011-03-30 15:19 ` jean.pihet at newoldbits.com
2011-03-31 11:20 ` Sergei Shtylyov [this message]
2011-03-31 11:20 ` Sergei Shtylyov
2011-03-31 11:29 ` Russell King - ARM Linux
2011-03-31 11:29 ` Russell King - ARM Linux
2011-03-30 15:19 ` [PATCH 5/8] OMAP: PM CONSTRAINTS: add an enum for the classes of constraint jean.pihet
2011-03-30 15:19 ` jean.pihet at newoldbits.com
2011-03-30 15:19 ` [PATCH 6/8] OMAP2+: omap_device: implement the constraints management code jean.pihet
2011-03-30 15:19 ` jean.pihet at newoldbits.com
2011-03-30 15:19 ` [PATCH 7/8] OMAP: PM CONSTRAINTS: implement wake-up latency constraints jean.pihet
2011-03-30 15:19 ` jean.pihet at newoldbits.com
2011-03-30 15:19 ` [PATCH 8/8] OMAP PM: early init of the pwrdms states jean.pihet
2011-03-30 15:19 ` jean.pihet at newoldbits.com
-- strict thread matches above, loose matches on Subject: below --
2011-05-04 13:35 [PATCH v4 0/8] OMAP: add PM_CONSTRAINTS framework jean.pihet
2011-05-04 13:35 ` [PATCH 4/8] OMAP2+: omap_hwmod: manage the omap_devices the wake-up latency constraints jean.pihet
2011-05-04 13:35 ` jean.pihet at newoldbits.com
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=4D946366.4000805@ru.mvista.com \
--to=sshtylyov@mvista.com \
--cc=j-pihet@ti.com \
--cc=jean.pihet@newoldbits.com \
--cc=khilman@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=paul@pwsan.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.