All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nishanth Menon <nm@ti.com>
To: Paul Walmsley <paul@pwsan.com>
Cc: Rajendra Nayak <rnayak@ti.com>,
	khilman@linaro.org, hvaibhav@ti.com, linux-omap@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 0/2] Remove unused voltagedomain data for AM33xx
Date: Fri, 14 Jun 2013 08:14:57 -0500	[thread overview]
Message-ID: <20130614131457.GA7569@kahuna> (raw)
In-Reply-To: <alpine.DEB.2.02.1306140243380.5514@utopia.booyaka.com>

On 02:46-20130614, Paul Walmsley wrote:
> cc Kevin, Vaibhav
> 
> On Thu, 13 Jun 2013, Rajendra Nayak wrote:
> 
> > The powerdomain framework today expects to always have a voltagedomain
> > associated with a given powerdomain. We already have AM33xx which
> > has no Voltage Controller/Voltage Processor as part of PRCM.
> > There are more SoCs' to follow starting with AM437x and DRA7xx
> > which do not have VC/VP.
> > 
> > Instead of adding dummy voltage domain data files, make the powerdomain
> > framework aware of the fact that some SoCs' might not really have
> > scalable voltage domains.
> 
> Fine with me in principle if AM335x doesn't support voltage scaling.  
> Vaibhav, if this is okay for you, please ack it.  
just a nitpick :)
There is no VFSM auto scaling to retention voltage, nor is VC-VP IP
available here, but that does not mean DVFS voltage scaling does not
exist - it is done with traditional regulator framework using regular
shared I2C.

We now seem to be moving to a generation of SoCs where VC-VP has been
dumped in favor of allowing integration with PMIC which may talk SPI/I2C
over standard interfaces - this allows us to reach better product
options, but gives up on extreme low power scenarios we had seen in the
past on OMAP.
Overall, I love this idea.
Acked-by: Nishanth Menon <nm@ti.com>
> 
> Then, in terms of merging, probably Kevin would be the right person for 
> this since he's done much of the voltagedomain work.
-- 
Regards,
Nishanth Menon

WARNING: multiple messages have this Message-ID (diff)
From: nm@ti.com (Nishanth Menon)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/2] Remove unused voltagedomain data for AM33xx
Date: Fri, 14 Jun 2013 08:14:57 -0500	[thread overview]
Message-ID: <20130614131457.GA7569@kahuna> (raw)
In-Reply-To: <alpine.DEB.2.02.1306140243380.5514@utopia.booyaka.com>

On 02:46-20130614, Paul Walmsley wrote:
> cc Kevin, Vaibhav
> 
> On Thu, 13 Jun 2013, Rajendra Nayak wrote:
> 
> > The powerdomain framework today expects to always have a voltagedomain
> > associated with a given powerdomain. We already have AM33xx which
> > has no Voltage Controller/Voltage Processor as part of PRCM.
> > There are more SoCs' to follow starting with AM437x and DRA7xx
> > which do not have VC/VP.
> > 
> > Instead of adding dummy voltage domain data files, make the powerdomain
> > framework aware of the fact that some SoCs' might not really have
> > scalable voltage domains.
> 
> Fine with me in principle if AM335x doesn't support voltage scaling.  
> Vaibhav, if this is okay for you, please ack it.  
just a nitpick :)
There is no VFSM auto scaling to retention voltage, nor is VC-VP IP
available here, but that does not mean DVFS voltage scaling does not
exist - it is done with traditional regulator framework using regular
shared I2C.

We now seem to be moving to a generation of SoCs where VC-VP has been
dumped in favor of allowing integration with PMIC which may talk SPI/I2C
over standard interfaces - this allows us to reach better product
options, but gives up on extreme low power scenarios we had seen in the
past on OMAP.
Overall, I love this idea.
Acked-by: Nishanth Menon <nm@ti.com>
> 
> Then, in terms of merging, probably Kevin would be the right person for 
> this since he's done much of the voltagedomain work.
-- 
Regards,
Nishanth Menon

  reply	other threads:[~2013-06-14 13:15 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-13 10:08 [PATCH 0/2] Remove unused voltagedomain data for AM33xx Rajendra Nayak
2013-06-13 10:08 ` Rajendra Nayak
2013-06-13 10:08 ` [PATCH 1/2] ARM: OMAP2+: Powerdomain: Remove the need to always have a voltdm associated to a pwrdm Rajendra Nayak
2013-06-13 10:08   ` Rajendra Nayak
2013-06-14 13:59   ` Kevin Hilman
2013-06-14 13:59     ` Kevin Hilman
2013-06-13 10:08 ` [PATCH 2/2] ARM: AM33xx: Remove the unused voltagedomain data Rajendra Nayak
2013-06-13 10:08   ` Rajendra Nayak
2013-06-14  2:46 ` [PATCH 0/2] Remove unused voltagedomain data for AM33xx Paul Walmsley
2013-06-14  2:46   ` Paul Walmsley
2013-06-14 13:14   ` Nishanth Menon [this message]
2013-06-14 13:14     ` Nishanth Menon
2013-06-14 14:01   ` Kevin Hilman
2013-06-14 14:01     ` Kevin Hilman
2013-06-17  5:08     ` Hiremath, Vaibhav
2013-06-17  5:08       ` Hiremath, Vaibhav
2013-06-17  5:12       ` Rajendra Nayak
2013-06-17  5:12         ` Rajendra Nayak

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=20130614131457.GA7569@kahuna \
    --to=nm@ti.com \
    --cc=hvaibhav@ti.com \
    --cc=khilman@linaro.org \
    --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.