All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@linux.intel.com>
To: imre.deak@intel.com, Rodrigo Vivi <rodrigo.vivi@gmail.com>
Cc: "intel-gfx@lists.freedesktop.org"
	<intel-gfx@lists.freedesktop.org>,
	"marcheu@google.com" <marcheu@google.com>,
	Matt Atwood <matthew.s.atwood@intel.corp-partner.google.com>
Subject: Re: [PATCH] drm/i915: decouple runtime PM enablement from DMC presence
Date: Mon, 19 Jun 2017 21:45:51 +0300	[thread overview]
Message-ID: <8737avrf34.fsf@intel.com> (raw)
In-Reply-To: <20170615173858.GD10859@ideak-desk.fi.intel.com>

On Thu, 15 Jun 2017, Imre Deak <imre.deak@intel.com> wrote:
> On Thu, Jun 15, 2017 at 10:20:57AM -0700, Rodrigo Vivi wrote:
>> I believe it is worth allowing RPM to work without requiring DMC, no?!
>
> Not if there is no good reason for not using DMC. It was decided early
> on that we won't support that configuration since if you care about the
> power saving provided by partially disabling things you probably also
> care about the bigger power saving provided by DMC. So that is the
> current state of the driver, enabling runtime PM without having DMC
> loaded is not supported. Proper support for that would need to be added
> after a justification why not to use the firmware.

Agreed. We already have too many configurations to support, and we
already struggle with our testing coverage as-is. Adding new
configurations to be tested is not to be taken lightly.

BR,
Jani.

-- 
Jani Nikula, Intel Open Source Technology Center
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2017-06-19 18:45 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-14 17:12 [PATCH] drm/i915: decouple runtime PM enablement from DMC presence matthew.s.atwood
2017-06-14 17:33 ` Imre Deak
2017-06-14 17:40   ` Atwood, Matthew S
2017-06-14 17:55     ` Imre Deak
2017-06-14 20:02       ` Rodrigo Vivi
2017-06-14 20:07         ` Atwood, Matthew S
2017-06-14 20:17         ` Imre Deak
2017-06-15 16:16           ` Atwood, Matthew S
2017-06-15 16:30             ` Imre Deak
2017-06-15 17:20               ` Rodrigo Vivi
2017-06-15 17:38                 ` Imre Deak
2017-06-19 18:45                   ` Jani Nikula [this message]
2017-08-18  1:00                     ` Stéphane Marchesin
2017-08-18  9:07                       ` Jani Nikula
2017-08-18 14:26                         ` Tahvanainen, Jari
2017-08-18 14:35                           ` Chris Wilson
2017-08-19  1:00                         ` Stéphane Marchesin
2017-06-14 17:40 ` ✗ Fi.CI.BAT: failure for " Patchwork

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=8737avrf34.fsf@intel.com \
    --to=jani.nikula@linux.intel.com \
    --cc=imre.deak@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=marcheu@google.com \
    --cc=matthew.s.atwood@intel.corp-partner.google.com \
    --cc=rodrigo.vivi@gmail.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.