This series will add a support to set the vrr_enabled property for
crtc based on the platform support and the request from userspace.
And userspace can also query to get the status of "vrr_enabled".
Test-with: 20220422075223.2792586-2-bhanuprakash.mo...@intel.com
Bhanuprakash Modem (2):
drm/vrr
Modern display hardware is capable of supporting variable refresh rates.
This patch introduces helpers to attach and set "vrr_enabled" property
on the crtc to allow userspace to query VRR enabled status on that crtc.
Atomic drivers should attach this property to crtcs those are capable of
driving
This function sets the vrr_enabled property for crtc based
on the platform support and the request from userspace.
V2: Check for platform support before updating the prop.
V3: Don't attach vrr_enabled prop, as it is alreay attached.
Cc: Ville Syrjälä
Cc: Manasi Navare
Signed-off-by: Bhanuprakas
Hi,
On 16/05/2022 22:22, Randy Dunlap wrote:
On 5/16/22 03:57, Stephen Rothwell wrote:
Hi all,
Changes since 20220513:
on i386:
CC drivers/gpu/drm/i915/gt/intel_gt_sysfs_pm.o
../drivers/gpu/drm/i915/gt/intel_gt_sysfs_pm.c: In function ‘act_freq_mhz_show’:
../drivers/gpu/drm/i91
== Series Details ==
Series: Attach and Set vrr_enabled property (rev3)
URL : https://patchwork.freedesktop.org/series/102978/
State : warning
== Summary ==
Error: dim checkpatch failed
ca69c64ffb44 drm/vrr: Attach vrr_enabled property to the drm crtc
-:81: CHECK:PARENTHESIS_ALIGNMENT: Alignme
== Series Details ==
Series: Attach and Set vrr_enabled property (rev3)
URL : https://patchwork.freedesktop.org/series/102978/
State : warning
== Summary ==
Error: dim sparse failed
Sparse version: v0.6.2
Fast mode used, each commit won't be checked separately.
-
+./drivers/gpu/drm/amd/amdgpu/
== Series Details ==
Series: Attach and Set vrr_enabled property (rev3)
URL : https://patchwork.freedesktop.org/series/102978/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_11662 -> Patchwork_102978v3
Summary
---
**F
On 16/05/2022 19:11, Matthew Auld wrote:
Add an entry for the new uapi needed for small BAR on DG2+.
v2:
- Some spelling fixes and other small tweaks. (Akeem & Thomas)
- Rework error capture interactions, including no longer needing
NEEDS_CPU_ACCESS for objects marked for capture. (
== Series Details ==
Series: Expose max and current bpc via debugfs (rev8)
URL : https://patchwork.freedesktop.org/series/102502/
State : warning
== Summary ==
Error: dim checkpatch failed
edfa55bea7ad drm/debug: Expose connector's max supported bpc via debugfs
-:21: WARNING:BAD_SIGN_OFF: 'Rev
On 17/05/2022 11:29, Tvrtko Ursulin wrote:
On 16/05/2022 19:11, Matthew Auld wrote:
Add an entry for the new uapi needed for small BAR on DG2+.
v2:
- Some spelling fixes and other small tweaks. (Akeem & Thomas)
- Rework error capture interactions, including no longer needing
NEEDS_C
On 17/05/2022 09:29, Tvrtko Ursulin wrote:
On 16/05/2022 19:11, Matthew Auld wrote:
Add an entry for the new uapi needed for small BAR on DG2+.
v2:
- Some spelling fixes and other small tweaks. (Akeem & Thomas)
- Rework error capture interactions, including no longer needing
NEEDS_C
On 17/05/2022 09:55, Lionel Landwerlin wrote:
On 17/05/2022 11:29, Tvrtko Ursulin wrote:
On 16/05/2022 19:11, Matthew Auld wrote:
Add an entry for the new uapi needed for small BAR on DG2+.
v2:
- Some spelling fixes and other small tweaks. (Akeem & Thomas)
- Rework error capture inter
On 17/05/2022 12:23, Tvrtko Ursulin wrote:
On 17/05/2022 09:55, Lionel Landwerlin wrote:
On 17/05/2022 11:29, Tvrtko Ursulin wrote:
On 16/05/2022 19:11, Matthew Auld wrote:
Add an entry for the new uapi needed for small BAR on DG2+.
v2:
- Some spelling fixes and other small tweaks. (Akee
On Mon, May 02, 2022 at 09:53:13AM -0700, Bjorn Andersson wrote:
> In some implementations, such as the Qualcomm platforms, the display
> driver has no way to query the current HPD state and as such it's
> impossible to distinguish between disconnect and attention events.
>
> Add a parameter to dr
Add an entry for the new uapi needed for small BAR on DG2+.
v2:
- Some spelling fixes and other small tweaks. (Akeem & Thomas)
- Rework error capture interactions, including no longer needing
NEEDS_CPU_ACCESS for objects marked for capture. (Thomas)
- Add probed_cpu_visible_size. (Lionel
_i915_vma_move_to_active() can receive > 1 fences for
multiple batch buffers submission. Because dma_resv_add_fence()
can only accept one fence at a time, change _i915_vma_move_to_active()
to be aware of multiple fences so that it can add individual
fences to the dma resv object.
v2: make sure to
On 17/05/2022 10:39, Lionel Landwerlin wrote:
On 17/05/2022 12:23, Tvrtko Ursulin wrote:
On 17/05/2022 09:55, Lionel Landwerlin wrote:
On 17/05/2022 11:29, Tvrtko Ursulin wrote:
On 16/05/2022 19:11, Matthew Auld wrote:
Add an entry for the new uapi needed for small BAR on DG2+.
v2:
-
On 17/05/2022 10:12, Matthew Auld wrote:
On 17/05/2022 09:29, Tvrtko Ursulin wrote:
On 16/05/2022 19:11, Matthew Auld wrote:
Add an entry for the new uapi needed for small BAR on DG2+.
v2:
- Some spelling fixes and other small tweaks. (Akeem & Thomas)
- Rework error capture interactio
On 17/05/2022 11:52, Matthew Auld wrote:
Add an entry for the new uapi needed for small BAR on DG2+.
v2:
- Some spelling fixes and other small tweaks. (Akeem & Thomas)
- Rework error capture interactions, including no longer needing
NEEDS_CPU_ACCESS for objects marked for capture. (
As with EU masks, it's easier to store subslice/DSS masks internally in
a format that's more natural for the driver to work with, and then only
covert into the u8[] uapi form when the query ioctl is invoked. Since
the hardware design changed significantly with Xe_HP, we'll use a union
to choose be
Hi All,
As mentioned in my RFC titled "drm/kms: control display brightness through
drm_connector properties":
https://lore.kernel.org/dri-devel/0d188965-d809-81b5-74ce-7d30c49fe...@redhat.com/
The first step towards this is to deal with some existing technical debt
in backlight handling on x86/AC
ATM on x86 laptops where we want userspace to use the acpi_video backlight
device we often register both the GPU's native backlight device and
acpi_video's firmware acpi_video# backlight device. This relies on
userspace preferring firmware type backlight devices over native ones, but
registering 2
Before this commit when we want userspace to use the acpi_video backlight
device we register both the GPU's native backlight device and acpi_video's
firmware acpi_video# backlight device. This relies on userspace preferring
firmware type backlight devices over native ones.
Registering 2 backlight
Before this commit when we want userspace to use the acpi_video backlight
device we register both the GPU's native backlight device and acpi_video's
firmware acpi_video# backlight device. This relies on userspace preferring
firmware type backlight devices over native ones.
Registering 2 backlight
Before this commit when we want userspace to use the acpi_video backlight
device we register both the GPU's native backlight device and acpi_video's
firmware acpi_video# backlight device. This relies on userspace preferring
firmware type backlight devices over native ones.
Registering 2 backlight
Now that all kms drivers which register native/BACKLIGHT_RAW type backlight
devices on x86/ACPI boards call acpi_video_get_backlight_type(true), with
the native=true value getting cached, there no longer is a need to call
backlight_device_get_by_type(BACKLIGHT_RAW) to see if a native backlight
devi
Move the list_del removing an acpi_video_bus from video_bus_head
on teardown to before the teardown is done, to avoid code iterating
over the video_bus_head list seeing acpi_video_bus objects on there
which are (partly) torn down already.
Signed-off-by: Hans de Goede
---
drivers/acpi/acpi_video.
Before this commit when we want userspace to use the acpi_video backlight
device we register both the GPU's native backlight device and acpi_video's
firmware acpi_video# backlight device. This relies on userspace preferring
firmware type backlight devices over native ones.
Registering 2 backlight
On x86/ACPI boards the acpi_video driver will usually initializing before
the kms driver (except i915). This causes /sys/class/backlight/acpi_video0
to show up and then the kms driver registers its own native backlight
device after which the drivers/acpi/video_detect.c code unregisters
the acpi_vid
Remove the code to unregister acpi_video backlight devices when
a native backlight device gets registered later.
Now that the acpi_video backlight device registration is a separate step
which runs later, after the drm/kms driver is done setting up its own
native backlight device, it is no longer n
On machins without an i915 opregion the acpi_video driver immediately
probes the ACPI video bus and used to also immediately register
acpi_video# backlight devices when supported.
Once the drm/kms driver then loaded later and possibly registered
a native backlight device then the drivers/acpi/vide
Typically the acpi_video driver will initialize before nouveau, which
used to cause /sys/class/backlight/acpi_video0 to get registered and then
nouveau would register its own nv_backlight device later. After which
the drivers/acpi/video_detect.c code unregistered the acpi_video0 device
to avoid the
When acpi_video_register() has not run yet the video_bus_head will be
empty, so there is no need to check the register_count flag first.
Signed-off-by: Hans de Goede
---
drivers/acpi/acpi_video.c | 12
1 file changed, 4 insertions(+), 8 deletions(-)
diff --git a/drivers/acpi/acpi_v
Typically the acpi_video driver will initialize before amdgpu, which
used to cause /sys/class/backlight/acpi_video0 to get registered and then
amdgpu would register its own amdgpu_bl# device later. After which
the drivers/acpi/video_detect.c code unregistered the acpi_video0 device
to avoid there b
Typically the acpi_video driver will initialize before radeon, which
used to cause /sys/class/backlight/acpi_video0 to get registered and then
radeon would register its own radeon_bl# device later. After which
the drivers/acpi/video_detect.c code unregistered the acpi_video0 device
to avoid there b
== Series Details ==
Series: drm/doc: add rfc section for small BAR uapi (rev3)
URL : https://patchwork.freedesktop.org/series/102875/
State : warning
== Summary ==
Error: dim checkpatch failed
9a6a6e3a4d2e drm/doc: add rfc section for small BAR uapi
-:31: WARNING:BAD_SIGN_OFF: Duplicate signa
== Series Details ==
Series: drm/doc: add rfc section for small BAR uapi (rev3)
URL : https://patchwork.freedesktop.org/series/102875/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_11665 -> Patchwork_102875v3
Summary
--
== Series Details ==
Series: drm/doc: add rfc section for small BAR uapi (rev3)
URL : https://patchwork.freedesktop.org/series/102875/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_11665_full -> Patchwork_102875v3_full
Summ
Bspec: 45810,54077,68173
Signed-off-by: Swathi Dhanavanthri
---
drivers/gpu/drm/i915/gt/intel_gt_regs.h | 1 +
drivers/gpu/drm/i915/gt/intel_workarounds.c | 9 +
2 files changed, 10 insertions(+)
diff --git a/drivers/gpu/drm/i915/gt/intel_gt_regs.h
b/drivers/gpu/drm/i915/gt/intel_g
> -Original Message-
> From: Tvrtko Ursulin
> Sent: Tuesday, May 17, 2022 6:49 AM
> To: Auld, Matthew ; intel-gfx@lists.freedesktop.org
> Cc: dri-de...@lists.freedesktop.org; Thomas Hellström
> ; Landwerlin, Lionel G
> ; Bloomfield, Jon ;
> Daniel Vetter ; Justen, Jordan L
> ; Kenneth Gr
On 5/17/22 00:35, Tvrtko Ursulin wrote:
>
> Hi,
>
> On 16/05/2022 22:22, Randy Dunlap wrote:
>>
>>
>> On 5/16/22 03:57, Stephen Rothwell wrote:
>>> Hi all,
>>>
>>> Changes since 20220513:
>>>
>>
>> on i386:
>>
>> CC drivers/gpu/drm/i915/gt/intel_gt_sysfs_pm.o
>> ../drivers/gpu/drm/i915
Jani, I have cleaned up the hsw_crtc_enable now removing the unused
function calls.
Could you please take a look?
Regards
Manasi
On Thu, May 12, 2022 at 12:52:04PM -0700, Manasi Navare wrote:
> Currently we reuse hsw_crtc_enable for SKL+ platforms.
> But this has added a lot of platform checks f
VM_BIND design document with description of intended use cases.
v2: Add more documentation and format as per review comments
from Daniel.
Signed-off-by: Niranjana Vishwanathapura
---
Documentation/driver-api/dma-buf.rst | 2 +
Documentation/gpu/rfc/i915_vm_bind.rst | 304 +++
This is the i915 driver VM_BIND feature design RFC patch series along
with the required uapi definition and description of intended use cases.
v2: Updated design and uapi, more documentation.
v3: Add more documentation and proper kernel-doc formatting with cross
references (including missing i
Add some missing i915 upai documentation which the new
i915 VM_BIND feature documentation will be refer to.
Signed-off-by: Niranjana Vishwanathapura
---
include/uapi/drm/i915_drm.h | 153 +++-
1 file changed, 116 insertions(+), 37 deletions(-)
diff --git a/includ
VM_BIND and related uapi definitions
v2: Ensure proper kernel-doc formatting with cross references.
Also add new uapi and documentation as per review comments
from Daniel.
Signed-off-by: Niranjana Vishwanathapura
---
Documentation/gpu/rfc/i915_vm_bind.h | 399 +++
== Series Details ==
Series: drm/i915: Individualize fences before adding to dma_resv obj
URL : https://patchwork.freedesktop.org/series/104074/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_11666 -> Patchwork_104074v1
Summ
== Series Details ==
Series: i915: SSEU handling updates (rev4)
URL : https://patchwork.freedesktop.org/series/103244/
State : warning
== Summary ==
Error: dim checkpatch failed
887126b08a62 drm/i915/xehp: Use separate sseu init function
913cf54798d2 drm/i915/xehp: Drop GETPARAM lookups of I91
== Series Details ==
Series: i915: SSEU handling updates (rev4)
URL : https://patchwork.freedesktop.org/series/103244/
State : warning
== Summary ==
Error: dim sparse failed
Sparse version: v0.6.2
Fast mode used, each commit won't be checked separately.
== Series Details ==
Series: drm/kms: Stop registering multiple /sys/class/backlight devs for a
single display
URL : https://patchwork.freedesktop.org/series/104084/
State : failure
== Summary ==
Error: patch
https://patchwork.freedesktop.org/api/1.0/series/104084/revisions/1/mbox/ not
appl
== Series Details ==
Series: i915: SSEU handling updates (rev4)
URL : https://patchwork.freedesktop.org/series/103244/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_11666 -> Patchwork_103244v4
Summary
---
**FAILURE**
On Tue, May 17, 2022 at 07:08:08PM +, Patchwork wrote:
> == Series Details ==
>
> Series: i915: SSEU handling updates (rev4)
> URL : https://patchwork.freedesktop.org/series/103244/
> State : failure
>
> == Summary ==
>
> CI Bug Log - changes from CI_DRM_11666 -> Patchwork_103244v4
> =
== Series Details ==
Series: drm/i915/dg2: Add workaround 22014600077
URL : https://patchwork.freedesktop.org/series/104097/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_11666 -> Patchwork_104097v1
Summary
---
**SUC
Signed-off-by: Swathi Dhanavanthri
---
drivers/gpu/drm/i915/intel_pm.c | 7 +++
1 file changed, 3 insertions(+), 4 deletions(-)
diff --git a/drivers/gpu/drm/i915/intel_pm.c b/drivers/gpu/drm/i915/intel_pm.c
index ee0047fdc95d..d0e0d6a324ee 100644
--- a/drivers/gpu/drm/i915/intel_pm.c
+++ b/d
== Series Details ==
Series: i915: SSEU handling updates (rev4)
URL : https://patchwork.freedesktop.org/series/103244/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_11666 -> Patchwork_103244v4
Summary
---
**SUCCESS**
On Tue, May 17, 2022 at 11:02:01AM -0700, Swathi Dhanavanthri wrote:
> Bspec: 45810,54077,68173
>
> Signed-off-by: Swathi Dhanavanthri
> ---
> drivers/gpu/drm/i915/gt/intel_gt_regs.h | 1 +
> drivers/gpu/drm/i915/gt/intel_workarounds.c | 9 +
> 2 files changed, 10 insertions(+)
>
>
On Tue, May 17, 2022 at 01:13:38PM -0700, Swathi Dhanavanthri wrote:
> Signed-off-by: Swathi Dhanavanthri
Reviewed-by: Matt Roper
> ---
> drivers/gpu/drm/i915/intel_pm.c | 7 +++
> 1 file changed, 3 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/intel_pm.c b/drivers/g
Since it's bat failure, I have filed a new issue
https://gitlab.freedesktop.org/drm/intel/-/issues/6025
igt@prime_vgem@basic-fence-read - incomplete - No warnings/errors
Thanks,
Lakshmi.
-Original Message-
From: Roper, Matthew D
Sent: Tuesday, May 17, 2022 12:20 PM
To: intel-gfx@lists.f
This patch is a second attempt at eliminating the old shmem memory region
and GEM object backend, in favour of a TTM-based one that is able to manage
objects placed on both system and local memory.
Questions addressed since previous revision:
* Creating an anonymous vfs mount for shmem files in T
Remove shmem region and object backend code as they are now unnecessary.
In the case of objects placed in SMEM and backed by kernel shmem files, the
file pointer has to be retrieved from the ttm_tt structure, so change this
as well. This means accessing an shmem-backed BO's file pointer requires
ge
== Series Details ==
Series: drm/doc/rfc: i915 VM_BIND feature design + uapi (rev3)
URL : https://patchwork.freedesktop.org/series/93447/
State : warning
== Summary ==
Error: dim checkpatch failed
b4f01b5605b4 drm/doc/rfc: VM_BIND feature design document
-:27: WARNING:FILE_PATH_CHANGES: added,
== Series Details ==
Series: drm/doc/rfc: i915 VM_BIND feature design + uapi (rev3)
URL : https://patchwork.freedesktop.org/series/93447/
State : warning
== Summary ==
Error: dim sparse failed
Sparse version: v0.6.2
Fast mode used, each commit won't be checked separately.
== Series Details ==
Series: series starting with [1/1] vfio: remove VFIO_GROUP_NOTIFY_SET_KVM
URL : https://patchwork.freedesktop.org/series/104101/
State : failure
== Summary ==
Error: patch
https://patchwork.freedesktop.org/api/1.0/series/104101/revisions/1/mbox/ not
applied
Applying: vfi
== Series Details ==
Series: drm/doc/rfc: i915 VM_BIND feature design + uapi (rev3)
URL : https://patchwork.freedesktop.org/series/93447/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_11668 -> Patchwork_93447v3
Summary
== Series Details ==
Series: drm/i915/dg2: Extend Wa_22010954014 to DG2-G11 and DG2-G12
URL : https://patchwork.freedesktop.org/series/104104/
State : warning
== Summary ==
Error: dim checkpatch failed
f3e4cba7117c drm/i915/dg2: Extend Wa_22010954014 to DG2-G11 and DG2-G12
-:7: WARNING:COMMIT_
Signed-off-by: Swathi Dhanavanthri
---
drivers/gpu/drm/i915/gt/intel_gt_regs.h | 1 +
drivers/gpu/drm/i915/gt/intel_workarounds.c | 10 ++
2 files changed, 11 insertions(+)
diff --git a/drivers/gpu/drm/i915/gt/intel_gt_regs.h
b/drivers/gpu/drm/i915/gt/intel_gt_regs.h
index 98ede9c9
>-Original Message-
>From: Intel-gfx On Behalf Of
>Adrian Larumbe
>Sent: Tuesday, May 17, 2022 4:45 PM
>To: dan...@ffwll.ch; intel-gfx@lists.freedesktop.org
>Cc: adrian.laru...@collabora.com
>Subject: [Intel-gfx] [RFC PATCH v2 1/1] drm/i915: Replace shmem memory
>region and object backend
== Series Details ==
Series: drm/i915/dg2: Extend Wa_22010954014 to DG2-G11 and DG2-G12
URL : https://patchwork.freedesktop.org/series/104104/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_11668 -> Patchwork_104104v1
Summar
== Series Details ==
Series: Replace shmem memory region and object backend
URL : https://patchwork.freedesktop.org/series/104105/
State : warning
== Summary ==
Error: dim checkpatch failed
a310d6e73af3 drm/i915: Replace shmem memory region and object backend with TTM
-:41: CHECK:COMPARISON_TO
== Series Details ==
Series: Replace shmem memory region and object backend
URL : https://patchwork.freedesktop.org/series/104105/
State : warning
== Summary ==
Error: dim sparse failed
Sparse version: v0.6.2
Fast mode used, each commit won't be checked separately.
== Series Details ==
Series: Replace shmem memory region and object backend
URL : https://patchwork.freedesktop.org/series/104105/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_11668 -> Patchwork_104105v1
Summary
---
== Series Details ==
Series: drm/i915/dg2: Add workaround 22014600077 (rev2)
URL : https://patchwork.freedesktop.org/series/104097/
State : warning
== Summary ==
Error: dim checkpatch failed
c6ced9357337 drm/i915/dg2: Add workaround 22014600077
-:7: WARNING:COMMIT_MESSAGE: Missing commit descr
== Series Details ==
Series: drm/i915/dg2: Add workaround 22014600077
URL : https://patchwork.freedesktop.org/series/104097/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_11666_full -> Patchwork_104097v1_full
Summary
--
== Series Details ==
Series: drm/i915/dg2: Add workaround 22014600077 (rev2)
URL : https://patchwork.freedesktop.org/series/104097/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_11668 -> Patchwork_104097v2
Summary
---
On 4/5/22 08:15, Borislav Petkov wrote:
> From: Borislav Petkov
>
> Fix:
>
> In file included from :0:0:
> drivers/gpu/drm/i915/gt/uc/intel_guc.c: In function ‘intel_guc_send_mmio’:
> ././include/linux/compiler_types.h:352:38: error: call to
> ‘__compiletime_assert_1047’ \
> declared
tree/branch:
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
branch HEAD: 47c1c54d1bcd0a69a56b49473bc20f17b70e5242 Add linux-next specific
files for 20220517
Error/Warning reports:
https://lore.kernel.org/linux-mm/202204181931.klac6fwo-...@intel.com
https
== Series Details ==
Series: i915: SSEU handling updates (rev4)
URL : https://patchwork.freedesktop.org/series/103244/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_11666_full -> Patchwork_103244v4_full
Summary
---
*
== Series Details ==
Series: drm/doc/rfc: i915 VM_BIND feature design + uapi (rev3)
URL : https://patchwork.freedesktop.org/series/93447/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_11668_full -> Patchwork_93447v3_full
Su
On Wed, May 18, 2022 at 12:34:11AM +, Patchwork wrote:
> == Series Details ==
>
> Series: i915: SSEU handling updates (rev4)
> URL : https://patchwork.freedesktop.org/series/103244/
> State : failure
>
> == Summary ==
>
> CI Bug Log - changes from CI_DRM_11666_full -> Patchwork_103244v4_fu
== Series Details ==
Series: drm/i915/dg2: Extend Wa_22010954014 to DG2-G11 and DG2-G12
URL : https://patchwork.freedesktop.org/series/104104/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_11668_full -> Patchwork_104104v1_full
==
== Series Details ==
Series: drm/i915/dg2: Add workaround 22014600077 (rev2)
URL : https://patchwork.freedesktop.org/series/104097/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_11668_full -> Patchwork_104097v2_full
Summary
On Mon-16-05-2022 02:09 pm, Jani Nikula wrote:
On Mon, 02 May 2022, Harry Wentland wrote:
Both the kernel and IGT series look good to me.
I recommend you merge the entire kernel set as one into drm-next. We
can pull it into amd-staging-drm-next so as not to break our CI once
the IGT patches la
On 2022-05-13 at 14:06:11 -0700, Jordan Justen wrote:
> On 2022-05-13 05:31:00, Lionel Landwerlin wrote:
> > On 02/05/2022 17:15, Ramalingam C wrote:
> > > Capture the impact of memory region preference list of the objects, on
> > > their memory residency and Flat-CCS capability.
> > >
> > > v2:
>
83 matches
Mail list logo
