From: Kevin Hilman <khilman@deeprootsystems.com>
To: Thara Gopinath <thara@ti.com>
Cc: linux-omap@vger.kernel.org, paul@pwsan.com, b-cousson@ti.com,
vishwanath.bs@ti.com, sawant@ti.com
Subject: Re: [PM-SR] [PATCH] OMAP: PM: Remove the usage of vdd id's.
Date: Fri, 25 Jun 2010 11:25:32 -0700 [thread overview]
Message-ID: <87hbkrm0kj.fsf@deeprootsystems.com> (raw)
In-Reply-To: <1277391768-3361-1-git-send-email-thara@ti.com> (Thara Gopinath's message of "Thu, 24 Jun 2010 20:32:48 +0530")
Thara Gopinath <thara@ti.com> writes:
> This patch removes the usage of vdd and sr id alltogether.
> This is achieved by introducing a separte voltage domain per
> VDD and hooking this up with the voltage and smartreflex
> internal info structure. Any user of voltage or smartreflex layer
> should call into omap_volt_domain_get to get the voltage
> domain handle and make use of this to call into the various
> exported API's.
Great, I'm glad to see those gone.
Minor comment on naming:
In current code, we currently have
struct clockdomain *clkdm;
struct powerdomain *pwrdm;
so, for consistency, I'd suggest using
struct voltagedomain *voltdm;
instead of this:
struct omap_volt_domain *volt_domain;
Also, it looks like your 'struct omap_vdd_info' is the real struct that
represents a voltage domain.
Maybe you're planning this already, but I suggest you get rid of
omap_vdd_info and just move all that stuff into the voltagedomain.
Again, that will probably create a diff with a ton of renames, so this
should just be part of your V2 series.
> These changes should be part of V2 of the sr/voltage series
> instead of being a separate patch in itself.
Agreed.
Kevin
next prev parent reply other threads:[~2010-06-25 18:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-24 15:02 [PM-SR] [PATCH] OMAP: PM: Remove the usage of vdd id's Thara Gopinath
2010-06-25 13:15 ` Menon, Nishanth
2010-06-25 13:15 ` Menon, Nishanth
2010-06-25 18:25 ` Kevin Hilman [this message]
2010-08-04 4:31 ` Gopinath, Thara
2010-08-04 14:14 ` Cousson, Benoit
2010-08-04 21:08 ` Kevin Hilman
2010-06-25 18:49 ` Kevin Hilman
2010-06-25 21:25 ` Cousson, Benoit
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=87hbkrm0kj.fsf@deeprootsystems.com \
--to=khilman@deeprootsystems.com \
--cc=b-cousson@ti.com \
--cc=linux-omap@vger.kernel.org \
--cc=paul@pwsan.com \
--cc=sawant@ti.com \
--cc=thara@ti.com \
--cc=vishwanath.bs@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.