From: Eric Rannaud <eric.rannaud@gmail.com>
To: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
Cc: Jani Nikula <jani.nikula@intel.com>,
Daniel Vetter <daniel.vetter@ffwll.ch>,
"intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Jon Kristensen <info@jonkri.com>
Subject: Re: i915: Regression: +4W in idle power use on Macbook Pro 15 (late 2013)
Date: Tue, 26 Aug 2014 06:38:07 -0700 [thread overview]
Message-ID: <CA+zRj8UN-49tWhwpWPz-oyBvPFydijaw5j44J87U9oAHwD7aDw@mail.gmail.com> (raw)
In-Reply-To: <20140826110604.GI4193@intel.com>
On Tue, Aug 26, 2014 at 4:06 AM, Ville Syrjälä
<ville.syrjala@linux.intel.com> wrote:
> FBC works best when the screen contents don't change. The more activity
> on the screen the less effective FBC becomes. 4W sounds way too much for
> FBC however. 0.4W is closer to what one might expect from FBC based on my
> observations. 4W sounds more like the difference between min vs. max
> display brightness to me.
That's why I'm here, because it is such a dramatic change. All
measurements were taken at constant brightness (4/100) and the
difference is indeed a full 4W, as reported by the battery (and seen
in: powertop(1),
/sys/bus/acpi/drivers/battery/PNP0C0A\:00/power_supply/BAT0/power_now,
and a noticeably faster drop in battery charge over time).
Could the FBC commit somehow also disable RC6, or similar?
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2014-08-26 13:38 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-22 17:40 i915: Regression: +4W in idle power use on Macbook Pro 15 (late 2013) Eric Rannaud
2014-08-25 10:19 ` Jani Nikula
2014-08-25 10:22 ` Jani Nikula
2014-08-25 12:19 ` Eric Rannaud
2014-08-26 11:06 ` Ville Syrjälä
2014-08-26 13:38 ` Eric Rannaud [this message]
2014-08-26 14:57 ` Eric Rannaud
2014-08-26 20:59 ` Daniel Vetter
2014-08-26 23:00 ` Eric Rannaud
2014-08-27 9:17 ` Ville Syrjälä
2014-08-27 17:50 ` Eric Rannaud
2014-08-28 20:08 ` Lu, Ran
2014-08-28 16:41 ` Sean V Kelley
2014-08-28 17:19 ` Eric Rannaud
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=CA+zRj8UN-49tWhwpWPz-oyBvPFydijaw5j44J87U9oAHwD7aDw@mail.gmail.com \
--to=eric.rannaud@gmail.com \
--cc=daniel.vetter@ffwll.ch \
--cc=gregkh@linuxfoundation.org \
--cc=info@jonkri.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@intel.com \
--cc=ville.syrjala@linux.intel.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.