On Thu, Jun 23, 2022 at 10:32:08PM -0700, Niranjana Vishwanathapura wrote:
VM_BIND and related uapi definitions
v2: Reduce the scope to simple Mesa use case.
v3: Expand VM_UNBIND documentation and add
I915_GEM_VM_BIND/UNBIND_FENCE_VALID
and I915_GEM_VM_BIND_TLB_FLUSH flags.
v4: Remove
Add some missing i915 upai documentation which the new
i915 VM_BIND feature documentation will be refer to.
Signed-off-by: Niranjana Vishwanathapura
Reviewed-by: Matthew Auld
---
include/uapi/drm/i915_drm.h | 205
1 file changed, 160 insertions(+), 45
VM_BIND and related uapi definitions
v2: Reduce the scope to simple Mesa use case.
v3: Expand VM_UNBIND documentation and add
I915_GEM_VM_BIND/UNBIND_FENCE_VALID
and I915_GEM_VM_BIND_TLB_FLUSH flags.
v4: Remove I915_GEM_VM_BIND_TLB_FLUSH flag and add additional
documentation for
VM_BIND design document with description of intended use cases.
v2: Reduce the scope to simple Mesa use case.
v3: Expand documentation on dma-resv usage, TLB flushing and
execbuf3.
v4: Remove vm_bind tlb flush request support.
v5: Update TLB flushing documentation.
Signed-off-by: Niranjana
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: Reduce the scope to simple Mesa use case.
Remove all compute related uapi, vm_bind/unbind queue support and
only support a timeline out fence
== Series Details ==
Series: drm/i915/dp: Check for Low voltage IO only for eDP
URL : https://patchwork.freedesktop.org/series/105573/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_11802 -> Patchwork_105573v1
Summary
> -Original Message-
> From: Christian König
> Sent: 18 June 2022 08:45 PM
> To: De Marchi, Lucas ; Bjorn Helgaas
>
> Cc: linux-...@vger.kernel.org; intel-gfx@lists.freedesktop.org; Sergei
> Miroshnichenko ; linux-
> ker...@vger.kernel.org; Dandamudi, Priyanka
> ; Auld, Matthew
> ;
The low voltage sku check can be ignored as OEMs need to consider that
when designing the board and then put any limits in VBT.
Due to this check many DP sink that can be run with higher link rate,
are run at lower link rate, thereby pruning the resolutions that are
intended to be working as per
== Series Details ==
Series: drm/i915/guc/slpc: Add a new SLPC selftest (rev3)
URL : https://patchwork.freedesktop.org/series/105005/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_11800 -> Patchwork_105005v3
Summary
== Series Details ==
Series: drm/i915/guc/slpc: Add a new SLPC selftest (rev3)
URL : https://patchwork.freedesktop.org/series/105005/
State : warning
== Summary ==
Error: dim checkpatch failed
4982a0bd3fa6 drm/i915/guc/slpc: Add a new SLPC selftest
-:13: WARNING:COMMIT_LOG_LONG_LINE: Possible
This test will validate we can achieve actual frequency of RP0. Pcode
grants frequencies based on what GuC is requesting. However, thermal
throttling can limit what is being granted. Add a test to request for
max, but don't fail the test if RP0 is not granted due to throttle
reasons.
Also
On 6/22/2022 1:32 PM, Dixit, Ashutosh wrote:
On Fri, 10 Jun 2022 16:47:12 -0700, Vinay Belgaumkar wrote:
This test will validate we can achieve actual frequency of RP0. Pcode
grants frequencies based on what GuC is requesting. However, thermal
throttling can limit what is being granted. Add a
Regards,
Oak
> -Original Message-
> From: Intel-gfx On Behalf Of Tvrtko
> Ursulin
> Sent: June 23, 2022 7:06 AM
> To: Landwerlin, Lionel G ; Vishwanathapura,
> Niranjana
> Cc: Zanoni, Paulo R ;
> intel-gfx@lists.freedesktop.org;
> dri-de...@lists.freedesktop.org; Hellstrom, Thomas
>
On Mon, Jun 20, 2022 at 11:38:02AM +0300, Jani Nikula wrote:
> Add initial runtime info that we can copy to runtime info at i915
> creation time. This lets us define the initial values for runtime info
> statically while making it possible to change them runtime. This will be
> the new home for
On Mon, Jun 20, 2022 at 11:37:40AM +0300, Jani Nikula wrote:
> We've just set up device info in i915_driver_create() so we can use
> GRAPHICS_VER() intead of looking at match_info directly.
>
> Signed-off-by: Jani Nikula
> ---
> drivers/gpu/drm/i915/i915_driver.c | 4 +---
> 1 file changed, 1
On Thu, Jun 23, 2022 at 08:04:54PM +0300, Jani Nikula wrote:
> On Thu, 23 Jun 2022, Ville Syrjälä wrote:
> > On Tue, Jun 21, 2022 at 03:37:32PM +0300, Jani Nikula wrote:
> >> The ddc pin and aux channel sanitization may disable DVI/HDMI and DP,
> >> respectively, of ports parsed earlier, in "last
On Wed, 22 Jun 2022, Ville Syrjala wrote:
> From: Ville Syrjälä
>
> The watermark code for ctg/elk has been atomic ready for a long time
> so let's just flip the switch now that some of the last CxSR issues
> have been sorted out (which granted was a problem for vlv/chv as well
> despite them
On Thu, 23 Jun 2022, Jani Nikula wrote:
> On Thu, 23 Jun 2022, Ville Syrjala wrote:
>> From: Ville Syrjälä
>>
>> Collect more stuff under INTEL_INFO->display, and clean up
>> some messy stuff in the related register macros.
>
> Makes me wonder if we should have DISPLAY_INFO(i915) macro that
On Thu, 23 Jun 2022, Ville Syrjala wrote:
> From: Ville Syrjälä
>
> Collect more stuff under INTEL_INFO->display, and clean up
> some messy stuff in the related register macros.
Makes me wonder if we should have DISPLAY_INFO(i915) macro that returns
a pointer to the display sub-struct.
Anyway,
On Thu, Jun 23, 2022 at 07:48:32AM -0700, Souza, Jose wrote:
> On Wed, 2022-06-22 at 15:19 -0700, Matt Roper wrote:
> > On Tue, Jun 21, 2022 at 10:03:04AM -0700, Souza, Jose wrote:
> > > On Fri, 2022-06-17 at 12:28 -0700, Matt Roper wrote:
> > > > On Fri, Jun 17, 2022 at 12:06:29PM -0700, José
On Thu, 23 Jun 2022, "Tangudu, Tilak" wrote:
>> -Original Message-
>> From: Vivi, Rodrigo
>> Sent: Thursday, June 23, 2022 2:11 AM
>> To: Jani Nikula
>> Cc: Tangudu, Tilak ; Gupta, Anshuman
>> ; intel-gfx@lists.freedesktop.org; Ewins, Jon
>> ; Belgaumkar, Vinay ;
>> Wilson, Chris P ;
== Series Details ==
Series: drm/i915/display: stop HPD workers before display driver unregister
URL : https://patchwork.freedesktop.org/series/105557/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_11799 -> Patchwork_105557v1
== Series Details ==
Series: drm/i915: Add D3Cold-Off support for runtime-pm (rev2)
URL : https://patchwork.freedesktop.org/series/105427/
State : failure
== Summary ==
Error: patch
https://patchwork.freedesktop.org/api/1.0/series/105427/revisions/2/mbox/ not
applied
Applying: drm/i915:
> -Original Message-
> From: Vivi, Rodrigo
> Sent: Thursday, June 23, 2022 2:11 AM
> To: Jani Nikula
> Cc: Tangudu, Tilak ; Gupta, Anshuman
> ; intel-gfx@lists.freedesktop.org; Ewins, Jon
> ; Belgaumkar, Vinay ;
> Wilson, Chris P ; Dixit, Ashutosh
> ; Nilawar, Badal ;
> Roper, Matthew
On Thu, 23 Jun 2022, Ville Syrjälä wrote:
> On Tue, Jun 21, 2022 at 03:37:32PM +0300, Jani Nikula wrote:
>> The ddc pin and aux channel sanitization may disable DVI/HDMI and DP,
>> respectively, of ports parsed earlier, in "last one wins" fashion. With
>> parsing and printing interleaved, we'll
On Thu, 23 Jun 2022, Jiang Jian wrote:
> there is an unexpected word 'for' in the comments that need to be dropped
While it's also unexpected, it's really *duplicated* word.
> file - drivers/gpu/drm/i915/i915_reg.h
> line - 2537
>
> * Please check the detailed lore in the commit message for
== Series Details ==
Series: drm/fourcc: Document the Intel CCS modifiers' CC plane expected pitch
URL : https://patchwork.freedesktop.org/series/105550/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_11799 -> Patchwork_105550v1
HPD event after fbdev unregistration can cause registration of deferred
fbdev which will not be unregistered later, causing use-after-free.
To avoid it HPD handling should be suspended before fbdev unregistration.
It should fix following GPF:
[272.634530] general protection fault, probably for
i915->hotplug.dig_port_work can be queued from intel_hpd_irq_handler
called by IRQ handler or by intel_hpd_trigger_irq called from dp_mst.
To avoid re-queuing lets cancel HPD work after intel_dp_mst_suspend.
It should fix following WARNINGS:
[283.405824] cpu_latency_qos_update_request called for
Hi Jani, Ville,
This patchset is replacement of patch
"drm/i915/display: disable HPD workers before display driver unregister" [1].
Ive decided to split patch into two parts - fbdev and MST, there are different
issues.
Ive also dropped shutdown path, as it has slightly different requirements,
and
== Series Details ==
Series: drm/fourcc: Document the Intel CCS modifiers' CC plane expected pitch
URL : https://patchwork.freedesktop.org/series/105550/
State : warning
== Summary ==
Error: dim sparse failed
Sparse version: v0.6.2
Fast mode used, each commit won't be checked separately.
Hi G.G.
On 6/23/2022 5:31 PM, Gwan-gyeong Mun wrote:
Commit message and code changes look good to me.
Reviewed-by: Gwan-gyeong Mun
This is a question about the issue mentioned in this patch, not the
patch. The tests
(igt@gem_ctx_persistence@legacy-engines-hostile@render) mentioned in
this
Commit message and code changes look good to me.
Reviewed-by: Gwan-gyeong Mun
This is a question about the issue mentioned in this patch, not the
patch. The tests
(igt@gem_ctx_persistence@legacy-engines-hostile@render) mentioned in
this issue (
On 23/06/2022 15:52, Christian König wrote:
Am 23.06.22 um 16:13 schrieb Matthew Auld:
[SNIP]
TTM_BO_VM_NUM_PREFAULT);
+ /*
+ * Ensure we check for any fatal errors if we had to
move/clear
+ * the object. The device should already be wedged if
we hit
The driver expects the pitch of the Intel CCS CC color planes to be
64 bytes aligned, adjust the modifier descriptions accordingly.
Cc: Nanley Chery
Signed-off-by: Imre Deak
---
include/uapi/drm/drm_fourcc.h | 8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git
On Wed, 2022-06-22 at 15:19 -0700, Matt Roper wrote:
> On Tue, Jun 21, 2022 at 10:03:04AM -0700, Souza, Jose wrote:
> > On Fri, 2022-06-17 at 12:28 -0700, Matt Roper wrote:
> > > On Fri, Jun 17, 2022 at 12:06:29PM -0700, José Roberto de Souza wrote:
> > > > Gem buffers could still be in use by
On Thu, Jun 23, 2022 at 09:27:22AM +0100, Tvrtko Ursulin wrote:
On 22/06/2022 17:44, Niranjana Vishwanathapura wrote:
On Wed, Jun 22, 2022 at 04:57:17PM +0100, Tvrtko Ursulin wrote:
On 22/06/2022 16:12, Niranjana Vishwanathapura wrote:
On Wed, Jun 22, 2022 at 09:10:07AM +0100, Tvrtko
On Thu, Jun 23, 2022 at 12:28:32PM +0300, Lionel Landwerlin wrote:
On 22/06/2022 18:12, Niranjana Vishwanathapura wrote:
On Wed, Jun 22, 2022 at 09:10:07AM +0100, Tvrtko Ursulin wrote:
On 22/06/2022 04:56, Niranjana Vishwanathapura wrote:
VM_BIND and related uapi definitions
v2: Reduce the
== Series Details ==
Series: drm/i915: Display info cleanup
URL : https://patchwork.freedesktop.org/series/105544/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_11797 -> Patchwork_105544v1
Summary
---
**SUCCESS**
On 23/06/2022 08:00, Thomas Hellström wrote:
On Tue, 2022-06-21 at 11:44 +0100, Matthew Auld wrote:
If the move or clear operation somehow fails, and the memory
underneath
is not cleared, like when moving to lmem, then we currently fallback
to
memcpy or memset. However with small-BAR systems
== Series Details ==
Series: drm/i915: Display info cleanup
URL : https://patchwork.freedesktop.org/series/105544/
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/i915: Display info cleanup
URL : https://patchwork.freedesktop.org/series/105544/
State : warning
== Summary ==
Error: dim checkpatch failed
bcf8c9fff0b4 drm/i915: Move dbuf details to INTEL_INFO->display
1822c399b492 drm/i195: Move pipe_offsets[] & co. to
On Thu, 2022-06-23 at 13:44 +, Souza, Jose wrote:
> On Mon, 2022-05-16 at 15:19 +0800, Hangyu Hua wrote:
> > If drm_connector_init fails, intel_connector_free will be called to take
> > care of proper free. So it is necessary to drop the refcount of port
> > before intel_connector_free.
>
>
On Mon, 2022-05-16 at 15:19 +0800, Hangyu Hua wrote:
> If drm_connector_init fails, intel_connector_free will be called to take
> care of proper free. So it is necessary to drop the refcount of port
> before intel_connector_free.
Reviewed-by: José Roberto de Souza
>
> Fixes: 091a4f91942a
From: Ville Syrjälä
The LUTs are a display feature so move the details into
the display portion of the device info.
Signed-off-by: Ville Syrjälä
---
drivers/gpu/drm/i915/display/intel_color.c | 28
drivers/gpu/drm/i915/i915_pci.c| 38 --
From: Ville Syrjälä
XE_LPD_CURSOR_OFFSETS is a duplicate of TGL_CURSOR_OFFSETS.
Just use the latter.
Signed-off-by: Ville Syrjälä
---
drivers/gpu/drm/i915/i915_pci.c | 10 +-
1 file changed, 1 insertion(+), 9 deletions(-)
diff --git a/drivers/gpu/drm/i915/i915_pci.c
From: Ville Syrjälä
Collect more stuff under INTEL_INFO->display, and clean up
some messy stuff in the related register macros.
Ville Syrjälä (9):
drm/i915: Move dbuf details to INTEL_INFO->display
drm/i195: Move pipe_offsets[] & co. to INTEL_INFO->display
drm/i915: Move
From: Ville Syrjälä
DBUF is a display thing, so move it into the display
portion of the device info.
Signed-off-by: Ville Syrjälä
---
drivers/gpu/drm/i915/display/intel_display.h | 2 +-
.../gpu/drm/i915/display/intel_display_power.c | 2 +-
drivers/gpu/drm/i915/i915_pci.c
From: Ville Syrjälä
Stop hand rolling _MMIO_TRANS2() and just use the real thing.
Note that this register isn't even used atm, hence why this
builds despite the _PIPE2() macro not actually existing.
Signed-off-by: Ville Syrjälä
---
drivers/gpu/drm/i915/i915_reg.h | 2 +-
1 file changed, 1
From: Ville Syrjälä
Stop hand rolling _MMIO_TRANS2() and just use the real thing.
Signed-off-by: Ville Syrjälä
---
drivers/gpu/drm/i915/i915_reg.h | 19 +--
1 file changed, 9 insertions(+), 10 deletions(-)
diff --git a/drivers/gpu/drm/i915/i915_reg.h
From: Ville Syrjälä
The other similar macros have the _MMIO prefix, so give
it also to _CURSOR2.
Signed-off-by: Ville Syrjälä
---
drivers/gpu/drm/i915/i915_reg.h | 14 +++---
1 file changed, 7 insertions(+), 7 deletions(-)
diff --git a/drivers/gpu/drm/i915/i915_reg.h
From: Ville Syrjälä
Using a signed type for the register offsets doesn't really
make sense. Switch to u32.
Signed-off-by: Ville Syrjälä
---
drivers/gpu/drm/i915/intel_device_info.h | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git
From: Ville Syrjälä
The display register offsets are display stuff so stick
into the display portion of the device info.
Signed-off-by: Ville Syrjälä
---
drivers/gpu/drm/i915/i915_pci.c | 44
drivers/gpu/drm/i915/i915_reg.h | 18 +-
From: Ville Syrjälä
The display register offsets are display stuff so stick
into the display portion of the device info.
Signed-off-by: Ville Syrjälä
---
drivers/gpu/drm/i915/i915_pci.c | 4 ++--
drivers/gpu/drm/i915/i915_reg.h | 2 +-
On 23/06/2022 14:05, Tvrtko Ursulin wrote:
On 23/06/2022 09:57, Lionel Landwerlin wrote:
On 23/06/2022 11:27, Tvrtko Ursulin wrote:
After a vm_unbind, UMD can re-bind to same VA range against an
active VM.
Though I am not sue with Mesa usecase if that new mapping is
required for
running
Hi Mauro,
On Wed, Jun 15, 2022 at 04:27:40PM +0100, Mauro Carvalho Chehab wrote:
> From: Chris Wilson
>
> Avoid trying to invalidate the TLB in the middle of performing an
> engine reset, as this may result in the reset timing out. Currently,
> the TLB invalidate is only serialised by its own
Hi Mauro,
On Wed, Jun 15, 2022 at 04:27:39PM +0100, Mauro Carvalho Chehab wrote:
> From: Chris Wilson
>
> Don't allow two engines to be reset in parallel, as they would both
> try to select a reset bit (and send requests to common registers)
> and wait on that register, at the same time.
Hi
The buddy allocator is still causing me issues in 5.19-rc3
(https://gitlab.freedesktop.org/drm/amd/-/issues/2059)
I'm no longer seeing null pointers though, so I think the bulk move
fix did it's bit
Let me know if there's anything I can help with, now there aren't
freezes I can offer remote
Hi Mauro,
On Wed, Jun 15, 2022 at 04:27:38PM +0100, Mauro Carvalho Chehab wrote:
> From: Chris Wilson
>
> Don't flush TLBs when the buffer is only used in the GGTT under full
> control of the kernel, as there's no risk of of concurrent access
> and stale access from prefetch.
>
> We only need
Hi Mauro,
On Wed, Jun 15, 2022 at 04:27:37PM +0100, Mauro Carvalho Chehab wrote:
> From: Chris Wilson
>
> Skip all further TLB invalidations once the device is wedged and
> had been reset, as, on such cases, it can no longer process instructions
> on the GPU and the user no longer has access to
Hi Mauro,
On Wed, Jun 15, 2022 at 04:27:36PM +0100, Mauro Carvalho Chehab wrote:
> From: Chris Wilson
>
> On gen12 HW, ensure that the TLB of the OA unit is also invalidated
> as just invalidating the TLB of an engine is not enough.
>
> Fixes: 7938d61591d3 ("drm/i915: Flush TLBs before
On 23/06/2022 09:57, Lionel Landwerlin wrote:
On 23/06/2022 11:27, Tvrtko Ursulin wrote:
After a vm_unbind, UMD can re-bind to same VA range against an active
VM.
Though I am not sue with Mesa usecase if that new mapping is required
for
running GPU job or it will be for the next
Hi Mauro,
On Wed, Jun 15, 2022 at 04:27:35PM +0100, Mauro Carvalho Chehab wrote:
> From: Chris Wilson
>
> As an extension of the current skip TLB invalidations,
> check if the device is powered down prior to any engine activity,
>
> as, on such cases, all the TLBs were already invalidated, so
On Thu, 2022-05-19 at 16:06 +, Sean Christopherson wrote:
> On Wed, Apr 27, 2022, Maxim Levitsky wrote:
> > Neither of these settings should be changed by the guest and it is
> > a burden to support it in the acceleration code, so just inhibit
> > it instead.
> >
> > Also add a boolean
On Mon, Jun 20, 2022 at 09:03:51PM +0300, Jani Nikula wrote:
> Group widely used display feature check macros together in one place.
I was also pondering whether we could pull in the whole INTEL_INFO->display
struct definition, but dunno if that would just make a bigger mess of the
includes.
>
On Mon, Jun 20, 2022 at 09:03:50PM +0300, Jani Nikula wrote:
> Expand single-use display feature macros around device info flags
> in-place, and remove the macros.
>
> Move display feature macros used in one file only into that file.
I suppose one counter argument would be that it might be
Dne 22. 06. 22 v 22:46 Rodrigo Vivi napsal(a):
Hi Zdenek,
On Wed, Jun 22, 2022 at 01:18:42PM +0200, Zdenek Kabelac wrote:
Hello
While somewhat oldish hw (T61, 4G, C2D) - I've now witnessed new crash with
Xorg:
(happened while reopening iconified Firefox window - running 'standard'
rawhide
On 22/06/2022 18:12, Niranjana Vishwanathapura wrote:
On Wed, Jun 22, 2022 at 09:10:07AM +0100, Tvrtko Ursulin wrote:
On 22/06/2022 04:56, Niranjana Vishwanathapura wrote:
VM_BIND and related uapi definitions
v2: Reduce the scope to simple Mesa use case.
v3: Expand VM_UNBIND documentation
== Series Details ==
Series: drm/edid: expand on struct drm_edid usage (rev6)
URL : https://patchwork.freedesktop.org/series/104309/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_11795 -> Patchwork_104309v6
Summary
---
On Tue, Jun 21, 2022 at 03:37:32PM +0300, Jani Nikula wrote:
> The ddc pin and aux channel sanitization may disable DVI/HDMI and DP,
> respectively, of ports parsed earlier, in "last one wins" fashion. With
> parsing and printing interleaved, we'll end up logging support first and
> disabling
On Thu, Jun 23, 2022 at 10:27:56AM +0300, Jani Nikula wrote:
> Convert all the connectors that use cached connector edid and
> detect_edid to drm_edid.
>
> v3: Don't leak vga switcheroo EDID in LVDS init (Ville)
>
> v2: Don't leak opregion fallback EDID (Ville)
>
> Signed-off-by: Jani Nikula
== Series Details ==
Series: drm/edid: expand on struct drm_edid usage (rev6)
URL : https://patchwork.freedesktop.org/series/104309/
State : warning
== Summary ==
Error: dim checkpatch failed
81051dc0bb2d drm/edid: move drm_connector_update_edid_property() to drm_edid.c
e87e79e1fff3 drm/edid:
On 23/06/2022 11:27, Tvrtko Ursulin wrote:
After a vm_unbind, UMD can re-bind to same VA range against an active
VM.
Though I am not sue with Mesa usecase if that new mapping is required
for
running GPU job or it will be for the next submission. But ensuring the
tlb flush upon unbind, KMD
On Thu, 23 Jun 2022, Thomas Zimmermann wrote:
> Hi
>
> Am 23.06.22 um 10:26 schrieb Jani Nikula:
>> On Thu, 23 Jun 2022, Thomas Zimmermann wrote:
>>> I forgot to mention that we backmerged v5.19-rc2. That's why the list of
>>> changed files is so long.
>>
>> I thought we should only backmerge
== Series Details ==
Series: drm/i915/selftests: Increase timeout for live_parallel_switch (rev2)
URL : https://patchwork.freedesktop.org/series/105490/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_11795 -> Patchwork_105490v2
Hi
Am 23.06.22 um 10:26 schrieb Jani Nikula:
On Thu, 23 Jun 2022, Thomas Zimmermann wrote:
I forgot to mention that we backmerged v5.19-rc2. That's why the list of
changed files is so long.
I thought we should only backmerge Linus' tree via backmerging drm-next,
which avoids this problem
On 22/06/2022 17:44, Niranjana Vishwanathapura wrote:
On Wed, Jun 22, 2022 at 04:57:17PM +0100, Tvrtko Ursulin wrote:
On 22/06/2022 16:12, Niranjana Vishwanathapura wrote:
On Wed, Jun 22, 2022 at 09:10:07AM +0100, Tvrtko Ursulin wrote:
On 22/06/2022 04:56, Niranjana Vishwanathapura wrote:
On Thu, 23 Jun 2022, Thomas Zimmermann wrote:
> I forgot to mention that we backmerged v5.19-rc2. That's why the list of
> changed files is so long.
I thought we should only backmerge Linus' tree via backmerging drm-next,
which avoids this problem altogether.
BR,
Jani.
--
Jani Nikula, Intel
== Series Details ==
Series: drm/edid: expand on struct drm_edid usage (rev5)
URL : https://patchwork.freedesktop.org/series/104309/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_11795 -> Patchwork_104309v5
Summary
---
On 22/06/2022 22:28, Dixit, Ashutosh wrote:
On Wed, 22 Jun 2022 13:30:23 -0700, Belgaumkar, Vinay wrote:
On 6/21/2022 5:26 PM, Dixit, Ashutosh wrote:
On Sat, 14 May 2022 23:05:06 -0700, Vinay Belgaumkar wrote:
The issue I have is what happens when we de-boost (restore min freq to its
On 23/06/2022 03:31, Alan Previn wrote:
Using two different types of workoads, it was observed that
guc_update_engine_gt_clks was being called too frequently and/or
causing a CPU-to-lmem bandwidth hit over PCIE. Details on
the workloads and numbers are in the notes below.
Background: At the
Hi
Am 23.06.22 um 10:02 schrieb Thomas Zimmermann:
Hi Dave and Daniel,
here's the drm-misc-next PR for this week.
I forgot to mention that we backmerged v5.19-rc2. That's why the list of
changed files is so long.
Best regards
Thomas
--
Thomas Zimmermann
Graphics Driver Developer
SUSE
== Series Details ==
Series: drm/edid: expand on struct drm_edid usage (rev5)
URL : https://patchwork.freedesktop.org/series/104309/
State : warning
== Summary ==
Error: dim checkpatch failed
6703c524e9e9 drm/edid: move drm_connector_update_edid_property() to drm_edid.c
59647b362ac2 drm/edid:
On Wed, 22 Jun 2022, Ville Syrjälä wrote:
> On Wed, Jun 22, 2022 at 01:59:22PM +0300, Jani Nikula wrote:
>> @@ -948,27 +948,30 @@ void intel_lvds_init(struct drm_i915_private *dev_priv)
>> * preferred mode is the right one.
>> */
>> mutex_lock(>mode_config.mutex);
>> -if
Convert all the connectors that use cached connector edid and
detect_edid to drm_edid.
v3: Don't leak vga switcheroo EDID in LVDS init (Ville)
v2: Don't leak opregion fallback EDID (Ville)
Signed-off-by: Jani Nikula
---
.../gpu/drm/i915/display/intel_connector.c| 4 +-
On Tue, 2022-06-21 at 11:44 +0100, Matthew Auld wrote:
> If the move or clear operation somehow fails, and the memory
> underneath
> is not cleared, like when moving to lmem, then we currently fallback
> to
> memcpy or memset. However with small-BAR systems this fallback might
> no
> longer be
Hi Dave, Daniel,
Here's this week drm-misc-fixes PR
Maxime
drm-misc-fixes-2022-06-23:
Multiple fixes in sun4i for suspend, DDC, DMA setup; A rework of vc4 to
properly split the driver between hardware capabilities that wasn't done
properly causing multiple crashes; and a panel quirk for Aya Neo
87 matches
Mail list logo
