Re: [PATCH v7 09/11] drm: uevent for connector status change

On Mon, 3 Jun 2019 15:19:13 + "Ser, Simon" wrote: > On Mon, 2019-06-03 at 17:08 +0200, Daniel Vetter wrote: > > It's definitely a very suboptimal situation. Not sure there's a good way > > out. The trouble here is that i915 ended up configuring crtc/connectors > > differently than -modesetti

Re: Panfrost impossible to probe without opp table

On Mon, 3 Jun 2019 at 19:24, Clément Péron wrote: > > Hi, > > > On Fri, 31 May 2019 at 14:13, Neil Armstrong wrote: > > > > On 31/05/2019 14:09, Tomeu Vizoso wrote: > > > On Fri, 31 May 2019 at 14:03, Neil Armstrong > > > wrote: > > >> > > >> Hi Tomeu, > > >> > > >> On 31/05/2019 13:59, Tomeu V

Re: drm_gem_dumb_map_offset patch

Hi all, Many thanks for your valuable support and answers. Since Dumb mmap is for buffer created using dumb_create ioctl we won't use it anymore. In place a mmap/ummap is called with DMA Buf FD. After some tests it seems working in our side. Many thanks again. Regards. On 5/31/19 1:36 PM, Danie

[RFC PATCH 00/57] drivers: Consolidate device lookup helpers

We have helper routines to lookup devices matching a criteria defined by a "match" helper for bus/class/driver. Often the search is based on a generic property of a device, such as of_node, fwnode, device type or device name. In the absense of a common set of match functions, we have drivers writin

Re: [PATCH v16 12/16] IB, arm64: untag user pointers in ib_uverbs_(re)reg_mr()

On Mon, Jun 03, 2019 at 06:55:14PM +0200, Andrey Konovalov wrote: > This patch is a part of a series that extends arm64 kernel ABI to allow to > pass tagged user pointers (with the top byte set to something else other > than 0x00) as syscall arguments. > > ib_uverbs_(re)reg_mr() use provided user

[PATCH v16 13/16] media/v4l2-core, arm64: untag user pointers in videobuf_dma_contig_user_get

This patch is a part of a series that extends arm64 kernel ABI to allow to pass tagged user pointers (with the top byte set to something else other than 0x00) as syscall arguments. videobuf_dma_contig_user_get() uses provided user pointers for vma lookups, which can only by done with untagged poin

[PATCH v16 10/16] drm/amdgpu, arm64: untag user pointers

This patch is a part of a series that extends arm64 kernel ABI to allow to pass tagged user pointers (with the top byte set to something else other than 0x00) as syscall arguments. In amdgpu_gem_userptr_ioctl() and amdgpu_amdkfd_gpuvm.c/init_user_pages() an MMU notifier is set up with a (tagged) u

[PATCH v16 09/16] fs, arm64: untag user pointers in fs/userfaultfd.c

This patch is a part of a series that extends arm64 kernel ABI to allow to pass tagged user pointers (with the top byte set to something else other than 0x00) as syscall arguments. userfaultfd code use provided user pointers for vma lookups, which can only by done with untagged pointers. Untag us

[PATCH v16 12/16] IB, arm64: untag user pointers in ib_uverbs_(re)reg_mr()

This patch is a part of a series that extends arm64 kernel ABI to allow to pass tagged user pointers (with the top byte set to something else other than 0x00) as syscall arguments. ib_uverbs_(re)reg_mr() use provided user pointers for vma lookups (through e.g. mlx4_get_umem_mr()), which can only b

[PATCH v16 03/16] lib, arm64: untag user pointers in strn*_user

This patch is a part of a series that extends arm64 kernel ABI to allow to pass tagged user pointers (with the top byte set to something else other than 0x00) as syscall arguments. strncpy_from_user and strnlen_user accept user addresses as arguments, and do not go through the same path as copy_fr

Re: [PATCH v16 01/16] uaccess: add untagged_addr definition for other arches

On 6/3/19 11:06 AM, Andrey Konovalov wrote: > On Mon, Jun 3, 2019 at 7:04 PM Khalid Aziz wrote: >> Andrey, >> >> This patch has now become part of the other patch series Chris Hellwig >> has sent out - >> . Can >> you coordinate with

[PATCH v16 00/16] arm64: untag user pointers passed to the kernel

=== Overview arm64 has a feature called Top Byte Ignore, which allows to embed pointer tags into the top byte of each pointer. Userspace programs (such as HWASan, a memory debugging tool [1]) might use this feature and pass tagged user pointers to the kernel through syscalls or other interfaces.

[PATCH v16 06/16] mm, arm64: untag user pointers in mm/gup.c

This patch is a part of a series that extends arm64 kernel ABI to allow to pass tagged user pointers (with the top byte set to something else other than 0x00) as syscall arguments. mm/gup.c provides a kernel interface that accepts user addresses and manipulates user pages directly (for example get

[PATCH v16 05/16] arm64: untag user pointers passed to memory syscalls

This patch is a part of a series that extends arm64 kernel ABI to allow to pass tagged user pointers (with the top byte set to something else other than 0x00) as syscall arguments. This patch allows tagged pointers to be passed to the following memory syscalls: get_mempolicy, madvise, mbind, minco

Re: [PATCH v16 01/16] uaccess: add untagged_addr definition for other arches

On 6/3/19 11:29 AM, Christoph Hellwig wrote: > On Mon, Jun 03, 2019 at 11:24:35AM -0600, Khalid Aziz wrote: >> On 6/3/19 11:06 AM, Andrey Konovalov wrote: >>> On Mon, Jun 3, 2019 at 7:04 PM Khalid Aziz wrote: Andrey, This patch has now become part of the other patch series Chris Hel

[PATCH v16 07/16] mm, arm64: untag user pointers in get_vaddr_frames

This patch is a part of a series that extends arm64 kernel ABI to allow to pass tagged user pointers (with the top byte set to something else other than 0x00) as syscall arguments. get_vaddr_frames uses provided user pointers for vma lookups, which can only by done with untagged pointers. Instead

[PATCH v16 16/16] selftests, arm64: add a selftest for passing tagged pointers to kernel

This patch is a part of a series that extends arm64 kernel ABI to allow to pass tagged user pointers (with the top byte set to something else other than 0x00) as syscall arguments. This patch adds a simple test, that calls the uname syscall with a tagged user pointer as an argument. Without the ke

[PATCH libdrm] etnaviv: Use hash table to track BO indexes

Use hash table instead of ad-hoc arrays. Signed-off-by: Marek Vasut Cc: Christian Gmeiner Cc: Lucas Stach --- etnaviv/etnaviv_bo.c | 6 +++--- etnaviv/etnaviv_cmd_stream.c | 31 ++- etnaviv/etnaviv_priv.h | 17 ++--- 3 files changed, 35 in

[RFC PATCH 05/57] drm: mipi_dsi: Use bus_find_device_by_of_node() helper

Switch to using the bus_find_device_by_of_node() helper. Cc: Maarten Lankhorst Cc: Maxime Ripard Cc: dri-devel@lists.freedesktop.org Cc: David Airlie Cc: Daniel Vetter Signed-off-by: Suzuki K Poulose --- drivers/gpu/drm/drm_mipi_dsi.c | 7 +-- 1 file changed, 1 insertion(+), 6 deletions(

Re: Panfrost impossible to probe without opp table

Hi, On Fri, 31 May 2019 at 14:13, Neil Armstrong wrote: > > On 31/05/2019 14:09, Tomeu Vizoso wrote: > > On Fri, 31 May 2019 at 14:03, Neil Armstrong > > wrote: > >> > >> Hi Tomeu, > >> > >> On 31/05/2019 13:59, Tomeu Vizoso wrote: > >>> On Wed, 29 May 2019 at 23:29, Clément Péron wrote: > >>

[PATCH v16 14/16] tee, arm64: untag user pointers in tee_shm_register

This patch is a part of a series that extends arm64 kernel ABI to allow to pass tagged user pointers (with the top byte set to something else other than 0x00) as syscall arguments. tee_shm_register()->optee_shm_unregister()->check_mem_type() uses provided user pointers for vma lookups (via __check

[PATCH v16 15/16] vfio/type1, arm64: untag user pointers in vaddr_get_pfn

This patch is a part of a series that extends arm64 kernel ABI to allow to pass tagged user pointers (with the top byte set to something else other than 0x00) as syscall arguments. vaddr_get_pfn() uses provided user pointers for vma lookups, which can only by done with untagged pointers. Untag us

Re: [PATCH v16 01/16] uaccess: add untagged_addr definition for other arches

On 6/3/19 10:55 AM, Andrey Konovalov wrote: > To allow arm64 syscalls to accept tagged pointers from userspace, we must > untag them when they are passed to the kernel. Since untagging is done in > generic parts of the kernel, the untagged_addr macro needs to be defined > for all architectures. >

[PATCH v16 04/16] mm: untag user pointers in do_pages_move

This patch is a part of a series that extends arm64 kernel ABI to allow to pass tagged user pointers (with the top byte set to something else other than 0x00) as syscall arguments. do_pages_move() is used in the implementation of the move_pages syscall. Untag user pointers in this function. Revi

Re: [PATCH v2] video: fbdev: Fix Warning comparing pointer to 0 reported by coccicheck

On Mon, Jun 3, 2019 at 1:21 PM wrote: > > From: Shobhit Kukreti > > Fixed Warning Comparing Pointer to 0. Changed return value to -ENOMEM to > report kzalloc failure > > drivers/video/fbdev/controlfb.c: WARNING comparing pointer to 0 > drivers/video/fbdev/controlfb.c: WARNING comparing pointer to

[PATCH v16 08/16] fs, arm64: untag user pointers in copy_mount_options

This patch is a part of a series that extends arm64 kernel ABI to allow to pass tagged user pointers (with the top byte set to something else other than 0x00) as syscall arguments. In copy_mount_options a user address is being subtracted from TASK_SIZE. If the address is lower than TASK_SIZE, the

Re: [PATCH v16 01/16] uaccess: add untagged_addr definition for other arches

On Mon, Jun 3, 2019 at 7:04 PM Khalid Aziz wrote: > > On 6/3/19 10:55 AM, Andrey Konovalov wrote: > > To allow arm64 syscalls to accept tagged pointers from userspace, we must > > untag them when they are passed to the kernel. Since untagging is done in > > generic parts of the kernel, the untagge

[PATCH v16 02/16] arm64: untag user pointers in access_ok and __uaccess_mask_ptr

This patch is a part of a series that extends arm64 kernel ABI to allow to pass tagged user pointers (with the top byte set to something else other than 0x00) as syscall arguments. copy_from_user (and a few other similar functions) are used to copy data from user memory into the kernel memory or v

[PATCH v16 01/16] uaccess: add untagged_addr definition for other arches

To allow arm64 syscalls to accept tagged pointers from userspace, we must untag them when they are passed to the kernel. Since untagging is done in generic parts of the kernel, the untagged_addr macro needs to be defined for all architectures. Define it as a noop for architectures other than arm64

[PATCH v16 11/16] drm/radeon, arm64: untag user pointers in radeon_gem_userptr_ioctl

This patch is a part of a series that extends arm64 kernel ABI to allow to pass tagged user pointers (with the top byte set to something else other than 0x00) as syscall arguments. In radeon_gem_userptr_ioctl() an MMU notifier is set up with a (tagged) userspace pointer. The untagged address shoul

Re: [PATCH 1/7] video: add HDMI state notifier support

On Mon, Jun 03, 2019 at 11:05:19AM +0200, Hans Verkuil wrote: > On 6/3/19 10:09 AM, Daniel Vetter wrote: > > On Mon, Jun 03, 2019 at 09:45:49AM +0200, Hans Verkuil wrote: > >> On 6/3/19 6:32 AM, Cheng-Yi Chiang wrote: > >>> From: Hans Verkuil > >>> > >>> Add support for HDMI hotplug and EDID notif

Re: [PATCH 1/7] video: add HDMI state notifier support

On Tue, Jun 04, 2019 at 10:32:50AM +0800, Cheng-yi Chiang wrote: > On Mon, Jun 3, 2019 at 4:09 PM Daniel Vetter wrote: > > > > On Mon, Jun 03, 2019 at 09:45:49AM +0200, Hans Verkuil wrote: > > > On 6/3/19 6:32 AM, Cheng-Yi Chiang wrote: > > > > From: Hans Verkuil > > > > > > > > Add support for H

[Bug 110276] Memory leak on kernel 5.0 using Vulkan applications, fixed on drm-tip and 5.1-rc1

https://bugs.freedesktop.org/show_bug.cgi?id=110276 Jani Nikula changed: What|Removed |Added Assignee|intel-gfx-bugs@lists.freede |dri-devel@lists.freedesktop

[Bug 110276] Memory leak on kernel 5.0 using Vulkan applications, fixed on drm-tip and 5.1-rc1

https://bugs.freedesktop.org/show_bug.cgi?id=110276 Jani Nikula changed: What|Removed |Added Assignee|dri-devel@lists.freedesktop |ckoenig.leichtzumerken@gmai

[Bug 110781] Radeon: heavy r300 performance drop regression between 11.x and 19.x

https://bugs.freedesktop.org/show_bug.cgi?id=110781 --- Comment #25 from Richard Thier --- In the assert problem this is the domain and flag meanings in case of only my hack is in place: domain(6) == RADEON_DOMAIN_GTT(2) | RADEON_DOMAIN_VRAM(4) flags(1) == RADEON_FLAG_GTT_WC (1 << 0) So I get -

Re: DRM/AST regression (likely 4.14 -> 4.19+), providing EDID manually fails

On Mon, 03 Jun 2019, Harish Chegondi wrote: > On Wed, May 29, 2019 at 01:22:30PM +0300, Jani Nikula wrote: >> On Wed, 29 May 2019, Ilpo Järvinen wrote: >> > On Tue, 28 May 2019, Jani Nikula wrote: >> > >> >> On Mon, 27 May 2019, Ashutosh Dixit wrote: >> >> > On Sun, 26 May 2019 12:50:51 -0700, I

[Bug 110781] Radeon: heavy r300 performance drop regression between 11.x and 19.x

https://bugs.freedesktop.org/show_bug.cgi?id=110781 Richard Thier changed: What|Removed |Added Attachment #144427|0 |1 is obsolete|

Re: [PATCH v4 0/5] drm: Fix fb changes for async updates

On Mon, 3 Jun 2019 13:56:05 -0300 Helen Koike wrote: > Hello, > > I'm re-sending this series with the acked by in the msm patch and > updating the docs in the last patch, the rest is the same. > > v3 link: https://patchwork.kernel.org/project/dri-devel/list/?series=91353 Series queued to drm-

Re: [PATCH v4 1/5] drm/rockchip: fix fb references in async update

On Mon, 3 Jun 2019 17:13:34 -0300 Helen Koike wrote: > On 6/3/19 1:56 PM, Helen Koike wrote: > > In the case of async update, modifications are done in place, i.e. in the > > current plane state, so the new_state is prepared and the new_state is > > cleaned up (instead of the old_state, unlike wh

[Bug 110822] booting with kernel version 5.1.0 or higher on RX 580 hangs

https://bugs.freedesktop.org/show_bug.cgi?id=110822 --- Comment #5 from Gobinda Joy --- (In reply to Alex Deucher from comment #4) > (In reply to Gobinda Joy from comment #3) > > I was curious so checked out the commit log on amd-staging-drm-next branch. > > And I see some reverts of powerplay re

[Bug 203779] booting with kernel version 5.1.6 on RX 580 hangs

https://bugzilla.kernel.org/show_bug.cgi?id=203779 --- Comment #4 from Gobinda Joy (gobinda@gmail.com) --- (In reply to Alex Deucher from comment #2) > Can you bisect? Same bug report: https://bugs.freedesktop.org/show_bug.cgi?id=110822 -- You are receiving this mail because: You are watchi

[Bug 110422] AMD_DEBUG=forcedma will crash OpenGL aps with SIGFAULT on VegaM 8706G

https://bugs.freedesktop.org/show_bug.cgi?id=110422 --- Comment #3 from Dimitar Atanasov --- Working correct now with Vega M. Please close. -- You are receiving this mail because: You are the assignee for the bug.___ dri-devel mailing list dri-devel@l

[Bug 110781] Radeon: heavy r300 performance drop regression between 11.x and 19.x

https://bugs.freedesktop.org/show_bug.cgi?id=110781 --- Comment #27 from Rui Salvaterra --- This is amazing work, Richard. I'd love to help you with testing, since I also have the same hardware, but unfortunately I don't have a build environment ready. I'm using padoka's PPA, though. FWIW, I'll b

Re: [PATCH v10 01/11] drm/sun4i: dsi: Fix TCON DRQ set bits

On Wed, May 29, 2019 at 11:44:56PM +0530, Jagan Teki wrote: > On Wed, May 29, 2019 at 8:24 PM Maxime Ripard > wrote: > > > > On Fri, May 24, 2019 at 03:48:51PM +0530, Jagan Teki wrote: > > > On Fri, May 24, 2019 at 2:04 AM Maxime Ripard > > > wrote: > > > > > > > > On Mon, May 20, 2019 at 02:33

[Bug 110781] Radeon: heavy r300 performance drop regression between 11.x and 19.x

https://bugs.freedesktop.org/show_bug.cgi?id=110781 --- Comment #28 from Richard Thier --- Hi Rui! We should also thank Marek for him proposing a possible fix. I am currently creating a "less hacky" solution based on that attachment and a better idea to not always force VRAM domain, but only if

Re: [PATCH 09/22] docs: mark orphan documents as such

Em Mon, 3 Jun 2019 09:32:54 +0200 Christophe Leroy escreveu: > Le 30/05/2019 à 01:23, Mauro Carvalho Chehab a écrit : > > Sphinx doesn't like orphan documents: > > > > Documentation/accelerators/ocxl.rst: WARNING: document isn't included > > in any toctree > > Documentation/arm/stm32/

[Bug 110795] Unable to install on latest Ubuntu (19.04)

https://bugs.freedesktop.org/show_bug.cgi?id=110795 Michel Dänzer changed: What|Removed |Added Component|DRM/AMDgpu |DRM/AMDgpu-pro -- You are receiving th

Re: [PATCH v7 2/8] drm/fb-helper: Remove drm_fb_helper_crtc

Den 31.05.2019 16.01, skrev Noralf Trønnes: > struct drm_fb_helper_crtc is now just a wrapper around drm_mode_set so > use that directly instead and attach it as a modeset array onto > drm_client_dev. drm_fb_helper will use this array to store its modesets > which means it will always initialize

[Bug 110781] Radeon: heavy r300 performance drop regression between 11.x and 19.x

https://bugs.freedesktop.org/show_bug.cgi?id=110781 Richard Thier changed: What|Removed |Added Attachment #144439|0 |1 is obsolete|

[Bug 110781] Radeon: heavy r300 performance drop regression between 11.x and 19.x

https://bugs.freedesktop.org/show_bug.cgi?id=110781 --- Comment #30 from Richard Thier --- Interesting to me is that the CREATE call number is still higher in strace output than how it was originally before the first slowdown, but the performance seems to be the same after applying the quickfix t

Re: [RESEND PATCH v2] drm/vmwgfx: fix a warning due to missing dma_parms

Reviewed-by: Thomas Hellstrom I'll just need to give this some more testing before queueing it on vmwgfx-fixes. Thanks, Thomas On Mon, 2019-06-03 at 16:44 -0400, Qian Cai wrote: > Booting up with DMA_API_DEBUG_SG=y generates a warning due to the > driver > forgot to set dma_parms appropriately

[Bug 110781] Radeon: heavy r300 performance drop regression between 11.x and 19.x

https://bugs.freedesktop.org/show_bug.cgi?id=110781 --- Comment #31 from Richard Thier --- While bisecting the original issue I saw a point where speed was already bad, but not that much as with latest however mostly like that (at least 90-95%). So there might be a little bit more speedup gain i

[Bug 110781] Radeon: heavy r300 performance drop regression between 11.x and 19.x

https://bugs.freedesktop.org/show_bug.cgi?id=110781 --- Comment #32 from Rui Salvaterra --- (In reply to Richard Thier from comment #28) > Hi Rui! Hi, Richard! > We should also thank Marek for him proposing a possible fix. Yeah, Marek kicks ass, he's one of the original developers of r300g. :)

Re: [PATCH 01/13] drm/amdgpu: introduce and honour DRM_FORCE_AUTH workaround

On 2019-05-28 10:03 a.m., Koenig, Christian wrote: > > I rather think that we should go down the route of completely dropping > command submission and buffer allocation through the primary node for > non master clients. And then as next step at some point drop support for > authentication/flink

[v3 2/3] drm: Fix docbook warnings in hdr metadata helper structures

Fixes the following warnings: ./include/drm/drm_mode_config.h:841: warning: Incorrect use of kernel-doc format: * hdr_output_metadata_property: Connector property containing hdr ./include/drm/drm_mode_config.h:918: warning: Function parameter or member 'hdr_output_metadata_property' not d

Re: [PATCH libdrm 00/10] Add C8, 30bpp and FP16 support to modetest

On Mon, Jun 03, 2019 at 04:57:43PM -0400, Ilia Mirkin wrote: > On Sun, Jun 2, 2019 at 8:40 PM Ilia Mirkin wrote: > > > > This series improves the pattern generation logic to support additional > > formats, as well as a new "gradient" pattern (see patch comments on why > > I found it useful). > > >

[PATCH] drm: Ignore drm_gem_vram_mm_funcs in generated documentation

The documentation tools interpret drm_gem_vram_mm_funcs as function and there appears to be no way of inline-documenting constants. This results in a warning by 'make htmldocs'. For now, removing drm_gem_vram_mm_funcs from generated documentation works around the issue. Signed-off-by: Thomas Zimme

Re: [PATCH 01/13] drm/amdgpu: introduce and honour DRM_FORCE_AUTH workaround

Am 04.06.19 um 12:50 schrieb Michel Dänzer: > On 2019-05-28 10:03 a.m., Koenig, Christian wrote: >> I rather think that we should go down the route of completely dropping >> command submission and buffer allocation through the primary node for >> non master clients. And then as next step at some po

[PATCH v2 0/7] Add anx6345 DP/eDP bridge for Olimex Teres-I

ANX6345 LVTTL->eDP video bridge, driver with device tree bindings. Changes from v1: * fixed up copyright information. Most code changes are only moves and thus retain copyright and module ownership. Even the new analogix-anx6345.c originates from the old 1495-line analogix-anx78xx.c, with

[PATCH v2 2/7] drm/bridge: split some definitions of ANX78xx to dedicated headers

From: Icenowy Zheng Some definitions currently in analogix-anx78xx.h are not restricted to the ANX78xx series, but also applicable to other DisplayPort transmitters by Analogix. Split out them to dedicated headers, and make analogix-anx78xx.h include them. Signed-off-by: Icenowy Zheng Signed-o

[PATCH v2 4/7] drm/bridge: Prepare Analogix anx6345 support

Add bit definitions required for the anx6345 and add a sanity check in anx_dp_aux_transfer. Signed-off-by: Icenowy Zheng Signed-off-by: Vasily Khoruzhick Signed-off-by: Torsten Duwe --- drivers/gpu/drm/bridge/analogix/analogix-i2c-dptx.c | 2 +- drivers/gpu/drm/bridge/analogix/analogix-i2c

[PATCH v2 6/7] dt-bindings: Add ANX6345 DP/eDP transmitter binding

The anx6345 is an ultra-low power DisplayPort/eDP transmitter designed for portable devices. Add a binding document for it. Signed-off-by: Icenowy Zheng Signed-off-by: Vasily Khoruzhick Reviewed-by: Rob Herring Signed-off-by: Torsten Duwe Reviewed-by: Laurent Pinchart --- .../devicetree/bin

[PATCH v2 5/7] drm/bridge: Add Analogix anx6345 support

From: Icenowy Zheng The ANX6345 is an ultra-low power DisplayPower/eDP transmitter designed for portable devices. This driver adds initial support for RGB to eDP mode, without HPD and interrupts. This is a configuration usually seen in eDP applications. Signed-off-by: Icenowy Zheng Signed-off-

[PATCH v2 3/7] drm/bridge: extract some Analogix I2C DP common code

From: Icenowy Zheng Some code can be shared within different DP bridges by Analogix. Extract them to analogix_dp. Signed-off-by: Icenowy Zheng Signed-off-by: Vasily Khoruzhick Signed-off-by: Torsten Duwe --- drivers/gpu/drm/bridge/analogix/Makefile | 2 +- drivers/gpu/drm/bridge/

[PATCH v2 1/7] drm/bridge: move ANA78xx driver to analogix subdirectory

From: Icenowy Zheng As ANA78xx chips are designed and produced by Analogix Semiconductor, Inc, move their driver codes into analogix subdirectory. Signed-off-by: Icenowy Zheng Signed-off-by: Vasily Khoruzhick Reviewed-by: Laurent Pinchart Signed-off-by: Torsten Duwe --- drivers/gpu/drm/brid

[PATCH v2 7/7] arm64: dts: allwinner: a64: enable ANX6345 bridge on Teres-I

Teres-I has an anx6345 bridge connected to the RGB666 LCD output, and the I2C controlling signals are connected to I2C0 bus. eDP output goes to an Innolux N116BGE panel. Enable it in the device tree. Signed-off-by: Icenowy Zheng Signed-off-by: Torsten Duwe --- .../boot/dts/allwinner/sun50i-a64

[Bug 110635] briefly flashing corruption when playing various OGL games

https://bugs.freedesktop.org/show_bug.cgi?id=110635 --- Comment #8 from tempel.jul...@gmail.com --- Could we get an update on this? Apparently AMD_DEBUG=nodma makes the corruption completely disappear, so it seems the issue really is caused by asynchronous DMA. If the cause of the issue is not ea

[Bug 203781] AMDGPU Radeon VII crashes with dual monitors

https://bugzilla.kernel.org/show_bug.cgi?id=203781 Tom B (t...@r.je) changed: What|Removed |Added CC||t...@r.je --- Comment #2 from Tom B (

[PATCH] dma-buf: Discard old fence_excl on retrying get_fences_rcu for realloc

If we have to drop the seqcount & rcu lock to perform a krealloc, we have to restart the loop. In doing so, be careful not to lose track of the already acquired exclusive fence. Fixes: fedf54132d24 ("dma-buf: Restart reservation_object_get_fences_rcu() after writes") #v4.10 Signed-off-by: Chris W

[Bug 110781] Radeon: heavy r300 performance drop regression between 11.x and 19.x

https://bugs.freedesktop.org/show_bug.cgi?id=110781 --- Comment #33 from Richard Thier --- I have compiled a "how to build" just for you - linking sources I used: http://ballmerpeak.web.elte.hu/devblog/building-your-own-mesa.html Everyone should be able to try the quickfix using this and the li

Re: [PATCH] dma-buf: Discard old fence_excl on retrying get_fences_rcu for realloc

Am 04.06.19 um 14:39 schrieb Chris Wilson: > If we have to drop the seqcount & rcu lock to perform a krealloc, we > have to restart the loop. In doing so, be careful not to lose track of > the already acquired exclusive fence. > > Fixes: fedf54132d24 ("dma-buf: Restart reservation_object_get_fences

Re: [PATCH v2 1/2] drm: bridge: dw-hdmi: Add hook for resume

Hi Douglas, Thank you for the patch. On Thu, May 16, 2019 at 02:40:21PM -0700, Douglas Anderson wrote: > On Rockchip rk3288-based Chromebooks when you do a suspend/resume > cycle: > > 1. You lose the ability to detect an HDMI device being plugged in. > > 2. If you're using the i2c bus built in

[PATCH v2] dma-buf: Discard old fence_excl on retrying get_fences_rcu for realloc

If we have to drop the seqcount & rcu lock to perform a krealloc, we have to restart the loop. In doing so, be careful not to lose track of the already acquired exclusive fence. Fixes: fedf54132d24 ("dma-buf: Restart reservation_object_get_fences_rcu() after writes") #v4.10 Signed-off-by: Chris W

[PATCH 0/2] drm/panel-simple: Add panel parameters for ortustech-com37h3m05dtc/99dtc and sharp-lq070y3dg3b

Since v5.2-rc1 OMAP is no longer using a special display driver architecture for DPI panels, but uses the general drm/panel/panel-simple. So we finally can add SoC independent panel definitions for two panel models which we already had worked on quite a while ago (before device tree was introduced

[PATCH 1/2] drm/panel: simple: Add Sharp LQ070Y3DG3B panel support

The change adds support for the Sharp LQ070Y3DG3B 7.0" TFT LCD panel. Signed-off-by: H. Nikolaus Schaller --- drivers/gpu/drm/panel/panel-simple.c | 30 1 file changed, 30 insertions(+) diff --git a/drivers/gpu/drm/panel/panel-simple.c b/drivers/gpu/drm/panel/panel

[PATCH 2/2] drm/panel: simple: Add Ortustech COM37H3M panel support

The change adds support for the Ortustech COM37H3M05DTC/99DTC 3.7" TFT LCD panel. Signed-off-by: H. Nikolaus Schaller --- drivers/gpu/drm/panel/panel-simple.c | 33 1 file changed, 33 insertions(+) diff --git a/drivers/gpu/drm/panel/panel-simple.c b/drivers/gpu/dr

[PATCH v3] dma-buf: Discard old fence_excl on retrying get_fences_rcu for realloc

If we have to drop the seqcount & rcu lock to perform a krealloc, we have to restart the loop. In doing so, be careful not to lose track of the already acquired exclusive fence. Fixes: fedf54132d24 ("dma-buf: Restart reservation_object_get_fences_rcu() after writes") #v4.10 Signed-off-by: Chris W

Re: [PATCH 01/13] drm/amdgpu: introduce and honour DRM_FORCE_AUTH workaround

On Tue, Jun 4, 2019 at 1:24 PM Koenig, Christian wrote: > > Am 04.06.19 um 12:50 schrieb Michel Dänzer: > > On 2019-05-28 10:03 a.m., Koenig, Christian wrote: > >> I rather think that we should go down the route of completely dropping > >> command submission and buffer allocation through the prima

[Bug 110457] System resumes failed and hits [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout on Acer Aspire A315-21G

https://bugs.freedesktop.org/show_bug.cgi?id=110457 --- Comment #8 from Matt Coffin --- This is probably related to bug 102322, yes? -- You are receiving this mail because: You are the assignee for the bug.___ dri-devel mailing list dri-devel@lists.fr

Re: [Bug 110822] booting with kernel version 5.1.0 or higher on RX 580 hangs

bisect is quite common in the git world. You'll find tons of tutorials on the web, namely you're good for a little bit of reading. Just don't forget to "git reset --hard" before calling "git bisect good|bad". (just performed a bisection on linux yesterday). _

[Bug 110822] booting with kernel version 5.1.0 or higher on RX 580 hangs

https://bugs.freedesktop.org/show_bug.cgi?id=110822 --- Comment #6 from Sylvain BERTRAND --- bisect is quite common in the git world. You'll find tons of tutorials on the web, namely you're good for a little bit of reading. Just don't forget to "git reset --hard" before calling "git bisect good|b

[PATCH v2 08/22] gpu: i915.rst: Fix references to renamed files

WARNING: kernel-doc './scripts/kernel-doc -rst -enable-lineno -function Hardware workarounds ./drivers/gpu/drm/i915/intel_workarounds.c' failed with return code 1 WARNING: kernel-doc './scripts/kernel-doc -rst -enable-lineno -function Logical Rings, Logical Ring Contexts and Execlists ./drivers/

[PATCH v2 06/22] docs: mark orphan documents as such

Sphinx doesn't like orphan documents: Documentation/accelerators/ocxl.rst: WARNING: document isn't included in any toctree Documentation/arm/stm32/overview.rst: WARNING: document isn't included in any toctree Documentation/arm/stm32/stm32f429-overview.rst: WARNING: document isn't in

Re: [PATCH 1/2] drm/arm/hdlcd: Actually validate CRTC modes

On Fri, May 17, 2019 at 05:37:21PM +0100, Robin Murphy wrote: > Rather than allowing any old mode through, then subsequently refusing > unmatchable clock rates in atomic_check when it's too late to back out > and pick a different mode, let's do that validation up-front where it > will cause unsuppo

Re: [PATCH 2/2] drm/arm/hdlcd: Allow a bit of clock tolerance

On Fri, May 17, 2019 at 05:37:22PM +0100, Robin Murphy wrote: > On the Arm Juno platform, the HDLCD pixel clock is constrained to 250KHz > resolution in order to avoid the tiny System Control Processor spending > aeons trying to calculate exact PLL coefficients. This means that modes > like my oddb

[Bug 110837] Mesa 19.0.5 breaks support for a WebGL 2 in a Firefox 67.0

https://bugs.freedesktop.org/show_bug.cgi?id=110837 Bug ID: 110837 Summary: Mesa 19.0.5 breaks support for a WebGL 2 in a Firefox 67.0 Product: Mesa Version: 19.0 Hardware: x86-64 (AMD64) OS: Linux (All)

Re: Panfrost impossible to probe without opp table

Hi Tomeu, On Tue, 4 Jun 2019 at 09:09, Tomeu Vizoso wrote: > > On Mon, 3 Jun 2019 at 19:24, Clément Péron wrote: > > > > Hi, > > > > > > On Fri, 31 May 2019 at 14:13, Neil Armstrong > > wrote: > > > > > > On 31/05/2019 14:09, Tomeu Vizoso wrote: > > > > On Fri, 31 May 2019 at 14:03, Neil Armst

Re: DRM/AST regression (likely 4.14 -> 4.19+), providing EDID manually fails

On Mon, 3 Jun 2019, Harish Chegondi wrote: > On Wed, May 29, 2019 at 01:22:30PM +0300, Jani Nikula wrote: > > On Wed, 29 May 2019, Ilpo Järvinen wrote: > > > On Tue, 28 May 2019, Jani Nikula wrote: > > > > > >> On Mon, 27 May 2019, Ashutosh Dixit wrote: > > >> > On Sun, 26 May 2019 12:50:51 -070

Re: [PATCH v10 04/11] drm/sun4i: tcon: Compute DCLK dividers based on format, lanes

On Fri, May 24, 2019 at 03:37:36PM +0530, Jagan Teki wrote: > On Fri, May 24, 2019 at 2:18 AM Maxime Ripard > wrote: > > > > On Mon, May 20, 2019 at 02:33:11PM +0530, Jagan Teki wrote: > > > pll-video => pll-mipi => tcon0 => tcon0-pixel-clock is the typical > > > MIPI clock topology in Allwinner

[GIT PULL] v5.2 fixes for Arm drivers

Hello DRM maintainers, I have collected an assorted set of patches for Arm DRM drivers that I maintain in my tree, so it's time to flush them out. Please pull! Best regards, Liviu The following changes since commit 2a3e0b716296a504d9e65fea7acb379c86fe4283: Merge tag 'imx-drm-fixes-2019-05-29

Re: [pull] amdgpu, amdkfd drm-next-5.3

On Mon, Jun 3, 2019 at 11:36 AM Daniel Vetter wrote: > > On Thu, May 30, 2019 at 12:09 AM Alex Deucher wrote: > > > > Hi Dave, Daniel, > > > > New stuff for 5.3: > > - Add new thermal sensors for vega asics > > - Various RAS fixes > > - Add sysfs interface for memory interface utilization > > - U

[Bug 110422] AMD_DEBUG=forcedma will crash OpenGL aps with SIGFAULT on VegaM 8706G

https://bugs.freedesktop.org/show_bug.cgi?id=110422 Alex Deucher changed: What|Removed |Added Resolution|--- |FIXED Status|NEW

Linking ALSA playback devices and DRM connectors

Hi, I'm trying to link ALSA playback devices and DRM connectors. In other words, I'd like to be able to know which ALSA device I should open to play audio on a given connector. Unfortunately, I haven't found a way to extract this information. I know /proc/asound/cardN/eld* expose the EDID-like da

Re: [PATCH v2 7/7] arm64: dts: allwinner: a64: enable ANX6345 bridge on Teres-I

On Tue, Jun 4, 2019 at 5:23 AM Torsten Duwe wrote: > > Teres-I has an anx6345 bridge connected to the RGB666 LCD output, and > the I2C controlling signals are connected to I2C0 bus. eDP output goes > to an Innolux N116BGE panel. > > Enable it in the device tree. > > Signed-off-by: Icenowy Zheng >

Re: Linking ALSA playback devices and DRM connectors

Am 04.06.19 um 17:05 schrieb Ser, Simon: Hi, I'm trying to link ALSA playback devices and DRM connectors. In other words, I'd like to be able to know which ALSA device I should open to play audio on a given connector. Unfortunately, I haven't found a way to extract this information. I know /pro

Re: [PATCH v2] drm/komeda: Added AFBC support for komeda driver

On Thu, May 23, 2019 at 10:56:54AM +0100, james qian wang (Arm Technology China) wrote: > For supporting AFBC: > 1. Check if the user requested modifier can be supported by display HW. > 2. Check the obj->size with AFBC's requirement. > 3. Configure HW according to the modifier (afbc features) >

[PATCH] drm/ttm: fix ttm_bo_unreserve

Since we now keep BOs on the LRU we need to make sure that they are removed when they are pinned. Signed-off-by: Christian König --- include/drm/ttm/ttm_bo_driver.h | 14 ++ 1 file changed, 6 insertions(+), 8 deletions(-) diff --git a/include/drm/ttm/ttm_bo_driver.h b/include/drm/tt

Re: Linking ALSA playback devices and DRM connectors

On Tue, Jun 4, 2019 at 5:15 PM Christian König wrote: > > Am 04.06.19 um 17:05 schrieb Ser, Simon: > > Hi, > > > > I'm trying to link ALSA playback devices and DRM connectors. In other > > words, I'd like to be able to know which ALSA device I should open to > > play audio on a given connector. >

[PATCH] gpu: host1x: Do not output error message for deferred probe

From: Thierry Reding When deferring probe, avoid logging a confusing error message. While at it, make the error message more informational. Signed-off-by: Thierry Reding --- drivers/gpu/host1x/dev.c | 5 - 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/drivers/gpu/host1x/dev.

[PATCH 2/8] drm/ast: Remove obsolete or unused cursor state

The ast driver's data structures store unused or uncecessary cursor state. Most of the cursor state is already stored elsewhere and can be retrieved when necessary. Remove the obsolete fields and adapt users accordingly. Signed-off-by: Thomas Zimmermann --- drivers/gpu/drm/ast/ast_drv.h | 7 --

  1   2   >