From: Ville Syrjälä
The DP spec says:
"If the receiver keeps the same value in the ADJUST_REQUEST_LANEx_y
register(s) while the LANEx_CR_DONE bits remain unset, the transmitter
must loop four times with the same voltage swing. On the fifth time,
the transmitter must down-shift to the lower bit
On Fri, Oct 01, 2021 at 12:57:13PM +0300, Jani Nikula wrote:
On Fri, 01 Oct 2021, Chris Wilson wrote:
Quoting Lucas De Marchi (2021-10-01 08:40:41)
When trying to bring IS_ACTIVE to linux/kconfig.h I thought it wouldn't
provide much value just encapsulating it in a boolean context. So I also
a
The formulae has been updated to include more variables. Make
sure the code carries the same.
Bspec: 64631
v2: Make GEN11 follow the default route and fix calculation of
maxdebw(RK)
v3: Fix div by zero on default case
Correct indent for fallthrough(Jani)
v4: Fix div by zero on gen11.
v5:
== Series Details ==
Series: drm/i915/reg: add AUD_TCA_DP_2DOT0_CTRL registers
URL : https://patchwork.freedesktop.org/series/95316/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_10678 -> Patchwork_21216
Summary
---
== Series Details ==
Series: drm/locking: add backtrace for locking contended locks without backoff
(rev2)
URL : https://patchwork.freedesktop.org/series/95182/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_10674_full -> Patchwork_21215_full
==
> -Original Message-
> From: Intel-gfx On Behalf Of Ville
> Syrjala
> Sent: Wednesday, September 29, 2021 12:21 AM
> To: intel-gfx@lists.freedesktop.org
> Subject: [Intel-gfx] [PATCH] drm/i915: Stop force enabling pipe bottom color
> gammma/csc
>
> From: Ville Syrjälä
>
> While sanit
On Fri, Oct 01, 2021 at 07:08:26PM +0300, Ville Syrjala wrote:
> From: Ville Syrjälä
>
> The DP spec says:
> "If the receiver keeps the same value in the ADJUST_REQUEST_LANEx_y
> register(s) while the LANEx_CR_DONE bits remain unset, the transmitter
> must loop four times with the same voltage
== Series Details ==
Series: drm/i915/dg2: update link training for 128b/132b
URL : https://patchwork.freedesktop.org/series/95317/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip
a29a3e413068 drm/i915/dg2: update link training for 128b/132b
-:27: WARNING:UNNECESSARY_ELSE: else i
On Fri, Oct 01, 2021 at 05:12:03PM +, Shankar, Uma wrote:
>
>
> > -Original Message-
> > From: Intel-gfx On Behalf Of
> > Ville Syrjala
> > Sent: Wednesday, September 29, 2021 12:21 AM
> > To: intel-gfx@lists.freedesktop.org
> > Subject: [Intel-gfx] [PATCH] drm/i915: Stop force enab
== Series Details ==
Series: drm/i915/dg2: update link training for 128b/132b
URL : https://patchwork.freedesktop.org/series/95317/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_10679 -> Patchwork_21217
Summary
---
*
== Series Details ==
Series: series starting with [01/28] dma-buf: add
dma_resv_for_each_fence_unlocked v7
URL : https://patchwork.freedesktop.org/series/95322/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip
245f2aaae8e7 dma-buf: add dma_resv_for_each_fence_unlocked v7
-:23: WA
On Fri, Oct 01, 2021 at 08:45:49PM +0300, Ville Syrjälä wrote:
> On Fri, Oct 01, 2021 at 05:12:03PM +, Shankar, Uma wrote:
> >
> >
> > > -Original Message-
> > > From: Intel-gfx On Behalf Of
> > > Ville Syrjala
> > > Sent: Wednesday, September 29, 2021 12:21 AM
> > > To: intel-gfx@l
== Series Details ==
Series: series starting with [01/28] dma-buf: add
dma_resv_for_each_fence_unlocked v7
URL : https://patchwork.freedesktop.org/series/95322/
State : warning
== Summary ==
$ dim sparse --fast origin/drm-tip
Sparse version: v0.6.2
Fast mode used, each commit won't be checked
On Fri, Oct 01, 2021 at 02:04:04PM +0300, Jani Nikula wrote:
> On Fri, 27 Aug 2021, Jason Gunthorpe wrote:
> > On Fri, Aug 27, 2021 at 03:12:36PM +, kernel test robot wrote:
> >> tree: https://github.com/awilliam/linux-vfio.git next
> >> head: ea870730d83fc13a5fa2bd0e175176d7ac8a400a
> >>
On Thu, Sep 30, 2021 at 03:01:19PM -0700, Matt Roper wrote:
> On Sun, Sep 26, 2021 at 10:10:05PM +0200, Michal Wajdeczko wrote:
> > We assumed that for all modern GENs the PTEs and register space are
> > split in the GTTMMADR BAR, but while it is true, we should rather use
> > fixed offset as it is
== Series Details ==
Series: series starting with [01/28] dma-buf: add
dma_resv_for_each_fence_unlocked v7
URL : https://patchwork.freedesktop.org/series/95322/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_10679 -> Patchwork_21218
On Fri, Sep 24, 2021 at 08:43:07AM +0200, Fernando Ramos wrote:
> Hi all,
>
> One of the things in the DRM TODO list ("Documentation/gpu/todo.rst") was to
> "use DRM_MODESET_LOCAL_ALL_* helpers instead of boilerplate". That's what this
> patch series is about.
>
> You will find two types of chang
On Fri, Oct 01, 2021 at 02:36:55PM -0400, Sean Paul wrote:
> On Fri, Sep 24, 2021 at 08:43:07AM +0200, Fernando Ramos wrote:
> > Hi all,
> >
> > One of the things in the DRM TODO list ("Documentation/gpu/todo.rst") was to
> > "use DRM_MODESET_LOCAL_ALL_* helpers instead of boilerplate". That's wha
On Fri, 01 Oct 2021 11:11:41 -0400, Sean Paul wrote:
> From: Sean Paul
>
> This patch adds the bindings for the MSM DisplayPort HDCP registers
> which are required to write the HDCP key into the display controller as
> well as the registers to enable HDCP authentication/key
> exchange/encryption.
On Sun, Sep 26, 2021 at 08:31:46PM +, Patchwork wrote:
> == Series Details ==
>
> Series: drm/i915/guc: Improve CTB error handling (rev3)
> URL : https://patchwork.freedesktop.org/series/92118/
> State : success
>
> == Summary ==
>
> CI Bug Log - changes from CI_DRM_10644_full -> Patchwork
== Series Details ==
Series: drm/i915: DP per-lane drive settings prep work (rev5)
URL : https://patchwork.freedesktop.org/series/95122/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip
cf1c2f180fc0 drm/i915: Introduce has_iboost()
0331dcae40fa drm/i915: Introduce has_buf_trans_se
== Series Details ==
Series: drm/i915: DP per-lane drive settings prep work (rev5)
URL : https://patchwork.freedesktop.org/series/95122/
State : warning
== Summary ==
$ dim sparse --fast origin/drm-tip
Sparse version: v0.6.2
Fast mode used, each commit won't be checked separately.
-
+drivers/g
On Fri, Oct 01, 2021 at 10:00:50PM +0300, Ville Syrjälä wrote:
> On Fri, Oct 01, 2021 at 02:36:55PM -0400, Sean Paul wrote:
> > On Fri, Sep 24, 2021 at 08:43:07AM +0200, Fernando Ramos wrote:
> > > Hi all,
> > >
> > > One of the things in the DRM TODO list ("Documentation/gpu/todo.rst") was
> > >
== Series Details ==
Series: drm/hdcp: Pull HDCP auth/exchange/check into helpers (rev2)
URL : https://patchwork.freedesktop.org/series/94712/
State : failure
== Summary ==
Applying: drm/hdcp: Add drm_hdcp_atomic_check()
Applying: drm/hdcp: Avoid changing crtc state in hdcp atomic check
Applyi
== Series Details ==
Series: drm/i915: DP per-lane drive settings prep work (rev5)
URL : https://patchwork.freedesktop.org/series/95122/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_10680 -> Patchwork_21219
Summary
---
On Thu, Sep 30, 2021 at 10:09:42PM +0300, Ville Syrjala wrote:
> From: Ville Syrjälä
>
> Looks like skl/bxt/derivatives also need the plane stride
> stretch w/a when using async flips and VT-d is enabled, or
> else we get corruption on screen. To my surprise this was
> even documented in bspec, b
== Series Details ==
Series: drm/i915: Fix bug in user proto-context creation that leaked contexts
(rev2)
URL : https://patchwork.freedesktop.org/series/94962/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_10680 -> Patchwork_21221
=
mdev_device should only be used in functions assigned to ops callbacks,
interior functions should use the struct vfio_ccw_private instead of
repeatedly trying to get it from the mdev.
Reviewed-by: Christoph Hellwig
Reviewed-by: Cornelia Huck
Reviewed-by: Eric Farman
Signed-off-by: Jason Gunthor
The subchannel should be left in a quiescent state unless the VFIO device
FD is opened. When the FD is opened bring the chanel to active and allow
the VFIO device to operate. When the device FD is closed then quiesce the
channel.
To make this work the FSM needs to handle the transitions to/from op
This is a more complicated conversion because vfio_ccw is sharing the
vfio_device between both the mdev_device, its vfio_device and the
css_driver.
The mdev is a singleton, and the reason for this sharing is so the extra
css_driver function callbacks to be delivered to the vfio_device
implementati
Since the ccw_io_region was split out of the private the allocation no
longer needs the GFP_DMA. Remove it.
Reported-by: Christoph Hellwig
Fixes: c98e16b2fa12 ("s390/cio: Convert ccw_io_region to pointer")
Signed-off-by: Jason Gunthorpe
---
drivers/s390/cio/vfio_ccw_drv.c | 2 +-
1 file changed
Makes the code easier to understand what is memory lifecycle and what is
other stuff.
Reviewed-by: Eric Farman
Signed-off-by: Jason Gunthorpe
---
drivers/s390/cio/vfio_ccw_drv.c | 137 ++--
1 file changed, 78 insertions(+), 59 deletions(-)
diff --git a/drivers/s390/
The css_driver's main purpose is to create/destroy the mdev and relay the
shutdown, irq, sch_event, and chp_event css_driver ops to the single
created vfio_device, if it exists.
Reframe the boundary where the css_driver domain switches to the vfio
domain by using rcu to read and refcount the vfio_
Every driver just emits a static string, simply feed it through the ops
and provide a standard sysfs show function.
Signed-off-by: Jason Gunthorpe
---
.../driver-api/vfio-mediated-device.rst | 4 ++-
drivers/gpu/drm/i915/gvt/kvmgt.c | 9 +--
drivers/s390/cio/vfio_ccw_ops
vfio_ccw will need it.
Signed-off-by: Jason Gunthorpe
---
drivers/vfio/vfio.c | 3 ++-
include/linux/vfio.h | 1 +
2 files changed, 3 insertions(+), 1 deletion(-)
diff --git a/drivers/vfio/vfio.c b/drivers/vfio/vfio.c
index 08b27b64f0f935..44adf112e3b5dd 100644
--- a/drivers/vfio/vfio.c
+++ b/
Having a mdev pointer floating about in addition to a struct vfio_device
is confusing. It is only used for three things:
- Getting the mdev 'struct device *' - this is the same as
private->vdev.dev
- Printing the uuid of the mdev in logging. The uuid is also the dev_name
of the mdev so thi
This addresses Cornelia's remark on the earlier patch that ccw has a
confusing lifecycle. While it doesn't seem like the original attempt was
functionally wrong, the result can be made better with a lot of further
work.
Reorganize the driver so that the mdev owns the private memory and
controls th
Many of the mdev drivers use a simple counter for keeping track of the
available instances. Move this code to the core code and store the counter
in the mdev_type. Implement it using correct locking, fixing mdpy.
Drivers provide a get_available() callback to set the number of available
instances f
On Fri, Oct 01, 2021 at 02:08:15PM -0700, Matt Roper wrote:
> On Thu, Sep 30, 2021 at 10:09:42PM +0300, Ville Syrjala wrote:
> > From: Ville Syrjälä
> >
> > Looks like skl/bxt/derivatives also need the plane stride
> > stretch w/a when using async flips and VT-d is enabled, or
> > else we get cor
On Fri, Oct 01, 2021 at 04:48:15PM -0400, Sean Paul wrote:
> On Fri, Oct 01, 2021 at 10:00:50PM +0300, Ville Syrjälä wrote:
> > On Fri, Oct 01, 2021 at 02:36:55PM -0400, Sean Paul wrote:
> > > On Fri, Sep 24, 2021 at 08:43:07AM +0200, Fernando Ramos wrote:
> > > > Hi all,
> > > >
> > > > One of th
== Series Details ==
Series: drm/i915/reg: add AUD_TCA_DP_2DOT0_CTRL registers
URL : https://patchwork.freedesktop.org/series/95316/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_10678_full -> Patchwork_21216_full
Summary
-
== Series Details ==
Series: drm/i915: remove IS_ACTIVE (rev2)
URL : https://patchwork.freedesktop.org/series/95312/
State : failure
== Summary ==
Applying: drm/i915: remove IS_ACTIVE
error: patch failed: drivers/gpu/drm/i915/i915_config.c:8
error: drivers/gpu/drm/i915/i915_config.c: patch doe
== Series Details ==
Series: drm/i915: Fix DP clock recovery "voltage_tries" handling
URL : https://patchwork.freedesktop.org/series/95339/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_10680 -> Patchwork_21222
Summary
On Sat, Oct 02, 2021 at 01:01:31AM +0300, Ville Syrjälä wrote:
> On Fri, Oct 01, 2021 at 02:08:15PM -0700, Matt Roper wrote:
> > On Thu, Sep 30, 2021 at 10:09:42PM +0300, Ville Syrjala wrote:
> > > From: Ville Syrjälä
> > >
> > > Looks like skl/bxt/derivatives also need the plane stride
> > > str
== Series Details ==
Series: drm/i915: Update memory bandwidth formulae (rev5)
URL : https://patchwork.freedesktop.org/series/95138/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_10680 -> Patchwork_21224
Summary
---
When I originally moved all of the VESA backlight code in i915 into DRM
helpers, one of the things I didn't have the hardware or time for
testing was machines that used a combination of PWM and DPCD in order to
control their backlights. This has since then caused some breakages and
resulted in us d
Since we don't support hybrid AUX/PWM backlights in nouveau right now,
let's add some explicit checks so that we don't break nouveau once we
enable support for these backlights in other drivers.
Signed-off-by: Lyude Paul
---
drivers/gpu/drm/nouveau/nouveau_backlight.c | 5 -
1 file changed,
This simply adds proper support for panel backlights that can be controlled
via VESA's backlight control protocol, but which also require that we
enable and disable the backlight via PWM instead of via the DPCD interface.
We also enable this by default, in order to fix some people's backlights
that
Hooray! We've managed to hit enough bugs upstream that I've been able to
come up with a pretty solid explanation for how backlight controls are
actually supposed to be detected and used these days. As well, having the
rest of the PWM bits in VESA's backlight interface implemented seems to
have fixe
Now that we've added support to i915 for controlling panel backlights that
need PWM to be enabled/disabled, let's finalize this and add support for
controlling brightness levels via PWM as well. This should hopefully put us
towards the path of supporting _ALL_ backlights via VESA's DPCD interface
w
On Fri, Oct 01, 2021 at 09:16:26AM -0700, Radhakrishna Sripada wrote:
> The formulae has been updated to include more variables. Make
> sure the code carries the same.
>
> Bspec: 64631
I notice .deburst should be set to 8 rather than 16 on RKL.
>
> v2: Make GEN11 follow the default route and fi
== Series Details ==
Series: Move vfio_ccw to the new mdev API (rev5)
URL : https://patchwork.freedesktop.org/series/94520/
State : failure
== Summary ==
Applying: vfio/ccw: Remove unneeded GFP_DMA
Applying: vfio/ccw: Use functions for alloc/free of the vfio_ccw_private
Applying: vfio/ccw: Pas
== Series Details ==
Series: drm/i915/display: Wait PSR2 get out of deep sleep to update pipe (rev2)
URL : https://patchwork.freedesktop.org/series/95309/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_10680 -> Patchwork_21225
===
== Series Details ==
Series: drm/dp, drm/i915: Finish basic PWM support for VESA backlight helpers
(rev3)
URL : https://patchwork.freedesktop.org/series/95127/
State : warning
== Summary ==
$ dim sparse --fast origin/drm-tip
Sparse version: v0.6.2
Fast mode used, each commit won't be checked
== Series Details ==
Series: drm/i915/dg2: update link training for 128b/132b
URL : https://patchwork.freedesktop.org/series/95317/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_10679_full -> Patchwork_21217_full
Summary
--
== Series Details ==
Series: drm/dp, drm/i915: Finish basic PWM support for VESA backlight helpers
(rev3)
URL : https://patchwork.freedesktop.org/series/95127/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_10680 -> Patchwork_21227
=
On Sat, Oct 02, 2021 at 01:05:47AM +0300, Ville Syrjälä wrote:
> On Fri, Oct 01, 2021 at 04:48:15PM -0400, Sean Paul wrote:
> > On Fri, Oct 01, 2021 at 10:00:50PM +0300, Ville Syrjälä wrote:
> > > On Fri, Oct 01, 2021 at 02:36:55PM -0400, Sean Paul wrote:
> > > > On Fri, Sep 24, 2021 at 08:43:07AM
== Series Details ==
Series: drm/i915: DP per-lane drive settings prep work (rev5)
URL : https://patchwork.freedesktop.org/series/95122/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_10680_full -> Patchwork_21219_full
Summa
== Series Details ==
Series: drm/i915: Fix bug in user proto-context creation that leaked contexts
(rev2)
URL : https://patchwork.freedesktop.org/series/94962/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_10680_full -> Patchwork_21221_full
===
== Series Details ==
Series: drm/i915: Fix DP clock recovery "voltage_tries" handling
URL : https://patchwork.freedesktop.org/series/95339/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_10680_full -> Patchwork_21222_full
Su
applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch]
url:
https://github.com/0day-ci/linux/commits/Lucas-De-Marchi/drm-i915-remove-IS_ACTIVE/20211001-154226
b
When I tried to test patches applied to v5.15-rc3, I hit this bug (and
hence can not test my code), on 32 bit x86.
[ cut here ]
kernel BUG at drivers/gpu/drm/i915/i915_sw_fence.c:245!
invalid opcode: [#1] SMP PTI
CPU: 3 PID: 1 Comm: swapper/0 Not tainted 5.14.0-rc1-tes
== Series Details ==
Series: drm/i915: Update memory bandwidth formulae (rev5)
URL : https://patchwork.freedesktop.org/series/95138/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_10680_full -> Patchwork_21224_full
Summary
-
101 - 163 of 163 matches
Mail list logo
