From: Jani Nikula <jani.nikula@linux.intel.com>
To: "Stéphane Marchesin" <marcheu@chromium.org>
Cc: "Tahvanainen, Jari" <jari.tahvanainen@intel.com>,
Matt Atwood <matthew.s.atwood@intel.corp-partner.google.com>,
"intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>
Subject: Re: [PATCH] drm/i915: decouple runtime PM enablement from DMC presence
Date: Fri, 18 Aug 2017 12:07:34 +0300 [thread overview]
Message-ID: <878tih8crt.fsf@nikula.org> (raw)
In-Reply-To: <CADMs+9bYgz0VK+z7ruF07DJm8jeRasrZga1ntJUCjbr9QzZLvQ@mail.gmail.com>
On Thu, 17 Aug 2017, Stéphane Marchesin <marcheu@chromium.org> wrote:
> On Mon, Jun 19, 2017 at 11:45 AM, Jani Nikula
> <jani.nikula@linux.intel.com> wrote:
>>
>> 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.
>>
>
> For context, we are seeing GPU hangs at suspend/resume with DMC
> enabled (feel free to email me if you want to be added to the internal
> bug) which is the reason for this patch. If those GPU hangs can be
> fixed instead, then that would be an even better solution, IMO. Is
> there someone on your side who could help with these hangs?
We need to get the GPU hangs fixed, obviously. Is this reproducible with
upstream code? Do we have a bug about this at bugs.freedesktop.org?
Jani, Jari?
BR,
Jani.
>
> Stéphane
>
>>
>> BR,
>> Jani.
>>
>> --
>> Jani Nikula, Intel Open Source Technology Center
--
Jani Nikula, Intel Open Source Technology Center
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2017-08-18 9:02 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
2017-08-18 1:00 ` Stéphane Marchesin
2017-08-18 9:07 ` Jani Nikula [this message]
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=878tih8crt.fsf@nikula.org \
--to=jani.nikula@linux.intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jari.tahvanainen@intel.com \
--cc=marcheu@chromium.org \
--cc=matthew.s.atwood@intel.corp-partner.google.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.