Using struct drm_device.pdev is deprecated. Convert i915 to struct
drm_device.dev. No functional changes.
Signed-off-by: Thomas Zimmermann
Cc: Jani Nikula
Cc: Joonas Lahtinen
Cc: Rodrigo Vivi
---
drivers/gpu/drm/i915/gvt/cfg_space.c | 5 +++--
drivers/gpu/drm/i915/gvt/firmware.c | 10
Using struct drm_device.pdev is deprecated. Convert hibmc to struct
drm_device.dev. No functional changes.
v3:
* rebased
Signed-off-by: Thomas Zimmermann
Reviewed-by: Tian Tao
Acked-by: Sam Ravnborg
Cc: Xinliang Liu
Cc: Tian Tao
Cc: John Stultz
Cc: Xinwei Kong
Cc: Chen Feng
---
Using struct drm_device.pdev is deprecated. Convert i915 to struct
drm_device.dev. No functional changes.
Signed-off-by: Thomas Zimmermann
Cc: Jani Nikula
Cc: Joonas Lahtinen
Cc: Rodrigo Vivi
---
drivers/gpu/drm/i915/gt/intel_engine_cs.c | 2 +-
drivers/gpu/drm/i915/gt/intel_ggtt.c |
Using struct drm_device.pdev is deprecated. Convert nouveau to struct
drm_device.dev. No functional changes.
v3:
* fix nv04_dfp_update_backlight() as well (Jeremy)
Signed-off-by: Thomas Zimmermann
Reviewed-by: Jeremy Cline
Cc: Ben Skeggs
---
drivers/gpu/drm/nouveau/dispnv04/arb.c
Using struct drm_device.pdev is deprecated. Convert i915 to struct
drm_device.dev. No functional changes.
v3:
* rebased
v2:
* move gt/ and gvt/ changes into separate patches
Signed-off-by: Thomas Zimmermann
Cc: Jani Nikula
Cc: Joonas Lahtinen
Cc: Rodrigo Vivi
---
We have DRM drivers based on USB, SPI and platform devices. All of them
are fine with storing their device reference in struct drm_device.dev.
PCI devices should be no exception. Therefore struct drm_device.pdev is
deprecated.
Instead upcast from struct drm_device.dev with to_pci_dev().
Adhere to kernel coding style.
Signed-off-by: Thomas Zimmermann
Reviewed-by: Christian König
Acked-by: Alex Deucher
Acked-by: Sam Ravnborg
Cc: Alex Deucher
Cc: Christian König
---
drivers/gpu/drm/amd/amdgpu/amdgpu_device.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff
Using struct drm_device.pdev is deprecated. Convert amdgpu to struct
drm_device.dev. No functional changes.
v3:
* rebased
Signed-off-by: Thomas Zimmermann
Acked-by: Christian König
Acked-by: Alex Deucher
Acked-by: Sam Ravnborg
Cc: Alex Deucher
Cc: Christian König
---
I merged many of the patches that were ready in v2 into drm-misc-next. In
v3 remain only patches that need an r-b/a-b (i915/gt/gvt) or required
a change from v2.
The pdev field in struct drm_device points to a PCI device structure and
goes back to UMS-only days when all DRM drivers were for PCI
== Series Details ==
Series: drm/i915/selftests: Skip unstable timing measurements
URL : https://patchwork.freedesktop.org/series/85554/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_9554_full -> Patchwork_19274_full
On 06/01/2021 16:08, Chris Wilson wrote:
Quoting Tvrtko Ursulin (2021-01-06 15:57:49)
[snip]
@@ -1363,16 +1336,16 @@ static void execlists_dequeue(struct intel_engine_cs
*engine)
__unwind_incomplete_requests(engine);
last = NULL;
-
Since we already report the per-engine runtime via PMU (using sampling
if a direct measure is not available), and in debugfs, also trivially
include the information for each engine under sysfs as a read-only
property. We only present the total milliseconds to hide any misleading
accuracy and to
On 06/01/2021 16:36, Chris Wilson wrote:
Refactor our timer_list.expires checking into its own timer_active()
helper.
Signed-off-by: Chris Wilson
Cc: Tvrtko Ursulin
---
drivers/gpu/drm/i915/i915_utils.c | 2 +-
drivers/gpu/drm/i915/i915_utils.h | 7 ++-
2 files changed, 7
On Wed, Jan 06, 2021 at 09:41:37AM +, Chris Wilson wrote:
> Quoting Janusz Krzysztofik (2020-12-04 19:50:07)
> > We may still be interested in results of a test even if it has tainted
> > the kernel. On the other hand, we need to kill the test on taint if no
> > other means of killing it on a
On Thu, Jan 07, 2021 at 09:49:23AM +, Chris Wilson wrote:
> Quoting Petri Latvala (2021-01-07 09:40:02)
> > On Wed, Jan 06, 2021 at 09:41:37AM +, Chris Wilson wrote:
> > > Quoting Janusz Krzysztofik (2020-12-04 19:50:07)
> > > > We may still be interested in results of a test even if it
In the next^W future patch, we remove the strict priority system and
continuously re-evaluate the relative priority of tasks. As such we need
to enable the timeslice whenever there is more than one context in the
pipeline. This simplifies the decision and removes some of the tweaks to
suppress
In the next^W future patch, we remove the strict priority system and
continuously re-evaluate the relative priority of tasks. As such we need
to enable the timeslice whenever there is more than one context in the
pipeline. This simplifies the decision and removes some of the tweaks to
suppress
We need a power_domain wakeref in pps_{lock,unlock} to prevent
a race while resetting pps state in intel_power_sequencer_reset().
intel_power_sequencer_reset() need a pps_mutex to access pps_pipe
but it can't grab pps_mutex due to deadlock with power_well
functions are called while holding
'--base' as documented in
https://git-scm.com/docs/git-format-patch]
url:
https://github.com/0day-ci/linux/commits/Thomas-Zimmermann/drm-Move-struct-drm_device-pdev-to-legacy/20210107-161007
base: git://anongit.freedesktop.org/drm/drm-tip drm-tip
config: microblaze-randconfig-r013-20210107
Quoting Petri Latvala (2021-01-07 09:40:02)
> On Wed, Jan 06, 2021 at 09:41:37AM +, Chris Wilson wrote:
> > Quoting Janusz Krzysztofik (2020-12-04 19:50:07)
> > > We may still be interested in results of a test even if it has tainted
> > > the kernel. On the other hand, we need to kill the
Quoting Tvrtko Ursulin (2021-01-07 10:16:57)
>
> On 06/01/2021 16:08, Chris Wilson wrote:
> > Quoting Tvrtko Ursulin (2021-01-06 15:57:49)
>
> [snip]
>
> >>> @@ -1363,16 +1336,16 @@ static void execlists_dequeue(struct
> >>> intel_engine_cs *engine)
> >>>
-to-legacy/20210107-161007
base: git://anongit.freedesktop.org/drm/drm-tip drm-tip
config: x86_64-randconfig-s021-20210107 (attached as .config)
compiler: gcc-9 (Debian 9.3.0-15) 9.3.0
reproduce:
# apt-get install sparse
# sparse version: v0.6.3-208-g46a52ca4-dirty
#
https
On Thu, Jan 07, 2021 at 09:50:28AM +0200, Jani Nikula wrote:
>
> Hi Dave & Daniel -
>
> Pretty quiet still, but here's some cc: stable fixes.
Pulled, thanks.
-Daniel
>
> (Well, one doesn't have the explicit stable tag, but the Fixes tag
> points at a commit in v3.9...)
>
>
'--base' as documented in
https://git-scm.com/docs/git-format-patch]
url:
https://github.com/0day-ci/linux/commits/Thomas-Zimmermann/drm-Move-struct-drm_device-pdev-to-legacy/20210107-161007
base: git://anongit.freedesktop.org/drm/drm-tip drm-tip
config: x86_64-randconfig-s021-20210107
On Thu, Dec 17, 2020 at 11:12 AM Maarten Lankhorst
wrote:
>
> drm-misc-next-2020-12-17:
> drm-misc-next for v5.12:
>
> UAPI Changes:
> - Not necessarily one, but we document that userspace needs to force probe
> connectors.
>
> Cross-subsystem Changes:
> - Require FB_ATY_CT for aty on sparc64.
>
== Series Details ==
Series: drm/i915/hdcp: Disable the QSES check for HDCP 1.4 over MST
URL : https://patchwork.freedesktop.org/series/8/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_9554_full -> Patchwork_19275_full
On Wed, Dec 23, 2020 at 10:14:58AM +0200, Jani Nikula wrote:
>
> Hi Maarten, Maxime, and Thomas -
>
> Here's the DP-HDMI2.1 PCON support topic pull consisting of the series
> [1]. The series is split roughly 50-50 between drm helpers and i915, so
> a topic branch seemed to be the right way to
== Series Details ==
Series: Introduce Intel PXP component - Mesa single session (rev19)
URL : https://patchwork.freedesktop.org/series/84620/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_9554_full -> Patchwork_19276_full
Hi,
On 11/24/20 4:49 PM, Ville Syrjälä wrote:
> On Wed, Nov 18, 2020 at 01:40:58PM +0100, Hans de Goede wrote:
>> Commit 25b4620ee822 ("drm/i915/dsi: Skip delays for v3 VBTs in vid-mode")
>> added an intel_dsi_msleep() helper which skips sleeping if the
>> MIPI-sequences have a version of 3 or
We need a power_domain wakeref in pps_{lock,unlock} to prevent
a race while resetting pps state in intel_power_sequencer_reset().
intel_power_sequencer_reset() need a pps_mutex to access pps_pipe
but it can't grab pps_mutex due to deadlock with power_well
functions are called while holding
On Mon, Jan 04, 2021 at 01:10:18PM -0800, Rodrigo Vivi wrote:
> Hi Dave and Daniel,
>
> Happy New Year.
>
> Here goes the first pull request targeting 5.12.
>
> drm-intel-next-2021-01-04:
> - Display hotplug fix for gen2/gen3 (Chris)
> - Remove trailing semicolon (Tom)
> - Suppress display
On Wed, Jan 06, 2021 at 12:13:12PM +0100, Maarten Lankhorst wrote:
> drm-misc-next-2021-01-06:
> drm-misc-next for v5.12:
>
> Core Changes:
> - Lots of drm documentation updates by Simor Ser.
Extra kudos for documentation work!
> - Require that each crtc has a unique primary plane.
> - Add
On 07/01/2021 11:05, Chris Wilson wrote:
In the next^W future patch, we remove the strict priority system and
continuously re-evaluate the relative priority of tasks. As such we need
to enable the timeslice whenever there is more than one context in the
pipeline. This simplifies the decision
On 07/01/2021 10:27, Chris Wilson wrote:
Quoting Tvrtko Ursulin (2021-01-07 10:16:57)
On 06/01/2021 16:08, Chris Wilson wrote:
Quoting Tvrtko Ursulin (2021-01-06 15:57:49)
[snip]
@@ -1363,16 +1336,16 @@ static void execlists_dequeue(struct intel_engine_cs
*engine)
On Fri, 2020-12-18 at 16:03 +0530, Swati Sharma wrote:
> DP does not support sending AVI info frame to panel. So we need to
> send AVI info frame to HDMI through some other DIP.
>
> When DP-to-HDMI protocol converter is present GMP DIP will be used
> to send AVI infoframe instead of static HDR
In the next^W future patch, we remove the strict priority system and
continuously re-evaluate the relative priority of tasks. As such we need
to enable the timeslice whenever there is more than one context in the
pipeline. This simplifies the decision and removes some of the tweaks to
suppress
On Fri, 2020-12-18 at 16:03 +0530, Swati Sharma wrote:
> In this patch readout for AVI infoframes enclosed in GMP
> DIP is implemented.
>
> Signed-off-by: Swati Sharma
> Signed-off-by: Ankit Nautiyal
> ---
> drivers/gpu/drm/i915/display/intel_dp.c | 74
> -
> 1 file
Refactor our timer_list.expires checking into its own timer_active()
helper.
Signed-off-by: Chris Wilson
Cc: Tvrtko Ursulin
Reviewed-by: Tvrtko Ursulin
---
drivers/gpu/drm/i915/i915_utils.c | 2 +-
drivers/gpu/drm/i915/i915_utils.h | 7 ++-
2 files changed, 7 insertions(+), 2 deletions(-)
In the next^W future patch, we remove the strict priority system and
continuously re-evaluate the relative priority of tasks. As such we need
to enable the timeslice whenever there is more than one context in the
pipeline. This simplifies the decision and removes some of the tweaks to
suppress
On Thu, Jan 07, 2021 at 09:01:40AM +0200, Jani Nikula wrote:
> On Wed, 09 Dec 2020, Imre Deak wrote:
> > For an enabled DSC during HW readout the corresponding power reference
> > is taken along the CRTC power domain references in
> > get_crtc_power_domains(). Remove the incorrect get ref from
On Wed, Jan 06, 2021 at 09:09:45PM +0200, Imre Deak wrote:
> On Wed, Jan 06, 2021 at 07:04:42PM +0100, Greg KH wrote:
> > On Wed, Jan 06, 2021 at 07:53:01PM +0200, Imre Deak wrote:
> > > Stable team, please backport the upstream commit
> > >
> > > 8f329967d596 ("drm/i915/tgl: Fix Combo PHY DPLL
== Series Details ==
Series: drm/i915/gt: Show the per-engine runtime in sysfs
URL : https://patchwork.freedesktop.org/series/85583/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_9562 -> Patchwork_19282
Summary
---
== Series Details ==
Series: series starting with [1/2] drm/i915: Try to use fast+narrow link on eDP
again and fall back to the old max strategy on failure
URL : https://patchwork.freedesktop.org/series/85588/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_9562 ->
== Series Details ==
Series: series starting with [CI,1/2] drm/i915: Wrap our timer_list.expires
checking (rev2)
URL : https://patchwork.freedesktop.org/series/85584/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_9562 -> Patchwork_19283
== Series Details ==
Series: series starting with [1/2] drm/i915: Try to use fast+narrow link on eDP
again and fall back to the old max strategy on failure
URL : https://patchwork.freedesktop.org/series/85588/
State : warning
== Summary ==
$ dim sparse --fast origin/drm-tip
Sparse version:
On Fri, Oct 16, 2020 at 06:54:11PM +0100, Chris Wilson wrote:
> MEDIA_STATE_VFE only accepts the 'maximum number of threads' in the
> range [0, n-1] where n is #EU * (#threads/EU) with the number of threads
> based on plaform and the number of EU based on the number of slices and
> subslices. This
Quoting Rodrigo Vivi (2021-01-07 19:50:37)
> On Fri, Oct 16, 2020 at 06:54:11PM +0100, Chris Wilson wrote:
> > MEDIA_STATE_VFE only accepts the 'maximum number of threads' in the
> > range [0, n-1] where n is #EU * (#threads/EU) with the number of threads
> > based on plaform and the number of EU
Before we mark the virtual engine as no longer inflight, flush any
ongoing signaling that may be using the ce->signal_link along the
previous breadcrumbs. On switch to a new physical engine, that link will
be inserted into the new set of breadcrumbs, causing confusion to an
ongoing iterator.
This
The reason why we did not enable preemption on Broadwater was due to
missing GPGPU workarounds. Since this only applies to rcs0, only
restrict rcs0 (and our global capabilities).
While this does not affect exposing a preemption capability to
userspace, it does affect our internal decisions on
If a request is submitted and known to require no preemption, disable
arbitration around the batch which prevents the HW from handling a
preemption request during the payload.
Signed-off-by: Chris Wilson
Cc: Mika Kuoppala
Cc: Matthew Brost
Cc: Lionel Landwerlin
---
We use the completion of the last active breadcrumb to retire the
requests along a timeline. This is purely opportunistic as nothing
guarantees that any particular timeline is terminated by a breadcrumb;
except for the parking the engine. We explicitly add a breadcrumb to
parking the engine so
If any of the perf tests run into 0 time, not only are we liable to
divide by zero, but the result would be highly questionable.
Nevertheless, let's not have a div-by-zero error.
Signed-off-by: Chris Wilson
---
drivers/gpu/drm/i915/selftests/intel_memory_region.c | 3 +++
1 file changed, 3
== Series Details ==
Series: drm/i915/pps: Reuse POWER_DOMAIN_DISPLAY_CORE in pps_{lock, unlock}
URL : https://patchwork.freedesktop.org/series/85582/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_9562_full -> Patchwork_19281_full
== Series Details ==
Series: series starting with [1/5] drm/i915/selftests: Skip unstable timing
measurements
URL : https://patchwork.freedesktop.org/series/85596/
State : warning
== Summary ==
$ dim sparse --fast origin/drm-tip
Sparse version: v0.6.2
Fast mode used, each commit won't be
== Series Details ==
Series: series starting with [v2,1/2] drm/i915: Wrap our timer_list.expires
checking (rev3)
URL : https://patchwork.freedesktop.org/series/85551/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_9562_full -> Patchwork_19279_full
== Series Details ==
Series: drm/i915/pps: Add PPS power domain (rev3)
URL : https://patchwork.freedesktop.org/series/85470/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_9562_full -> Patchwork_19280_full
Summary
---
== Series Details ==
Series: series starting with [1/5] drm/i915/selftests: Skip unstable timing
measurements
URL : https://patchwork.freedesktop.org/series/85596/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip
d55262c7a0fc drm/i915/selftests: Skip unstable timing measurements
Currently, every different type of backlight hook that i915 supports is
pretty straight forward - you have a backlight, probably through PWM
(but maybe DPCD), with a single set of platform-specific hooks that are
used for controlling it.
HDR backlights, in particular VESA and Intel's HDR
Since we now support controlling panel backlights through DPCD using
both the standard VESA interface, and Intel's proprietary HDR backlight
interface, we should allow the user to be able to explicitly choose
between one or the other in the event that we're wrong about panels
reliably reporting
So-recently a bunch of laptops on the market have started using DPCD
backlight controls instead of the traditional DDI backlight controls.
Originally we thought we had this handled by adding VESA backlight
control support to i915, but the story ended up being a lot more
complicated then that.
This reverts commit 0883ce8146ed6074c76399f4e70dbed788582e12. Originally
these quirks were added because of the issues with using the eDP
backlight interfaces on certain laptop panels, which made it impossible
to properly probe for DPCD backlight support without having a whitelist
for panels that
A while ago we ran into issues while trying to enable the eDP backlight
control interface as defined by VESA, in order to make the DPCD
backlight controls on newer laptop panels work. The issue ended up being
much more complicated however, as we also apparently needed to add
support for an
On Wed, 2021-01-06 at 15:12 -0800, Huang, Sean Z wrote:
> Set the KCR init during the boot time, which is
> required by hardware, to allow us doing further
> protection operation such as sending commands to
> GPU or TEE.
>
> Signed-off-by: Huang, Sean Z
> ---
>
On Wed, 2021-01-06 at 15:12 -0800, Huang, Sean Z wrote:
> Create the arbitrary session, with the fixed session id 0xf, after
> system boot, for the case that application allocates the protected
> buffer without establishing any protection session. Because the
> hardware requires at least one alive
== Series Details ==
Series: drm/i915: Remove obj->mm.lock! (rev13)
URL : https://patchwork.freedesktop.org/series/82337/
State : warning
== Summary ==
$ dim sparse --fast origin/drm-tip
Sparse version: v0.6.2
Fast mode used, each commit won't be checked separately.
== Series Details ==
Series: drm/i915: Remove obj->mm.lock! (rev13)
URL : https://patchwork.freedesktop.org/series/82337/
State : warning
== Summary ==
$ make htmldocs 2>&1 > /dev/null | grep i915
./drivers/gpu/drm/i915/gem/i915_gem_shrinker.c:102: warning: Function parameter
or member 'ww'
On Wed, 2021-01-06 at 15:12 -0800, Huang, Sean Z wrote:
> During the power event S3+ sleep/resume, hardware will lose all the
> encryption keys for every hardware session, even though the
> software session state was marked as alive after resume. So to
> handle such case, PXP should terminate all
On Wed, 2021-01-06 at 15:12 -0800, Huang, Sean Z wrote:
> PXP (Protected Xe Path) is an i915 componment, available on GEN12+,
> that helps to establish the hardware protected session and manage
> the status of the alive software session, as well as its life cycle.
>
> This patch series is to
On Wed, 2021-01-06 at 15:12 -0800, Huang, Sean Z wrote:
> Implement the funcs to create the TEE channel, so kernel can
> send the TEE commands directly to TEE for creating the arbitrary
> (defualt) session.
>
> Signed-off-by: Huang, Sean Z
> ---
> drivers/gpu/drm/i915/Makefile | 3
== Series Details ==
Series: drm: Move struct drm_device.pdev to legacy (rev3)
URL : https://patchwork.freedesktop.org/series/84205/
State : failure
== Summary ==
Applying: drm/amdgpu: Fix trailing whitespaces
Applying: drm/amdgpu: Remove references to struct drm_device.pdev
Applying:
On Wed, 2021-01-06 at 15:12 -0800, Huang, Sean Z wrote:
> PXP (Protected Xe Path) is an i915 component, available on
> GEN12+ that helps to establish the hardware protected session
> and manage the status of the alive software session, as well
> as its life cycle.
>
> This patch series is to
== Series Details ==
Series: drm/i915: Remove obj->mm.lock! (rev13)
URL : https://patchwork.freedesktop.org/series/82337/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip
cbc0237dc775 drm/i915: Do not share hwsp across contexts any more, v6
-:558: WARNING:CONSTANT_COMPARISON:
On Wed, 2021-01-06 at 15:12 -0800, Huang, Sean Z wrote:
> Implement the functions to allow PXP to send a GPU command, in
> order to terminate the hardware session, so hardware can recycle
> this session slot for the next usage.
>
> Signed-off-by: Huang, Sean Z
> ---
>
On Thu, Jan 07, 2021 at 04:45:31PM +, Chris Wilson wrote:
> Quoting Matthew Brost (2021-01-07 16:05:07)
> > On Tue, Dec 29, 2020 at 12:01:25PM +, Chris Wilson wrote:
> > > The first "scheduler" was a topographical sorting of requests into
> > > priority order. The execution order was
== Series Details ==
Series: series starting with [v2,1/2] drm/i915: Wrap our timer_list.expires
checking (rev3)
URL : https://patchwork.freedesktop.org/series/85551/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_9562 -> Patchwork_19279
On Mon, 04 Jan 2021, Saichandana S wrote:
> From: Saichandana
>
> PM_REQ register provides the value of the last PM request from PCU to
> Display Engine.PM_RES register provides the value of the last PM
> response from Display Engine to PCU.This debugfs will be used by
> DC9 IGT test to know
== Series Details ==
Series: series starting with [1/5] drm/i915/selftests: Skip unstable timing
measurements
URL : https://patchwork.freedesktop.org/series/85596/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_9563 -> Patchwork_19285
== Series Details ==
Series: series starting with [1/5] drm/i915/selftests: Skip unstable timing
measurements (rev2)
URL : https://patchwork.freedesktop.org/series/85596/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip
00bfab2df5c6 drm/i915/selftests: Skip unstable timing
== Series Details ==
Series: series starting with [1/5] drm/i915/selftests: Skip unstable timing
measurements (rev2)
URL : https://patchwork.freedesktop.org/series/85596/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_9563 -> Patchwork_19287
== Series Details ==
Series: drm/i915/gt: Show the per-engine runtime in sysfs
URL : https://patchwork.freedesktop.org/series/85583/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_9562_full -> Patchwork_19282_full
Summary
== Series Details ==
Series: drm/i915: Add support for Intel's eDP backlight controls (rev8)
URL : https://patchwork.freedesktop.org/series/81702/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_9563 -> Patchwork_19286
== Series Details ==
Series: series starting with [1/5] drm/i915/selftests: Skip unstable timing
measurements (rev2)
URL : https://patchwork.freedesktop.org/series/85596/
State : warning
== Summary ==
$ dim sparse --fast origin/drm-tip
Sparse version: v0.6.2
Fast mode used, each commit won't
== Series Details ==
Series: series starting with [CI,1/2] drm/i915: Wrap our timer_list.expires
checking (rev2)
URL : https://patchwork.freedesktop.org/series/85584/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_9562_full -> Patchwork_19283_full
On 1/5/2021 1:13 PM, john.c.harri...@intel.com wrote:
From: John Harrison
There is a module parameter for controlling what GuC/HuC features are
enabled. Setting to -1 means 'use the default'. However, the default
is not well defined, out of date and needs to be different across
platforms.
== Series Details ==
Series: series starting with [1/5] drm/i915/selftests: Skip unstable timing
measurements (rev2)
URL : https://patchwork.freedesktop.org/series/85596/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_9563_full -> Patchwork_19287_full
Hi,
Here's one gvt fixes for VFIO edid on APL/BXT with virtual display
hotplug fixed that feature is enabled again.
Thanks.
--
The following changes since commit e71ba9452f0b5b2e8dc8aa5445198cd9214a6a62:
Linux 5.11-rc2 (2021-01-03 15:55:30 -0800)
are available in the Git repository at:
== Series Details ==
Series: series starting with [1/2] drm/i915: Try to use fast+narrow link on eDP
again and fall back to the old max strategy on failure
URL : https://patchwork.freedesktop.org/series/85588/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_9562_full ->
' as documented in
https://git-scm.com/docs/git-format-patch]
url:
https://github.com/0day-ci/linux/commits/Thomas-Zimmermann/drm-Move-struct-drm_device-pdev-to-legacy/20210107-161007
base: git://anongit.freedesktop.org/drm/drm-tip drm-tip
config: x86_64-randconfig-s021-20210107 (attached as .config
mapfb/displays/panel-dsi-cm.ko
> drivers/gpu/drm/panel/panel-dsi-cm.ko
>
> Maybe caused by commit
>
> cf64148abcfd ("drm/panel: Move OMAP's DSI command mode panel driver")
>
> I have used the drm tree from next-20210107 for today.
This has affected the drm-misc
On Wed, 2021-01-06 at 15:12 -0800, Huang, Sean Z wrote:
> From: Bommu Krishnaiah
>
> This api allow user mode to create Protected buffer and context
> creation.
>
> Signed-off-by: Bommu Krishnaiah
> Cc: Telukuntla Sreedhar
> Cc: Kondapally Kalyan
> Cc: Gupta Anshuman
> Cc: Huang Sean Z
>
On Wed, 2021-01-06 at 23:47 +, Patchwork wrote:
> == Series Details ==
>
> Series: Introduce Intel PXP component - Mesa single session (rev19)
> URL : https://patchwork.freedesktop.org/series/84620/
> State : warning
>
> == Summary ==
>
> $ dim checkpatch origin/drm-tip
> fbdd4e2e287d
On Tue, Dec 29, 2020 at 12:01:25PM +, Chris Wilson wrote:
> The first "scheduler" was a topographical sorting of requests into
> priority order. The execution order was deterministic, the earliest
> submitted, highest priority request would be executed first. Priority
> inheritance ensured
== Series Details ==
Series: series starting with [v2,1/2] drm/i915: Wrap our timer_list.expires
checking (rev3)
URL : https://patchwork.freedesktop.org/series/85551/
State : warning
== Summary ==
$ dim sparse --fast origin/drm-tip
Sparse version: v0.6.2
Fast mode used, each commit won't be
On Wed, 2021-01-06 at 15:12 -0800, Huang, Sean Z wrote:
> Implement the intel_pxp_gem_object_status() to allow i915 display
> querying the current PXP session state. In the design, display
> should not perform protection flip on the protected buffers if
> there is no PXP session alive. And
== Series Details ==
Series: drm/i915: Remove obj->mm.lock! (rev13)
URL : https://patchwork.freedesktop.org/series/82337/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_9562 -> Patchwork_19278
Summary
---
**FAILURE**
Hi Chris,
On Thu, Jan 07, 2021 at 11:05:55AM +, Chris Wilson wrote:
> In the next^W future patch, we remove the strict priority system and
> continuously re-evaluate the relative priority of tasks. As such we need
> to enable the timeslice whenever there is more than one context in the
>
Quoting Matthew Brost (2021-01-07 16:05:07)
> On Tue, Dec 29, 2020 at 12:01:25PM +, Chris Wilson wrote:
> > The first "scheduler" was a topographical sorting of requests into
> > priority order. The execution order was deterministic, the earliest
> > submitted, highest priority request would
== Series Details ==
Series: drm/i915/pps: Add PPS power domain (rev3)
URL : https://patchwork.freedesktop.org/series/85470/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_9562 -> Patchwork_19280
Summary
---
On Tue, 05 Jan 2021, Tejas Upadhyay
wrote:
> We have TGP PCH support for Tigerlake and Rocketlake. Similarly
> now TGP PCH can be used with Cometlake CPU.
>
> Changes since V2 :
> - IS_COMETLAKE replaced with IS_GEN9_BC
> - VBT ddc pin remapping added
> - Added dedicated
From: Ville Syrjälä
Some new eDP panels don't like to operate at the max parameters, and
instead we need to go for an optimal confiugration. That unfortunately
doesn't work with older eDP panels which are generally only guaranteed
to work at the max parameters.
To solve these two conflicting
1 - 100 of 102 matches
Mail list logo
