linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: ben@datarespons.no (Bjørn Erik Nilsen)
To: linux-arm-kernel@lists.infradead.org
Subject: imx6 power consumption
Date: Thu, 19 Dec 2013 09:15:14 +0100	[thread overview]
Message-ID: <mailman.20.1387440945.1056.linux-arm-kernel@lists.infradead.org> (raw)
In-Reply-To: <b43eb01926cf4b1f9413a66cc5791d9b@DM2PR03MB317.namprd03.prod.outlook.com>

Hi Anson,

On Thu, 2013-12-19 at 03:28 +0100, Anson.Huang at freescale.com wrote:
> 
> Best Regards.
> Anson huang ???
>  
> Freescale Semiconductor Shanghai
> ?????????192?A?2?
> 201203
> Tel:021-28937058
> 
> 
> >-----Original Message-----
> >From: linux-arm-kernel [mailto:linux-arm-kernel-bounces at lists.infradead.org]
> >On Behalf Of Shawn Guo
> >Sent: Wednesday, December 18, 2013 7:33 PM
> >To: Bj?rn Erik Nilsen
> >Cc: linux-arm-kernel at lists.infradead.org
> >Subject: Re: imx6 power consumption
> >
> >On Wed, Dec 18, 2013 at 12:12:05PM +0100, Bj?rn Erik Nilsen wrote:
> >> As far as I can tell, commit e95dddb34c8 "ARM: imx: enable anatop
> >> suspend/resume" is the common ancestor for mainline and freescale, and
> >> from there pm-imx6q.c starts to diverge.
> >>
> >> I haven not looked at it in great detail yet, but it seems there are
> >> not too many patches missing in mainline. Any idea why remaining
> >> patches haven't been upstreamed?
> >
> >Probably because no one cares and would spend time to upstream these patches.
> 
> This root cause is we did NOT put the DSM code in IRAM and free DDR IO in DSM.
> We have done this in our internal v3.10 kernel, so I will do the upstream soon,
> Below is the DSM number of i.MX6Q SabreSD we got on v3.10 release:
> 
> VDDARM_IN(R27)             0mA at 0.97V
> VDDSOC_IN(R21)             4.2 at 0.97V
> DDR(R25)                   14.8mA at 1.5V
> VDDHIGH_IN + SNVS(SH17)    0.35mA at 2.98V, 0.9mA


I successfully managed to cherry-pick a handful of commits from
freescale 3.10 and got down to approximately half the consumption.
That's already very good news.

Looking forward to see these patches upstream. Will you be able upstream
them before 3.14 you think?

Good work!

Best regards,
Bj?rn Erik Nilsen

  reply	other threads:[~2013-12-19  8:15 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <E1VszO5-00060R-Gp@merlin.infradead.org>
2013-12-18  2:45 ` imx6 power consumption Shawn Guo
2013-12-18 11:12   ` Bjørn Erik Nilsen
     [not found]   ` <E1VtF3I-0002MQ-Ra@merlin.infradead.org>
2013-12-18 11:32     ` Shawn Guo
2013-12-19  2:28       ` Anson.Huang at freescale.com
2013-12-19  8:15         ` Bjørn Erik Nilsen [this message]
     [not found]         ` <1387440914.4131.4.camel@bnilsen-HP>
2014-01-29 16:17           ` Bjørn Erik Nilsen
     [not found]           ` <E1W8XqE-0000Ml-GE@merlin.infradead.org>
2014-01-29 16:21             ` Fabio Estevam
2014-01-29 16:33               ` Bjørn Erik Nilsen
2013-12-17 18:28 Bjørn Erik Nilsen

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=mailman.20.1387440945.1056.linux-arm-kernel@lists.infradead.org \
    --to=ben@datarespons.no \
    --cc=linux-arm-kernel@lists.infradead.org \
    /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).