All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kevin Hilman <khilman@ti.com>
To: "Gulati, Shweta" <shweta.gulati@ti.com>
Cc: "Cousson, Benoit" <b-cousson@ti.com>,
	"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
	Paul Walmsely <paul@pwsan.com>
Subject: Re: [PATCH 1/7] OMAP2+: hwmod: remove unused voltagedomain pointer
Date: Thu, 24 Mar 2011 07:00:55 -0700	[thread overview]
Message-ID: <87tyes39ew.fsf@ti.com> (raw)
In-Reply-To: <AANLkTi==Mz=szoa78EaRKgqTddOeu5xEeg5hfNWbWWO2@mail.gmail.com> (Shweta Gulati's message of "Thu, 24 Mar 2011 18:33:06 +0530")

Hi Shweta,

"Gulati, Shweta" <shweta.gulati@ti.com> writes:

[...]

>>>
>>> And what about vdd_name? It should probably be removed as well.
>>>
>>
>> Yes, but it's currently used by the SR layer (currently the only user.)
>>
>> Removing it required cleaning up the SR layer as well, so I decided to
>> leave the SR cleanups for someone else for the moment while I focus on
>> the voltage layer(s)
>>
> Even if we try to remove 'vdd_name', how should we get 'struct voltagedomain'
> info corresponding to sr_mpu, sr_core in sr_dev_init API?
>
> As functional clock of SR1 and SR2 are from wake up domain, so even if
> we try to use current Clockdomain and Powerdomain framework APIs, to
> get 'clkdomain' pointer and then retrieve 'pwrdomain' pointer, finally
> getting 'voltdomain' pointer we would get 'WKUP' voltage domain ptr
> not the 'mpu' or 'core' voltdomain pointer.

Correct.

I got this far and realized not only does the voltage layer need a
cleanup, the SR layer needs a cleanup, but I need to focus on one thing
at a time.

As you noticed, what we need is the voltage domain of the SR sensor, not
the voltage domain of the SR IP.  

Probably the best way to do this is ad the sensor voltage domain to the 
dev_attr of each SR module.

Kevin

  reply	other threads:[~2011-03-24 14:00 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 [this message]
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
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=87tyes39ew.fsf@ti.com \
    --to=khilman@ti.com \
    --cc=b-cousson@ti.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=paul@pwsan.com \
    --cc=shweta.gulati@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.