Am 16.04.19 um 13:20 schrieb Karol Herbst:
On Tue, Apr 16, 2019 at 1:07 PM Koenig, Christian
wrote:
Am 16.04.19 um 12:54 schrieb Karol Herbst:
On Tue, Apr 16, 2019 at 11:12 AM Koenig, Christian
wrote:
Am 16.04.19 um 11:10 schrieb Karol Herbst:
On Tue, Apr 16, 2019 at 8:38 AM Christian
On Tue, 2019-04-16 at 16:37 +0800, Yongqiang Niu wrote:
> On Tue, 2019-04-16 at 16:00 +0800, CK Hu wrote:
> > Hi, Yongqiang:
> >
> > On Wed, 2019-03-27 at 14:19 +0800, yongqiang@mediatek.com wrote:
> > > From: Yongqiang Niu
> > >
> > > This patch add RDMA fifo size error handle
> > > rdma
From: Colin Ian King
There is a spelling mistake in a DRM_INFO message. Fix it.
Signed-off-by: Colin Ian King
---
drivers/gpu/drm/amd/amdgpu/vce_v2_0.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/gpu/drm/amd/amdgpu/vce_v2_0.c
The turnout for the first election and the vote on the bylaw changes was 80%
(56/70).
Harry
On 2019-04-11 8:03 p.m., Harry Wentland wrote:
> To all X.Org Foundation Members:
>
> The 2019 X.Org ballot closed yesterday. There is some good and some bad news.
>
> The Good News:
> The vote on the
On 4/16/19 5:47 AM, Christian König wrote:
> Am 15.04.19 um 23:17 schrieb Eric Anholt:
>> Andrey Grodzovsky writes:
>>
>>> From: Christian König
>>>
>>> We now destroy finished jobs from the worker thread to make sure that
>>> we never destroy a job currently in timeout processing.
>>> By this
Hi,
On 16-04-19 16:32, Patrik Jakobsson wrote:
On Wed, Apr 10, 2019 at 1:51 PM Dominik 'Rathann' Mierzejewski
wrote:
On Wednesday, 10 April 2019 at 13:33, Patrik Jakobsson wrote:
On Wed, Apr 10, 2019 at 1:18 PM Dominik 'Rathann' Mierzejewski
wrote:
On Wednesday, 10 April 2019 at 11:08,
Some machines have an lvds child device in vbt even though a panel is
not attached. To make detection more reliable we now also check the lvds
config bits available in the vbt.
Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1665766
Signed-off-by: Patrik Jakobsson
Cc: Hans de Goede
Cc:
On Tue, Apr 16, 2019 at 11:05:33AM +0200, Gerd Hoffmann wrote:
> Also drop the dstclip parameter sphinx has warned about (leftolver from
> an earlier patch version).
>
> Signed-off-by: Gerd Hoffmann
Assuming it all builds cleanly and all the links work and no warnings from
sphinx:
Acked-by:
On Tue, Apr 16, 2019 at 2:43 PM Liviu Dudau wrote:
>
> On Tue, Apr 16, 2019 at 11:55:34AM +0200, Daniel Vetter wrote:
> > On Tue, Apr 16, 2019 at 11:17 AM Liviu Dudau wrote:
> > >
> > > On Tue, Apr 16, 2019 at 09:34:20AM +0200, Daniel Vetter wrote:
> > > > On Mon, Apr 15, 2019 at 10:20:45AM
From: Thierry Reding
The audio configuration is only valid if the HDMI codec has been
properly set up. Do not attempt to set up audio before that happens
because it causes a division by zero.
Note that this is only problematic on Tegra20 and Tegra30. Later chips
implement the division
On Mon, Apr 15, 2019 at 09:20:55PM +0200, Daniel Vetter wrote:
> On Mon, Apr 15, 2019 at 4:14 PM Lankhorst, Maarten
> wrote:
> >
> > mån 2019-04-15 klockan 19:26 +0530 skrev Sharma, Shashank:
> > > > -Original Message-
> > > > From: Lankhorst, Maarten
> > > > Sent: Monday, April 15, 2019
On Tue, Apr 16, 2019 at 1:07 PM Koenig, Christian
wrote:
>
> Am 16.04.19 um 12:54 schrieb Karol Herbst:
> > On Tue, Apr 16, 2019 at 11:12 AM Koenig, Christian
> > wrote:
> >> Am 16.04.19 um 11:10 schrieb Karol Herbst:
> >>> On Tue, Apr 16, 2019 at 8:38 AM Christian König
> >>> wrote:
> Am
On Tue, Apr 16, 2019 at 11:06:54AM +, Koenig, Christian wrote:
> Am 16.04.19 um 12:54 schrieb Karol Herbst:
> > On Tue, Apr 16, 2019 at 11:12 AM Koenig, Christian
> > wrote:
> >> Am 16.04.19 um 11:10 schrieb Karol Herbst:
> >>> On Tue, Apr 16, 2019 at 8:38 AM Christian König
> >>> wrote:
>
Unfortunately userspace users of this API cannot be publicly disclosed
yet.
This commit effectively disables timeline syncobj ioctls for all
drivers. Each driver wishing to support this feature will need to
expose DRIVER_SYNCOBJ_TIMELINE.
Signed-off-by: Lionel Landwerlin
Cc: Dave Airlie
Cc:
Am 16.04.19 um 14:18 schrieb Daniel Vetter:
> On Tue, Apr 16, 2019 at 11:06:54AM +, Koenig, Christian wrote:
>> Am 16.04.19 um 12:54 schrieb Karol Herbst:
>>> On Tue, Apr 16, 2019 at 11:12 AM Koenig, Christian
>>> wrote:
Am 16.04.19 um 11:10 schrieb Karol Herbst:
> On Tue, Apr 16,
On 16/04/2019 13:40, Christian König wrote:
Am 16.04.19 um 14:30 schrieb Lionel Landwerlin:
We've been somewhat inconsistent when adding the new ioctl and
returned ENODEV instead of EOPNOTSUPPORTED upon failing the syncobj
capibility.
Signed-off-by: Lionel Landwerlin
Fixes: ea569910cbab98
On 4/16/19 10:43 AM, Koenig, Christian wrote:
> Am 16.04.19 um 16:36 schrieb Grodzovsky, Andrey:
>> On 4/16/19 5:47 AM, Christian König wrote:
>>> Am 15.04.19 um 23:17 schrieb Eric Anholt:
Andrey Grodzovsky writes:
> From: Christian König
>
> We now destroy finished jobs
Den 16.04.2019 11.42, skrev Maxime Ripard:
> Hi,
>
> On Sun, Apr 07, 2019 at 06:52:40PM +0200, Noralf Trønnes wrote:
>> All drivers add all their connectors so there's no need to keep around an
>> array of available connectors.
>>
>> Rename functions which signature is changed since they will
On Tue, Apr 16, 2019 at 04:41:37PM +0200, Thierry Reding wrote:
> From: Thierry Reding
>
> The audio configuration is only valid if the HDMI codec has been
> properly set up. Do not attempt to set up audio before that happens
> because it causes a division by zero.
>
> Note that this is only
Le 13/04/2019 16:14, Yue Haibing a écrit :
> From: YueHaibing
>
> Fix sparse warnings:
>
> drivers/gpu/drm/meson/meson_viu.c:93:6: warning: symbol
> 'meson_viu_set_g12a_osd1_matrix' was not declared. Should it be static?
> drivers/gpu/drm/meson/meson_viu.c:121:6: warning: symbol
>
On Tue, Apr 16, 2019 at 02:40:37PM +0200, Christian König wrote:
> Am 16.04.19 um 14:30 schrieb Lionel Landwerlin:
> > We've been somewhat inconsistent when adding the new ioctl and
> > returned ENODEV instead of EOPNOTSUPPORTED upon failing the syncobj
> > capibility.
> >
> > Signed-off-by:
On Tue, Apr 16, 2019 at 11:55:34AM +0200, Daniel Vetter wrote:
> On Tue, Apr 16, 2019 at 11:17 AM Liviu Dudau wrote:
> >
> > On Tue, Apr 16, 2019 at 09:34:20AM +0200, Daniel Vetter wrote:
> > > On Mon, Apr 15, 2019 at 10:20:45AM +0100, Liviu Dudau wrote:
> > > > On Mon, Apr 15, 2019 at 08:59:30AM
Hi,
Le lundi 15 avril 2019 à 18:15 +0200, Paul Kocialkowski a écrit :
> Our driver makes a typical use of CMA, with GEM object allocated as
> GEM CMA objects. Use DRM_GEM_CMA_VMAP_DRIVER_OPS to describe the ops
> instead of duplicating them.
>
> Because DRM_GEM_CMA_VMAP_DRIVER_OPS implements a
Am 16.04.19 um 14:30 schrieb Lionel Landwerlin:
We've been somewhat inconsistent when adding the new ioctl and
returned ENODEV instead of EOPNOTSUPPORTED upon failing the syncobj
capibility.
Signed-off-by: Lionel Landwerlin
Fixes: ea569910cbab98 ("drm/syncobj: add transition iotcls between
This adds the device tree bindings for the ST-Ericsson
Multi Channel Display Engine MCDE as found in the U8500
SoCs.
Cc: devicet...@vger.kernel.org
Signed-off-by: Linus Walleij
---
ChangeLog v1->v2:
- Drop the graph representation of a port from DSI host
to panel child. Just have panels or
Am 16.04.19 um 16:36 schrieb Grodzovsky, Andrey:
> On 4/16/19 5:47 AM, Christian König wrote:
>> Am 15.04.19 um 23:17 schrieb Eric Anholt:
>>> Andrey Grodzovsky writes:
>>>
From: Christian König
We now destroy finished jobs from the worker thread to make sure that
we never
https://bugs.freedesktop.org/show_bug.cgi?id=110327
--- Comment #3 from andrzej.ha...@gmail.com ---
Looking at the code apparently you are setting V4L2_PIX_FMT_NV12MT_16X16 in
MFC, but MIXER requires V4L2_PIX_FMT_NV12MT.
--
You are receiving this mail because:
You are the assignee for the
On Wed, Apr 10, 2019 at 1:51 PM Dominik 'Rathann' Mierzejewski
wrote:
>
> On Wednesday, 10 April 2019 at 13:33, Patrik Jakobsson wrote:
> > On Wed, Apr 10, 2019 at 1:18 PM Dominik 'Rathann' Mierzejewski
> > wrote:
> > >
> > > On Wednesday, 10 April 2019 at 11:08, Hans de Goede wrote:
> > > > On
From: Thierry Reding
The audio configuration is only valid if the HDMI codec has been
properly set up. Do not attempt to set up audio before that happens
because it causes a division by zero.
Note that this is only problematic on Tegra20 and Tegra30. Later chips
implement the division
Am 16.04.19 um 14:43 schrieb Daniel Vetter:
> On Tue, Apr 16, 2019 at 02:40:37PM +0200, Christian König wrote:
>> Am 16.04.19 um 14:30 schrieb Lionel Landwerlin:
>>> We've been somewhat inconsistent when adding the new ioctl and
>>> returned ENODEV instead of EOPNOTSUPPORTED upon failing the
Unfortunately userspace users of this API cannot be publicly disclosed
yet.
This commit effectively disables timeline syncobj ioctls for all
drivers. Each driver wishing to support this feature will need to
expose DRIVER_SYNCOBJ_TIMELINE.
v2: Add uAPI capability check (Christian)
Signed-off-by:
On Sat, Apr 13, 2019 at 08:34:02AM +, Thomas Hellstrom wrote:
> Hi, Jérôme
>
> On Fri, 2019-04-12 at 17:07 -0400, Jerome Glisse wrote:
> > On Fri, Apr 12, 2019 at 04:04:18PM +, Thomas Hellstrom wrote:
> > > This is basically apply_to_page_range with added functionality:
> > > Allocating
Den 11.04.2019 15.22, skrev Maxime Ripard:
> Properly configuring the overscan properties might be needed for the
> initial setup of the framebuffer for display that still have overscan.
> Let's allow for more properties on the kernel command line to setup each
> margin.
>
> Signed-off-by:
We've been somewhat inconsistent when adding the new ioctl and
returned ENODEV instead of EOPNOTSUPPORTED upon failing the syncobj
capibility.
Signed-off-by: Lionel Landwerlin
Fixes: ea569910cbab98 ("drm/syncobj: add transition iotcls between binary and
timeline v2")
Fixes: 01d6c357837918
Reviewed-by: Chunming Zhou for series.
Original Message
Subject: [PATCH v2] drm: introduce a capability flag for syncobj timeline
support
From: Lionel Landwerlin
To: dri-devel@lists.freedesktop.org
CC: Lionel Landwerlin ,"Koenig, Christian" ,Dave Airlie ,Daniel Vetter ,"Zhou,
On Thu, 2019-04-11 at 17:00 +0100, Lisovskiy, Stanislav wrote:
> On Thu, 2019-04-11 at 17:36 +0300, Gwan-gyeong Mun wrote:
> > The hotplug detection routine of drm_helper_hpd_irq_event() can
> > detect
> > changing of status of connector, but it can not detect changing of
> > edid.
> >
> >
On Mon, 2019-03-11 at 12:45 +0100, Paul Cercueil wrote:
> Hi Ezequiel,
>
> On Mon, Mar 11, 2019 at 1:02 AM, Ezequiel Garcia
> wrote:
> > On Thu, 2019-02-28 at 19:07 -0300, Paul Cercueil wrote:
> > > Hi,
> > >
> > > This is a first attempt at a KMS driver for the JZ47xx MIPS SoCs by
> > >
This adds and updates the device tree nodes for the MCDE
display controller and connects the Samsung display to
the TVK1281618 user interface board (UIB) so we get
nicely working graphics on this reference design.
Signed-off-by: Linus Walleij
---
ChangeLog v1->v2:
- Drop the port graph links
Den 11.04.2019 15.22, skrev Maxime Ripard:
> Rotations and reflections setup are needed in some scenarios to initialise
> properly the initial framebuffer. Some drivers already had a bunch of
> quirks to deal with this, such as either a private kernel command line
> parameter (omapdss) or on the
Am 16.04.19 um 13:03 schrieb Daniel Vetter:
> On Tue, Apr 16, 2019 at 12:05 PM Koenig, Christian
> wrote:
>> Am 15.04.19 um 21:17 schrieb Daniel Vetter:
>>> On Mon, Apr 15, 2019 at 6:21 PM Thomas Zimmermann
>>> wrote:
Hi
Am 15.04.19 um 17:54 schrieb Daniel Vetter:
> On Tue,
On Tue, Apr 16, 2019 at 12:53 PM Christian König
wrote:
>
> When a driver unloads without unloading TTM we don't correctly
> clear the global structures leading to errors on re-init.
>
> Next step should probably be to remove the global structures and
> kobjs all together, but this is tricky
I can't judge if that UAPI is actually sufficient, but the rest still
looks good to me.
Acked-by: Christian König
Christian.
Am 16.04.19 um 15:15 schrieb Zhou, David(ChunMing):
Reviewed-by: Chunming Zhou for series.
Original Message
Subject: [PATCH v2] drm: introduce a
To all X.Org Foundation Members:
as per my last email the election for X.Org board members was invalid due to a
bug with the voting systems. We apologize for this and the inconvenience caused
to you all. The bug has been fixed and tested with a mock election (see results
at the end).
Round 2
>> Hmm. My MST-foo is admittedly weak so I'm not sure. A quick trawl through
>> the spec didn't provide any solid explanations either :( However eg.
>> "Figure 2-83: Example Multi-function MST Branch-Sink Device Enumeration"
>> in the DP 1.4 spec does appear to show kind of virtual DPCD thing
On 4/16/19 10:58 AM, Grodzovsky, Andrey wrote:
> On 4/16/19 10:43 AM, Koenig, Christian wrote:
>> Am 16.04.19 um 16:36 schrieb Grodzovsky, Andrey:
>>> On 4/16/19 5:47 AM, Christian König wrote:
Am 15.04.19 um 23:17 schrieb Eric Anholt:
> Andrey Grodzovsky writes:
>
>> From:
Patch '5edb0c9b Fix deadlock with display during hanged ring recovery'
was accidentaly removed during one of DALs code merges.
v4: Update description.
Signed-off-by: Andrey Grodzovsky
Reviewed-by: Nicholas Kazlauskas
---
drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.c | 15 +--
From: Christian König
We now destroy finished jobs from the worker thread to make sure that
we never destroy a job currently in timeout processing.
By this we avoid holding lock around ring mirror list in drm_sched_stop
which should solve a deadlock reported by a user.
v2: Remove unused
Also reject TDRs if another one already running.
v2:
Stop all schedulers across device and entire XGMI hive before
force signaling HW fences.
Avoid passing job_signaled to helper fnctions to keep all the decision
making about skipping HW reset in one place.
v3:
Fix SW sched. hang after non HW
For later driver's reference to see if the fence is signaled.
v2: Move parent fence put to resubmit jobs.
Signed-off-by: Andrey Grodzovsky
Reviewed-by: Christian König
---
drivers/gpu/drm/scheduler/sched_main.c | 11 +--
1 file changed, 9 insertions(+), 2 deletions(-)
diff --git
On Tue, Apr 16, 2019 at 11:29 AM Sean Paul wrote:
> On Tue, Apr 16, 2019 at 09:43:49AM -0700, John Stultz wrote:
> > In trying to further align the AOSP libdrm branch with upstream,
> > I wanted to submit the added test planetest that they have been
> > carrying for awhile.
> >
> > Mostly sending
On Tue, 2019-04-16 at 09:42 +0200, Daniel Vetter wrote:
> On Mon, Apr 15, 2019 at 05:28:05PM +, Deepak Singh Rawat wrote:
> > Plane property "FB_DAMAGE_CLIPS" can only be used by atomic aware
> > user-space, so no point exposing it otherwise.
> >
> > Signed-off-by: Deepak Rawat
> > Fixes:
On Tue, Apr 16, 2019 at 03:28:24PM +, Li, Sun peng (Leo) wrote:
> >> Hmm. My MST-foo is admittedly weak so I'm not sure. A quick trawl through
> >> the spec didn't provide any solid explanations either :( However eg.
> >> "Figure 2-83: Example Multi-function MST Branch-Sink Device Enumeration"
That is now done by the DMA-buf helpers instead.
Signed-off-by: Christian König
---
drivers/gpu/drm/drm_prime.c | 76 -
1 file changed, 16 insertions(+), 60 deletions(-)
diff --git a/drivers/gpu/drm/drm_prime.c b/drivers/gpu/drm/drm_prime.c
index
To allow a smooth transition from pinning buffer objects to dynamic
invalidation we first start to cache the sg_table for an attachment
unless the driver explicitly says to not do so.
Signed-off-by: Christian König
---
drivers/dma-buf/dma-buf.c | 24
Instead of relying on the DRM functions just implement our own import
functions. This prepares support for taking care of unpinned DMA-buf.
v2: enable for all exporters, not just amdgpu, fix invalidation
handling, lock reservation object while setting callback
v3: change to new dma_buf attach
Pin and unpin the DMA-buf exported BOs only on demand and invalidate all
DMA-buf mappings when the underlying BO moves.
Signed-off-by: Christian König
---
drivers/gpu/drm/amd/amdgpu/amdgpu_object.c | 5 ++
drivers/gpu/drm/amd/amdgpu/amdgpu_prime.c | 73 --
2 files changed,
Add optional explicit pinning callbacks instead of implicitly assume the
exporter pins the buffer when a mapping is created.
Signed-off-by: Christian König
---
drivers/dma-buf/dma-buf.c | 39 +++
include/linux/dma-buf.h | 37
This way we can even pipeline imported BO evictions.
Signed-off-by: Christian König
---
drivers/gpu/drm/ttm/ttm_bo_util.c | 18 +-
1 file changed, 1 insertion(+), 17 deletions(-)
diff --git a/drivers/gpu/drm/ttm/ttm_bo_util.c
b/drivers/gpu/drm/ttm/ttm_bo_util.c
index
Each importer can now provide an invalidate_mappings callback.
This allows the exporter to provide the mappings without the need to pin
the backing store.
v2: don't try to invalidate mappings when the callback is NULL,
lock the reservation obj while using the attachments,
add helper to
The caching of SGT's is actually quite harmful and should probably removed
altogether when all drivers are audited.
Start by providing a separate DMA-buf export implementation in amdgpu. This is
also a prerequisite of unpinned DMA-buf handling.
v2: fix unintended recursion, remove debugging
Pipeline removal of the BOs backing store when no placement is given
during validation.
Signed-off-by: Christian König
---
drivers/gpu/drm/ttm/ttm_bo.c | 12
1 file changed, 12 insertions(+)
diff --git a/drivers/gpu/drm/ttm/ttm_bo.c b/drivers/gpu/drm/ttm/ttm_bo.c
index
Allow for invalidation of imported DMA-bufs.
v2: add dma_buf_pin/dma_buf_unpin support
Signed-off-by: Christian König
---
drivers/gpu/drm/amd/amdgpu/amdgpu_object.c | 6 ++
drivers/gpu/drm/amd/amdgpu/amdgpu_prime.c | 24 ++
2 files changed, 30 insertions(+)
diff
In trying to further align the AOSP libdrm branch with upstream,
I wanted to submit the added test planetest that they have been
carrying for awhile.
Mostly sending this out for initial reactions and to stir some
discussion on if folks think upstreaming this would be useful.
Feedback and thoughts
From: Christian König
Don't block others while waiting for the fences to finish, concurrent
submission is perfectly valid in this case and holding the lock can
prevent killed applications from terminating.
Signed-off-by: Christian König
Reviewed-by: Nicholas Kazlauskas
---
Den 16.04.2019 09.59, skrev Daniel Vetter:
> On Sun, Apr 07, 2019 at 06:52:33PM +0200, Noralf Trønnes wrote:
>> drm_fb_helper_is_bound() is used to check if DRM userspace is in control.
>> This is done by looking at the fb on the primary plane. By the time
>> fb-helper gets around to committing,
Make it mandatory for dynamic dma-buf callbacks to be called with the
reservation lock held.
For static dma-buf exporters we still have the fallback of using cached sgt.
v2: reordered
v3: rebased on sgt caching
v4: use the cached sgt when possible
Signed-off-by: Christian König
---
Hi everybody,
core idea in this patch set is that DMA-buf importers can now provide an
optional invalidate callback. Using this callback and the reservation object
exporters can now avoid pinning DMA-buf memory for a long time while sharing it
between devices.
I've already send out an older
Add function variants which can be called with the reservation lock
already held.
v2: reordered, add lockdep asserts, fix kerneldoc
v3: rebased on sgt caching
Signed-off-by: Christian König
---
drivers/dma-buf/dma-buf.c | 63 +++
include/linux/dma-buf.h |
On Tue, 2019-04-16 at 20:15 +0200, Daniel Vetter wrote:
> On Tue, Apr 16, 2019 at 6:21 PM Deepak Singh Rawat > wrote:
> >
> > On Tue, 2019-04-16 at 09:42 +0200, Daniel Vetter wrote:
> > > On Mon, Apr 15, 2019 at 05:28:05PM +, Deepak Singh Rawat
> > > wrote:
> > > > Plane property
On Tue, Apr 16, 2019 at 09:43:49AM -0700, John Stultz wrote:
> In trying to further align the AOSP libdrm branch with upstream,
> I wanted to submit the added test planetest that they have been
> carrying for awhile.
>
> Mostly sending this out for initial reactions and to stir some
> discussion
Am 16.04.19 um 17:42 schrieb Grodzovsky, Andrey:
> On 4/16/19 10:58 AM, Grodzovsky, Andrey wrote:
>> On 4/16/19 10:43 AM, Koenig, Christian wrote:
>>> Am 16.04.19 um 16:36 schrieb Grodzovsky, Andrey:
On 4/16/19 5:47 AM, Christian König wrote:
> Am 15.04.19 um 23:17 schrieb Eric Anholt:
On Tue, Apr 16, 2019 at 6:21 PM Deepak Singh Rawat wrote:
>
> On Tue, 2019-04-16 at 09:42 +0200, Daniel Vetter wrote:
> > On Mon, Apr 15, 2019 at 05:28:05PM +, Deepak Singh Rawat wrote:
> > > Plane property "FB_DAMAGE_CLIPS" can only be used by atomic aware
> > > user-space, so no point
On Tue, 16 Apr 2019 at 22:58, Lionel Landwerlin
wrote:
>
> Unfortunately userspace users of this API cannot be publicly disclosed
> yet.
>
> This commit effectively disables timeline syncobj ioctls for all
> drivers. Each driver wishing to support this feature will need to
> expose
https://bugs.freedesktop.org/show_bug.cgi?id=110443
--- Comment #2 from Julien Isorce ---
Thx for your comment. What about the following in vlVaDeriveImage:
- w = align(surf->buffer->width, 2);
- h = align(surf->buffer->height, 2);
+
+ alignment = screen->get_param(screen,
After a recent commit, access to the DRM_AUTH ioctls become more
permissive. This resulted in a buggy check for drm_master capabilities
inside radv stop working.
This commit adds a backwards compatibility workaround so that the radv
drm_master check keeps working as previously expected.
This
On Fri, 2019-04-12 at 12:05 -0400, sunpeng...@amd.com wrote:
> From: Ville Syrjälä
>
> Expose AUX devices for MST ports, similar to how they are exposed for
> SST.
>
> The registered device will have it's MST port path appended in order to
> identify it. i.e. /dev/drm_dp_aux4_mst:0-2-1
>
> So
The .ioctl and .compat_ioctl file operations have the same prototype so
they can both point to the same function, which works great almost all
the time when all the commands are compatible.
One exception is the s390 architecture, where a compat pointer is only
31 bit wide, and converting it into
> >
> > If you mean ssh on annarchy.freedesktop.org, I already have one
> > with
> > username - drawat
>
> You're added. Please check out the dim toturial and pls ask any
> questions here or on irc or wherever - drm(-misc) maintainers are
> happy to help out.
> -Daniel
>
Hi I followed the
https://bugs.freedesktop.org/show_bug.cgi?id=110443
--- Comment #3 from Marek Olšák ---
That's incorrect. The only way to get the stride is through winsys_handle. We
could add a separate query function though.
--
You are receiving this mail because:
You are the assignee for the
https://bugs.freedesktop.org/show_bug.cgi?id=110443
--- Comment #1 from Marek Olšák ---
(In reply to Julien Isorce from comment #0)
> vaDeriveImage reports wrong stride.
>
> Indeed Mesa's vlVaDeriveImage always sets the stride to w * 4 for RGBA
> format
>
On Tue, Apr 16, 2019 at 8:28 PM Deepak Singh Rawat wrote:
>
> On Tue, 2019-04-16 at 20:15 +0200, Daniel Vetter wrote:
> > On Tue, Apr 16, 2019 at 6:21 PM Deepak Singh Rawat > > wrote:
> > >
> > > On Tue, 2019-04-16 at 09:42 +0200, Daniel Vetter wrote:
> > > > On Mon, Apr 15, 2019 at 05:28:05PM
Sorry for the slow response, I've been really busy ;_;
On Fri, 2019-04-12 at 12:05 -0400, sunpeng...@amd.com wrote:
> From: Leo Li
>
> In preparation for adding aux devices for DP MST:
>
> 1. A non-cyclic idr is used for the device minor version. That way,
>hotplug cycling MST devices
https://bugzilla.kernel.org/show_bug.cgi?id=203339
Bug ID: 203339
Summary: AMDGPU: virtual_display disables physical outputs
Product: Drivers
Version: 2.5
Kernel Version: 5.0.7
Hardware: All
OS: Linux
Tree:
The CL submission had two jobs embedded in an exec struct. When I
added TFU support, I had to replicate some of the exec stuff and some
of the job stuff. As I went to add CSD, it became clear that actually
what was in exec should just be in the two CL jobs, and it would let
us share a lot more
We only set the excl (possible-writing) fence pointer and never add a
shared (read-only) fence.
Signed-off-by: Eric Anholt
---
drivers/gpu/drm/v3d/v3d_gem.c | 12
1 file changed, 12 deletions(-)
diff --git a/drivers/gpu/drm/v3d/v3d_gem.c b/drivers/gpu/drm/v3d/v3d_gem.c
index
The compute shader dispatch interface is pretty simple -- just pass in
the regs that userspace has passed us, with no CLs to run. However,
with no CL to run it means that we need to do manual cache flushing of
the L2 after the HW execution completes (for SSBO, atomic, and
image_load_store writes
It is the expectation of existing userspace (X11 + Mesa, in
particular) that jobs submitted to the kernel against a shared BO will
get implicitly synchronized by their submission order. If we want to
allow clever userspace to disable implicit synchronization, we should
do that under its own
This is a resend of my April 1st series, rebased on the merge of the
fence array helpers, and with little fixes for bugs reported by static
analysis and one minor race fix I noticed while re-reviewing.
Eric Anholt (5):
drm/v3d: Switch the type of job-> to reduce casting.
drm/v3d: Refactor job
All consumers wanted drm_gem_object * now.
Signed-off-by: Eric Anholt
---
drivers/gpu/drm/v3d/v3d_drv.h | 4 ++--
drivers/gpu/drm/v3d/v3d_gem.c | 42 +--
2 files changed, 17 insertions(+), 29 deletions(-)
diff --git a/drivers/gpu/drm/v3d/v3d_drv.h
Hi Al,
It took me way longer than I had hoped to revisit this series, see
https://lore.kernel.org/lkml/20180912150142.157913-1-a...@arndb.de/
for the previously posted version.
I've come to the point where all conversion handlers and most
COMPATIBLE_IOCTL() entries are gone from this file, but
Qiang Yu writes:
> Indeed not that important, so patch 5&7 is:
> Reviewed-and-tested-by: Qiang Yu
Merged these two. Thanks for trying it out!
signature.asc
Description: PGP signature
___
dri-devel mailing list
dri-devel@lists.freedesktop.org
Christian König writes:
> Am 16.04.19 um 02:35 schrieb Karol Herbst:
>> Kobjects are supposed to be dynamically allocated, but with recent changes
>> this rule was violated. Reverting those commits fixes crashes when a drm
>> driver using TTM gets loaded again.
>>
>> The object in question is
These are two obscure ioctl commands, in a driver that only
has compatible commands, so just let the driver handle this
itself.
Signed-off-by: Arnd Bergmann
---
drivers/video/fbdev/aty/atyfb_base.c | 12 +++-
fs/compat_ioctl.c| 2 --
2 files changed, 11
Hi, Frank:
On Wed, 2019-04-17 at 07:30 +0200, Frank Wunderlich wrote:
> Hi CK Hu,
>
> you mean the problematic patch is fix possible_crtcs (4/4) and the others are
> ok?
>
> can you push the first 3 while working on the last one?
I think 3 patches is related to possible crtc problem: (1/4),
From: Rob Clark
For KHR_robustness, userspace wants to know two things, the count of GPU
faults globally, and the count of faults attributed to a given context.
This patch providees the former, and the next patch provides the latter.
Signed-off-by: Rob Clark
---
https://bugs.freedesktop.org/show_bug.cgi?id=110457
Bug ID: 110457
Summary: System resumes failed and hits
[drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx
timeout on Acer Squirtle_SR laptop
Product: DRI
On Wed, Apr 17, 2019 at 1:09 AM Eric Anholt wrote:
>
> Christian König writes:
>
> > Am 16.04.19 um 02:35 schrieb Karol Herbst:
> >> Kobjects are supposed to be dynamically allocated, but with recent changes
> >> this rule was violated. Reverting those commits fixes crashes when a drm
> >>
From: Jordan Crouse
Add the capability to query information from a submit queue.
The first available parameter is for querying the number of GPU faults
(hangs) that can be attributed to the queue.
This is useful for implementing context robustness. A user context can
regularly query the number
From: Rob Clark
For now it always returns '0' (false), but once the iommu work is in
place to enable per-process pagetables we can update the value returned.
Userspace needs to know this to make an informed decision about exposing
KHR_robustness.
Signed-off-by: Rob Clark
---
Collection of a few small UABI updates from Jordan and myself to enable
userspace support for robustness[1]. The userspace side of this is at:
https://gitlab.freedesktop.org/mesa/mesa/merge_requests/673/commits
[1] it doesn't *quite* enable it yet, since we don't have per-context
1 - 100 of 196 matches
Mail list logo
