> -Original Message-
> From: Vivi, Rodrigo
> Sent: Tuesday, August 9, 2022 8:36 PM
> To: Gupta, Anshuman
> Cc: intel-gfx@lists.freedesktop.org; dan...@ffwll.ch; Wilson, Chris P
> ; dri-de...@lists.freedesktop.org
> Subject: Re: [Intel-gfx] [RFC 1/1] drm/i915/dgfx: Avoid parent bridge
== Series Details ==
Series: drm/i915/pxp: don't start pxp without mei_pxp bind (rev2)
URL : https://patchwork.freedesktop.org/series/107099/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_11977_full -> Patchwork_107099v2_full
> -Original Message-
> From: Intel-gfx On Behalf Of Jani
> Nikula
> Sent: Thursday, August 4, 2022 3:29 PM
> To: intel-gfx@lists.freedesktop.org
> Cc: Nikula, Jani
> Subject: [Intel-gfx] [PATCH 2/2] drm/i915/hdcp: replace BIT() with REG_BIT()
> in register definitions
>
> Registers
> -Original Message-
> From: Intel-gfx On Behalf Of Jani
> Nikula
> Sent: Thursday, August 4, 2022 3:29 PM
> To: intel-gfx@lists.freedesktop.org
> Cc: Nikula, Jani
> Subject: [Intel-gfx] [PATCH 1/2] drm/i915/hdcp: split out hdcp registers to a
> separate file
>
> Reduce the bloat of
> -Original Message-
> From: Intel-gfx On Behalf Of Imre
> Deak
> Sent: Monday, August 8, 2022 4:01 PM
> To: intel-gfx@lists.freedesktop.org
> Subject: [Intel-gfx] [PATCH] drm/i915/d13: Fix unclaimed accesses while
> loading PIPEDMC-C/D
>
> At the moment on DG2 at least loading the DMC
== Series Details ==
Series: drm/display/dp_mst: Drop Radeon MST support, make MST atomic-only (rev2)
URL : https://patchwork.freedesktop.org/series/107073/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_11977_full -> Patchwork_107073v2_full
== Series Details ==
Series: drm/i915/guc/slpc: Allow SLPC to use efficient frequency
URL : https://patchwork.freedesktop.org/series/107101/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_11977 -> Patchwork_107101v1
Summary
== Series Details ==
Series: drm/i915/pxp: don't start pxp without mei_pxp bind
URL : https://patchwork.freedesktop.org/series/107099/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_11977_full -> Patchwork_107099v1_full
== Series Details ==
Series: drm/i915/pxp: don't start pxp without mei_pxp bind (rev2)
URL : https://patchwork.freedesktop.org/series/107099/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_11977 -> Patchwork_107099v2
Host Turbo operates at efficient frequency when GT is not idle unless
the user or workload has forced it to a higher level. Replicate the same
behavior in SLPC by allowing the algorithm to use efficient frequency.
We had disabled it during boot due to concerns that it might break
kernel ABI for
== Series Details ==
Series: drm/display/dp_mst: Drop Radeon MST support, make MST atomic-only (rev2)
URL : https://patchwork.freedesktop.org/series/107073/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_11977 -> Patchwork_107073v2
== Series Details ==
Series: drm/i915/pxp: don't start pxp without mei_pxp bind
URL : https://patchwork.freedesktop.org/series/107099/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_11977 -> Patchwork_107099v1
Summary
There's another kind of situation where we could potentially race with
nonblocking modesets and MST, especially if we were to only use the locking
provided by atomic modesetting:
* Display 1 begins as enabled on DP-1 in SST mode
* Display 1 switches to MST mode, exposes one sink in MST mode
*
On 8/9/2022 4:20 PM, Juston Li wrote:
On Tue, Aug 9, 2022 at 4:10 PM Ceraolo Spurio, Daniele
wrote:
On 8/9/2022 3:57 PM, Juston Li wrote:
pxp will not start correctly until after mei_pxp bind completes and
intel_pxp_init_hw() is called.
Signed-off-by: Juston Li
---
On Tue, Aug 9, 2022 at 4:10 PM Ceraolo Spurio, Daniele
wrote:
>
>
>
> On 8/9/2022 3:57 PM, Juston Li wrote:
> > pxp will not start correctly until after mei_pxp bind completes and
> > intel_pxp_init_hw() is called.
> >
> > Signed-off-by: Juston Li
> > ---
> >
On 8/9/2022 3:57 PM, Juston Li wrote:
pxp will not start correctly until after mei_pxp bind completes and
intel_pxp_init_hw() is called.
Signed-off-by: Juston Li
---
drivers/gpu/drm/i915/pxp/intel_pxp.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
On Tue, Aug 09, 2022 at 12:36:50PM +0100, Tvrtko Ursulin wrote:
>
> Digging through git history at least running as Xen dom0 looks to have been
> impacted, but commits such as abb0deacb5a6 ("drm/i915: Fallback to single
> PAGE_SIZE segments for DMA remapping") are older and suggest problem was
On Mon, Aug 08, 2022 at 03:48:02PM +, Hellstrom, Thomas wrote:
> This whole thing looks a bit strange to me since with SWIOTLB actually
> used for i915, the driver should malfunction anyway as it doesn't do
> any dma_sync_sg_for_cpu() or dma_sync_sg_for_device(),
Yeah, I can't actually see
> -Original Message-
> From: Intel-gfx On Behalf Of Matt
> Roper
> Sent: Tuesday, August 2, 2022 11:23 AM
> To: Sripada, Radhakrishna
> Cc: intel-gfx@lists.freedesktop.org
> Subject: Re: [Intel-gfx] [PATCH 21/23] drm/i915/dmc: MTL DMC debugfs
> entries
>
> On Wed, Jul 27, 2022 at
On Tue, 09 Aug 2022, Adrian Larumbe wrote:
> On 03.08.2022 17:22, Jani Nikula wrote:
>>On Tue, 02 Aug 2022, Adrian Larumbe wrote:
>>> Introduces a new module parameter, 'use_pool_alloc', which defaults to
>>> 'false'. Its goal is to make the driver fall back on TTM for setting up
>>> the system
Hi,
On 05/08/2022 14:14, Tetsuo Handa wrote:
On 2022/06/30 22:09, Tvrtko Ursulin wrote:
On the i915 specifics, the caller in
drivers/gpu/drm/i915/gt/selftest_execlists.c
I am pretty sure can be removed. It is synchronized with the error capture side
of
things which is not required for the
[Catching up on mails]
Did you see the feedback form Steven from tracing side of things? Does
this version have that taken into account already?
I think once we have that and acks from dyndbg maintainers then I think we
should just land this and polish from there? Maybe some acks from drm
On 03.08.2022 17:22, Jani Nikula wrote:
>On Tue, 02 Aug 2022, Adrian Larumbe wrote:
>> Introduces a new module parameter, 'use_pool_alloc', which defaults to
>> 'false'. Its goal is to make the driver fall back on TTM for setting up
>> the system memory region, so that object allocation will be
On Mon, Aug 08, 2022 at 04:05:55PM +0530, Anshuman Gupta wrote:
> As per PCIe Spec Section 5.3,
> When a Type 1 Function associated with a Switch/Root
> Port (a “virtual bridge”) is in a non-D0 power state,
> it will emulate the behavior of a conventional PCI bridge
> in its handling of Memory,
On Sat, Jul 02, 2022 at 08:05:54PM +0200, Helge Deller wrote:
> On 6/29/22 12:56, Geert Uytterhoeven wrote:
> > The DRM fbdev emulation layer does not support pushing back
> > changes to fb_var_screeninfo to KMS.
> >
> > However, drm_fb_helper still implements the fb_ops.fb_check_var() and
> >
Am 25.07.22 um 17:18 schrieb Dmitry Osipenko:
The new common dma-buf locking convention will require buffer importers
to hold the reservation lock around mapping operations. Make DRM GEM core
to take the lock around the vmapping operations and update QXL and i915
drivers to use the locked
Am 25.07.22 um 17:18 schrieb Dmitry Osipenko:
Add _unlocked postfix to the dma-buf API function names in a preparation
to move all non-dynamic dma-buf users over to the dynamic locking
specification. This patch only renames API functions, preparing drivers
to the common locking convention. Later
== Series Details ==
Series: series starting with [v5,1/6] drm/ttm: Add new callbacks to ttm res mgr
URL : https://patchwork.freedesktop.org/series/107088/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_11975_full -> Patchwork_107088v1_full
On 08/08/2022 16:48, Hellstrom, Thomas wrote:
Hi, [back from vacation]
On Tue, 2022-07-26 at 16:39 +0100, Robert Beckett wrote:
Calling swiotlb functions directly is nowadays considered harmful.
See
https://lore.kernel.org/intel-gfx/20220711082614.ga29...@lst.de/
Replace
== Series Details ==
Series: drm/ttm: Fix dummy res NULL ptr deref bug (rev3)
URL : https://patchwork.freedesktop.org/series/106727/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_11975 -> Patchwork_106727v3
Summary
---
Everything we are testing here unfortunately fits within one packet (8M)
which means we have zero coverage when we need to split the copy over
multiple packets (including the aux CCS state).
v2:
- Add some coverage for 2G objects, just to see if something blows up
with overflowing int. (Ram)
On Wed, Jul 13, 2022 at 09:11:59AM +0100, Mauro Carvalho Chehab wrote:
> The documentation for the flags field is missing there. It sounds
> that some last-time change converted some bools into flags, but
> the kernel-doc change didn't follow it.
>
> Fix those warnings:
>
>
On Wed, Jul 13, 2022 at 09:12:23AM +0100, Mauro Carvalho Chehab wrote:
> There are other files with kernel-doc markups:
>
> $ git grep -l "/\*\*" $(git ls-files|grep drivers/gpu/drm/i915/)
> >kernel-doc-files
> $ for i in $(cat kernel-doc-files); do if [ "$(git grep $i
>
== Series Details ==
Series: series starting with [v5,1/6] drm/ttm: Add new callbacks to ttm res mgr
URL : https://patchwork.freedesktop.org/series/107088/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_11975 -> Patchwork_107088v1
On Wed, Jul 13, 2022 at 09:12:27AM +0100, Mauro Carvalho Chehab wrote:
> Currently, functions inside GuC aren't presented as part of the
> GuC documentation.
>
> Add them.
>
> Signed-off-by: Mauro Carvalho Chehab
could be squashed to the other guc patch, but anyways:
Reviewed-by: Rodrigo Vivi
On Wed, Jul 13, 2022 at 09:12:19AM +0100, Mauro Carvalho Chehab wrote:
> There are several documented GuC kAPI that aren't currently part
> of the docs. Add them, as this allows identifying issues with
> badly-formatted tags.
>
> Signed-off-by: Mauro Carvalho Chehab
Reviewed-by: Rodrigo Vivi
>
On Wed, Jul 13, 2022 at 09:12:26AM +0100, Mauro Carvalho Chehab wrote:
> The intel_gt_pm.h file contains some convenient macros to be used
> in GT code in order to get/put runtime PM references and for
> checking them.
>
> Add descriptions based on the ones at intel_wakeref.h and
>
On Wed, Jul 13, 2022 at 09:12:24AM +0100, Mauro Carvalho Chehab wrote:
> commit d1b48c1e7184 ("drm/i915: Replace execbuf vma ht with an idr")
> added a rbtree list to allow searching for obj/ctx.
>
> Document it.
>
> Signed-off-by: Mauro Carvalho Chehab
Reviewed-by: Rodrigo Vivi
> ---
>
> To
On Wed, Jul 13, 2022 at 09:12:25AM +0100, Mauro Carvalho Chehab wrote:
> This is a large struct used to describe gem objects. It is
> currently partially documented. Finish its documentation, filling
> the gaps from git logs.
>
> Signed-off-by: Mauro Carvalho Chehab
Reviewed-by: Rodrigo Vivi
>
On Wed, Jul 13, 2022 at 09:12:21AM +0100, Mauro Carvalho Chehab wrote:
> Both intel_runtime_pm.h and intel_pm.c contains kAPI for
> runtime PM. So, add them to the documentation.
>
> Signed-off-by: Mauro Carvalho Chehab
Reviewed-by: Rodrigo Vivi
> ---
>
> To avoid mailbombing on a large
On Wed, Jul 13, 2022 at 09:12:22AM +0100, Mauro Carvalho Chehab wrote:
> There are several documented GEM/TTM kAPI that aren't currently part
> of the docs. Add them, as this allows identifying issues with
> badly-formatted tags.
>
> Signed-off-by: Mauro Carvalho Chehab
Reviewed-by: Rodrigo
On Wed, Jul 13, 2022 at 09:12:18AM +0100, Mauro Carvalho Chehab wrote:
> There are several documented GT kAPI that aren't currently part
> of the docs. Add them, as this allows identifying issues with
> badly-formatted tags.
>
> Signed-off-by: Mauro Carvalho Chehab
> ---
>
> To avoid
On Wed, Jul 13, 2022 at 09:12:07AM +0100, Mauro Carvalho Chehab wrote:
> The kernel-doc markup for i915_gem_apply_to_region_ops() has some
> issues:
>
> 1. The field should be marked as @process_obj;
> 2. The callback parameters aren't document properly, as sphinx
>will consider them to be
On Wed, Jul 13, 2022 at 09:12:17AM +0100, Mauro Carvalho Chehab wrote:
> There are several documented kAPI at the display side that
> aren't currently part of the docs. Add them, as this allows
> identifying issues with badly-formatted tags.
>
> Signed-off-by: Mauro Carvalho Chehab
same here,
On Wed, Jul 13, 2022 at 09:12:20AM +0100, Mauro Carvalho Chehab wrote:
> There are several documented GVT kAPI that aren't currently part
> of the docs. Add them, as this allows identifying issues with
> badly-formatted tags.
>
> Signed-off-by: Mauro Carvalho Chehab
I haven't checked if these
== Series Details ==
Series: series starting with [v5,1/6] drm/ttm: Add new callbacks to ttm res mgr
URL : https://patchwork.freedesktop.org/series/107088/
State : warning
== Summary ==
Error: dim sparse failed
Sparse version: v0.6.2
Fast mode used, each commit won't be checked separately.
On Wed, Jul 13, 2022 at 09:12:06AM +0100, Mauro Carvalho Chehab wrote:
> Preserving ascii artwork on kernel-docs is tricky, as it needs
> to respect both the Sphinx rules and be properly parsed by
> kernel-doc script.
>
> The Sphinx syntax require code-blocks, which is:
>
> ::
>
>
Am 09.08.22 um 11:22 schrieb Arunpravin Paneer Selvam:
Apply new intersect and compatible callback instead
of having a generic placement range verfications.
v2: Added a separate callback for compatiblilty
checks (Christian)
We need to move parts of this patch earlier or the i915 will
On Wed, Jul 13, 2022 at 09:12:03AM +0100, Mauro Carvalho Chehab wrote:
> The return code table is not properly marked, causing warnings
> and being badly parsed by Sphinx:
>
> Documentation/gpu/i915:130:
> ./drivers/gpu/drm/i915/display/intel_dp_link_training.c:183: WARNING: Block
> quote
On 8/4/22 12:06 PM, Andi Shyti wrote:
Hi Jani,
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 performs a type conversion
(cast) of an source
== Series Details ==
Series: drm/i915/display: avoid abnormal pixel output when turn eDP display off
(rev2)
URL : https://patchwork.freedesktop.org/series/106910/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_11975 -> Patchwork_106910v2
On Tue, 9 Aug 2022 00:15:14 +
"Vivi, Rodrigo" wrote:
> On Tue, 2022-08-09 at 01:09 +0200, Andi Shyti wrote:
> > Hi Rodrigo,
> >
> > On Mon, Aug 08, 2022 at 03:04:13PM -0400, Rodrigo Vivi wrote:
> > > On Mon, Aug 08, 2022 at 06:37:58PM +0200, Andi Shyti wrote:
> > > > Hi Mauro,
> > > >
> >
52 matches
Mail list logo
