[Bug 101672] radeonsi: 3D engines causing frequent GPU lockups

https://bugs.freedesktop.org/show_bug.cgi?id=101672 --- Comment #23 from Christian König --- (In reply to MirceaKitsune from comment #22) > Wasn't sure whether to bump this same bug report, as the original issue has > clearly been fixed during nearly an year of

Re: [radeon-alex:amd-staging-dkms-4.13 3272/3830] drivers/staging//vboxvideo/vbox_ttm.c:190:9: error: incompatible type for argument 2 of 'ttm_bo_move_memcpy'

Hi Kevin & Roger, the problem is that you might need to request whitelisting. Otherwise the gerrit server might reject your patch. Regards, Christian. Am 22.02.2018 um 05:49 schrieb He, Roger: Hi Kevin: Please help to check if the below patch is merged into staging branch? If not, please

Re: [PATCH] drm/radeon: insist on 32-bit DMA for Cedar

Am 22.02.2018 um 03:05 schrieb Alex Deucher: On Wed, Feb 21, 2018 at 6:41 PM, Ben Crocker wrote: In radeon_device_init, set the need_dma32 flag for Cedar chips (e.g. FirePro 2270). This fixes, or at least works around, a bug on PowerPC exposed by last year's commits

[PATCH v1] drm/simple_kms_helper: Fix NULL pointer dereference with no active CRTC

From: Oleksandr Andrushchenko It is possible that drm_simple_kms_plane_atomic_check called with no CRTC set, e.g. when user-space application sets CRTC_ID/FB_ID to 0 before doing any actual drawing. This leads to NULL pointer dereference because in this case new

RE: [radeon-alex:amd-staging-dkms-4.13 3272/3830] drivers/staging//vboxvideo/vbox_ttm.c:190:9: error: incompatible type for argument 2 of 'ttm_bo_move_memcpy'

Hi Kevin: Please help to check if the below patch is merged into staging branch? If not, please cherry pick that to fix build error. Thanks! commit 3f3a7c8259312084291859d3b623db4317365a07 Author: Christian König Date: Fri Nov 24 11:32:59 2017 +0100

[Bug 99353] Kaveri 7400K shows random colored noise instead of GUI in X or Wayland

https://bugs.freedesktop.org/show_bug.cgi?id=99353 --- Comment #40 from Bong Cosca --- I'm afraid forcing si_write_harvested_raster_configs() doesn't help any. We're back to the old tiled garbage. -- You are receiving this mail because: You are the assignee for the

[Bug 99353] Kaveri 7400K shows random colored noise instead of GUI in X or Wayland

https://bugs.freedesktop.org/show_bug.cgi?id=99353 --- Comment #39 from Bong Cosca --- Created attachment 137521 --> https://bugs.freedesktop.org/attachment.cgi?id=137521=edit dmesg -- You are receiving this mail because: You are the assignee for the

[RFC PATCH hwc] drm_hwcomposer: set CRTC background color when available

Android assumes an implicit black background layer is always present behind all layers it specifies for composition. drm_hwcomposer currently punts responsibility for this to the kernel/DRM platform and puts layers with per-pixel alpha content on the primary plane when requested. On some

[Bug 99353] Kaveri 7400K shows random colored noise instead of GUI in X or Wayland

https://bugs.freedesktop.org/show_bug.cgi?id=99353 --- Comment #38 from Alex Deucher --- Does forcing si_write_harvested_raster_configs() in si_state.c help? -- You are receiving this mail because: You are the assignee for the

[Bug 99353] Kaveri 7400K shows random colored noise instead of GUI in X or Wayland

https://bugs.freedesktop.org/show_bug.cgi?id=99353 --- Comment #37 from Alex Deucher --- (In reply to Bong Cosca from comment #36) > Mesa 18.1 shows no problems with this patch. Are we going to see this code > change in the mainstream anytime soon? That will break other

Re: [PATCH v4 4/6] arm64: dts: exynos: add OF graph between MHL and USB connector

Hi Andrzej, I love your patch! Yet something to improve: [auto build test ERROR on robh/for-next] [also build test ERROR on v4.16-rc2 next-20180221] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url: https://github.com/0day-ci/linux

Re: [PATCH v5 1/5] drm: xlnx: Xilinx DRM KMS module

Hi Laurent, On Wed, 2018-02-21 at 15:22:31 -0800, Laurent Pinchart wrote: > Hi Hyun, > > On Tuesday, 20 February 2018 19:11:42 EET hyun.k...@xilinx.com wrote: > > On Monday, February 19, 2018 1:43 AM Daniel Vetter wrote: > > > On Tue, Feb 06, 2018 at 05:36:36PM -0800, Hyun Kwon wrote: > > >>

Re: [PATCH v5 4/5] drm: xlnx: DRM KMS driver for Xilinx ZynqMP DisplayPort

Hi Laurent, Thanks for the comment. On Wed, 2018-02-21 at 16:18:35 -0800, Laurent Pinchart wrote: > Hi Hyun, > > Thank you for the patch. > > On Wednesday, 7 February 2018 03:36:39 EET Hyun Kwon wrote: > > This driver creates DRM encoder and connector for ZynqMP DisplayPort. > > > >

[Bug 99353] Kaveri 7400K shows random colored noise instead of GUI in X or Wayland

https://bugs.freedesktop.org/show_bug.cgi?id=99353 --- Comment #36 from Bong Cosca --- Mesa 18.1 shows no problems with this patch. Are we going to see this code change in the mainstream anytime soon? -- You are receiving this mail because: You are the assignee for the

Re: [PATCH v5 1/5] drm: xlnx: Xilinx DRM KMS module

Hi Laurent, Thanks for the review. On Wed, 2018-02-21 at 15:17:25 -0800, Laurent Pinchart wrote: > Hi Hyun, > > Thank you for the patch. > > On Wednesday, 7 February 2018 03:36:36 EET Hyun Kwon wrote: > > Xilinx has various platforms for display, where users can create > > using multiple IPs

Re: [PATCH] drm/radeon: insist on 32-bit DMA for Cedar

On Wed, Feb 21, 2018 at 6:41 PM, Ben Crocker wrote: > In radeon_device_init, set the need_dma32 flag for Cedar chips > (e.g. FirePro 2270). This fixes, or at least works around, a bug > on PowerPC exposed by last year's commits > > 8e3f1b1d8255105f31556aacf8aeb6071b00d469

[Bug 105200] [r600g] Regression: ImageMagick OpenCL kernel no longer compiles

https://bugs.freedesktop.org/show_bug.cgi?id=105200 Bug ID: 105200 Summary: [r600g] Regression: ImageMagick OpenCL kernel no longer compiles Product: Mesa Version: git Hardware: x86-64 (AMD64) OS: Linux

Re: [PATCH v5 4/5] drm: xlnx: DRM KMS driver for Xilinx ZynqMP DisplayPort

Hi Hyun, Thank you for the patch. On Wednesday, 7 February 2018 03:36:39 EET Hyun Kwon wrote: > This driver creates DRM encoder and connector for ZynqMP DisplayPort. > > Signed-off-by: Hyun Kwon > Acked-by: Daniel Vetter Before I go and review

[Bug 101672] radeonsi: 3D engines causing frequent GPU lockups

https://bugs.freedesktop.org/show_bug.cgi?id=101672 MirceaKitsune changed: What|Removed |Added See Also|

[Bug 101672] radeonsi: 3D engines causing frequent GPU lockups

https://bugs.freedesktop.org/show_bug.cgi?id=101672 MirceaKitsune changed: What|Removed |Added Priority|medium

[PATCH v5 6/8] i2c: demux: Use changeset helpers for clarity

From: Pantelis Antoniou The changeset helpers are easier to use, use them instead of using the static property. Signed-off-by: Pantelis Antoniou Acked-by: Wolfram Sang ["okay" -> "ok"] Signed-off-by: Laurent

[PATCH v5 8/8] drm: rcar-du: Convert LVDS encoder code to bridge driver

The LVDS encoders used to be described in DT as part of the DU. They now have their own DT node, linked to the DU using the OF graph bindings. This allows moving internal LVDS encoder support to a separate driver modelled as a DRM bridge. Backward compatibility is retained as legacy DT is patched

[PATCH v5 4/8] of: changesets: Introduce changeset helper methods

From: Pantelis Antoniou Changesets are very powerful, but the lack of a helper API makes using them cumbersome. Introduce a simple copy based API that makes things considerably easier. To wit, adding a property using the raw API. struct property *prop;

[PATCH v5 5/8] of: unittest: changeset helpers

From: Pantelis Antoniou Add a unitest specific for the new changeset helpers. Signed-off-by: Pantelis Antoniou [Use IS_ENABLED instead of #ifdef] Signed-off-by: Laurent Pinchart

[PATCH v5 0/8] R-Car DU: Convert LVDS code to bridge driver

Hello, This patch series addresses a design mistake that dates back from the initial DU support. Support for the LVDS encoders, which are IP cores separate from the DU, was bundled in the DU driver. Worse, both the DU and LVDS were described through a single DT node. To fix the, patches 1/8 and

[PATCH v5 7/8] drm: rcar-du: Fix legacy DT to create LVDS encoder nodes

The internal LVDS encoders now have their own DT bindings. Before switching the driver infrastructure to those new bindings, implement backward-compatibility through live DT patching. Patching is disabled and will be enabled along with support for the new DT bindings in the DU driver.

[PATCH v5 3/8] of: dynamic: Add __of_node_dupv()

From: Pantelis Antoniou Add an __of_node_dupv() private method and make __of_node_dup() use it. This is required for the subsequent changeset accessors which will make use of it. Signed-off-by: Pantelis Antoniou [Make

[PATCH v5 2/8] dt-bindings: display: renesas: Deprecate LVDS support in the DU bindings

The internal LVDS encoders now have their own DT bindings, representing them as part of the DU is deprecated. Signed-off-by: Laurent Pinchart Reviewed-by: Rob Herring --- Changes since v1: - Remove the LVDS reg range from the example

[PATCH v5 1/8] dt-bindings: display: renesas: Add R-Car LVDS encoder DT bindings

The Renesas R-Car Gen2 and Gen3 SoCs have internal LVDS encoders. Add corresponding device tree bindings. Signed-off-by: Laurent Pinchart Reviewed-by: Rob Herring --- Changes since v1: - Move the SoC name before the IP name in

Re: [Mesa-dev] Allocator Nouveau driver, Mesa EXT_external_objects, and DRM metadata import interfaces

On Wed, Feb 21, 2018 at 1:14 AM, Chad Versace wrote: > On Thu 21 Dec 2017, Daniel Vetter wrote: >> On Thu, Dec 21, 2017 at 12:22 AM, Kristian Kristensen >> wrote: >>> On Wed, Dec 20, 2017 at 12:41 PM, Miguel Angel Vico >>>

RE: [PATCH libdrm 1/2] intel: align reuse buffer's size on page size instead

On Wed, Feb 21, 2018 at 09:43:55PM +, Chris Wilson wrote: > Quoting James Xiong (2018-02-20 17:48:03) > > From: "Xiong, James" > > > > With gem_reuse enabled, when a buffer size is different than > > the sizes of buckets, it is aligned to the next bucket's size, > >

Re: [PATCH v4 08/16] drm: rcar-du: Fix legacy DT to create LVDS encoder nodes

Hi Rob, On Thursday, 22 February 2018 01:28:48 EET Rob Herring wrote: > On Tue, Feb 20, 2018 at 5:10 PM, Laurent Pinchart wrote: > > The internal LVDS encoders now have their own DT bindings. Before > > switching the driver infrastructure to those new bindings, implement > >

Re: [PATCH v4 06/16] of: unittest: changeset helpers

On Wed, Feb 21, 2018 at 5:39 PM, Laurent Pinchart wrote: > Hi Rob, > > On Thursday, 22 February 2018 01:10:25 EET Rob Herring wrote: >> On Tue, Feb 20, 2018 at 5:10 PM, Laurent Pinchart wrote: >> > From: Pantelis Antoniou >> > >>

[PATCH] drm/radeon: insist on 32-bit DMA for Cedar

In radeon_device_init, set the need_dma32 flag for Cedar chips (e.g. FirePro 2270). This fixes, or at least works around, a bug on PowerPC exposed by last year's commits 8e3f1b1d8255105f31556aacf8aeb6071b00d469 (Russell Currey) and 253fd51e2f533552ae35a0c661705da6c4842c1b (Alistair Popple)

Re: [PATCH v4 05/16] of: changeset: Add of_changeset_node_move method

Hi Rob, On Thursday, 22 February 2018 01:20:36 EET Rob Herring wrote: > On Tue, Feb 20, 2018 at 5:10 PM, Laurent Pinchart wrote: > > From: Pantelis Antoniou > > > > Adds a changeset helper for moving a subtree to a different place > > in the running tree. This is

Re: [PATCH v4 06/16] of: unittest: changeset helpers

Hi Rob, On Thursday, 22 February 2018 01:10:25 EET Rob Herring wrote: > On Tue, Feb 20, 2018 at 5:10 PM, Laurent Pinchart wrote: > > From: Pantelis Antoniou > > > > Add a unitest specific for the new changeset helpers. > > > > Signed-off-by: Pantelis Antoniou

Re: [PATCH v4 08/16] drm: rcar-du: Fix legacy DT to create LVDS encoder nodes

On Tue, Feb 20, 2018 at 5:10 PM, Laurent Pinchart wrote: > The internal LVDS encoders now have their own DT bindings. Before > switching the driver infrastructure to those new bindings, implement > backward-compatibility through live DT patching. > >

Re: [Mesa-dev] Allocator Nouveau driver, Mesa EXT_external_objects, and DRM metadata import interfaces

On Wed 21 Feb 2018, Daniel Vetter wrote: > On Tue, Feb 20, 2018 at 10:14:47PM -0800, Chad Versace wrote: > > On Thu 21 Dec 2017, Daniel Vetter wrote: > > > On Thu, Dec 21, 2017 at 12:22 AM, Kristian Kristensen > > > wrote: > > >> On Wed, Dec 20, 2017 at 12:41 PM, Miguel

Re: [PATCH v5 1/5] drm: xlnx: Xilinx DRM KMS module

Hi Hyun, On Tuesday, 20 February 2018 19:11:42 EET hyun.k...@xilinx.com wrote: > On Monday, February 19, 2018 1:43 AM Daniel Vetter wrote: > > On Tue, Feb 06, 2018 at 05:36:36PM -0800, Hyun Kwon wrote: > >> Xilinx has various platforms for display, where users can create > >> using multiple IPs

Re: [PATCH v4 05/16] of: changeset: Add of_changeset_node_move method

On Tue, Feb 20, 2018 at 5:10 PM, Laurent Pinchart wrote: > From: Pantelis Antoniou > > Adds a changeset helper for moving a subtree to a different place > in the running tree. This is useful in advances cases of dynamic >

Re: [PATCH v4 03/16] of: dynamic: Add __of_node_dupv()

On Tue, Feb 20, 2018 at 5:10 PM, Laurent Pinchart wrote: > From: Pantelis Antoniou > > Add an __of_node_dupv() private method and make __of_node_dup() use it. > This is required for the subsequent changeset accessors

Re: [PATCH v5 1/5] drm: xlnx: Xilinx DRM KMS module

Hi Hyun, Thank you for the patch. On Wednesday, 7 February 2018 03:36:36 EET Hyun Kwon wrote: > Xilinx has various platforms for display, where users can create > using multiple IPs in the programmable FPGA fabric, or where > some hardened piepline is available on the chip. Furthermore,

Re: [PATCH v4 04/16] of: changesets: Introduce changeset helper methods

On Tue, Feb 20, 2018 at 5:10 PM, Laurent Pinchart wrote: > From: Pantelis Antoniou > > Changesets are very powerful, but the lack of a helper API > makes using them cumbersome. Introduce a simple copy based > API that

Re: [PATCH v4 06/16] of: unittest: changeset helpers

On Tue, Feb 20, 2018 at 5:10 PM, Laurent Pinchart wrote: > From: Pantelis Antoniou > > Add a unitest specific for the new changeset helpers. > > Signed-off-by: Pantelis Antoniou >

[PATCH 13/14] drm/msm: Support per-instance address spaces

Create a per-instance address spaces when a new DRM file instance is opened assuming the target supports it and the underlying infrastructure exists. If the operation is unsupported fall back quietly to use the global pagetable. Signed-off-by: Jordan Crouse ---

[PATCH 10/14] drm/msm: Add msm_mmu features

Add a few simple support functions to support a bitmask of features that a specific MMU implementation supports. The first feature will be per-instance pagetables coming in the following patch. Signed-off-by: Jordan Crouse --- drivers/gpu/drm/msm/msm_mmu.h | 13

[PATCH 14/14] drm/msm/a5xx: Support per-instance pagetables

Add support for per-instance pagetables for 5XX targets. Create a support buffer for preemption to hold the SMMU pagetable information for a preempted ring, enable TTBR1 to support split pagetables and add the necessary PM4 commands to trigger a pagetable switch at the beginning of a user command.

[PATCH 12/14] drm/msm: Add support for per-instance address spaces

Add a function to allocate a new pasid from a existing MMU domain and create a per-instance address space. Signed-off-by: Jordan Crouse --- drivers/gpu/drm/msm/msm_drv.h | 3 +++ drivers/gpu/drm/msm/msm_gem_vma.c | 36 +++- 2 files

[PATCH 11/14] drm/msm: Add support for iommu-sva PASIDs

The IOMMU core can support creating multiple pagetables for a specific domai and making them available to a client driver that has the means to manage the pagetable itself. PASIDs are unique indexes to a software created pagetable with the same format and characteristics as the parent IOMMU

[PATCH 09/14] drm/msm/gpu: Support using TTBR1 for kernel buffer objects

arm-smmu based targets can support split pagetables (TTBR0/TTBR1). This is most useful for implementing per-instance pagetables so that the "user" pagetable can be swapped out while the "kernel" or "global" pagetable remains entact. if the target specifies a global virtual memory range then try

[PATCH 08/14] drm/msm: Pass the MMU domain index in struct msm_file_private

Pass the index of the MMU domain in struct msm_file_private instead of assuming gpu->id throughout the submit path. This clears the way to change ctx->aspace to a per-instance pagetable. Signed-off-by: Jordan Crouse --- drivers/gpu/drm/msm/msm_drv.c| 16

[PATCH 04/14] iommu: sva: Add support for pasid allocation

Some older SMMU implementations that do not have a fully featured PASID model have alternate workarounds for using multiple pagetables. For example, MSM GPUs have logic to automatically switch the user pagetable from hardware by writing the context bank directly. Instead of binding and sharing

[PATCH 07/14] drm/msm: Enable 64 bit mode by default

A5XX GPUs can be run in either 32 or 64 bit mode. The GPU registers and the microcode use 64 bit virtual addressing in either case but the upper 32 bits are ignored if the GPU is in 32 bit mode. There is no performance disadvantage to remaining in 64 bit mode even if we are only generating 32 bit

[PATCH 06/14] iommu: arm-smmu: Add side-band function to specific pasid callbacks

Just allowing a client driver to create and manage a a software pasid isn't interesting if the client driver doesn't have enough information about the pagetable to be able to use it. Add a side band function for arm-smmu that lets the client device register pasid operations to pass the relevant

[PATCH 05/14] iommu: arm-smmu: Add pasid implementation

Add support for allocating and populating pagetables indexed by pasid. Each new pasid is allocated a pagetable with the same parameters and format as the parent domain. Signed-off-by: Jordan Crouse --- drivers/iommu/arm-smmu.c | 148

[PATCH 03/14] iommu: Create a base struct for io_mm

In order to support both shared mm sva pagetables as well as io-pgtable backed tables add a base structure to io_mm so that the two styles can share the same idr. Signed-off-by: Jordan Crouse --- drivers/iommu/arm-smmu-v3.c | 8 drivers/iommu/iommu-sva.c | 50

[RFC 00/14] Per-instance pagetables for MSM GPUs

This is a request for comment for support in the iommu, arm-smmu and MSM GPU driver to support per (GPU) instance pagetables. The general idea behind per-instance pagetables is that each GPU client can have its own pagetable and virtual memory space which prevents malicious or accidental

[PATCH 02/14] iommu/arm-smmu: Add support for TTBR1

Allow a SMMU device to opt into allocating a TTBR1 pagetable. The size of the TTBR1 region will be the same as the TTBR0 size with the sign extension bit set on the highest bit in the region unless the upstream size is 49 bits and then the sign-extension bit will be set on the 49th bit. The

[PATCH 01/14] iommu: Add DOMAIN_ATTR_ENABLE_TTBR1

Add a new domain attribute to enable the TTBR1 pagetable for drivers and devices that support it. This will enabled using a TTBR1 (otherwise known as a "global" or "system" pagetable for devices that support a split pagetable scheme for switching pagetables quickly and safely. Signed-off-by:

Re: [PATCH] drm/nouveau: prefer XBGR2101010 for addfb ioctl

On Thu, Feb 22, 2018 at 3:20 AM, Ilia Mirkin wrote: > On Mon, Feb 19, 2018 at 4:33 AM, Daniel Vetter wrote: >> On Mon, Feb 19, 2018 at 10:21:54AM +0100, Daniel Vetter wrote: >>> On Mon, Feb 05, 2018 at 09:10:12AM -0500, Ilia Mirkin wrote: >>> > On Mon, Feb

Re: [PATCH v2] drm/panel: Fix ARM Versatile panel clocks

Linus Walleij writes: > These clocks are in kHz not in Hz, oops. Fix it so my > new bandwidth calculations patch starts working with these > panels. > > Cc: Eric Anholt > Signed-off-by: Linus Walleij > --- > ChangeLog v1->v2:

Re: [PATCH 4/4] drm/pl111: Do not use deprecated drm_driver.{enable|disable)_vblank

Oleksandr Andrushchenko writes: > From: Oleksandr Andrushchenko > > Do not use deprecated drm_driver.{enable|disable)_vblank callbacks, > but use drm_simple_kms_helpe's pipe callbacks instead. > > Signed-off-by: Oleksandr Andrushchenko

[Bug 105179] DiRT Rally: wrong frames appear during camera transition

https://bugs.freedesktop.org/show_bug.cgi?id=105179 Gregor Münch changed: What|Removed |Added CC|

[PATCHv2 1/2] selftests: ion: Remove some prints

There's no need to print messages each time we alloc and free. Remove them. Signed-off-by: Laura Abbott --- v2: No changes --- tools/testing/selftests/android/ion/ionutils.c | 6 -- 1 file changed, 6 deletions(-) diff --git

[PATCHv2 0/2] Ion unit test with VGEM

Hi, This is v2 of the series to add a unit test to Ion with VGEM. From v1: Ion hasn't had much in the way of unit tests and fixing that is something that needs to happen before it can move out of staging. The difficult part of testing parts of Ion is that it relies on having a kernel driver to

[PATCHv2 2/2] selftests: ion: Add simple test with the vgem driver

Ion is designed to be a framework used by other clients who perform operations on the buffer. Use the DRM vgem client as a simple consumer. In conjunction with the dma-buf sync ioctls, this tests the full attach/map path for the system heap. Reviewed-by: Daniel Vetter

[Bug 105177] amdgpu wrong colors with rx460 connected via hdmi

https://bugs.freedesktop.org/show_bug.cgi?id=105177 --- Comment #12 from Harry Wentland --- There's a mismatch in colorspace we program and tell the HDMI receiver because we program the infoframe too early in our sequence. I'll send a patch tomorrow. -- You are

Re: [PATCH libdrm 1/2] intel: align reuse buffer's size on page size instead

Quoting James Xiong (2018-02-20 17:48:03) > From: "Xiong, James" > > With gem_reuse enabled, when a buffer size is different than > the sizes of buckets, it is aligned to the next bucket's size, > which means about 25% more memory than the requested is allocated > in the

[Bug 103277] [bisected] Systems hangs on resume from S3 sleep due to "Match actual state during S3 resume" commit

https://bugs.freedesktop.org/show_bug.cgi?id=103277 --- Comment #18 from dwagner --- (In reply to Alex Deucher from comment #17) > amd-staging-drm-next is still based on 4.15-rc4 which still has the > regression mentioned in comment 14. Can you try 4.15 final or my >

[Bug 105177] amdgpu wrong colors with rx460 connected via hdmi

https://bugs.freedesktop.org/show_bug.cgi?id=105177 --- Comment #11 from Reimar Imhof --- btw, all tests were done with amdgpu.dc=1, because suse configured the kernel that way. -- You are receiving this mail because: You are the assignee for the

[Bug 105177] amdgpu wrong colors with rx460 connected via hdmi

https://bugs.freedesktop.org/show_bug.cgi?id=105177 --- Comment #10 from Reimar Imhof --- Created attachment 137514 --> https://bugs.freedesktop.org/attachment.cgi?id=137514=edit x.org.log (dvi) -- You are receiving this mail because: You are the assignee for the

[Bug 105177] amdgpu wrong colors with rx460 connected via hdmi

https://bugs.freedesktop.org/show_bug.cgi?id=105177 --- Comment #9 from Reimar Imhof --- Created attachment 137513 --> https://bugs.freedesktop.org/attachment.cgi?id=137513=edit x.org.log (hdmi) -- You are receiving this mail because: You are the assignee for the

[Bug 105177] amdgpu wrong colors with rx460 connected via hdmi

https://bugs.freedesktop.org/show_bug.cgi?id=105177 --- Comment #8 from Reimar Imhof --- Created attachment 137512 --> https://bugs.freedesktop.org/attachment.cgi?id=137512=edit desktop (dvi) - console is black, like expected -- You are receiving this mail because:

[Bug 105177] amdgpu wrong colors with rx460 connected via hdmi

https://bugs.freedesktop.org/show_bug.cgi?id=105177 --- Comment #7 from Reimar Imhof --- Created attachment 137511 --> https://bugs.freedesktop.org/attachment.cgi?id=137511=edit desktop (hdmi) - console should be black but is violet -- You are receiving this mail

[Bug 105177] amdgpu wrong colors with rx460 connected via hdmi

https://bugs.freedesktop.org/show_bug.cgi?id=105177 --- Comment #6 from Reimar Imhof --- Created attachment 137510 --> https://bugs.freedesktop.org/attachment.cgi?id=137510=edit framebuffer console via hdmi frame buffer console should be black but is violet (hdmi)

Re: [PATCH 1/4] locking/ww_mutex: add ww_mutex_is_owned_by function v3

On 20 February 2018 at 13:12, Peter Zijlstra wrote: > On Tue, Feb 20, 2018 at 01:58:26PM +0100, Christian König wrote: >> amdgpu needs to verify if userspace sends us valid addresses and the simplest >> way of doing this is to check if the buffer object is locked with the

Re: [Mesa-dev] Allocator Nouveau driver, Mesa EXT_external_objects, and DRM metadata import interfaces

On Tue, Feb 20, 2018 at 10:14:47PM -0800, Chad Versace wrote: > On Thu 21 Dec 2017, Daniel Vetter wrote: > > On Thu, Dec 21, 2017 at 12:22 AM, Kristian Kristensen > > wrote: > >> On Wed, Dec 20, 2017 at 12:41 PM, Miguel Angel Vico > >> wrote: > >>>

Re: [PATCH v3 1/8] drm/blend: Add a generic alpha property

Hi Daniel, On Monday, 19 February 2018 23:58:40 EET Daniel Vetter wrote: > On Mon, Feb 19, 2018 at 9:19 PM, Laurent Pinchart wrote: > > On Friday, 16 February 2018 20:20:41 EET Ville Syrjälä wrote: > >> On Fri, Feb 16, 2018 at 06:39:29PM +0100, Maxime Ripard wrote: > >> Some drivers duplicate the

[PULL] drm-misc-next

Hi Dave, A delicious collection of fixes and features for you this week. The backlight helpers have been picked up by Lee Jones in the backlight tree, so hopefully no fireworks there. Everything else is business as usual. drm-misc-next-2018-02-21: drm-misc-next for 4.17: Cross-subsystem

Re: [Intel-gfx] [PATCH] drm/atomic: Call ww_acquire_done after drm_modeset_lock_all

On Wed, Feb 21, 2018 at 04:23:31PM +0100, Maarten Lankhorst wrote: > After we acquired all generic modeset locks in drm_modeset_lock_all, it's > unsafe acquire any other so just mark acquisition as done. > > Atomic drivers shouldn't use drm_modeset_lock_all. > > Signed-off-by: Maarten Lankhorst

Re: [PATCH RFC] drm/bridge: panel: Add device_link between panel and master drm device

On Wed, Feb 21, 2018 at 10:51:50AM +0200, Jyri Sarha wrote: > On 21/02/18 01:47, Daniel Vetter wrote: > > On Wed, Feb 21, 2018 at 12:21:50AM +0200, Jyri Sarha wrote: > >> Currently the master drm driver is not protected against the attached > >> panel driver from becoming unavailable. Adding a

Re: [PATCH] drm/doc: Fix documentation for _vblank_restore().

On Tue, Feb 20, 2018 at 11:39:08PM -0800, Dhinakaran Pandiyan wrote: > No code changes, fixes doc build warnings and polish some doc text. > > Reported-by: Daniel Vetter > Cc: Rodrigo Vivi > Cc: Daniel Vetter >

Re: [PATCH v2 3/8] drm/bridge: dw-hdmi: allow overriding of phy-type reading

Hi Heiko, On Wednesday, 21 February 2018 20:55:12 EET Heiko Stuebner wrote: > Am Montag, 19. Februar 2018, 20:06:40 CET schrieb Laurent Pinchart: > > On Monday, 19 February 2018 20:46:46 EET Heiko Stuebner wrote: > > > Am Montag, 19. Februar 2018, 17:59:02 CET schrieb Laurent Pinchart: > > > > On

Re: [RFC PATCH v2 0/9] hyper_dmabuf: Hyper_DMABUF driver

On Mon, Feb 19, 2018 at 06:01:29PM +0100, Daniel Vetter wrote: > On Tue, Feb 13, 2018 at 05:49:59PM -0800, Dongwon Kim wrote: > > This patch series contains the implementation of a new device driver, > > hyper_DMABUF driver, which provides a way to expand the boundary of > > Linux DMA-BUF sharing

Re: [PATCH v4 01/16] dt-bindings: display: renesas: Add R-Car LVDS encoder DT bindings

Hi Sergei, On Wednesday, 21 February 2018 10:35:13 EET Sergei Shtylyov wrote: > On 2/21/2018 2:10 AM, Laurent Pinchart wrote: > > The Renesas R-Car Gen2 and Gen3 SoCs have internal LVDS encoders. Add > > corresponding device tree bindings. > > > > Signed-off-by: Laurent Pinchart > >

Re: [Intel-gfx] [PATCH] drm/atomic: Call ww_acquire_done after drm_modeset_lock_all

On 2018-02-21 01:36 PM, Daniel Vetter wrote: > On Wed, Feb 21, 2018 at 04:23:31PM +0100, Maarten Lankhorst wrote: >> After we acquired all generic modeset locks in drm_modeset_lock_all, it's >> unsafe acquire any other so just mark acquisition as done. >> >> Atomic drivers shouldn't use

Re: [PATCH v2 3/8] drm/bridge: dw-hdmi: allow overriding of phy-type reading

Hi Laurent, Am Montag, 19. Februar 2018, 20:06:40 CET schrieb Laurent Pinchart: > On Monday, 19 February 2018 20:46:46 EET Heiko Stuebner wrote: > > Am Montag, 19. Februar 2018, 17:59:02 CET schrieb Laurent Pinchart: > > > On Friday, 16 February 2018 22:41:53 EET Heiko Stuebner wrote: > > >> In

[Bug 105188] Monitors don't always wake up after sleep

https://bugs.freedesktop.org/show_bug.cgi?id=105188 --- Comment #3 from Michał Bartoszkiewicz --- The monitors are set to DP input, auto-scan is disabled. -- You are receiving this mail because: You are the assignee for the

Re: [PATCH 1/4] drm/atomic: integrate modeset lock with private objects

On Wed, Feb 21, 2018 at 11:36 AM, Ville Syrjälä wrote: > On Wed, Feb 21, 2018 at 11:17:21AM -0500, Rob Clark wrote: >> On Wed, Feb 21, 2018 at 10:54 AM, Ville Syrjälä >> wrote: >> > On Wed, Feb 21, 2018 at 10:36:06AM -0500, Rob Clark

Re: [PATCH] drm/nouveau: prefer XBGR2101010 for addfb ioctl

On Mon, Feb 19, 2018 at 4:33 AM, Daniel Vetter wrote: > On Mon, Feb 19, 2018 at 10:21:54AM +0100, Daniel Vetter wrote: >> On Mon, Feb 05, 2018 at 09:10:12AM -0500, Ilia Mirkin wrote: >> > On Mon, Feb 5, 2018 at 8:58 AM, Ville Syrjälä >> > wrote: >>

Re: [PATCH] radeon: hide pointless #warning when compile testing

On 2018-02-16 04:26 PM, Arnd Bergmann wrote: > In randconfig testing, we sometimes get this warning: > > drivers/gpu/drm/radeon/radeon_object.c: In function 'radeon_bo_create': > drivers/gpu/drm/radeon/radeon_object.c:242:2: error: #warning Please enable > CONFIG_MTRR and CONFIG_X86_PAT for

Re: [PATCH 1/4] drm/atomic: integrate modeset lock with private objects

On Wed, Feb 21, 2018 at 11:17:21AM -0500, Rob Clark wrote: > On Wed, Feb 21, 2018 at 10:54 AM, Ville Syrjälä > wrote: > > On Wed, Feb 21, 2018 at 10:36:06AM -0500, Rob Clark wrote: > >> On Wed, Feb 21, 2018 at 10:27 AM, Ville Syrjälä > >>

[Bug 105188] Monitors don't always wake up after sleep

https://bugs.freedesktop.org/show_bug.cgi?id=105188 --- Comment #2 from Harry Wentland --- Are the monitors set to DP input or to auto-scan the inputs? We've seen similar issues with some monitors that auto-scan inputs and disappear on us when we try to enable them. --

Re: [PATCH 1/4] drm/atomic: integrate modeset lock with private objects

On Wed, Feb 21, 2018 at 10:54 AM, Ville Syrjälä wrote: > On Wed, Feb 21, 2018 at 10:36:06AM -0500, Rob Clark wrote: >> On Wed, Feb 21, 2018 at 10:27 AM, Ville Syrjälä >> wrote: >> > On Wed, Feb 21, 2018 at 10:20:03AM -0500, Rob Clark

Re: [PATCH 1/4] drm/atomic: integrate modeset lock with private objects

On Wed, Feb 21, 2018 at 10:36:06AM -0500, Rob Clark wrote: > On Wed, Feb 21, 2018 at 10:27 AM, Ville Syrjälä > wrote: > > On Wed, Feb 21, 2018 at 10:20:03AM -0500, Rob Clark wrote: > >> On Wed, Feb 21, 2018 at 10:07 AM, Ville Syrjälä > >>

Re: [PATCH v4 5/6] extcon: add possibility to get extcon device by OF node

On 21.02.2018 15:27, Andy Shevchenko wrote: > On Wed, Feb 21, 2018 at 10:55 AM, Andrzej Hajda wrote: >> Since extcon property is not allowed in DT, extcon subsystem requires >> another way to get extcon device. Lets try the simplest approach - get >> edev by of_node. >> +/*

Re: [PATCH v4 04/16] of: changesets: Introduce changeset helper methods

Hi Rob, On Wed, Feb 21, 2018 at 4:23 PM, Rob Herring wrote: > On Wed, Feb 21, 2018 at 4:21 AM, Geert Uytterhoeven > wrote: >> You missed one fix I have in my topic/overlays branch >>

Re: [PATCH 1/4] drm/atomic: integrate modeset lock with private objects

On Wed, Feb 21, 2018 at 10:27 AM, Ville Syrjälä wrote: > On Wed, Feb 21, 2018 at 10:20:03AM -0500, Rob Clark wrote: >> On Wed, Feb 21, 2018 at 10:07 AM, Ville Syrjälä >> wrote: >> > On Wed, Feb 21, 2018 at 09:54:49AM -0500, Rob Clark

Re: [PATCH v2 08/10] drm/panel: Add Huarui LHR050H41 panel driver

Hi, On Wed, Feb 21, 2018 at 5:20 PM, Maxime Ripard wrote: > From: Maxime Ripard > > The LHR050H41 panel is the panel shipped with the BananaPi M2-Magic. Add a > driver for it. So I distinctly remember questioning the vendor name the

Re: [PATCH 1/4] drm/atomic: integrate modeset lock with private objects

On Wed, Feb 21, 2018 at 10:20:03AM -0500, Rob Clark wrote: > On Wed, Feb 21, 2018 at 10:07 AM, Ville Syrjälä > wrote: > > On Wed, Feb 21, 2018 at 09:54:49AM -0500, Rob Clark wrote: > >> On Wed, Feb 21, 2018 at 9:49 AM, Ville Syrjälä > >>

  1   2   3   >