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: Wed, 18 Dec 2013 12:12:05 +0100	[thread overview]
Message-ID: <mailman.19.1387365151.1056.linux-arm-kernel@lists.infradead.org> (raw)
In-Reply-To: <20131218024546.GA6691@S2101-09.ap.freescale.net>

On Wed, 2013-12-18 at 03:45 +0100, Shawn Guo wrote:
> On Tue, Dec 17, 2013 at 07:28:27PM +0100, Bj?rn Erik Nilsen wrote:
> > Hi,
> > 
> > I have measured power consumption for imx6 in mem mode on the 3.12.4 mainstream kernel vs. 3.0.35 kernel from freescale/boundary devices. I noticed a significant increase going from 3.0 to 3.12 . I have at least identified one big difference: DDR is no longer tri-stated, which accounts for some of the difference.
> > 
> > I use 'echo mem > /sys/power/state' for my test case.
> > 
> > Do you know if someone is looking into this issue, or if there are pending patches somewhere?
> 
> It's an unimplemented feature rather than an issue.  There are some
> patches on Freescale 3.10 kernel, and you're welcomed to bring these
> patches to mainline kernel.


Right.

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?

If it is just a matter of someone doing the work, what would be the
recommended approach?


Best regards,
Bj?rn Erik Nilsen

  reply	other threads:[~2013-12-18 11:12 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 [this message]
     [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
     [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.19.1387365151.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).