== Series Details ==
Series: series starting with [1/2] drm/i915/aux: add separate register macros
and functions for VLV/CHV
URL : https://patchwork.freedesktop.org/series/124999/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_13744_full -> Patchwork_124999v1_full
== Series Details ==
Series: drm/i915: Store DSC DPCD capabilities in the connector (rev9)
URL : https://patchwork.freedesktop.org/series/124723/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_13751 -> Patchwork_124723v9
> -Original Message-
> From: Christopher Braga
> Sent: Friday, September 8, 2023 1:39 AM
> To: Shankar, Uma ; intel-gfx@lists.freedesktop.org;
> dri-
> de...@lists.freedesktop.org
> Cc: Borah, Chaitanya Kumar ; wayland-
> de...@lists.freedesktop.org
> Subject: Re: [RFC 01/33]
== Series Details ==
Series: drm/i915: Store DSC DPCD capabilities in the connector (rev9)
URL : https://patchwork.freedesktop.org/series/124723/
State : warning
== Summary ==
Error: dim checkpatch failed
6f400555c8b5 drm/i915/dp: Sanitize DPCD revision check in
intel_dp_get_dsc_sink_cap()
We encounter a unexpected error on chrome book device while
running kms_busy test. It will restore GPU engine's timeout
value but open incorrect file name (XR24 in below).
openat(AT_FDCWD, "/sys/dev/char/226:0", O_RDONLY) = 12
openat(12, "dev", O_RDONLY) = 13
read(13, "226:0\n", 1023)
== Series Details ==
Series: series starting with [1/3] drm/i915: make some error capture functions
static (rev2)
URL : https://patchwork.freedesktop.org/series/124993/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_13749 -> Patchwork_124993v2
== Series Details ==
Series: series starting with [1/3] drm/i915: make some error capture functions
static (rev2)
URL : https://patchwork.freedesktop.org/series/124993/
State : warning
== Summary ==
Error: dim sparse failed
Sparse version: v0.6.2
Fast mode used, each commit won't be checked
== Series Details ==
Series: series starting with [1/3] drm/i915: make some error capture functions
static (rev2)
URL : https://patchwork.freedesktop.org/series/124993/
State : warning
== Summary ==
Error: dim checkpatch failed
e2e0d9ee6ffa drm/i915: make some error capture functions static
== Series Details ==
Series: drm/i915: stop including i915_utils.h from intel_runtime_pm.h (rev2)
URL : https://patchwork.freedesktop.org/series/124989/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_13749 -> Patchwork_124989v2
== Series Details ==
Series: drm/i915: stop including i915_utils.h from intel_runtime_pm.h (rev2)
URL : https://patchwork.freedesktop.org/series/124989/
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: drop gt/intel_gt.h include from skl_universal_plane.c (rev2)
URL : https://patchwork.freedesktop.org/series/124980/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_13749 -> Patchwork_124980v2
On 10/12/2023 15:38, Jonathan Cavitt wrote:
From: Prathap Kumar Valsan
The GuC firmware had defined the interface for Translation Look-Aside
Buffer (TLB) invalidation. We should use this interface when
invalidating the engine and GuC TLBs.
Add additional functionality to
On 10/12/2023 15:38, Jonathan Cavitt wrote:
In case of GT is suspended, don't allow submission of new TLB invalidation
request and cancel all pending requests. The TLB entries will be
invalidated either during GuC reload or on system resume.
Signed-off-by: Fei Yang
Signed-off-by: Jonathan
== Series Details ==
Series: drm/i915/gt: Temporarily force MTL into uncached mode (rev4)
URL : https://patchwork.freedesktop.org/series/124866/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_13749 -> Patchwork_124866v4
Hi all,
Today's linux-next merge of the drm-misc tree got a conflict in:
arch/ia64/include/asm/fb.h
between commit:
cf8e8658100d ("arch: Remove Itanium (IA-64) architecture")
from the asm-generic tree and commit:
052ddf7b86d2 ("fbdev: Replace fb_pgprotect() with pgprot_framebuffer()")
== Series Details ==
Series: drm/i915/gt: Temporarily force MTL into uncached mode (rev4)
URL : https://patchwork.freedesktop.org/series/124866/
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: Prevent potential null-ptr-deref in engine_init_common (rev2)
URL : https://patchwork.freedesktop.org/series/124971/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_13749 -> Patchwork_124971v2
On 9/19/2023 11:04 AM, Alan Previn wrote:
Debugging PXP issues can't even begin without understanding precedding
sequence of important events. Add drm_dbg into the most important PXP
events.
v3 : - move gt_dbg to after mutex block in function
i915_gsc_proxy_component_bind. (Vivaik)
== Series Details ==
Series: Frontbuffer tracking preparing for Xe (rev2)
URL : https://patchwork.freedesktop.org/series/125033/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_13749 -> Patchwork_125033v2
Summary
---
== Series Details ==
Series: Panel replay phase1 implementation (rev9)
URL : https://patchwork.freedesktop.org/series/94470/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_13742_full -> Patchwork_94470v9_full
Summary
== Series Details ==
Series: Frontbuffer tracking preparing for Xe (rev2)
URL : https://patchwork.freedesktop.org/series/125033/
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: Support FP16 compressed formats on MTL (rev3)
URL : https://patchwork.freedesktop.org/series/124957/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_13749 -> Patchwork_124957v3
Summary
Enable GuC TLB invalidations for MTL. Though more platforms than just
MTL support GuC TLB invalidations, MTL is presently the only platform
that requires it for any purpose, so only enable it there for now to
minimize cross-platform impact.
Signed-off-by: Jonathan Cavitt
Reviewed-by: Andi Shyti
For the gt_tlb live selftest, when operating on the GSC engine,
increase the timeout from 10 ms to 200 ms because the GSC
engine is a bit slower than the rest.
Signed-off-by: Jonathan Cavitt
Reviewed-by: Andi Shyti
Acked-by: Tvrtko Ursulin
Reviewed-by: Nirmoy Das
---
It is not an error for GuC TLB invalidations to fail when the GT is
wedged or disabled, so do not process a wait failure as one in
guc_send_invalidate_tlb.
Signed-off-by: Fei Yang
Signed-off-by: Jonathan Cavitt
CC: John Harrison
Reviewed-by: Andi Shyti
Acked-by: Tvrtko Ursulin
Acked-by:
Implement GuC-based TLB invalidations and use them on MTL.
Some complexity in the implementation was introduced early on
and will be required for range-based TLB invalidations.
RFC: https://patchwork.freedesktop.org/series/124922/
v2:
- Add missing supporting patches.
v3:
- Split suspend/resume
As of now, there is no mechanism for tracking a given request's
progress through the queue. Instead, add a helper that returns
an estimated maximum time the queue should take to drain if
completely full.
Suggested-by: John Harrison
Signed-off-by: Jonathan Cavitt
Reviewed-by: Andi Shyti
In case of GT is suspended, don't allow submission of new TLB invalidation
request and cancel all pending requests. The TLB entries will be
invalidated either during GuC reload or on system resume.
Signed-off-by: Fei Yang
Signed-off-by: Jonathan Cavitt
CC: John Harrison
Reviewed-by: Andi Shyti
From: Prathap Kumar Valsan
The GuC firmware had defined the interface for Translation Look-Aside
Buffer (TLB) invalidation. We should use this interface when
invalidating the engine and GuC TLBs.
Add additional functionality to intel_gt_invalidate_tlb, invalidating
the GuC TLBs and falling back
Add device info flags for if GuC TLB Invalidation is enabled.
Signed-off-by: Jonathan Cavitt
Reviewed-by: Andi Shyti
Acked-by: Tvrtko Ursulin
Reviewed-by: Nirmoy Das
---
drivers/gpu/drm/i915/i915_drv.h | 2 ++
drivers/gpu/drm/i915/intel_device_info.h | 1 +
2 files changed, 3
On Wed, Oct 11, 2023 at 05:27:04PM +0300, Jani Nikula wrote:
> No longer needed after commit 94bcf876cb6a ("drm/i915/mtl: Drop
> Wa_14017240301").
>
> Signed-off-by: Jani Nikula
Reviewed-by: Matt Roper
> ---
> drivers/gpu/drm/i915/display/skl_universal_plane.c | 1 -
> 1 file changed, 1
== Series Details ==
Series: drm/i915/sprite: move sprite_name() to intel_sprite.c (rev2)
URL : https://patchwork.freedesktop.org/series/125000/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_13749 -> Patchwork_125000v2
== Series Details ==
Series: linux-next: build failure after merge of the drm-misc tree (rev2)
URL : https://patchwork.freedesktop.org/series/125017/
State : failure
== Summary ==
Error: patch
https://patchwork.freedesktop.org/api/1.0/series/125017/revisions/2/mbox/ not
applied
Applying:
> -Original Message-
> From: Intel-gfx On Behalf Of Ville
> Syrjala
> Sent: Monday, October 9, 2023 6:52 PM
> To: intel-gfx@lists.freedesktop.org
> Subject: [Intel-gfx] [PATCH 2/4] drm/i915/dsb: Correct DSB command buffer
> cache coherency settings
>
> From: Ville Syrjälä
>
> The
== Series Details ==
Series: drm/i915: Remove the module parameter 'fastboot' (rev5)
URL : https://patchwork.freedesktop.org/series/124255/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_13741_full -> Patchwork_124255v5_full
> -Original Message-
> From: Intel-gfx On Behalf Of Ville
> Syrjala
> Sent: Monday, October 9, 2023 6:52 PM
> To: intel-gfx@lists.freedesktop.org
> Subject: [Intel-gfx] [PATCH 1/4] drm/i915/dsb: Allocate command buffer from
> local memory
>
> From: Ville Syrjälä
>
> Using system
== Series Details ==
Series: drm/i915: Retry gtt fault when out of fence register
URL : https://patchwork.freedesktop.org/series/125058/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_13748 -> Patchwork_125058v1
Summary
== Series Details ==
Series: drm/i915: Retry gtt fault when out of fence register
URL : https://patchwork.freedesktop.org/series/125058/
State : warning
== Summary ==
Error: dim checkpatch failed
34c4698cf822 drm/i915: Retry gtt fault when out of fence register
-:19:
== Series Details ==
Series: drm/i915: Move the g45 PEG band gap HPD workaround to the HPD code
URL : https://patchwork.freedesktop.org/series/125053/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_13748 -> Patchwork_125053v1
Patch calculates bigjoiner pipes in mst compute.
Patch also passes bigjoiner bool to validate plane
max size.
Signed-off-by: vsrini4
---
drivers/gpu/drm/i915/display/intel_dp_mst.c | 19 ---
1 file changed, 12 insertions(+), 7 deletions(-)
diff --git
== Series Details ==
Series: drm/i915: DPLL code cleanups
URL : https://patchwork.freedesktop.org/series/125052/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_13747 -> Patchwork_125052v1
Summary
---
**FAILURE**
== Series Details ==
Series: drm/i915: DPLL code cleanups
URL : https://patchwork.freedesktop.org/series/125052/
State : warning
== Summary ==
Error: dim sparse failed
Sparse version: v0.6.2
Fast mode used, each commit won't be checked separately.
On 10/12/2023 06:45, Patchwork wrote:
Project List - Patchwork *Patch Details*
*Series:* drm/i915: Define and use GuC and CTB TLB invalidation
routines (rev2)
*URL:* https://patchwork.freedesktop.org/series/125002/
*State:*failure
*Details:*
On Thu, Oct 12, 2023 at 03:26:14AM -, Patchwork wrote:
> == Series Details ==
>
> Series: drm/i915: Add new DG2 PCI IDs (rev2)
> URL : https://patchwork.freedesktop.org/series/124937/
> State : success
>
> == Summary ==
>
> CI Bug Log - changes from CI_DRM_13741 -> Patchwork_124937v2
>
On 10/12/2023 03:21, Tvrtko Ursulin wrote:
On 21/09/2023 19:20, john.c.harri...@intel.com wrote:
From: John Harrison
If an active context has been banned (e.g. Ctrl+C killed) then it is
likely to be reset as part of evicting it from the hardware. That
results in a 'ignoring context reset
== Series Details ==
Series: drm/i915: Add bigjoiner force enable option to debugfs (rev3)
URL : https://patchwork.freedesktop.org/series/124730/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_13747 -> Patchwork_124730v3
== Series Details ==
Series: drm/i915: Add bigjoiner force enable option to debugfs (rev3)
URL : https://patchwork.freedesktop.org/series/124730/
State : warning
== Summary ==
Error: dim checkpatch failed
e206f80af151 drm/i915: Add bigjoiner force enable option to debugfs
-:61:
Add some basic info on classmap usage and api
Signed-off-by: Jim Cromie
---
v5- adjustments per Randy Dunlap, me
---
.../admin-guide/dynamic-debug-howto.rst | 59 ++-
1 file changed, 58 insertions(+), 1 deletion(-)
diff --git
Lots of burn-in testing needed before signing, upstreaming.
NOTE: I set default Y to maximize testing by default.
Is there a better way to do this ?
Signed-off-by: Jim Cromie
---
drivers/gpu/drm/Kconfig | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git
Add a DRM_CLASSMAP_USE declaration to 2nd batch of helpers and *_drv.c
files. For drivers, add the decl just above the module's PARAMs,
since it identifies the "inherited" drm.debug param.
Note: with CONFIG_DRM_USE_DYNAMIC_DEBUG=y, a module not also declaring
DRM_CLASSMAP_USE will have its
Incorrectly spelled CFLAGS- failed to add -DDYNAMIC_DEBUG_MODULE,
which broke builds with:
CONFIG_DRM_USE_DYNAMIC_DEBUG=y
CONFIG_DYNAMIC_DEBUG_CORE=y
CONFIG_DYNAMIC_DEBUG=n
Also add subdir-ccflags so that all drivers pick up the addition.
Fixes: 84ec67288c10 ("drm_print: wrap drm_*_dbg in
Reserve bit 7 to remember that a pr-debug callsite is/was:
- enabled, with +p
- wants a dynamic-prefix, with one+ of module:function:sourcfile
- was previously called
- was thus saved in the cache. NOT YET.
Its unclear whether any cache fetch would be faster than 2-3 field
fetches, but theres
dyndbg's dynamic prefixing (by +tmfsl flags) is needlessly expensive.
When an enabled (with +p) pr_debug is called, _DPRINTK_FLAGS_INCL_ANY
prefix decorations are sprintf'd into stack-mem for every call.
This string (or part of it) could be cached once its 1st generated,
and retreived
convert a WARN on 3 conditions, into BUG_ON 2 of them (which don't
happen), and an early return on (!cli->user_mod_name), which *was*
happening, so should be seen going forward. Maybe this should be a
WARN.
NB: The underlying problem was a missing __align(8) in the
DYNDBG_CLASSMAP_USE, which
Remove the NAMED class types; these 2 classmap types accept class
names at the PARAM interface, for example:
echo +DRM_UT_CORE,-DRM_UT_KMS > /sys/module/drm/parameters/debug_names
The code works, but its only used by test-dynamic-debug, and wasn't
asked for by anyone else, so simplify things
Refactor the split of duties between outer & inner fns.
The outer fn was previously just an inline unlikely forward to inner,
which did all the work.
Now, outer handles +t and +l flags itself, and calls inner only when
_DPRINTK_FLAGS_INCL_LOOKUP is needed.
No functional change.
But it does
Extract input validation code, from param_set_dyndbg_module_classes()
(the sys-node >handler) to new: ddebug_classparam_clamp_input(kp),
call it from former. It takes kernel-param arg, so it can complain
about "foo: bad input".
Reuse ddparam_clamp_input(kp) in ddebug_sync_classbits(),
to
move macro from test-dynamic-debug.c into header, and refine it.
Distinguish the 2 use cases of DYNDBG_CLASSMAP_PARAM*
1.DYNDBG_CLASSMAP_PARAM_REF
for DRM, to pass in extern __drm_debug by name.
dyndbg keeps bits in it, so drm can still use it as before
2.DYNDBG_CLASSMAP_PARAM
new
Add a for_each iterator to walk a counted vector member in a struct
(ie the box), and use it to replace 8 open-coded loops.
Signed-off-by: Jim Cromie
---
v5- parens-on-box-force-precedence
---
lib/dynamic_debug.c | 20 +++-
1 file changed, 11 insertions(+), 9 deletions(-)
diff
DECLARE_DYNDBG_CLASSMAP() has a design error; it fails a basic K
rule: "define once, refer many times".
When DRM_USE_DYNAMIC_DEBUG=y, DECLARE_DYNDBG_CLASSMAP() is used across
DRM core & drivers; they all repeat the same classmap-defn args, which
must match for the modules to respond together when
check for actual changes before announcing them, declutter logs.
Signed-off-by: Jim Cromie
---
lib/dynamic_debug.c | 12 +++-
1 file changed, 7 insertions(+), 5 deletions(-)
diff --git a/lib/dynamic_debug.c b/lib/dynamic_debug.c
index b0e11f6bfaa2..b07aab422604 100644
---
Change function's 1st arg-type, and deref in the caller.
The fn doesn't need any other fields in the struct.
no functional change.
Signed-off-by: Jim Cromie
---
lib/dynamic_debug.c | 10 +-
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/lib/dynamic_debug.c
old_bits arg is currently a pointer to the input bits, but this could
allow inadvertent changes to the input by the fn. Disallow this.
And constify new_bits while here.
Signed-off-by: Jim Cromie
---
lib/dynamic_debug.c | 21 +++--
1 file changed, 11 insertions(+), 10
The fn currently says "add-module", then "skipping" if the module has
no prdbgs. Just check 1st and return quietly.
no functional change
Signed-off-by: Jim Cromie
---
lib/dynamic_debug.c | 7 +++
1 file changed, 3 insertions(+), 4 deletions(-)
diff --git a/lib/dynamic_debug.c
rename param_set_dyndbg_classes: add _module_ name & arg, old name is
wrapper to new. New arg allows caller to specify that only one module
is affected by a prdbgs update.
Outer fn preserves kernel_param interface, passing NULL to inner fn.
This selectivity will be used later to narrow the scope
ARRAY_SIZE works here, since array decl is complete.
no functional change
Signed-off-by: Jim Cromie
---
include/linux/dynamic_debug.h | 4 +---
1 file changed, 1 insertion(+), 3 deletions(-)
diff --git a/include/linux/dynamic_debug.h b/include/linux/dynamic_debug.h
index
currently, for verbose=3, these are logged (blank lines for clarity):
dyndbg: query 0: "class DRM_UT_CORE +p" mod:*
dyndbg: split into words: "class" "DRM_UT_CORE" "+p"
dyndbg: op='+'
dyndbg: flags=0x1
dyndbg: *flagsp=0x1 *maskp=0x
dyndbg: parsed: func="" file="" module=""
Add query_module param to ddebug_apply_class_bitmap(). This allows
its caller to update just one module, or all (as currently). We'll
use this later to propagate drm.debug to each USEr as they're
modprobed.
No functional change.
Signed-off-by: Jim Cromie
---
after `modprobe i915`, heres the
Classmaps are stored/linked in a section/array, but are each added to
the module's ddebug_table.maps list-head.
This is unnecessary; even when ddebug_attach_classmap() is handling
the builtin section (with classmaps for multiple builtin modules), its
contents are ordered, so a module's possibly
struct ddebug_class_param keeps a ref to the state-storage of the
param, make both flavors use the same unsigned long under-type.
ISTM this is simpler and safer.
Signed-off-by: Jim Cromie
---
include/linux/dynamic_debug.h | 2 +-
lib/dynamic_debug.c | 2 +-
2 files changed, 2
more careful reading of test output reveals:
lib/test_dynamic_debug.c:103 [test_dynamic_debug]do_cats =pmf "doing
categories\n"
lib/test_dynamic_debug.c:105 [test_dynamic_debug]do_cats =p "LOW msg\n"
class:MID
lib/test_dynamic_debug.c:106 [test_dynamic_debug]do_cats =p "MID msg\n" class:HI
This appears in the control-file to report an unknown class-name, which
indicates that the class_id is not authorized, and dyndbg will ignore
changes to it. Generally, this means that a DYNDBG_CLASSMAP_DEFINE or
DYNDBG_CLASSMAP_USE is missing.
But the word "unknown" appears in quite a few prdbg
hi Jason, DRM-folk
This patchest fixes the chicken-egg initialization problem in the 1st
version of ddebug-class-maps, that DRM-CI uncovered.
The root-problem was DECLARE_DYNDBG_CLASSMAP, which broke the K rule:
"define once, refer many". In patch 14 it is replaced by:
DYNDBG_CLASSMAP_DEFINE
hi Jason, DRM-folk
This patchest fixes the chicken-egg initialization problem in the 1st
version of ddebug-class-maps, that DRM-CI uncovered.
The root-problem was DECLARE_DYNDBG_CLASSMAP, which broke the K rule:
"define once, refer many". In patch 14 it is replaced by:
DYNDBG_CLASSMAP_DEFINE
== Series Details ==
Series: drm/i915: Clean up zero initializers
URL : https://patchwork.freedesktop.org/series/125050/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_13746 -> Patchwork_125050v1
Summary
---
== Series Details ==
Series: drm/i915: Clean up zero initializers
URL : https://patchwork.freedesktop.org/series/125050/
State : warning
== Summary ==
Error: dim sparse failed
Sparse version: v0.6.2
Fast mode used, each commit won't be checked separately.
On Thu, Oct 12, 2023 at 05:56:34PM +0300, Jani Nikula wrote:
> On Thu, 12 Oct 2023, Ville Syrjala wrote:
> > From: Ville Syrjälä
> >
> > Just include the JSL/EHL DPLL4 extra power domain in the dpll_info
> > struct. This way the same approach could be used by other platforms
> > as well (should
On Thu, Oct 12, 2023 at 04:53:38PM +0300, Ville Syrjälä wrote:
> On Thu, Oct 12, 2023 at 03:40:08PM +0200, Greg KH wrote:
> > On Thu, Oct 12, 2023 at 04:28:01PM +0300, Ville Syrjala wrote:
> > > From: Ville Syrjälä
> > >
> > > If we can't find a free fence register to handle a fault in the GMADR
On Tue, 10 Oct 2023, Jouni Högander wrote:
> Currently all module parameters are handled by i915_param.c/h. This
> is a problem for display parameters when Xe driver is used.
>
> This patch set adds a mechanism to add parameters specific to the
> display. This is mainly copied from existing i915
On Thu, 12 Oct 2023, Ville Syrjala wrote:
> From: Ville Syrjälä
>
> Unify the array/struct zero initialization to use the least
> awkward form (= {}).
Yes, please!
Reviewed-by: Jani Nikula
on the series
>
> Ville Syrjälä (6):
> drm/i915/display: Clean up zero initializers
>
On Thu, 12 Oct 2023, Stanislav Lisovskiy wrote:
> For validation purposes, it might be useful to be able to
> force Bigjoiner mode, even if current dotclock/resolution
> do not require that.
> Lets add such to option to debugfs.
>
> v2: - Apparently intel_dp_need_bigjoiner can't be used, when
>
On Thu, 12 Oct 2023, Ville Syrjala wrote:
> From: Ville Syrjälä
>
> We have a bit of duplicated code around the DPLL disabling. Extact
*extract
> that to new function, and for symmetry also do the same for the
> enable direction.
>
> Signed-off-by: Ville Syrjälä
Reviewed-by: Jani Nikula
>
On Thu, 12 Oct 2023, Ville Syrjala wrote:
> From: Ville Syrjälä
>
> The extra DPLL power domain is currently handled in three places:
> - combo_pll_enable()
> - combo_pll_disable()
> - readout_dpll_hw_state()
>
> First two of those are low level PLL funcs, but the third is a higher
> level
On Thu, 12 Oct 2023, Ville Syrjala wrote:
> From: Ville Syrjälä
>
> Just include the JSL/EHL DPLL4 extra power domain in the dpll_info
> struct. This way the same approach could be used by other platforms
> as well (should the need arise), and we don't have to sprinkle
> platform checks all over
On Thu, 12 Oct 2023, Ville Syrjala wrote:
> From: Ville Syrjälä
>
> Use named initializers when populating the DPLL info. This
> is just more convenient and less error prone as we no longer
> have to keep the initializers in a specific order.
>
> Signed-off-by: Ville Syrjälä
Nitpick, it's
On Thu, 12 Oct 2023, Ville Syrjala wrote:
> From: Ville Syrjälä
>
> We are asked to reprogram PEG_BAND_GAP_DATA prior to enabling
> hotplug detection on the g45 HDMI/DP ports. Currently we do said
> reprogamming from the DP/HDMI connector initialization functions.
> That code should be mostly
On Wed, 11 Oct 2023 16:17:39 +0200
Janusz Krzysztofik wrote:
> When igt_kunit() was converted to a helper and wrapped with a new function
> promoted to take the name and role of the library API, related
> documentation was left unchanged and still placed in front the demoted
> function. Update
On Wed, 11 Oct 2023 16:17:37 +0200
Janusz Krzysztofik wrote:
> Function fcntl(..., F_GETFL, ...) that returns file status flags may also
> return a negative error code. Handle that error instead of blindly using
> the returned value as flags.
>
> Signed-off-by: Janusz Krzysztofik
>
On Wed, 11 Oct 2023 16:17:36 +0200
Janusz Krzysztofik wrote:
> A workaround was implemented in IGT KTAP parser so it could accepted KTAP
> reports with missing top level KTAP version and test suite plan headers.
> While the issue has been fixed by a kernel side commit c95e7c05c139
> ("kunit:
== Series Details ==
Series: drm/i915: Remove the modparam verbose_state_checks
URL : https://patchwork.freedesktop.org/series/125047/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_13746 -> Patchwork_125047v1
Summary
== Series Details ==
Series: drm/i915: Remove the modparam verbose_state_checks
URL : https://patchwork.freedesktop.org/series/125047/
State : warning
== Summary ==
Error: dim sparse failed
Sparse version: v0.6.2
Fast mode used, each commit won't be checked separately.
On Thu, Oct 12, 2023 at 03:40:08PM +0200, Greg KH wrote:
> On Thu, Oct 12, 2023 at 04:28:01PM +0300, Ville Syrjala wrote:
> > From: Ville Syrjälä
> >
> > If we can't find a free fence register to handle a fault in the GMADR
> > range just return VM_FAULT_NOPAGE without populating the PTE so that
== Series Details ==
Series: drm/i915: Define and use GuC and CTB TLB invalidation routines (rev2)
URL : https://patchwork.freedesktop.org/series/125002/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_13746 -> Patchwork_125002v2
Hi Dave & Sima -
Here's the 2nd i915 feature pull for v6.7.
There might be another small feature pull coming next week, mainly to
remove force probe for Meteorlake, and promote it to fully
supported. There are some final issues being ironed out still.
There's a backmerge in there; I
On Thu, Oct 12, 2023 at 04:28:01PM +0300, Ville Syrjala wrote:
> From: Ville Syrjälä
>
> If we can't find a free fence register to handle a fault in the GMADR
> range just return VM_FAULT_NOPAGE without populating the PTE so that
> userspace will retry the access and trigger another fault.
From: Ville Syrjälä
If we can't find a free fence register to handle a fault in the GMADR
range just return VM_FAULT_NOPAGE without populating the PTE so that
userspace will retry the access and trigger another fault. Eventually
we should find a free fence and the fault will get properly
== Series Details ==
Series: drm/i915: Define and use GuC and CTB TLB invalidation routines (rev2)
URL : https://patchwork.freedesktop.org/series/125002/
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: Define and use GuC and CTB TLB invalidation routines (rev2)
URL : https://patchwork.freedesktop.org/series/125002/
State : warning
== Summary ==
Error: dim checkpatch failed
d834878536d9 drm/i915: Add GuC TLB Invalidation device info flags
5a90bbf66c6e
On Wed, Oct 11, 2023 at 07:21:02PM +0300, Jani Nikula wrote:
> Remove an unnecessary include.
>
> Signed-off-by: Jani Nikula
Reviewed-by: Ville Syrjälä
> ---
> drivers/gpu/drm/i915/intel_runtime_pm.h | 2 --
> 1 file changed, 2 deletions(-)
>
> diff --git
On Wed, Oct 11, 2023 at 11:22:59PM +0300, Jani Nikula wrote:
> Move sprite_name() where its only user is, and convert it to a function,
> removing the implicit dev_priv usage.
>
> Signed-off-by: Jani Nikula
Reviewed-by: Ville Syrjälä
> ---
> drivers/gpu/drm/i915/display/intel_display.h | 1 -
1 - 100 of 150 matches
Mail list logo
