From: Chris Wilson <chris@chris-wilson.co.uk>
To: "K, SrinivasX" <srinivasx.k@intel.com>,
Rodrigo Vivi <rodrigo.vivi@intel.com>
Cc: "Pandey, Hariom" <hariom.pandey@intel.com>,
"Ausmus, James" <james.ausmus@intel.com>,
"Nikula, Jani" <jani.nikula@intel.com>,
intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
"Souza, Jose" <jose.souza@intel.com>,
"Surendrakumar Upadhyay,
TejaskumarX" <tejaskumarx.surendrakumar.upadhyay@intel.com>
Subject: Re: [Intel-gfx] [PATCH] drm/i915/ehl: Remove require_force_probe protection
Date: Mon, 19 Oct 2020 19:33:32 +0100 [thread overview]
Message-ID: <160313241261.4425.3184593266306110227@build.alporthouse.com> (raw)
In-Reply-To: <20201019182936.GA3149316@intel.com>
Quoting Rodrigo Vivi (2020-10-19 19:29:36)
>
> I just checked the CI picture and it looks much better indeed.
>
> Only bad case being the gt_pm, which is also failing on other platforms.
Not nearly in the same manner. CI is indicating that there is no RC6
entry and no power saving at all; neither in the selftests nor visible
from userspace. That is a critical battery eating bug.
If there's a patch to fix it for ehl and jsl, send it to CI for proving.
-Chris
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2020-10-19 18:33 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-06 14:56 [PATCH] drm/i915/ehl: Remove require_force_probe protection Kamati Srinivas
2020-10-06 17:46 ` [Intel-gfx] " Souza, Jose
2020-10-06 17:48 ` Chris Wilson
2020-10-06 17:55 ` Vivi, Rodrigo
2020-10-06 18:02 ` Souza, Jose
2020-10-09 8:31 ` K, SrinivasX
2020-10-09 13:38 ` Vivi, Rodrigo
2020-10-09 18:08 ` Pandey, Hariom
2020-10-15 8:41 ` K, SrinivasX
2020-10-19 18:29 ` Rodrigo Vivi
2020-10-19 18:33 ` Chris Wilson [this message]
[not found] ` <CO1PR11MB50750A169A14FCC84C70C936F61F0@CO1PR11MB5075.namprd11.prod.outlook.com>
[not found] ` <CO1PR11MB5075AAFA3500F4A3A610FC52F6170@CO1PR11MB5075.namprd11.prod.outlook.com>
2020-10-28 11:53 ` Vivi, Rodrigo
2020-10-28 11:55 ` Pandey, Hariom
2020-11-27 20:36 ` Chris Wilson
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=160313241261.4425.3184593266306110227@build.alporthouse.com \
--to=chris@chris-wilson.co.uk \
--cc=dri-devel@lists.freedesktop.org \
--cc=hariom.pandey@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=james.ausmus@intel.com \
--cc=jani.nikula@intel.com \
--cc=jose.souza@intel.com \
--cc=rodrigo.vivi@intel.com \
--cc=srinivasx.k@intel.com \
--cc=tejaskumarx.surendrakumar.upadhyay@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 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).