> From: Alex Williamson
> Sent: Wednesday, April 12, 2023 5:58 AM
>
> On Tue, 11 Apr 2023 15:40:07 -0300
> Jason Gunthorpe wrote:
>
> > On Tue, Apr 11, 2023 at 11:11:17AM -0600, Alex Williamson wrote:
> > > [Appears the list got dropped, replying to my previous message to re-add]
> >
> > Wowo t
> From: Jason Gunthorpe
> Sent: Wednesday, April 12, 2023 8:01 AM
>
> I see this problem as a few basic requirements from a qemu-like
> application:
>
> 1) Does the configuration I was given support reset right now?
> 2) Will the configuration I was given support reset for the duration
> of
On Tue, Apr 11, 2023 at 08:41:11AM +0300, Ville Syrjälä wrote:
> On Mon, Mar 27, 2023 at 08:05:49PM +, Golani, Mitulkumar Ajitkumar wrote:
> > Hi Ville,
> >
> > > -Original Message-
> > > From: Intel-gfx On Behalf Of
> > > Ville
> > > Syrjala
> > > Sent: 21 March 2023 19:26
> > > To:
== Series Details ==
Series: drm/i915: (mostly) PSR related register cleanups (rev4)
URL : https://patchwork.freedesktop.org/series/115708/
State : warning
== Summary ==
Error: dim checkpatch failed
2dc5a9d9fa77 drm/i915: Fix up whitespace in some display chicken registers
4a048ba4896f drm/i91
== Series Details ==
Series: drm/i915: (mostly) PSR related register cleanups (rev4)
URL : https://patchwork.freedesktop.org/series/115708/
State : warning
== Summary ==
Error: dim sparse failed
Sparse version: v0.6.2
Fast mode used, each commit won't be checked separately.
+./arch/x86/include
== Series Details ==
Series: drm/i915: (mostly) PSR related register cleanups (rev4)
URL : https://patchwork.freedesktop.org/series/115708/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_12993 -> Patchwork_115708v4
Summary
-
On Tue, 11 Apr 2023 at 15:45, Daniel Vetter wrote:
>
> On Tue, Apr 11, 2023 at 02:11:18PM +0200, Christian König wrote:
> > Am 11.04.23 um 11:51 schrieb Daniel Vetter:
> > > On Tue, Apr 04, 2023 at 10:06:49PM +0200, Thomas Hellström wrote:
> > > > When swapping out, we will split multi-order pages
Instead of mixing display & non-display stuff together, move
display specific clock info to new debugfs. This patch will
move Current & Max cdclk and Max pixel clock frequency info
to the new debugfs file "i915_display_clock_info".
Cc: Jani Nikula
Signed-off-by: Bhanuprakash Modem
---
.../gpu/d
Instead of mixing display & non-display stuff together, move
display specific clock info to new debugfs. This patch will
move Current & Max cdclk and Max pixel clock frequency info
to the new debugfs file "i915_display_clock_info".
Test-with: 20230412090557.810996-1-bhanuprakash.mo...@intel.com
B
On Wed, 12 Apr 2023, Bhanuprakash Modem wrote:
> Instead of mixing display & non-display stuff together, move
> display specific clock info to new debugfs. This patch will
> move Current & Max cdclk and Max pixel clock frequency info
> to the new debugfs file "i915_display_clock_info".
>
> Cc: Jan
On Wed, 12 Apr 2023, Rui Salvaterra wrote:
> Hi, everyone,
>
> I apologise in advance if I've sent this to {too many, the wrong}
> people. For some time now, I've been getting sporadic (in about one
> out of five boots) DRM-related RCU complaints on an Ivy Bridge-based
> (Core i7-3720QM) Mac Mini.
On Tue, 11 Apr 2023, Gustavo Sousa wrote:
> Quoting Mika Kahola (2023-04-03 05:50:43)
>> @@ -8250,6 +8259,7 @@ void intel_init_display_hooks(struct drm_i915_private
>> *dev_priv)
>> intel_color_init_hooks(dev_priv);
>> intel_init_cdclk_hooks(dev_priv);
>> intel_audio_hooks
Am 12.04.23 um 00:56 schrieb Rob Clark:
From: Rob Clark
Similar motivation to other similar recent attempt[1]. But with an
attempt to have some shared code for this. As well as documentation.
It is probably a bit UMA-centric, I guess devices with VRAM might want
some placement stats as well.
> From: Jason Gunthorpe
> Sent: Wednesday, April 12, 2023 8:01 AM
>
> On Tue, Apr 11, 2023 at 03:58:27PM -0600, Alex Williamson wrote:
>
> > > Management tools already need to understand dev_set if they want to
> > > offer reliable reset support to the VMs. Same as today.
> >
> > I don't think t
Instead of mixing display & non-display stuff together, move
display specific clock info to new debugfs. This patch will
create a new debugfs "i915_cdclk_info" to expose Current & Max
cdclk and Max pixel clock frequency info.
Example:
$ cat /sys/kernel/debug/dri/0/i915_cdclk_info
Current CD clock
Instead of mixing display & non-display stuff together, move
display specific clock info to new debugfs. This patch will
create a new debugfs "i915_cdclk_info" to expose Current & Max
cdclk and Max pixel clock frequency info.
Test-with: 20230412103448.826946-1-bhanuprakash.mo...@intel.com
Bhanupr
Hi Jani,
Thanks for the review, I have floated a new rev [*] by addressing your
comments.
[*]: https://patchwork.freedesktop.org/series/116372/
- Bhanu
On Wed-12-04-2023 02:52 pm, Jani Nikula wrote:
On Wed, 12 Apr 2023, Bhanuprakash Modem wrote:
Instead of mixing display & non-display stu
Hi Rodrigo,
> > > Currently, when we perform operations such as clearing or copying
> > > large blocks of memory, we generate multiple requests that are
> > > executed in a chain.
> > >
> > > However, if one of these requests fails, we may not realize it
> > > unless it happens to be the last req
On Wed, Apr 12, 2023 at 11:17:22AM +0700, Bagas Sanjaya wrote:
> From gitlab issue above, I don't see any progress on bisection attempt.
> Ammar, have you successfully boot Ubuntu 20.04 with v5.10 kernel and
> test there?
I am still using Ubuntu 22.04. Haven't tried 20.04. I'll arrange time
for it
On Wed, 12 Apr 2023, Bhanuprakash Modem wrote:
> Instead of mixing display & non-display stuff together, move
> display specific clock info to new debugfs. This patch will
> create a new debugfs "i915_cdclk_info" to expose Current & Max
> cdclk and Max pixel clock frequency info.
>
> Example:
> $
Hi,
This series of two patches fixes the issue introduced in
cf586021642d80 ("drm/i915/gt: Pipelined page migration") where,
as reported by Matt, in a chain of requests an error is reported
only if happens in the last request.
However Chris noticed that without ensuring exclusivity in the
locking
We have:
- intel_context_timeline_lock()
- intel_context_timeline_unlock()
In the next patches we will also need:
- intel_context_timeline_is_locked()
Add it.
Signed-off-by: Andi Shyti
Cc: sta...@vger.kernel.org
Reviewed-by: Nirmoy Das
---
drivers/gpu/drm/i915/gt/intel_context.h | 6
Make version of the request creation that doesn't hold any
lock.
Signed-off-by: Andi Shyti
Cc: sta...@vger.kernel.org
Reviewed-by: Nirmoy Das
---
drivers/gpu/drm/i915/i915_request.c | 38 +
drivers/gpu/drm/i915/i915_request.h | 2 ++
2 files changed, 30 insertions(+
i915_request_add() assumes that the timeline is locked whtn the
function is called. Before exiting it releases the lock. But in
the next commit we have one case where releasing the timeline
mutex is not necessary and we don't want that.
Make a new i915_request_add_locked() version of the function
From: Chris Wilson
Before taking exclusive ownership of the ring for emitting the request,
wait for space in the ring to become available. This allows others to
take the timeline->mutex to make forward progresses while userspace is
blocked.
In particular, this allows regular clients to issue req
Currently, when we perform operations such as clearing or copying
large blocks of memory, we generate multiple requests that are
executed in a chain.
However, if one of these requests fails, we may not realize it
unless it happens to be the last request in the chain. This is
because errors are not
On 12/04/2023 10:34, Christian König wrote:
Am 12.04.23 um 00:56 schrieb Rob Clark:
From: Rob Clark
Similar motivation to other similar recent attempt[1]. But with an
attempt to have some shared code for this. As well as documentation.
It is probably a bit UMA-centric, I guess devices wit
On 12.04.2023 13:33, Andi Shyti wrote:
We have:
- intel_context_timeline_lock()
- intel_context_timeline_unlock()
In the next patches we will also need:
- intel_context_timeline_is_locked()
Add it.
Signed-off-by: Andi Shyti
Cc: sta...@vger.kernel.org
Reviewed-by: Nirmoy Das
Revi
== Series Details ==
Series: drm/i915: Query compressed bpp properly using correct DPCD and DP Spec
info (rev2)
URL : https://patchwork.freedesktop.org/series/116179/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_12993_full -> Patchwork_116179v2_full
=
== Series Details ==
Series: drm/i915/debugfs: New debugfs for display clock frequencies
URL : https://patchwork.freedesktop.org/series/116369/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_12995 -> Patchwork_116369v1
Summa
Am 12.04.23 um 14:10 schrieb Tvrtko Ursulin:
On 12/04/2023 10:34, Christian König wrote:
Am 12.04.23 um 00:56 schrieb Rob Clark:
From: Rob Clark
Similar motivation to other similar recent attempt[1]. But with an
attempt to have some shared code for this. As well as documentation.
It is pr
Quoting Jani Nikula (2023-04-12 06:33:54)
> On Tue, 11 Apr 2023, Gustavo Sousa wrote:
> > Quoting Mika Kahola (2023-04-03 05:50:43)
> >> @@ -8250,6 +8259,7 @@ void intel_init_display_hooks(struct
> >> drm_i915_private *dev_priv)
> >> intel_color_init_hooks(dev_priv);
> >> intel_in
On 11/04/2023 23:56, Rob Clark wrote:
From: Rob Clark
Signed-off-by: Rob Clark
---
drivers/gpu/drm/i915/i915_driver.c | 3 ++-
drivers/gpu/drm/i915/i915_drm_client.c | 18 +-
drivers/gpu/drm/i915/i915_drm_client.h | 2 +-
3 files changed, 8 insertions(+), 15 deleti
== Series Details ==
Series: series starting with [1/2] drm: Spelling s/sempahore/semaphore/
URL : https://patchwork.freedesktop.org/series/116307/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_12993_full -> Patchwork_116307v1_full
=
== Series Details ==
Series: series starting with [v2,1/2] drm: Spelling s/sempahore/semaphore/
URL : https://patchwork.freedesktop.org/series/116309/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_12993_full -> Patchwork_116309v1_full
==
== Series Details ==
Series: drm/i915/debugfs: New debugfs for display clock frequencies
URL : https://patchwork.freedesktop.org/series/116372/
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: hide mkwrite_device_info() better (rev2)
URL : https://patchwork.freedesktop.org/series/113017/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_12993_full -> Patchwork_113017v2_full
Summ
== Series Details ==
Series: drm/i915/debugfs: New debugfs for display clock frequencies
URL : https://patchwork.freedesktop.org/series/116372/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_12995 -> Patchwork_116372v1
Summa
On 12.04.2023 13:33, Andi Shyti wrote:
Make version of the request creation that doesn't hold any
lock.
Signed-off-by: Andi Shyti
Cc: sta...@vger.kernel.org
Reviewed-by: Nirmoy Das
---
drivers/gpu/drm/i915/i915_request.c | 38 +
drivers/gpu/drm/i915/i915_reque
On 12.04.2023 13:33, Andi Shyti wrote:
i915_request_add() assumes that the timeline is locked whtn the
*when
function is called. Before exiting it releases the lock. But in
the next commit we have one case where releasing the timeline
mutex is not necessary and we don't want that.
Make a new i
On Wed, Apr 12, 2023 at 12:56:26PM +0200, Andi Shyti wrote:
> Hi Rodrigo,
>
> > > > Currently, when we perform operations such as clearing or copying
> > > > large blocks of memory, we generate multiple requests that are
> > > > executed in a chain.
> > > >
> > > > However, if one of these reques
== Series Details ==
Series: drm/i915/display: remove unnecessary i915_debugfs.h includes
URL : https://patchwork.freedesktop.org/series/116315/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_12993_full -> Patchwork_116315v1_full
On Thu, Apr 06, 2023 at 04:02:21PM +0300, Mika Kahola wrote:
Please move this patch before the HDMI one, as the latter has a
dependency on this one.
> From: José Roberto de Souza
>
> The differences between MTL and TGL DP sequences are big enough to
> MTL have its own functions.
>
> Also it is
== Series Details ==
Series: drm/i915: Initialize dkl_phy spin lock from display code path
URL : https://patchwork.freedesktop.org/series/116325/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_12993_full -> Patchwork_116325v1_full
===
Good afternoon Daniel, Dave,
One last pull request for drm-misc-next.
Small one, so easy to merge. As a result also more likely to eat your
computer alive. ;)
Cheers,
~Maarten
drm-misc-next-2023-04-12:
drm-misc-next for v6.4-rc1:
Cross-subsystem Changes:
- Convert MIPI DSIM bridge to ya
On Wed, 12 Apr 2023, Gustavo Sousa wrote:
> Quoting Jani Nikula (2023-04-12 06:33:54)
>> On Tue, 11 Apr 2023, Gustavo Sousa wrote:
>> > Quoting Mika Kahola (2023-04-03 05:50:43)
>> >> @@ -8250,6 +8259,7 @@ void intel_init_display_hooks(struct
>> >> drm_i915_private *dev_priv)
>> >> intel
== Series Details ==
Series: drm/i915/display: Return correct err code for bpc < 0
URL : https://patchwork.freedesktop.org/series/116331/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_12993_full -> Patchwork_116331v1_full
S
On Tue, 11 Apr 2023, "Das, Nirmoy" wrote:
> On 4/11/2023 3:19 PM, Jani Nikula wrote:
>> Leftovers from before display debugfs was separated to its own file.
>>
>> Signed-off-by: Jani Nikula
>
> Reviewed-by: Nirmoy Das
Thanks, pushed to drm-intel-next.
BR,
Jani.
>
>
>> ---
>> drivers/gpu/drm
On Wed, Apr 12, 2023 at 01:32:43PM +0100, Tvrtko Ursulin wrote:
>
> On 11/04/2023 23:56, Rob Clark wrote:
> > From: Rob Clark
> >
> > Signed-off-by: Rob Clark
> > ---
> > drivers/gpu/drm/i915/i915_driver.c | 3 ++-
> > drivers/gpu/drm/i915/i915_drm_client.c | 18 +-
> >
Hi Ville,
> -Original Message-
> From: Ville Syrjälä
> Sent: 11 April 2023 11:11
> To: Golani, Mitulkumar Ajitkumar
> Cc: intel-gfx@lists.freedesktop.org
> Subject: Re: [Intel-gfx] [PATCH v2 5/6] drm/i915/vrr: Relocate VRR
> enable/disable
>
> On Mon, Mar 27, 2023 at 08:05:49PM +, G
Hi Ville,
> -Original Message-
> From: Ville Syrjälä
> Sent: 12 April 2023 13:15
> To: Golani, Mitulkumar Ajitkumar
> Cc: intel-gfx@lists.freedesktop.org
> Subject: Re: [Intel-gfx] [PATCH v2 5/6] drm/i915/vrr: Relocate VRR
> enable/disable
>
> On Tue, Apr 11, 2023 at 08:41:11AM +0300, V
HI Ville,
> -Original Message-
> From: Intel-gfx On Behalf Of
> Golani, Mitulkumar Ajitkumar
> Sent: 12 April 2023 19:45
> To: Ville Syrjälä
> Cc: intel-gfx@lists.freedesktop.org
> Subject: Re: [Intel-gfx] [PATCH v2 5/6] drm/i915/vrr: Relocate VRR
> enable/disable
>
> Hi Ville,
>
> > -
Am 12.04.23 um 11:08 schrieb Daniel Vetter:
On Tue, 11 Apr 2023 at 15:45, Daniel Vetter wrote:
On Tue, Apr 11, 2023 at 02:11:18PM +0200, Christian König wrote:
Am 11.04.23 um 11:51 schrieb Daniel Vetter:
On Tue, Apr 04, 2023 at 10:06:49PM +0200, Thomas Hellström wrote:
When swapping out, we
== Series Details ==
Series: drm/i915/hdcp: Fix CP current state
URL : https://patchwork.freedesktop.org/series/116359/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_12993_full -> Patchwork_116359v1_full
Summary
---
On Wed, Apr 12, 2023 at 02:11:29PM +, Golani, Mitulkumar Ajitkumar wrote:
> Hi Ville,
>
> > -Original Message-
> > From: Ville Syrjälä
> > Sent: 11 April 2023 11:11
> > To: Golani, Mitulkumar Ajitkumar
> > Cc: intel-gfx@lists.freedesktop.org
> > Subject: Re: [Intel-gfx] [PATCH v2 5/6
On Wed, Apr 12, 2023 at 03:32:30PM +0200, Maarten Lankhorst wrote:
>
> Good afternoon Daniel, Dave,
>
> One last pull request for drm-misc-next.
>
> Small one, so easy to merge. As a result also more likely to eat your
> computer alive. ;)
>
> Cheers,
>
> ~Maarten
>
> drm-misc-next-2023-04-12
On 06/04/2023 18:06, Dmitry Osipenko wrote:
> Don't assert held dma-buf reservation lock on memory mapping of exported
> buffer.
>
> We're going to change dma-buf mmap() locking policy such that exporters
> will have to handle the lock. The previous locking policy caused deadlock
> problem for DRM
== Series Details ==
Series: drm/i915: (mostly) PSR related register cleanups (rev4)
URL : https://patchwork.freedesktop.org/series/115708/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_12993_full -> Patchwork_115708v4_full
On Wed, Apr 12, 2023 at 07:27:43AM +, Tian, Kevin wrote:
> > From: Jason Gunthorpe
> > Sent: Wednesday, April 12, 2023 8:01 AM
> >
> > I see this problem as a few basic requirements from a qemu-like
> > application:
> >
> > 1) Does the configuration I was given support reset right now?
> >
On Wed, Apr 12, 2023 at 02:16:22PM +, Golani, Mitulkumar Ajitkumar wrote:
> HI Ville,
>
> > -Original Message-
> > From: Intel-gfx On Behalf Of
> > Golani, Mitulkumar Ajitkumar
> > Sent: 12 April 2023 19:45
> > To: Ville Syrjälä
> > Cc: intel-gfx@lists.freedesktop.org
> > Subject: Re
On 12/04/2023 14:51, Daniel Vetter wrote:
On Wed, Apr 12, 2023 at 01:32:43PM +0100, Tvrtko Ursulin wrote:
On 11/04/2023 23:56, Rob Clark wrote:
From: Rob Clark
Signed-off-by: Rob Clark
---
drivers/gpu/drm/i915/i915_driver.c | 3 ++-
drivers/gpu/drm/i915/i915_drm_client.c | 18 ++
On 31/03/2023 16:32, Fabio M. De Francesco wrote:
On venerdì 31 marzo 2023 13:30:20 CEST Tvrtko Ursulin wrote:
On 31/03/2023 05:18, Ira Weiny wrote:
Zhao Liu wrote:
From: Zhao Liu
The use of kmap_atomic() is being deprecated in favor of
kmap_local_page()[1], and this patch converts the cal
On Tue, 11 Apr 2023 21:01:06 -0300
Jason Gunthorpe wrote:
> On Tue, Apr 11, 2023 at 03:58:27PM -0600, Alex Williamson wrote:
>
> > > Management tools already need to understand dev_set if they want to
> > > offer reliable reset support to the VMs. Same as today.
> >
> > I don't think that's t
On Wed, 12 Apr 2023 10:09:32 +
"Liu, Yi L" wrote:
> > From: Jason Gunthorpe
> > Sent: Wednesday, April 12, 2023 8:01 AM
> >
> > On Tue, Apr 11, 2023 at 03:58:27PM -0600, Alex Williamson wrote:
> >
> > > > Management tools already need to understand dev_set if they want to
> > > > offer r
On Wed, 12 Apr 2023 12:05:50 -0300
Jason Gunthorpe wrote:
> On Wed, Apr 12, 2023 at 07:27:43AM +, Tian, Kevin wrote:
> > > From: Jason Gunthorpe
> > > Sent: Wednesday, April 12, 2023 8:01 AM
> > >
> > > I see this problem as a few basic requirements from a qemu-like
> > > application:
> > >
On Tue, 2023-04-11 at 14:20 -0700, Lucas De Marchi wrote:
> On Tue, Apr 11, 2023 at 08:07:12PM +, Jose Souza wrote:
> > On Tue, 2023-04-11 at 12:59 -0700, Lucas De Marchi wrote:
> > > On Tue, Apr 11, 2023 at 10:51:04AM -0400, Rodrigo Vivi wrote:
> > > > On Tue, Apr 11, 2023 at 12:14:36PM +0300,
== Series Details ==
Series: Fix error propagation amongst request (rev3)
URL : https://patchwork.freedesktop.org/series/114451/
State : warning
== Summary ==
Error: dim checkpatch failed
9e4d4a173f02 drm/i915/gt: Add intel_context_timeline_is_locked helper
5e0b2f6541d9 drm/i915: Create the lo
== Series Details ==
Series: Fix error propagation amongst request (rev3)
URL : https://patchwork.freedesktop.org/series/114451/
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: Fix error propagation amongst request (rev3)
URL : https://patchwork.freedesktop.org/series/114451/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_12996 -> Patchwork_114451v3
Summary
---
*
tree/branch:
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
branch HEAD: 7d8214bba44c1aa6a75921a09a691945d26a8d43 Add linux-next specific
files for 20230412
Error/Warning reports:
https://lore.kernel.org/oe-kbuild-all/202303161521.jbgbafjj-...@intel.com
https
On Wed, Apr 12, 2023 at 04:12:41PM +0100, Tvrtko Ursulin wrote:
>
> On 12/04/2023 14:51, Daniel Vetter wrote:
> > On Wed, Apr 12, 2023 at 01:32:43PM +0100, Tvrtko Ursulin wrote:
> > >
> > > On 11/04/2023 23:56, Rob Clark wrote:
> > > > From: Rob Clark
> > > >
> > > > Signed-off-by: Rob Clark
>
Hi Nikita,
kernel test robot noticed the following build warnings:
[auto build test WARNING on drm-misc/drm-misc-next]
[also build test WARNING on tegra/for-next drm-intel/for-linux-next
drm-intel/for-linux-next-fixes linus/master v6.3-rc6 next-20230412]
[If your patch is applied to the wrong
On Wed, Apr 12, 2023 at 10:50:45AM -0600, Alex Williamson wrote:
> > You keep going back to this, but I maintain userspace doesn't
> > care. qemu is given a list of VFIO devices to use, all it wants to
> > know is if it is allowed to use reset or not. Why should it need to
> > know groups and grou
== Series Details ==
Series: drm/i915/debugfs: New debugfs for display clock frequencies
URL : https://patchwork.freedesktop.org/series/116369/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_12995_full -> Patchwork_116369v1_full
=
== Series Details ==
Series: drm/i915/debugfs: New debugfs for display clock frequencies
URL : https://patchwork.freedesktop.org/series/116372/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_12995_full -> Patchwork_116372v1_full
=
From: Jonathan Cavitt
Convert the igt_mock_ppgtt_huge_fill and igt_mock_ppgtt_64K mock selftests into
live selftests as their requirements have recently become platform-dependent.
Additionally, apply necessary platform dependency checks to these tests.
Signed-off-by: Jonathan Cavitt
Reviewed-by
Hi,
just taking these patches over and respinning them, almost as
they were the last time, just did some trivial cosmetic.
Andi
Changelog
=
v5 -> v6
- Trivial variable declaration reordering
v4 -> v5
- Reorder
v3 -> v4
- Break mock subtest changes into separate patch.
v2 -> v3
- U
From: Jonathan Cavitt
MTL currently uses gen8_ppgtt_insert_huge when managing huge pages. This is
because
MTL reports as not supporting 64K pages, or more accurately, the system that
reports
whether a platform has 64K pages reports false for MTL. This is only half
correct,
as the 64K page su
== Series Details ==
Series: Hugepage manager and test for MTL
URL : https://patchwork.freedesktop.org/series/116401/
State : warning
== Summary ==
Error: dim checkpatch failed
847bd4cec92b drm/i915: Migrate platform-dependent mock hugepage selftests to
live
-:7: WARNING:COMMIT_LOG_LONG_LINE:
== Series Details ==
Series: Hugepage manager and test for MTL
URL : https://patchwork.freedesktop.org/series/116401/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_12997 -> Patchwork_116401v1
Summary
---
**FAILURE**
From: Rob Clark
Similar motivation to other similar recent attempt[1]. But with an
attempt to have some shared code for this. As well as documentation.
It is probably a bit UMA-centric, I guess devices with VRAM might want
some placement stats as well. But this seems like a reasonable start.
From: Rob Clark
Signed-off-by: Rob Clark
---
drivers/gpu/drm/i915/i915_driver.c | 3 ++-
drivers/gpu/drm/i915/i915_drm_client.c | 18 +-
drivers/gpu/drm/i915/i915_drm_client.h | 2 +-
3 files changed, 8 insertions(+), 15 deletions(-)
diff --git a/drivers/gpu/drm/i915/i915
This is a new rev for the series with the same title posted
by Mika Kahola at [1].
Reusing the commit message from the series to preserve the version history.
Phy programming support for C10 phy. This is the first part of
the series that adds support for PICA phy. Later stage the support
for C20 p
From: Mika Kahola
Add DP rates for Meteorlake.
Reviewed-by: Vinod Govindapillai
Signed-off-by: Radhakrishna Sripada
Signed-off-by: Mika Kahola
---
drivers/gpu/drm/i915/display/intel_dp.c | 15 ++-
1 file changed, 14 insertions(+), 1 deletion(-)
diff --git a/drivers/gpu/drm/i915/
From: Mika Kahola
PICA is used for DP alt mode and TBT modes. Hotplug interruption is routed
from PICA chip to south display engine and from there to north display
engine. This patch adds functionality to enable hotplug detection for
all Type-C ports (4 ports available).
Differently from HPD in
From: Clint Taylor
Initialization sequences and C10 phy are in place to be able to enable
the first 2 ports of MTL. The other ports use C20 phy that still need
to be properly added. Enable the first ports for now, keeping a TODO
comment about the others.
Reviewed-by: Lucas De Marchi
Signed-off-
XELPDP has C10 and C20 phys from Synopsys to drive displays. Each phy
has a dedicated PIPE 5.2 Message bus for configuration. This message
bus is used to configure the phy internal registers.
XELPDP has C10 phys to drive output to the EDP and the native output
from the display engine. Add structur
From: Mika Kahola
C10 phys uses direct mapping internally for voltage and pre-emphasis levels.
Program the levels directly to the fields in the VDR Registers.
Bspec: 65449
v2: From table "C10: Tx EQ settings for DP 1.4x" it shows level 1
and preemphasis 1 instead of two times of level 1 pre
From: Ankit Nautiyal
MTL requires the PORT_CTL_WIDTH, TRANS_DDI_FUNC_CTL and DDI_BUF_CTL
to be filled with 4 lanes for TMDS mode.
This patch enables D2D link and fills PORT_WIDTH in appropriate
registers.
v2:
- Added fixes from Clint's Add HDMI implementation changes.
- Modified commit messa
From: Mika Kahola
Create a separate file to store registers for PICA chips
C10 and C20.
v2: Rename file (Jani)
v3: Use _PICK_EVEN_2RANGES() macro (Lucas)
Coding style fixed (Lucas)
v4: Redefine macros (Imre)
Reviewed-by: Vinod Govindapillai (v3)
Signed-off-by: Radhakrishna Sripada
Signed-
Like DG2, we still don't have a proper algorithm that can be used
for calculating PHY settings, but we do have tables of register
values for a handful of the more common link rates. Some support is
better than none, so let's go ahead and add/use these tables when we
can, and also add some logic to
From: José Roberto de Souza
The differences between MTL and TGL DP sequences are big enough to
MTL have its own functions.
Also it is much easier to follow MTL sequences against spec with
its own functions.
One change worthy to mention is the move of
'intel_display_power_get(dev_priv, dig_port-
== Series Details ==
Series: drm/i915/mtl: Add Support for C10 phy (rev2)
URL : https://patchwork.freedesktop.org/series/116191/
State : warning
== Summary ==
Error: dim checkpatch failed
643cdd1a6fc0 drm/i915/mtl: Add DP rates
ad8be772880d drm/i915/mtl: Create separate reg file for PICA regis
== Series Details ==
Series: drm/i915/mtl: Add Support for C10 phy (rev2)
URL : https://patchwork.freedesktop.org/series/116191/
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/mtl: Add Support for C10 phy (rev2)
URL : https://patchwork.freedesktop.org/series/116191/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_12997 -> Patchwork_116191v2
Summary
---
*
Borrow some subtests from xe_guc_pc. Also add per GT debugfs helpers.
v3: Review comments and add HAX patch
v4: Modify the condition for skipping the test
Signed-off-by: Vinay Belgaumkar
Vinay Belgaumkar (3):
lib/debugfs: Add per GT debugfs helpers
i915_pm_freq_api: Add some basic SLPC ig
These can be used to open per-gt debugfs files.
Reviewed-by: Ashutosh Dixit
Signed-off-by: Tvrtko Ursulin
Signed-off-by: Vinay Belgaumkar
---
lib/igt_debugfs.c | 60 +++
lib/igt_debugfs.h | 4
2 files changed, 64 insertions(+)
diff --git a/lib
Validate basic api for GT freq control. Also test
interaction with GT reset. We skip rps tests with
SLPC enabled, this will re-introduce some coverage.
SLPC selftests are already covering some other workload
related scenarios.
v2: Rename test (Rodrigo)
v3: Review comments (Ashutosh)
v4: Skip when
Trying out for CI. Do not review.
Signed-off-by: Vinay Belgaumkar
---
tests/intel-ci/fast-feedback.testlist | 2 ++
1 file changed, 2 insertions(+)
diff --git a/tests/intel-ci/fast-feedback.testlist
b/tests/intel-ci/fast-feedback.testlist
index d9fcb62d..653668dd 100644
--- a/tests/intel-ci/fa
> From: Jason Gunthorpe
> Sent: Wednesday, April 12, 2023 11:06 PM
>
> On Wed, Apr 12, 2023 at 07:27:43AM +, Tian, Kevin wrote:
> > > From: Jason Gunthorpe
> > > Sent: Wednesday, April 12, 2023 8:01 AM
> > >
> > > I see this problem as a few basic requirements from a qemu-like
> > > applicati
1 - 100 of 105 matches
Mail list logo
