public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: Roger Quadros <rogerq@ti.com>
Cc: Nishanth Menon <nm@ti.com>,
	linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
	linux-omap@vger.kernel.org
Subject: Re: [PATCH] ARM: dts: dra7-evm: Keep all VDD rails always-on
Date: Mon, 10 Nov 2014 12:39:23 -0800	[thread overview]
Message-ID: <20141110203922.GX31454@atomide.com> (raw)
In-Reply-To: <54579476.10702@ti.com>

* Roger Quadros <rogerq@ti.com> [141103 06:44]:
> Hi Nishant,
> 
> On 10/21/2014 05:38 PM, Nishanth Menon wrote:
> > DRA7 Data Manual (SPRS857L - August 2014) section 4.1.1 states: "All
> > unused power supply balls must be supplied with the voltages specified
> > in the Section 5.2, Recommended Operating Conditions".
> > 
> > This implies that all unused voltage rails for Vayu can never be
> > switched off even if the hardware blocks inside that voltage domain is
> > unused. Switching off these unused rails may result in stability issues
> > on other domains and increased leakage and power-on-hour impacts.
> > 
> > J6eco-evm dts file already considers this, however j6evm-dts file needs
> > to be fixed to consider this constraint of the SoC.
> > 
> > Signed-off-by: Nishanth Menon <nm@ti.com>
> 
> Acked-by: Roger Quadros <rogerq@ti.com>
> 
> I'm assuming that vddshv8 (MMC1 power group) can be switched off.

Applying into omap-for-v3.19/dt thanks.

Tony

      reply	other threads:[~2014-11-10 20:40 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-21 14:38 [PATCH] ARM: dts: dra7-evm: Keep all VDD rails always-on Nishanth Menon
2014-11-03 14:43 ` Roger Quadros
2014-11-10 20:39   ` Tony Lindgren [this message]

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=20141110203922.GX31454@atomide.com \
    --to=tony@atomide.com \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=nm@ti.com \
    --cc=rogerq@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox