Hi Dave,
On Wed, 27 Jul 2022 13:24:45 +1000 Dave Airlie wrote:
>
> My assumption is I fix this on sending my -next tree to Linus with a
> resolution I create at that time?
>
> Is there another option, we have this fixed in out drm-tip tree already.
Sounds good, no problem.
--
Cheers,
Stephen
On Wed, 27 Jul 2022 at 12:55, Stephen Rothwell wrote:
>
> Hi all,
>
> On Mon, 18 Jul 2022 09:44:53 +1000 Stephen Rothwell
> wrote:
> >
> > On Mon, 11 Jul 2022 10:05:45 +0200 Christian König
> > wrote:
> > >
> > > Am 11.07.22 um 04:47 schrieb Stephen Rothwell:
> > > >
> > > > Today's
Hi all,
On Mon, 18 Jul 2022 09:44:53 +1000 Stephen Rothwell
wrote:
>
> On Mon, 11 Jul 2022 10:05:45 +0200 Christian König
> wrote:
> >
> > Am 11.07.22 um 04:47 schrieb Stephen Rothwell:
> > >
> > > Today's linux-next merge of the drm tree got a conflict in:
> > >
> > >
code looks in order and this patch hasnt too much meat to it anyways.
I have 1 question but its not pertaining to the code but rather to the backend
firmware expectation, see below:
On Thu, 2022-06-09 at 16:19 -0700, Ceraolo Spurio, Daniele wrote:
> From: Vitaly Lubart
>
> Adding command
== Series Details ==
Series: drm/ttm: Fix dummy res NULL ptr deref bug
URL : https://patchwork.freedesktop.org/series/106727/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_11945_full -> Patchwork_106727v1_full
Summary
On Thu, 2022-06-09 at 16:19 -0700, Ceraolo Spurio, Daniele wrote:
> From: Tomas Winkler
>
> Support matching with a discrete graphics card.
>
> Signed-off-by: Tomas Winkler
> Cc: Vitaly Lubart
> ---
> drivers/misc/mei/pxp/mei_pxp.c | 13 ++---
> 1 file changed, 10 insertions(+), 3
All looks good:
Reviewed-by: Alan Previn
On Thu, 2022-06-09 at 16:19 -0700, Ceraolo Spurio, Daniele wrote:
> Wait on the fence to be signalled to avoid the submissions finding HuC
> not yet loaded.
>
> Signed-off-by: Daniele Ceraolo Spurio
> Cc: Tony Ye
> ---
>
== Series Details ==
Series: drm/i915: stop using swiotlb (rev5)
URL : https://patchwork.freedesktop.org/series/106589/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_11944_full -> Patchwork_106589v5_full
Summary
---
== Series Details ==
Series: drm/i915/guc: Cancel GuC engine busyness worker synchronously
URL : https://patchwork.freedesktop.org/series/106738/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_11945 -> Patchwork_106738v1
== Series Details ==
Series: drm/i915/guc: Cancel GuC engine busyness worker synchronously
URL : https://patchwork.freedesktop.org/series/106738/
State : warning
== Summary ==
Error: dim checkpatch failed
1dd66d8a76c6 drm/i915/guc: Cancel GuC engine busyness worker synchronously
-:32:
The worker is canceled in gt_park path, but earlier it was assumed that
gt_park path cannot sleep and the cancel is asynchronous. This caused a
race with suspend flow where the worker runs after suspend and causes an
unclaimed register access warning. Cancel the worker synchronously since
the
== Series Details ==
Series: drm/i915/gem: Remove shared locking on freeing objects
URL : https://patchwork.freedesktop.org/series/106720/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_11943_full -> Patchwork_106720v1_full
On 20/07/2022 11:16, Janusz Krzysztofik wrote:
From: Chris Wilson
Inside the shrinker, we cannot wake the device as that may cause
recursion into fs-reclaim, so instead we only unbind vma if the device
is currently awake. (In order to provide reclaim while asleep, we do
wake the device up
== Series Details ==
Series: drm/ttm: Fix dummy res NULL ptr deref bug
URL : https://patchwork.freedesktop.org/series/106727/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_11945 -> Patchwork_106727v1
Summary
---
On 26/07/2022 15:48, Nirmoy Das wrote:
From: Chris Wilson
The obj->base.resv may be shared across many objects, some of which may
still be live and locked, preventing objects from being freed
indefintely. We could individualise the lock during the free, or rely on
a freed object having no
== Series Details ==
Series: drm/i915: Suppress oom warning for shmemfs object allocation failure
(rev3)
URL : https://patchwork.freedesktop.org/series/106528/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_11943_full -> Patchwork_106528v3_full
== Series Details ==
Series: drm/ttm: Fix dummy res NULL ptr deref bug
URL : https://patchwork.freedesktop.org/series/106727/
State : warning
== Summary ==
Error: dim checkpatch failed
f8fdc80c51ce drm/ttm: Fix dummy res NULL ptr deref bug
-:107: WARNING:COMMIT_LOG_LONG_LINE: Possible
== Series Details ==
Series: drm/i915/dp: Check for Low voltage IO only for eDP (rev2)
URL : https://patchwork.freedesktop.org/series/105573/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_11943_full -> Patchwork_105573v2_full
On Mon, Jul 04, 2022 at 04:01:23PM +, Murthy, Arun R wrote:
> > On Mon, Jul 04, 2022 at 12:53:52PM +0530, Arun R Murthy wrote:
> > > On linktraining error/timeout before retry need to wait for 400usec as
> > > per the DP CTS spec1.2
> >
> > s/CTS//
> >
> > > Under section 2.7.2 AUX
== Series Details ==
Series: drm/i915: stop using swiotlb (rev5)
URL : https://patchwork.freedesktop.org/series/106589/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_11944 -> Patchwork_106589v5
Summary
---
Hi,
On Fri, 22 Jul 2022, Taylor, Clinton A wrote:
> Use BSPEC values for the Audio Keep alive M and N values as included in
> the cdclk BSPEC pages for display > 13
looks good, only a few very minor style comments.
I had a table in my original patch, but Ville preferred calculating
Thanks Tvrtko :)
@Roper, Matthew D Did you have any other feedback on this patch?
Anusha
> -Original Message-
> From: Tvrtko Ursulin
> Sent: Tuesday, July 26, 2022 1:59 AM
> To: Srivatsa, Anusha ; intel-
> g...@lists.freedesktop.org; Ursulin, Tvrtko
> Subject: Re: [Intel-gfx] [PATCH]
== Series Details ==
Series: drm/i915/tc: Fix PHY ownership programming in HDMI legacy mode
URL : https://patchwork.freedesktop.org/series/106718/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_11943_full -> Patchwork_106718v1_full
== Series Details ==
Series: drm/i915/gem: Remove shared locking on freeing objects
URL : https://patchwork.freedesktop.org/series/106720/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_11943 -> Patchwork_106720v1
Summary
Calling swiotlb functions directly is nowadays considered harmful. See
https://lore.kernel.org/intel-gfx/20220711082614.ga29...@lst.de/
Replace swiotlb_max_segment() calls with dma_max_mapping_size().
In i915_gem_object_get_pages_internal() no longer consider max_segment
only if CONFIG_SWIOTLB is
== Series Details ==
Series: drm/i915/gem: Remove shared locking on freeing objects
URL : https://patchwork.freedesktop.org/series/106720/
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: Suppress oom warning for shmemfs object allocation failure
(rev3)
URL : https://patchwork.freedesktop.org/series/106528/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_11943 -> Patchwork_106528v3
== Series Details ==
Series: drm/i915: Suppress oom warning for shmemfs object allocation failure
(rev3)
URL : https://patchwork.freedesktop.org/series/106528/
State : warning
== Summary ==
Error: dim sparse failed
Sparse version: v0.6.2
Fast mode used, each commit won't be checked
Please ignore this one.
Nirmoy
On 7/26/2022 4:47 PM, Nirmoy Das wrote:
From: Chris Wilson
We report object allocation failures to userspace with ENOMEM, yet we
still show the memory warning after failing to shrink device allocated
pages. While this warning is similar to other system page
From: Chris Wilson
The obj->base.resv may be shared across many objects, some of which may
still be live and locked, preventing objects from being freed
indefintely. We could individualise the lock during the free, or rely on
a freed object having no contention and being able to immediately free
From: Chris Wilson
We report object allocation failures to userspace with ENOMEM, yet we
still show the memory warning after failing to shrink device allocated
pages. While this warning is similar to other system page allocation
failures, it is superfluous to the ENOMEM provided directly to
== Series Details ==
Series: drm/i915/tc: Fix PHY ownership programming in HDMI legacy mode
URL : https://patchwork.freedesktop.org/series/106718/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_11943 -> Patchwork_106718v1
On 26/07/2022 14:12, Tvrtko Ursulin wrote:
On 25/07/2022 15:18, Robert Beckett wrote:
Calling swiotlb functions directly is nowadays considered harmful. See
https://lore.kernel.org/intel-gfx/20220711082614.ga29...@lst.de/
Replace swiotlb_max_segment() calls with dma_max_mapping_size().
In
Make sure the TypeC PHY ownership flag is not getting reset during
an HDMI modeset on the given port. Besides the WARN this triggered, it
didn't cause other issues, since for TypeC legacy mode setting the
PHY ownership flag is optional (there is no other user of the PHY
besides display).
On 25/07/2022 15:18, Robert Beckett wrote:
Calling swiotlb functions directly is nowadays considered harmful. See
https://lore.kernel.org/intel-gfx/20220711082614.ga29...@lst.de/
Replace swiotlb_max_segment() calls with dma_max_mapping_size().
In i915_gem_object_get_pages_internal() no longer
== Series Details ==
Series: drm/i915: disable pci resize on 32-bit machine
URL : https://patchwork.freedesktop.org/series/106708/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_11943_full -> Patchwork_106708v1_full
Summary
== Series Details ==
Series: drm/i915/dp: Check for Low voltage IO only for eDP (rev2)
URL : https://patchwork.freedesktop.org/series/105573/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_11943_full -> Patchwork_105573v2_full
On 25/07/2022 12:42, Arunpravin Paneer Selvam wrote:
Implemented a new intersect and compatible callback function
fetching start offset from drm buddy allocator.
Signed-off-by: Christian König
Signed-off-by: Arunpravin Paneer Selvam
---
drivers/gpu/drm/i915/i915_ttm_buddy_manager.c | 43
Patchwork wrote on pon [2022-lip-25 19:45:33
+]:
> == Series Details ==
>
> Series: Sanitycheck PCI BARs
> URL : https://patchwork.freedesktop.org/series/106686/
> State : failure
>
> == Summary ==
>
> Error: make failed
> CALLscripts/checksyscalls.sh
> CALL
== Series Details ==
Series: drm/i915: disable pci resize on 32-bit machine
URL : https://patchwork.freedesktop.org/series/106708/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_11943 -> Patchwork_106708v1
Summary
---
On 25/07/2022 19:38, Srivatsa, Anusha wrote:
@Ursulin, Tvrtko Is this wat you had in mind?
Two functions aligned in prototype yes - but I left to you guys which
prototype is correct. AFAICT Matt looked and concluded i915 is correct
so that's good for me.
Regards,
Tvrtko
-Original
On 26/07/2022 06:07, Niranjana Vishwanathapura wrote:
On Mon, Jul 18, 2022 at 11:55:41AM +0100, Tvrtko Ursulin wrote:
On 01/07/2022 23:50, Niranjana Vishwanathapura wrote:
Bind and unbind the mappings upon VM_BIND and VM_UNBIND calls.
Signed-off-by: Niranjana Vishwanathapura
== Series Details ==
Series: drm/i915/dp: Check for Low voltage IO only for eDP (rev2)
URL : https://patchwork.freedesktop.org/series/105573/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_11943 -> Patchwork_105573v2
PCI bar resize only works with 64 bit BAR so disable
this on 32-bit machine.
Fixes: a91d1a17cd341 ("drm/i915: Add support for LMEM PCIe resizable bar")
Signed-off-by: Nirmoy Das
---
drivers/gpu/drm/i915/gt/intel_region_lmem.c | 4
1 file changed, 4 insertions(+)
diff --git
On 7/25/22 2:36 PM, Andrzej Hajda wrote:
On 25.07.2022 11:25, Gwan-gyeong Mun wrote:
It moves overflows_type utility macro into drm util header from
i915_utils
header. The overflows_type can be used to catch the truncation between
data
types. And it adds safe_conversion() macro which
this patch is not related this incomplete issue.
This patch series fixes integer overflow or integer truncation issues in
page lookups, ttm place configuration and scatterlist creation, etc.
This patch has no code changes affecting the test case reported here
(cache mode change after suspend).
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
> -Original Message-
> From: Hajda, Andrzej
> Sent: Friday, July 22, 2022 6:22 PM
> To: Jani Nikula ; Ville Syrjälä
> ; Murthy, Arun R
> Cc: Hajda, Andrzej ; Joonas Lahtinen
> ; Vivi, Rodrigo ;
> Tvrtko Ursulin ; Daniel Vetter
> ; intel-gfx@lists.freedesktop.org; dri-
>
48 matches
Mail list logo
