From: "Cousson, Benoit" <b-cousson@ti.com>
To: Paul Walmsley <paul@pwsan.com>
Cc: "Hilman, Kevin" <khilman@ti.com>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: [PATCH 4/7] OMAP2+: powerdomain: add voltage domain lookup during register
Date: Tue, 22 Mar 2011 21:59:10 +0100 [thread overview]
Message-ID: <4D890D9E.804@ti.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1103221313460.11798@utopia.booyaka.com>
Hi Paul,
On 3/22/2011 8:23 PM, Paul Walmsley wrote:
> Hi Kevin,
>
> a couple of comments, now that i have the chance to look this over
> closely.
>
> Probably we should require every powerdomain to have a voltagedomain.
> This will avoid the problems we're having with the clocks, in which not
> every clock has a clockdomain pointer.
I do agree with you, but not for the same reason :-)
Every power domain belongs to a voltage domain, scalable or not, so
that's why we should always have it.
On the other hand not every clock belong to a clockdomain, that's why we
have clock without clockdomain on OMAP.
A clockdomain is a just group of IPs that share the same interface clock.
Benoit
> So I'd suggest splitting this patch up into two patches -- one to make the
> changes the powerdomain structure, and the second to add the code into the
> powerdomain.c. Between these two patches, we'd need patches to the
> powerdomain data to add the voltagedomain names in.
>
> then...
>
> On Fri, 18 Mar 2011, Kevin Hilman wrote:
>
>> When a powerdomain is registered, lookup the voltage domain by name
>> and keep a pointer to the containing voltagedomain in the powerdomain
>> structure.
>>
>> Modeled after similar method between powerdomain and clockdomain layers.
>>
>> Signed-off-by: Kevin Hilman<khilman@ti.com>
>>
>> ---
>> arch/arm/mach-omap2/powerdomain.c | 26 ++++++++++++++++++++++++++
>> arch/arm/mach-omap2/powerdomain.h | 8 ++++++++
>> arch/arm/mach-omap2/voltage.h | 1 +
>> 3 files changed, 35 insertions(+), 0 deletions(-)
>>
>> diff --git a/arch/arm/mach-omap2/powerdomain.c b/arch/arm/mach-omap2/powerdomain.c
>> index 49c6513..da86c72 100644
>> --- a/arch/arm/mach-omap2/powerdomain.c
>> +++ b/arch/arm/mach-omap2/powerdomain.c
>> @@ -77,6 +77,7 @@ static struct powerdomain *_pwrdm_lookup(const char *name)
>> static int _pwrdm_register(struct powerdomain *pwrdm)
>> {
>> int i;
>> + struct voltagedomain *voltdm;
>>
>> if (!pwrdm || !pwrdm->name)
>> return -EINVAL;
>> @@ -94,6 +95,16 @@ static int _pwrdm_register(struct powerdomain *pwrdm)
>> if (_pwrdm_lookup(pwrdm->name))
>> return -EEXIST;
>>
>> + if (pwrdm->voltdm.name) {
>
> we'd drop this
>
>> + voltdm = voltdm_lookup(pwrdm->voltdm.name);
>> + if (!voltdm) {
>> + pr_err("powerdomain: %s: voltagedomain %s does not exist\n",
>> + pwrdm->name, pwrdm->voltdm.name);
>> + return -EINVAL;
>> + }
>> + pwrdm->voltdm.ptr = voltdm;
>> + }
>> +
>> list_add(&pwrdm->node,&pwrdm_list);
>>
>> /* Initialize the powerdomain's state counter */
>> @@ -383,6 +394,21 @@ int pwrdm_for_each_clkdm(struct powerdomain *pwrdm,
>> }
>>
>> /**
>> + * pwrdm_get_voltdm - return a ptr to the voltdm that this pwrdm resides in
>> + * @pwrdm: struct powerdomain *
>> + *
>> + * Return a pointer to the struct voltageomain that the specified powerdomain
>> + * @pwrdm exists in, or returns NULL if @pwrdm is NULL.
>> + */
>> +struct voltagedomain *pwrdm_get_voltdm(struct powerdomain *pwrdm)
>> +{
>> + if (!pwrdm)
>> + return NULL;
>
> and this
>
>> +
>> + return pwrdm->voltdm.ptr;
>> +}
>> +
>> +/**
>> * pwrdm_get_mem_bank_count - get number of memory banks in this powerdomain
>> * @pwrdm: struct powerdomain *
>> *
>> diff --git a/arch/arm/mach-omap2/powerdomain.h b/arch/arm/mach-omap2/powerdomain.h
>> index 027f40b..3a1ec37 100644
>> --- a/arch/arm/mach-omap2/powerdomain.h
>> +++ b/arch/arm/mach-omap2/powerdomain.h
>> @@ -24,6 +24,8 @@
>>
>> #include<plat/cpu.h>
>>
>> +#include "voltage.h"
>> +
>> /* Powerdomain basic power states */
>> #define PWRDM_POWER_OFF 0x0
>> #define PWRDM_POWER_RET 0x1
>> @@ -78,6 +80,7 @@ struct powerdomain;
>> /**
>> * struct powerdomain - OMAP powerdomain
>> * @name: Powerdomain name
>> + * @voltdm: voltagedomain containing this powerdomain
>> * @omap_chip: represents the OMAP chip types containing this pwrdm
>> * @prcm_offs: the address offset from CM_BASE/PRM_BASE
>> * @prcm_partition: (OMAP4 only) the PRCM partition ID containing @prcm_offs
>> @@ -98,6 +101,10 @@ struct powerdomain;
>> */
>> struct powerdomain {
>> const char *name;
>> + union {
>> + const char *name;
>> + struct voltagedomain *ptr;
>> + } voltdm;
>> const struct omap_chip_id omap_chip;
>> const s16 prcm_offs;
>> const u8 pwrsts;
>> @@ -176,6 +183,7 @@ int pwrdm_del_clkdm(struct powerdomain *pwrdm, struct clockdomain *clkdm);
>> int pwrdm_for_each_clkdm(struct powerdomain *pwrdm,
>> int (*fn)(struct powerdomain *pwrdm,
>> struct clockdomain *clkdm));
>> +struct voltagedomain *pwrdm_get_voltdm(struct powerdomain *pwrdm);
>>
>> int pwrdm_get_mem_bank_count(struct powerdomain *pwrdm);
>>
>> diff --git a/arch/arm/mach-omap2/voltage.h b/arch/arm/mach-omap2/voltage.h
>> index 122d8c1..13e5ed9 100644
>> --- a/arch/arm/mach-omap2/voltage.h
>> +++ b/arch/arm/mach-omap2/voltage.h
>> @@ -182,4 +182,5 @@ extern void omap44xx_voltagedomains_init(void);
>>
>> struct voltagedomain *voltdm_lookup(const char *name);
>> void voltdm_init(struct voltagedomain **voltdm_list);
>> +int voltdm_add_pwrdm(struct voltagedomain *voltdm, struct powerdomain *pwrdm);
>> #endif
>> --
>> 1.7.4
>>
>> --
>> To unsubscribe from this list: send the line "unsubscribe linux-omap" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at http://vger.kernel.org/majordomo-info.html
>>
>
>
> - Paul
next prev parent reply other threads:[~2011-03-22 20:59 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-19 0:18 [PATCH 0/7] OMAP2+: voltage layer cleanup and restructure Kevin Hilman
2011-03-19 0:18 ` [PATCH 1/7] OMAP2+: hwmod: remove unused voltagedomain pointer Kevin Hilman
2011-03-21 13:08 ` Cousson, Benoit
2011-03-21 15:32 ` Kevin Hilman
2011-03-24 13:03 ` Gulati, Shweta
2011-03-24 14:00 ` Kevin Hilman
2011-03-24 15:14 ` Cousson, Benoit
2011-03-25 5:00 ` Gulati, Shweta
2011-03-22 19:13 ` Paul Walmsley
2011-03-19 0:18 ` [PATCH 2/7] OMAP2+: voltage: move PRCM mod offets into VDD structure Kevin Hilman
2011-03-19 4:41 ` Santosh Shilimkar
2011-03-21 15:21 ` Kevin Hilman
2011-03-21 10:53 ` Premi, Sanjeev
2011-03-21 15:26 ` Kevin Hilman
2011-03-23 14:16 ` Kevin Hilman
2011-03-19 0:18 ` [PATCH 3/7] OMAP2+: voltage: start towards a new voltagedomain layer Kevin Hilman
2011-03-19 0:18 ` [PATCH 4/7] OMAP2+: powerdomain: add voltage domain lookup during register Kevin Hilman
2011-03-22 19:23 ` Paul Walmsley
2011-03-22 20:59 ` Cousson, Benoit [this message]
2011-03-22 22:08 ` Paul Walmsley
2011-03-22 23:04 ` Cousson, Benoit
2011-04-02 1:17 ` Paul Walmsley
2011-03-23 0:17 ` Kevin Hilman
2011-03-19 0:18 ` [PATCH 5/7] OMAP2+: voltage: keep track of powerdomains in each voltagedomain Kevin Hilman
2011-03-22 19:35 ` Paul Walmsley
2011-03-23 0:18 ` Kevin Hilman
2011-03-19 0:18 ` [PATCH 6/7] OMAP2+: voltage: move prm_irqst_reg from VP into voltage domain Kevin Hilman
2011-03-19 0:18 ` [PATCH 7/7] OMAP3: powerdomain data: add voltage domains Kevin Hilman
2011-03-22 19:30 ` Paul Walmsley
2011-03-22 21:09 ` Cousson, Benoit
2011-03-22 22:15 ` Paul Walmsley
2011-03-23 0:20 ` Kevin Hilman
2011-03-23 0:31 ` [PATCH 0/7] OMAP2+: voltage layer cleanup and restructure 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=4D890D9E.804@ti.com \
--to=b-cousson@ti.com \
--cc=khilman@ti.com \
--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 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).