On Tue, Nov 27, 2018 at 08:44:14PM -0500, Lyude Paul wrote:
> On Tue, 2018-11-27 at 20:44 +0100, Daniel Vetter wrote:
> > On Tue, Nov 27, 2018 at 12:48:59PM -0500, Lyude Paul wrote:
> > > On Mon, 2018-11-26 at 22:22 +0100, Daniel Vetter wrote:
> > > > On Mon, Nov 26, 2018 at 10:04:21PM +0100,
We need to handle allocation failures and bail out. While at it, tune
the allocation failures down to debug level.
syzbot injected an allocation failure and then hit this WARN_ON.
Reported-by: syzbot+eb6e5365f23c02517...@syzkaller.appspotmail.com
Signed-off-by: Daniel Vetter
Cc: Haneen Mohammed
Hi Uma,
On Tue, Nov 27, 2018 at 10:10:42PM +0530, Uma Shankar wrote:
> This patch adds a DP colorspace property, enabling
> userspace to switch to various supported colorspaces.
> This will help enable BT2020 along with other colorspaces.
>
> v2: Addressed Maarten and Ville's review comments.
https://bugzilla.kernel.org/show_bug.cgi?id=201795
--- Comment #3 from Michel Dänzer (mic...@daenzer.net) ---
Please also attach the output of dmesg and the Xorg log file in each case.
--
You are receiving this mail because:
You are watching the assignee of the bug.
Hi Dave,
Here's the next pull request for v4.21. :)
drm-misc-next-2018-11-28:
drm-misc-next for v4.21:
Core Changes:
- Merge drm_info.c into drm_debugfs.c
- Complete the fake drm_crtc_commit's hw_done/flip_done sooner.
- Remove deprecated drm_obj_ref/unref functions. All drivers use get/put
https://bugs.freedesktop.org/show_bug.cgi?id=108781
--- Comment #28 from Linnea S ---
(In reply to freedesktop from comment #27)
> OK there seems to be something screwy going on with the amdgpu.dpm option -
> if that's set to 0, it still results in a blank screen. It has to be removed
> entirely
On Tue, Nov 27, 2018 at 12:38:44PM -0800, Eric Anholt wrote:
> Daniel Vetter writes:
>
> > On Mon, Nov 26, 2018 at 04:36:21PM -0800, Eric Anholt wrote:
> >> Noralf Trønnes writes:
> >> > +static void drm_gem_shmem_vm_close(struct vm_area_struct *vma)
> >> > +{
> >> > +struct
On Tue, 27 Nov 2018, Brian Starkey wrote:
> Hi Liam,
>
> On Mon, Nov 26, 2018 at 08:59:44PM -0800, Liam Mark wrote:
> > On Tue, 20 Nov 2018, Brian Starkey wrote:
> >
> > > Hi Liam,
> > >
> > > I'm missing a bit of context here, but I did read the v1 thread.
> > > Please accept my apologies if
On 11/27/18 10:11 AM, Tomasz Figa wrote:
>
> I don't see display support enabled in the rk3066-mk808.dts in latest
> upstream:
> https://elixir.bootlin.com/linux/latest/source/arch/arm/boot/dts/rk3066a-mk808.dts
>
> Do you have any local changes in your kernel sources?
>
Thanks for your
From: Kuninori Morimoto
This patch updates license to use SPDX-License-Identifier
instead of verbose license text.
Signed-off-by: Kuninori Morimoto
---
2weeks passed. resend
drivers/gpu/drm/bridge/synopsys/dw-hdmi-i2s-audio.c | 5 +
1 file changed, 1 insertion(+), 4 deletions(-)
diff
On Tue, Nov 6, 2018 at 10:35 AM Neil Armstrong wrote:
>
> Add the timings for the HDMI 1.4 4K modes support :
> - 3840x2160@30
> - 3840x2160@25
> - 3840x2160@24
>
> Since the 297000Hz pixel clock is already managed and the modes are
> compatible with the HDMI 1.4 current HDMI PHY+Controller
From: Young Xiao
See commit a8f976473196 ("drm/amd/display: Bunch of smatch error and
warning fixes in DC") for detail.
Signed-off-by: Young Xiao
---
drivers/gpu/drm/amd/display/dc/bios/bios_parser.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git
From: yezengruan
Hi all,
When I run linux-4.19.2 on arm64, I got panic in sys_imageblit. My test steps
are as fllows:
1) Remote login using BMC;
2) Enter a bunch of 'Enter' keys;
3) Execute the 'top' command and continuously press shift + page up several
times.
This gives the following panic
On Tue, Nov 6, 2018 at 11:55 AM Neil Armstrong wrote:
>
> This change is an attempt to handle the alternate clock for the CEA mode.
> 60Hz vs. 59.94Hz, 30Hz vs 29.97Hz or 24Hz vs 23.97Hz on the Amlogic Meson SoC
> DRM Driver pixel clock generation.
>
> The actual clock generation will be moved to
Hi all,
When I run linux-4.19.2 on arm64, I got panic in sys_imageblit. My test steps
are as fllows:
1) Remote login using BMC;
2) Enter a bunch of 'Enter' keys;
3) Execute the 'top' command and continuously press shift + page up several
times.
This gives the following panic on the serial
+linux-acpi
Hi Michael,
On Mon, Nov 26, 2018 at 10:53:26PM -0500, Michael S. Tsirkin wrote:
> So a new thinkpad:
> 01:00.0 VGA compatible controller: NVIDIA Corporation GP107GLM [Quadro P2000
> Mobile] (rev a1)
>
> Hangs whenever I try to poke at the card. It starts happily enough with
>
> [
Anshuman Khandual writes:
> At present there are multiple places where invalid node number is encoded
> as -1. Even though implicitly understood it is always better to have macros
> in there. Replace these open encodings for an invalid node number with the
> global macro NUMA_NO_NODE. This helps
Pass the shadow bo to qxl_io_create_primary() instead of expecting
qxl_io_create_primary to check bo->shadow. Set is_primary flag on the
shadow bo. Move the is_primary tracking into qxl_io_create_primary()
and qxl_io_destroy_primary() functions.
That simplifies primary surface tracking and the
Track which bo is used as primary surface. With that in place we don't
need the primary_created flag any more, we can just check the primary bo
pointer instead.
Also verify we don't already have a primary surface in
qxl_io_create_primary().
Signed-off-by: Gerd Hoffmann
---
Skip the pointless and slightly confusing indirection via
qdev->monitors_config->max_allowed. Just use qxl_num_crtc instead.
Signed-off-by: Gerd Hoffmann
---
drivers/gpu/drm/qxl/qxl_display.c | 25 +++--
1 file changed, 11 insertions(+), 14 deletions(-)
diff --git
The qxl device supports only a single active framebuffer ("primary
surface" in spice terminology). In multihead configurations are handled
by defining rectangles within the primary surface for each head/crtc.
Userspace which uses the qxl ioctl interface (xorg qxl driver) is aware
of this
The cursor must be set again after creating the primary surface.
Also drop the error message.
Signed-off-by: Gerd Hoffmann
---
drivers/gpu/drm/qxl/qxl_display.c | 10 +++---
1 file changed, 3 insertions(+), 7 deletions(-)
diff --git a/drivers/gpu/drm/qxl/qxl_display.c
Some cleanups and preparations (patches 1-4, also 6).
The change which makes wayland actually work in multihead
configurations is patch 5.
Gerd Hoffmann (6):
drm/qxl: move qxl_primary_apply_cursor to correct place
drm/qxl: drop unused offset parameter from qxl_io_create_primary()
drm/qxl:
Signed-off-by: Gerd Hoffmann
---
drivers/gpu/drm/qxl/qxl_drv.h | 1 -
drivers/gpu/drm/qxl/qxl_cmd.c | 7 +++
drivers/gpu/drm/qxl/qxl_display.c | 2 +-
3 files changed, 4 insertions(+), 6 deletions(-)
diff --git a/drivers/gpu/drm/qxl/qxl_drv.h b/drivers/gpu/drm/qxl/qxl_drv.h
index
On Tue, Nov 27, 2018 at 05:46:39PM -0500, Sean Paul wrote:
> From: Sean Paul
>
> drm_atomic_state_put doesn't require any locking, and this makes things
> easier for switching to modeset_lock_all helpers in a future patch
>
> Cc: Daniel Vetter
> Signed-off-by: Sean Paul
> ---
>
On Tue, Nov 27, 2018 at 05:46:40PM -0500, Sean Paul wrote:
> From: Sean Paul
>
> This patch adds a couple of helpers to remove the boilerplate involved
> in grabbing all of the modeset locks.
>
> I've also converted the obvious cases in drm core to use the helpers.
>
> The only remaining
Quoting Ho, Kenny (2018-11-27 17:41:17)
> On Tue, Nov 27, 2018 at 4:46 AM Joonas Lahtinen
> wrote:
> > I think a more abstract property "% of GPU (processing power)" might
> > be a more universal approach. One can then implement that through
> > subdividing the resources or timeslicing them,
https://bugs.freedesktop.org/show_bug.cgi?id=108781
--- Comment #27 from freedesk...@nuclearsunshine.com ---
OK there seems to be something screwy going on with the amdgpu.dpm option - if
that's set to 0, it still results in a blank screen. It has to be removed
entirely from the kernel command
Hi,
On Thu, 2018-10-25 at 14:45 +0200, Boris Brezillon wrote:
> Hello,
>
> This is the 2nd version of the VC4 load tracker patch.
>
> Daniel, as you suggested, I've implemented a generic infrastructure to
> track and report underrun errors (patch 1). Not sure this is what you
> had in mind, but
https://bugs.freedesktop.org/show_bug.cgi?id=105725
--- Comment #14 from hjpries...@gmail.com ---
I am now running 4.19.4 and did not get the messages anymore.
The messages where there from 4.5.11 to 4.18.16
--
You are receiving this mail because:
You are the assignee for the
On Tue, Nov 27, 2018 at 05:46:38PM -0500, Sean Paul wrote:
> From: Sean Paul
>
> Instead of always re-initializing the variables we need to clean up on
> out, move the re-initialization into the branch that goes back to retry
> label.
>
> This is a lateral move right now, but will allow us to
On Wed, 28 Nov 2018 10:16:17 +0100
Paul Kocialkowski wrote:
> Hi,
>
> On Thu, 2018-10-25 at 14:45 +0200, Boris Brezillon wrote:
> > Hello,
> >
> > This is the 2nd version of the VC4 load tracker patch.
> >
> > Daniel, as you suggested, I've implemented a generic infrastructure to
> > track
On Wed, Nov 28, 2018 at 08:17:04AM +0100, Maarten Lankhorst wrote:
> Op 27-11-18 om 18:34 schreef Daniel Vetter:
> > KMS drivers really should all be able to restore their display state
> > on resume without fbcon helping out. So make this the default.
> >
> > Since I'm not entirely foolish, make
Hey Dan,
On 2018-11-20 4:13 p.m., Dan Williams wrote:
> The last step before devm_memremap_pages() returns success is to
> allocate a release action, devm_memremap_pages_release(), to tear the
> entire setup down. However, the result from devm_add_action() is not
> checked.
>
> Checking the
My local changes for VOP and HDMI. (PART 2)
From 81bc4d4f83b57161c8ba7005875a2f9ff9ec1d3a Mon Sep 17 00:00:00 2001
From: Finley Xiao
Date: Mon, 6 Nov 2017 11:50:54 +0800
Subject: [PATCH] clk: rockchip: rk3188: Add CLK_SET_RATE_PARENT for lcdc dclk
Add CLK_SET_RATE_PARENT for lcdc dclk.
On Tue, Nov 27, 2018 at 3:55 PM Maxime Ripard wrote:
>
> On Tue, Nov 20, 2018 at 09:55:42PM +0530, Jagan Teki wrote:
> > On Tue, Nov 20, 2018 at 9:27 PM Maxime Ripard
> > wrote:
> > >
> > > On Thu, Nov 15, 2018 at 11:19:53PM +0530, Jagan Teki wrote:
> > > > On Thu, Nov 15, 2018 at 3:26 PM
From: Young Xiao
the type mem->start is unsigned long, so this can overflow on
32bit system, since the type addr is uint64_t.
Signed-off-by: Young Xiao
---
drivers/gpu/drm/radeon/radeon_vm.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/gpu/drm/radeon/radeon_vm.c
This fixes the error in the compatible documentation for the EDT
etm0700[g].. panels which have accidentally documented as etm0700[8]0..
Signed-off-by: Jan Tuerk
---
.../devicetree/bindings/display/panel/edt,et-series.txt | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
Changes
Hi Liam,
On Tue, Nov 27, 2018 at 10:46:07PM -0800, Liam Mark wrote:
> On Tue, 27 Nov 2018, Brian Starkey wrote:
>
> > Hi Liam,
> >
> > On Mon, Nov 26, 2018 at 08:59:44PM -0800, Liam Mark wrote:
> > > On Tue, 20 Nov 2018, Brian Starkey wrote:
> > >
> > > > Hi Liam,
> > > >
> > > > I'm missing
Am 27.11.18 um 12:50 schrieb Yang Xiao:
From: Young Xiao
the type mem->start is unsigned long, so this can overflow on
32bit system, since the type addr is uint64_t.
Signed-off-by: Young Xiao
Reviewed-by: Christian König
---
drivers/gpu/drm/radeon/radeon_vm.c | 2 +-
1 file changed,
On the Amlogic GXL & GXM SoCs, a bug occurs on the primary plane when
alpha is used where the alpha is not aligned with the pixel content.
The woraround Amlogic implemented is to reset the OSD1 plane hardware
block each time the plane is (re)enabled, solving the issue.
In the reset, we still
I've misplaced two functions by accident:
- drm_atomic_helper_duplicate_state is really part of the
resume/suspend/shutdown device-wide helpers.
- drm_atomic_helper_legacy_gamma_set is part of the legacy ioctl
compat helpers.
Move them both back.
Fixes: 9ef8a9dc4b21 ("drm: Extract
https://bugs.freedesktop.org/show_bug.cgi?id=108892
--- Comment #1 from Christian König ---
What kernel version is this? Please also try with the latest.
--
You are receiving this mail because:
You are the assignee for the bug.___
dri-devel mailing
https://bugs.freedesktop.org/show_bug.cgi?id=108892
Bug ID: 108892
Summary: kernel BUG at kernel/time/timer.c:1137 in
drm_sched_job_finish [gpu_sched]
Product: DRI
Version: DRI git
Hardware: x86-64 (AMD64)
Add an optional property to allow applications to indicate what range their
floating point pixel data is normalized to. Drivers are free to choose what
ranges they want to support and can attach this property to each plane that
actually supports floating point formats
Signed-off-by: Kevin
This series defines new formats and adds a plane property to be used for
floating point framebuffer content. Implementation is then added to i915.
I have shared an IGT branch which adds test coverage for the new formats:
https://github.com/strassek/xorg-intel-gpu-tools/tree/fp16
Kevin Strasser
Add 64 bpp 16:16:16:16 half float pixel formats. Each 16 bit component is
formatted in IEEE-754 half-precision float (binary16) 1:5:10
MSb-sign:exponent:fraction form.
An 'is_fp' attribute is added to drm_format_info so that drivers can easily
distinguish these formats from those that might
64 bpp half float formats are supported on hdr planes only and are subject
to the following restrictions:
* 90/270 rotation not supported
* Yf Tiling not supported
* Frame Buffer Compression not supported
* Color Keying not supported
The behavior of pixel normalize with non-float formats
On Wed, 2018-11-28 at 22:21 +0100, Daniel Vetter wrote:
> On Wed, Nov 28, 2018 at 09:51:13PM +0100, Daniel Vetter wrote:
> > On Wed, Nov 28, 2018 at 03:55:58PM +0200, Stanislav Lisovskiy
> > wrote:
> > > Currently kernel might allocate different connector ids
> > > for the same outputs in case of
tree: git://people.freedesktop.org/~agd5f/linux.git amd-staging-drm-next
head: 2e41bee6b61f2f0a460a8fb71b795d756a38bc85
commit: e64abff2f1330b536b2973719b74ba92950ff254 [429/451] drm/amd/display: Use
private obj helpers for dm_atomic_state
reproduce: make htmldocs
All warnings (new ones
https://bugs.freedesktop.org/show_bug.cgi?id=106175
--- Comment #72 from Brandon Wright ---
(In reply to bmilreu from comment #71)
> @Nicholas Kazlauskas
> any reason not to push this fix to staging or next?
I agree. This will reduce stuttering for everyone, especially those who think
the
Change the license of the i915_sw_fence files to MIT matching
most of the other i915 files. This makes it possible to use them
in a new port of i915 to OpenBSD.
Besides some mechanical tree wide changes Chris Wilson is the sole
author of these files with Intel holding the copyright.
Intel's
https://bugs.freedesktop.org/show_bug.cgi?id=108317
Timothy Arceri changed:
What|Removed |Added
Status|NEW |NEEDINFO
--- Comment #18 from Timothy
https://bugs.freedesktop.org/show_bug.cgi?id=106287
Timothy Arceri changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
On Thu, Nov 29, 2018 at 12:21:31AM +0100, Karol Herbst wrote:
> this was already debugged and there is no point in searching inside
> the Firmware. It's not a firmware bug or anything.
>
> The proper fix is to do something inside Nouveau so that we don't
> upset the device and being able to
https://bugs.freedesktop.org/show_bug.cgi?id=107990
Timothy Arceri changed:
What|Removed |Added
CC||henrik.hol...@gmail.com
--- Comment
From: Nicholas Kazlauskas
[ Upstream commit 69756c6ff0de478c10100481f16c966dde3b5339 ]
[Why]
Many panels support more than 8bpc but some modes are unavailable while
running at greater than 8bpc due to DP/HDMI bandwidth constraints.
Support for more than 8bpc was added recently in the driver
From: Nicholas Kazlauskas
[ Upstream commit 07e3a1cfb0568b6d8d7862077029af96af6690ea ]
[Why]
Many panels support more than 8bpc but some modes are unavailable while
running at greater than 8bpc due to DP/HDMI bandwidth constraints.
Support for more than 8bpc was added recently in the driver
On Wed, 2018-11-28 at 09:17 +0100, Daniel Vetter wrote:
> On Tue, Nov 27, 2018 at 08:44:14PM -0500, Lyude Paul wrote:
> > On Tue, 2018-11-27 at 20:44 +0100, Daniel Vetter wrote:
> >
> > We could do this the other way around so it looks like this maybe
> >
> > struct kref; /* manages kfree() */
On Tue, Nov 27, 2018 at 1:44 PM Logan Gunthorpe wrote:
>
> Hey Dan,
>
> On 2018-11-20 4:13 p.m., Dan Williams wrote:
> > The last step before devm_memremap_pages() returns success is to
> > allocate a release action, devm_memremap_pages_release(), to tear the
> > entire setup down. However, the
https://bugs.freedesktop.org/show_bug.cgi?id=105725
--- Comment #15 from Petr Cvek ---
(In reply to hjpriester from comment #14)
> I am now running 4.19.4 and did not get the messages anymore.
> The messages where there from 4.5.11 to 4.18.16
I've got the warnings with vanilla 4.20-rc2
https://bugs.freedesktop.org/show_bug.cgi?id=108572
--- Comment #3 from Timothy Arceri ---
If you build radeonsi with debug sysmbols i.e. use --enable-debug you should be
able to run gimp in gdb and see exactly were the segfault is. Could be as
simple as a NULL check missing somewhere.
--
You
https://bugs.freedesktop.org/show_bug.cgi?id=108317
--- Comment #19 from John ---
This is a problem with mesa master, I've never used mild myself and still have
the issue.
--
You are receiving this mail because:
You are the assignee for the bug.___
On Wed, Nov 28, 2018 at 2:39 AM Christoph Hellwig wrote:
>
> > + /*
> > + * dma_sync_sg_*() flush the physical pages, so point
> > + * sg->dma_address to the physical ones for the right
> > behavior.
> > + */
> > +
https://bugs.freedesktop.org/show_bug.cgi?id=93826
--- Comment #79 from Timo Gurr ---
Just like Scott Mereau posted before I also run into the problem with a
FreeSync monitor @75Hz with the default power_dpm_force_performance_level set
to auto.
Manually setting it to high works around the
>-Original Message-
>From: Brian Starkey [mailto:brian.star...@arm.com]
>Sent: Wednesday, November 28, 2018 5:12 PM
>To: Shankar, Uma
>Cc: intel-...@lists.freedesktop.org; dri-devel@lists.freedesktop.org;
>Lankhorst,
>Maarten ; Syrjala, Ville
>;
>Sharma, Shashank ; jo...@kwiboo.se;
https://bugs.freedesktop.org/show_bug.cgi?id=108825
--- Comment #6 from Nicholas Kazlauskas ---
(In reply to Samantha McVey from comment #5)
> I have bisected it to commit: drm/amd/display: Support amdgpu "max bpc"
> connector property
> 307638884f721b02b6a54ee8b351c5b4434bd4a6 Author: Nicholas
https://bugs.freedesktop.org/show_bug.cgi?id=108781
--- Comment #29 from pascalp ---
For me it is the other way round:
With my 290x I used to boot fine under 4.18 without amdgpu.dpm set at all.
After updating to 4.19 and being unable to boot I read that amdgpu.dpm defaults
to "enabled" so I
From: Chunming Zhou
v2: drop DRM_SYNCOBJ_CREATE_TYPE_TIMELINE, fix timeout calculation,
fix some warnings
Signed-off-by: Chunming Zhou
Signed-off-by: Christian König
---
tests/amdgpu/Makefile.am | 3 +-
tests/amdgpu/amdgpu_test.c | 12 ++
tests/amdgpu/amdgpu_test.h | 21
This completes "drm/syncobj: Drop add/remove_callback from driver
interface" and cleans up the implementation a bit.
Signed-off-by: Christian König
---
drivers/gpu/drm/drm_syncobj.c | 91 ++-
include/drm/drm_syncobj.h | 21 --
2 files changed,
From: Chunming Zhou
Signed-off-by: Chunming Zhou
---
include/drm/amdgpu_drm.h | 9 +
1 file changed, 9 insertions(+)
diff --git a/include/drm/amdgpu_drm.h b/include/drm/amdgpu_drm.h
index 1ceec56d..a3c067dd 100644
--- a/include/drm/amdgpu_drm.h
+++ b/include/drm/amdgpu_drm.h
@@ -517,6
From: Chunming Zhou
v2: drop export/import
Signed-off-by: Chunming Zhou
---
xf86drm.c | 44
xf86drm.h | 8
2 files changed, 52 insertions(+)
diff --git a/xf86drm.c b/xf86drm.c
index 71ad54ba..afa2f466 100644
--- a/xf86drm.c
+++
From: Chunming Zhou
v2: symbos are stored in lexical order.
v3: drop export/import and extra query indirection
Signed-off-by: Chunming Zhou
Signed-off-by: Christian König
---
amdgpu/amdgpu-symbol-check | 2 ++
amdgpu/amdgpu.h| 39 +++
From: Chunming Zhou
v2: drop not implemented IOCTLs and flags
Signed-off-by: Chunming Zhou
Signed-off-by: Christian König
---
include/drm/drm.h | 25 +
1 file changed, 25 insertions(+)
diff --git a/include/drm/drm.h b/include/drm/drm.h
index 85c685a2..34f1e3f9 100644
Am Dienstag, 27. November 2018, 18:34:24 CET schrieb Daniel Vetter:
> KMS drivers really should all be able to restore their display state
> on resume without fbcon helping out. So make this the default.
>
> Since I'm not entirely foolish, make it only a default, which drivers
> can still
From: Thierry Reding
Display controllers that don't own any windows and which therefore
aren't currently being assigned a primary plane are not registered
as a CRTC with the DRM framework. They request neither a syncpoint
nor an interrupt because they don't use them, so avoid cleaning up
those
From: Thierry Reding
The display architecture on Tegra186 and Tegra194 requires that there be
some valid clock on all domains before accessing any display register. A
further requirement is that in addition to the host1x, hub, disp and dsc
clocks, all the head clocks (pclk0-2 on Tegra186 or
This reverts commit 9a09a42369a4a37a959c051d8e1a1f948c1529a4.
The whole interface isn't thought through. Since this function can't
fail we actually can't allocate an object to store the sync point.
Sorry, I should have taken the lead on this from the very beginning and
reviewed it more
From: Chunming Zhou
points array is one-to-one match with syncobjs array.
v2:
add seperate ioctl for timeline point wait, otherwise break uapi.
v3:
userspace can specify two kinds waits::
a. Wait for time point to be completed.
b. and wait for time point to become available
v4:
rebase
v5:
add
From: Chunming Zhou
syncobj wait/signal operation is appending in command submission.
v2: separate to two kinds in/out_deps functions
Signed-off-by: Chunming Zhou
Cc: Daniel Rakos
Cc: Jason Ekstrand
Cc: Bas Nieuwenhuizen
Cc: Dave Airlie
Cc: Christian König
Cc: Chris Wilson
---
Use the dma_fence_chain object to create a timeline of fence objects
instead of just replacing the existing fence.
v2: rebase and cleanup
Signed-off-by: Christian König
---
drivers/gpu/drm/drm_syncobj.c | 37 +
include/drm/drm_syncobj.h | 5 +
2
From: Chunming Zhou
Signed-off-by: Chunming Zhou
---
drivers/gpu/drm/amd/amdgpu/amdgpu_drv.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/drivers/gpu/drm/amd/amdgpu/amdgpu_drv.c
b/drivers/gpu/drm/amd/amdgpu/amdgpu_drv.c
index 90f474f98b6e..316bfc1a6a75 100644
---
Lockless container implementation similar to a dma_fence_array, but with
only two elements per node and automatic garbage collection.
v2: properly document dma_fence_chain_for_each, add dma_fence_chain_find_seqno,
drop prev reference during garbage collection if it's not a chain fence.
Implement finding the right timeline point in drm_syncobj_find_fence.
v2: return -EINVAL when the point is not submitted yet.
v3: fix reference counting bug, add flags handling as well
Signed-off-by: Christian König
---
drivers/gpu/drm/drm_syncobj.c | 43
From: Chunming Zhou
user mode can query timeline payload.
v2: check return value of copy_to_user
v3: handle querying entry by entry
v4: rebase on new chain container, simplify interface
Signed-off-by: Chunming Zhou
Cc: Daniel Rakos
Cc: Jason Ekstrand
Cc: Bas Nieuwenhuizen
Cc: Dave Airlie
Extract of useful code from the timeline work. Let's use just a single
stub fence instance instead of allocating a new one all the time.
Signed-off-by: Chunming Zhou
Signed-off-by: Christian König
---
drivers/gpu/drm/drm_syncobj.c | 67 ++-
1 file
On Wed, Nov 28, 2018 at 01:08:57PM +0200, Mika Westerberg wrote:
> On Tue, Nov 27, 2018 at 09:49:44PM -0500, Michael S. Tsirkin wrote:
> > On Tue, Nov 27, 2018 at 11:36:50AM +0200, Mika Westerberg wrote:
> > > +linux-acpi
> > >
> > > Hi Michael,
> > >
> > > On Mon, Nov 26, 2018 at 10:53:26PM
https://bugs.freedesktop.org/show_bug.cgi?id=108889
Martin Peres changed:
What|Removed |Added
Whiteboard||ReadyForDev
Priority|medium
Regards
Shashank
On 11/27/2018 10:10 PM, Uma Shankar wrote:
This patch adds a DP colorspace property, enabling
userspace to switch to various supported colorspaces.
This will help enable BT2020 along with other colorspaces.
v2: Addressed Maarten and Ville's review comments. Enhanced
the
On Wed, Nov 28, 2018 at 10:01:07AM +0100, Daniel Vetter wrote:
> On Tue, Nov 27, 2018 at 05:46:40PM -0500, Sean Paul wrote:
> > From: Sean Paul
> >
> > This patch adds a couple of helpers to remove the boilerplate involved
> > in grabbing all of the modeset locks.
> >
> > I've also converted
Signed-off-by: Gerd Hoffmann
---
drivers/gpu/drm/virtio/virtgpu_drv.h | 3 +--
drivers/gpu/drm/virtio/virtgpu_ioctl.c | 2 +-
drivers/gpu/drm/virtio/virtgpu_vq.c| 5 ++---
3 files changed, 4 insertions(+), 6 deletions(-)
diff --git a/drivers/gpu/drm/virtio/virtgpu_drv.h
Since commit "9fdd90c0f4 drm/virtio: add virtio_gpu_alloc_fence()"
fences are not allocated any more by virtio_gpu_fence_emit(). So there
is no need to pass down a reference to the fence pointer, a plain
pointer is enough now.
Convert virtio_gpu_fence_emit() and callers.
Signed-off-by: Gerd
Gerd Hoffmann (2):
drm/virtio: fence: pass plain pointer
drm/virtio: virtio_gpu_cmd_resource_create_3d: drop unused fence arg
drivers/gpu/drm/virtio/virtgpu_drv.h | 15 +++
drivers/gpu/drm/virtio/virtgpu_fence.c | 10 +-
drivers/gpu/drm/virtio/virtgpu_ioctl.c | 10
Hi Souptick,
Am Montag, 26. November 2018, 06:36:42 CET schrieb Souptick Joarder:
> On Thu, Nov 15, 2018 at 9:14 PM Souptick Joarder
wrote:
> > Convert to use vm_insert_range() to map range of kernel
> > memory to user vma.
> >
> > Signed-off-by: Souptick Joarder
>
> Any feedback for this
On Tue, Nov 27, 2018 at 03:58:13PM -0800, Jeykumar Sankaran wrote:
> Specify geometry for DPU iommu domain which sets
> the address space for gem allocations.
>
> Signed-off-by: Jeykumar Sankaran
> Suggested-by: Jordan Crouse
> Suggested-by: Vivek Gautam
There is a lot of confusion
From: Colin Ian King
There is a spelling mistake in the module parameter description, fix it.
Signed-off-by: Colin Ian King
---
drivers/video/fbdev/uvesafb.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/video/fbdev/uvesafb.c b/drivers/video/fbdev/uvesafb.c
index
Regards
Shashank
On 11/27/2018 10:10 PM, Uma Shankar wrote:
This patch adds a HDMI colorspace property, enabling
userspace to switch to various supported colorspaces.
This will help enable BT2020 along with other colorspaces.
v2: Addressed Maarten and Ville's review comments. Enhanced
the
From: Colin Ian King
There is a spelling mistake in the module parameter description, fix it.
Signed-off-by: Colin Ian King
---
drivers/video/fbdev/uvesafb.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/video/fbdev/uvesafb.c b/drivers/video/fbdev/uvesafb.c
index
https://bugs.freedesktop.org/show_bug.cgi?id=108889
Bug ID: 108889
Summary: [CI][SHARDS] igt@sw_sync@sync_busy_fork_unixsocket -
incomplete - __igt_fork_helper: Assertion
`!proc->running' failed.
Product: DRI
Am Donnerstag, 15. November 2018, 16:45:30 CET schrieb Souptick Joarder:
> Previouly drivers have their own way of mapping range of
> kernel pages/memory into user vma and this was done by
> invoking vm_insert_page() within a loop.
>
> As this pattern is common across different drivers, it can
>
1 - 100 of 194 matches
Mail list logo
