Re: [PATCH 2/2] drm: adv7511: Add support for i2c_new_secondary_device

On 22/01/18 13:00, Lars-Peter Clausen wrote: > On 01/22/2018 01:50 PM, Kieran Bingham wrote: >> The ADV7511 has four 256-byte maps that can be accessed via the main I²C >> ports. Each map has it own I²C address and acts as a standard slave >> device on the I²C bus. >> >> Allow a device tree node

[Bug 104745] HEVC VDPAU decoding broken on RX 460 with UVD Firmware v1.130

https://bugs.freedesktop.org/show_bug.cgi?id=104745 saunders...@wright.edu changed: What|Removed |Added Status|NEW |RESOLVED

[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 #15 from Alex Deucher --- It was supposedly fixed in -rc6 so my drm-next branches don't have the fix yet. -- You are receiving this mail because: You are the assignee for 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 #14 from Alex Deucher --- The regression was caused by: commit ca37e57bbe0cf1455ea3e84eb89ed04a132d59e1 (refs/bisect/bad) Author: Andy Lutomirski Date: Wed Nov 22 20:39:16 2017 -0800

[Bug 104745] HEVC VDPAU decoding broken on RX 460 with UVD Firmware v1.130

https://bugs.freedesktop.org/show_bug.cgi?id=104745 --- Comment #3 from Alex Deucher --- This newer firmware exposes a bug in mesa which was fixed in December. You need a newer version of mesa that contains this patch:

Re: [RFC] Per file OOM badness

On 01/22/2018 06:23 PM, Andrew Morton wrote: On Thu, 18 Jan 2018 11:47:48 -0500 Andrey Grodzovsky wrote: Hi, this series is a revised version of an RFC sent by Christian König a few years ago. The original RFC can be found at

[Bug 103838] Random segfaults in applications from radeonsi_dri.so

https://bugs.freedesktop.org/show_bug.cgi?id=103838 Alex Ford changed: What|Removed |Added Resolution|--- |FIXED

[Bug 104744] [r600] Total War: Warhammer black textures and flickering.

https://bugs.freedesktop.org/show_bug.cgi?id=104744 --- Comment #1 from Roland Scheidegger --- There is probably a reason why the game requirements state rx480 as a minimum... Even on macs its says amd cards newer than 2014, which excludes everything pre-gcn. I wouldn't be

Re: [PATCH libdrm] modetest: Fix to check return value of asprintf()

Hello, On 2018년 01월 22일 21:09, Eric Engestrom wrote: > On Wednesday, 2018-01-10 11:16:41 +0900, Seung-Woo Kim wrote: >> There is warning about ignoring return value of 'asprintf'. Fix to >> check return value of asprintf(). >> >> Signed-off-by: Seung-Woo Kim > >

[Bug 104745] HEVC VDPAU decoding broken on RX 460 with UVD Firmware v1.130

https://bugs.freedesktop.org/show_bug.cgi?id=104745 saunders...@wright.edu changed: What|Removed |Added OS|All |Linux (All)

[Bug 104745] HEVC VDPAU decoding broken on RX 460 with UVD Firmware v1.130

https://bugs.freedesktop.org/show_bug.cgi?id=104745 --- Comment #1 from saunders...@wright.edu --- Created attachment 136912 --> https://bugs.freedesktop.org/attachment.cgi?id=136912=edit Software decoded version of the same timestamp in the file. -- You are receiving this mail because: You

[Bug 104745] HEVC VDPAU decoding broken on RX 460 with UVD Firmware v1.130

https://bugs.freedesktop.org/show_bug.cgi?id=104745 Bug ID: 104745 Summary: HEVC VDPAU decoding broken on RX 460 with UVD Firmware v1.130 Product: DRI Version: XOrg git Hardware: Other OS: All

[Bug 104744] [r600] Total War: Warhammer black textures and flickering.

https://bugs.freedesktop.org/show_bug.cgi?id=104744 Bug ID: 104744 Summary: [r600] Total War: Warhammer black textures and flickering. Product: Mesa Version: git Hardware: Other OS: All Status:

[Bug 99316] Radeon crash when laptop on AC power

https://bugs.freedesktop.org/show_bug.cgi?id=99316 --- Comment #14 from Samuel Anderson --- (In reply to l.hartmail from comment #13) > Hi! > As an owner of the same GPU, I can confirm this bug still appears under > linux 4.15.0-rc7. > The card card crashes or hangs when

Re: [PATCH] drm/bridge/synopsys: dsi: Adopt SPDX identifiers

Hi Philippe, Thank you for the patch. On Monday, 22 January 2018 12:26:08 EET Philippe Cornu wrote: > Add SPDX identifiers to the Synopsys DesignWare MIPI DSI > host controller driver. > > Signed-off-by: Philippe Cornu > --- >

Re: [RFC] Per file OOM badness

On Thu, 18 Jan 2018 11:47:48 -0500 Andrey Grodzovsky wrote: > Hi, this series is a revised version of an RFC sent by Christian König > a few years ago. The original RFC can be found at > https://lists.freedesktop.org/archives/dri-devel/2015-September/089778.html > >

[Bug 198551] New: amdgpu error on shutdown or gpu intense game

https://bugzilla.kernel.org/show_bug.cgi?id=198551 Bug ID: 198551 Summary: amdgpu error on shutdown or gpu intense game Product: Drivers Version: 2.5 Kernel Version: 4.14.14-1 Hardware: All OS: Linux Tree:

[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 #13 from dwagner --- (In reply to Harry Wentland from comment #12) > Can you try blacklisting amdgpu and try S3 again? (Assuming you mean adding "module_blacklist=amdgpu" on the kernel command line:) Sure,

[PATCH 1/2] drm/dp: Add HBR3 support in existing DRM DP helpers

Existing helpers add support upto HBR2. This patch adds support for HBR3 rate (8.1 Gbps) introduced as part of DP 1.4 specification. Cc: Rodrigo Vivi Cc: Jani Nikula Cc: dri-devel@lists.freedesktop.org Signed-off-by: Manasi Navare

[PATCH 2/2] drm/dp: Add definitions for TPS4 bits and macros to check the support

DP 1.4 spec adds a TPS4 training pattern sequence required for HBR3. This patch adds the corresponding bit definitions in MAX_DOWNSPREAD register and TRAINING_PATTERN_SET and inline functions to check if this bit is set and for selecting a proper TRAINING_PATTERN_MASK that changed to 0x7 on DP

[Bug 104655] AMD R9 Fury + BenQ XL2546: Setting 240 Hz results in screen distortion

https://bugs.freedesktop.org/show_bug.cgi?id=104655 omin...@autistici.org changed: What|Removed |Added Resolution|--- |FIXED Status|NEW

Re: [PATCH v2 05/19] drm/vc4: Use the alpha format field in drm_format_info

Maxime Ripard writes: > Now that the drm_format_info has a alpha field to tell if a format embeds > an alpha component in it, let's use it. > > Cc: Eric Anholt > Reviewed-by: Daniel Vetter > Signed-off-by: Maxime

[Bug 104737] amdgpu module does not bind to 1002:6660 R5 M330

https://bugs.freedesktop.org/show_bug.cgi?id=104737 Tj <0.freedesk...@iam.tj> changed: What|Removed |Added Resolution|NOTABUG |FIXED --- Comment #3 from

Re: [PATCH] dma-buf: fix reservation_object_wait_timeout_rcu once more v2

Quoting Christian König (2018-01-22 20:00:03) > We need to set shared_count even if we already have a fence to wait for. > > v2: init i to -1 as well > > Signed-off-by: Christian König > Cc: sta...@vger.kernel.org > Tested-by: Lyude Paul >

[Bug 104737] amdgpu module does not bind to 1002:6660 R5 M330

https://bugs.freedesktop.org/show_bug.cgi?id=104737 Bas Nieuwenhuizen changed: What|Removed |Added Resolution|--- |NOTABUG

Re: [PATCH] dma-buf: fix reservation_object_wait_timeout_rcu once more

Am 22.01.2018 um 20:47 schrieb Chris Wilson: Quoting Christian König (2018-01-22 19:32:39) We need to set shared_count even if we already have a fence to wait for. You mean for the if (ret > 0 && wait_all && (i + 1 < shared_count) clause. In the case of having the exclusive fence, i=0 (erm,

[PATCH] dma-buf: fix reservation_object_wait_timeout_rcu once more v2

We need to set shared_count even if we already have a fence to wait for. v2: init i to -1 as well Signed-off-by: Christian König Cc: sta...@vger.kernel.org Tested-by: Lyude Paul Reviewed-by: Lyude Paul ---

Re: [PATCH] dma-buf: fix reservation_object_wait_timeout_rcu once more

Quoting Christian König (2018-01-22 19:32:39) > We need to set shared_count even if we already have a fence to wait for. You mean for the if (ret > 0 && wait_all && (i + 1 < shared_count) clause. In the case of having the exclusive fence, i=0 (erm, once), but shared_count may still be just 1

Re: [PATCH] dma-buf: fix reservation_object_wait_timeout_rcu once more

Am 22.01.2018 um 20:42 schrieb Lyude Paul: Could you please make sure to add Cc: sta...@vger.kernel.org for this? Sure, just pushed into our upstream branch. Alex can you pick that up for your next drm-fixes pull request? Sorry for the noise, Christian. This is causing crashing of wayland

Re: [PATCH] dma-buf: fix reservation_object_wait_timeout_rcu once more

Could you please make sure to add Cc: sta...@vger.kernel.org for this? This is causing crashing of wayland sessions on Fedora so we should definitely get this into stable. Other then that: Tested-by: Lyude Paul Reviewed-by: Lyude Paul On Mon, 2018-01-22 at

[PATCH] dma-buf: fix reservation_object_wait_timeout_rcu once more

We need to set shared_count even if we already have a fence to wait for. Signed-off-by: Christian König --- drivers/dma-buf/reservation.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/drivers/dma-buf/reservation.c

[Bug 104738] Radeon HD 6970M/6990M crash on iMac on boot - only nomodeset helps

https://bugs.freedesktop.org/show_bug.cgi?id=104738 Bug ID: 104738 Summary: Radeon HD 6970M/6990M crash on iMac on boot - only nomodeset helps Product: DRI Version: unspecified Hardware: x86-64 (AMD64) OS:

[Bug 104737] amdgpu module does not bind to 1002:6660 R5 M330

https://bugs.freedesktop.org/show_bug.cgi?id=104737 --- Comment #1 from Tj <0.freedesk...@iam.tj> --- I helped this user for several hours in #ubuntu IRc support diagnosing this issue. It's: DMI: HP HP Notebook/81EC, BIOS F.23 12/01/2016 with integrated Intel and AMD GPUs. We fetched the

[Bug 104731] UVD lockup on MPEG2 missing Field

https://bugs.freedesktop.org/show_bug.cgi?id=104731 --- Comment #4 from Christian König --- (In reply to Francois Cartegnie from comment #3) > What do you mean by stopping ? > Ring N lockup kernel messages ? Yes, exactly. -- You are receiving this mail

[Bug 104731] UVD lockup on MPEG2 missing Field

https://bugs.freedesktop.org/show_bug.cgi?id=104731 --- Comment #3 from Francois Cartegnie --- What do you mean by stopping ? Ring N lockup kernel messages ? -- You are receiving this mail because: You are the assignee for the

[Bug 104737] amdgpu module does not bind to 1002:6660 R5 M330

https://bugs.freedesktop.org/show_bug.cgi?id=104737 Gopal Sharma changed: What|Removed |Added QA Contact||s10go...@gmail.com

[Bug 104737] amdgpu module does not bind to 1002:6660 R5 M330

https://bugs.freedesktop.org/show_bug.cgi?id=104737 Gopal Sharma changed: What|Removed |Added Priority|medium |highest

[Bug 104737] amdgpu module does not bind to 1002:6660 R5 M330

https://bugs.freedesktop.org/show_bug.cgi?id=104737 Bug ID: 104737 Summary: amdgpu module does not bind to 1002:6660 R5 M330 Product: DRI Version: unspecified Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW

[Bug 104736] Kernel panic with agd5's drm-next-4.17-wip & GFX8/Polaris10/Ellesmere/Rx-480-8GiB

https://bugs.freedesktop.org/show_bug.cgi?id=104736 --- Comment #1 from Robin Kauffman --- Oops, s/kennel/kernel/ -- You are receiving this mail because: You are the assignee for the bug.___ dri-devel mailing list

[Bug 104736] Kernel panic with agd5's drm-next-4.17-wip & GFX8/Polaris10/Ellesmere/Rx-480-8GiB

https://bugs.freedesktop.org/show_bug.cgi?id=104736 Bug ID: 104736 Summary: Kernel panic with agd5's drm-next-4.17-wip & GFX8/Polaris10/Ellesmere/Rx-480-8GiB Product: DRI Version: XOrg git Hardware: Other

[Bug 104731] UVD lockup on MPEG2 missing Field

https://bugs.freedesktop.org/show_bug.cgi?id=104731 Christian König changed: What|Removed |Added Status|NEW

[Bug 104731] UVD lockup on MPEG2 missing Field

https://bugs.freedesktop.org/show_bug.cgi?id=104731 --- Comment #1 from Andy Furniss --- FWIW UVD has never (AFAIK) been able to decode field coded mpeg2, as it seems to be quite rare in the wild it doesn't come up much. A long time ago I managed to lock older h/w with a

[PATCH 1/5] drm/msm/adreno: Make microcode loading target specific

Move microcode loading to be target specific. While this results in a bit more code duplication (especially between A3XX/A4XX) this gives us more flexibility for newer targets that don't need to keep an extra copy of the firmware data around in memory. Signed-off-by: Jordan Crouse

[PATCH 3/5] drm/msm/gpu: Set number of clocks to 0 if the list allocation fails

If we fail to allocate gpu->grp_clks reset the number of available clocks to zero to avoid referencing the missing array later. Signed-off-by: Jordan Crouse --- drivers/gpu/drm/msm/msm_gpu.c | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git

[PATCH 4/5] drm/msm: Pass the correct aperture end to drm_mm_init

drm_mm_init() takes the start and length of the intended virtual memory address region but the msm code is passing the end of the region instead. That would work out if the region started at 0 but it doesn't so the top of the region sneaks above the 32 bit boundary which won't work because the

[PATCH 5/5] drm/msm/adreno: Rename gpmufw to powerfw

The power management device on the a5xx cores is known as the GPMU (Graphics Power Management Unit). On a6xx cores the device was expanded and renamed as the GMU (Graphics Management Unit). Rename the 'gpmufw' name struct adreno_info as 'powerfw' to avoid confusion. Signed-off-by: Jordan Crouse

[PATCH 2/5] drm/msm/adreno: Use generic function to load firwmare to a buffer object

Move a5xx specific code to load firmware into a buffer object to the generic Adreno code. This will come in useful for future targets. Signed-off-by: Jordan Crouse --- drivers/gpu/drm/msm/adreno/a5xx_gpu.c | 32 ++--

[v2 PATCH 0/5] drm/msm/gpu: Code reorganization ahead of a6xx

In anticipation of forthcoming a6xx support here is a handful of changes to reorganize the generic code a bit to make it easier to plug in the new target. Also included are a few minor bug fixes for issues that popped up in the midst of the new code development. Resending because I messed up a

[PATCH 1/5] drm/msm/adreno: Make microcode loading target specific

Move microcode loading to be target specific. While this results in a bit more code duplication (especially between A3XX/A4XX) this gives us more flexibility for newer targets that don't need to keep an extra copy of the firmware data around in memory. Signed-off-by: Jordan Crouse

[PATCH 4/5] drm/msm: Pass the correct aperture end to drm_mm_init

drm_mm_init() takes the start and length of the intended virtual memory address region but the msm code is passing the end of the region instead. That would work out if the region started at 0 but it doesn't so the top of the region sneaks above the 32 bit boundary which won't work because the

[PATCH 2/5] drm/msm/adreno: Use generic function to load firwmare to a buffer object

Move a5xx specific code to load firmware into a buffer object to the generic Adreno code. This will come in useful for future targets. Signed-off-by: Jordan Crouse --- drivers/gpu/drm/msm/adreno/a5xx_gpu.c | 32 ++--

[PATCH 5/5] drm/msm/adreno: Rename gpmufw to powerfw

The power management device on the a5xx cores is known as the GPMU (Graphics Power Management Unit). On a6xx cores the device was expanded and renamed as the GMU (Graphics Management Unit). Rename the 'gpmufw' name struct adreno_info as 'powerfw' to avoid confusion. Signed-off-by: Jordan Crouse

[PATCH 0/5] drm/msm/gpu: Code reorganization ahead of a6xx

In anticipation of forthcoming a6xx support here is a handful of changes to reorganize the generic code a bit to make it easier to plug in the new target. Also included are a few minor bug fixes for issues that popped up in the midst of the new code development. Jordan Crouse (5):

[PATCH 3/5] drm/msm/gpu: Set number of clocks to 0 if the list allocation fails

If we fail to allocate gpu->grp_clks reset the number of available clocks to zero to avoid referencing the missing array later. Signed-off-by: Jordan Crouse --- drivers/gpu/drm/msm/msm_gpu.c | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git

[PATCH] drm/i915: Restore HDCP DRM_INFO when with no downstream

The commit below returned earlier than before, but failed to move the info message when authenticating without downstream devices. This patch restores the message on authentication success. Fixes: 87eb3ec818fa ("drm/i915: II stage HDCP auth for repeater only") Cc: Ramalingam C

Re: [PATCH] drm/panel: panasonic-vvx10f034n00: More return value fixes

On Thu, Jan 18, 2018 at 10:48:52AM +, Philippe CORNU wrote: > Hi Sean, > > Reviewed-by: Philippe Cornu > > (do you mean you write patches during meetings :o ... I never did that > and I will not ;-) Haha, only the boring ones ;) Applied to -misc. Thanks for the

[PATCH] drm/sun4i: Fix build warnings in sunxi_engine.h

Fixes the following build warnings: In file included from ../drivers/gpu/drm/sun4i/sun8i_mixer.h:18:0, from ../drivers/gpu/drm/sun4i/sun8i_vi_scaler.h:13, from ../drivers/gpu/drm/sun4i/sun8i_vi_scaler.c:12: ../drivers/gpu/drm/sun4i/sunxi_engine.h:36:16: warning:

Re: [PATCH 1/3] drm/etnaviv: add generic compatible for the GPU subsystem node

On Fri, Jan 19, 2018 at 01:06:32PM +0100, Lucas Stach wrote: > With different SoCs gaining support for etnaviv it doesn't make much sense > to add specific compatibles for the generic GPU subsystem node, which is > only used to find all GPU core nodes. How many other SoC families? Is it really

[Bug 104730] VLC crashes on playback with "READ_ONLY without WC is disallowed"

https://bugs.freedesktop.org/show_bug.cgi?id=104730 --- Comment #1 from Christoph Haag --- This happens with vaapi and omx with assertions enabled. My patch https://lists.freedesktop.org/archives/mesa-dev/2018-January/182646.html works around that by setting the

[Bug 104731] UVD lockup on MPEG2 missing Field

https://bugs.freedesktop.org/show_bug.cgi?id=104731 Bug ID: 104731 Summary: UVD lockup on MPEG2 missing Field Product: DRI Version: XOrg git Hardware: Other OS: All Status: NEW Severity: normal

[PATCH] drm/stm: dsi: Add 1.31 version support

Add support for the stm dsi phy/wrapper version 1.31. Only lane capabilities need to be modified. Signed-off-by: Philippe Cornu --- drivers/gpu/drm/stm/dw_mipi_dsi-stm.c | 39 +++ 1 file changed, 30 insertions(+), 9 deletions(-) diff --git

[PATCH 08/10] drm/etnaviv: handle security states

GPUs with support for the security features need some additional setup to get the frontend started. Signed-off-by: Lucas Stach --- drivers/gpu/drm/etnaviv/etnaviv_gpu.c | 37 +-- 1 file changed, 35 insertions(+), 2 deletions(-) diff --git

[PATCH 07/10] drm/etnaviv: add security handling mode enum

With the introduction of GPU security we have 3 different modes of GPU operation: - GPU core doesn't have security features -> no handling required - the security related states are handled by the kernel driver - the security related states are handled by a TrustZone application Add a enum to

[PATCH 04/10] drm/etnaviv: update hardware headers from rnndb

Update the state HI and common header from rnndb commit 222fc7822e2d (rnndb: add more feature bits). Signed-off-by: Lucas Stach --- drivers/gpu/drm/etnaviv/common.xml.h | 281 ++--- drivers/gpu/drm/etnaviv/state_hi.xml.h | 149

[PATCH 10/10] drm/etnaviv: add PTA handling to MMUv2

The Page Table Array is a new first level structure above the MTLB availabale on GPUs with the security feature. Use the PTa to set up the MMU when the security related states are handled by the kernel driver. Signed-off-by: Lucas Stach ---

[PATCH 09/10] drm/etnaviv: add function to load the initial PTA state

On GPUs with the security feature the MTLB config is stored in the PTA. Add a function to trigger the initial PTA load through the FE. Signed-off-by: Lucas Stach --- drivers/gpu/drm/etnaviv/etnaviv_buffer.c | 18 ++ drivers/gpu/drm/etnaviv/etnaviv_drv.h

[PATCH 05/10] drm/etnaviv: add more minor features fields

Newer GPU cores added yet more feature bits. Make room for them and let userspace query them. Signed-off-by: Lucas Stach --- drivers/gpu/drm/etnaviv/etnaviv_gpu.c | 36 +++ drivers/gpu/drm/etnaviv/etnaviv_gpu.h | 16 ++--

[PATCH 01/10] drm/etnaviv: use correct format specifier for size_t

Signed-off-by: Lucas Stach --- drivers/gpu/drm/etnaviv/etnaviv_mmu.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/drivers/gpu/drm/etnaviv/etnaviv_mmu.c b/drivers/gpu/drm/etnaviv/etnaviv_mmu.c index d113fe06e6b5..49e049713a52 100644 ---

[PATCH 00/10] GC7000L aka i.MX8M support

Hi all, the following series adds the necessary bits to get the GC7000L, as found on the NXP i.MX8M, up and running. It's not enough to run the GL userspace bits yet, as we are still missing reloc support for the texture descriptors, but it gets the basic FE and MMU state setup into place. I've

[PATCH 02/10] drm/etnaviv: split out and optimize MMU fault dumping

Split out the fault dumping, as this will get more complex in the future. Also there is no need to read and dump the fault address from MMUs that didn't signal a fault. Signed-off-by: Lucas Stach --- drivers/gpu/drm/etnaviv/etnaviv_gpu.c | 31

[PATCH 03/10] drm/etnaviv: add support for slave interface clock

The slave interface clock is a clock input found on newer cores to gate the register interface. For now we simply ungate it when the GPU is in active state. Signed-off-by: Lucas Stach --- drivers/gpu/drm/etnaviv/etnaviv_gpu.c | 13 +

[PATCH 06/10] drm/etnaviv: add hardware database

New versions of the Vivante kernel driver don't trust the hardware feature bits anymore, but use an internal hardware database. This also includes more feature fields than are available in hardware. As we can't trust the hardware feature bits to be correct anymore, we need to replicate the HWDB

Re: [PATCH 2/3] dt-bindings: etnaviv: change clocks to be optional

Am Montag, den 22.01.2018, 10:28 -0600 schrieb Rob Herring: > On Fri, Jan 19, 2018 at 6:06 AM, Lucas Stach > wrote: > > While the clocks were documented as required, the driver always > > treated them > > as optional and there are existing Marvell Dove DTs, which would > >

Re: [PATCH 2/3] dt-bindings: etnaviv: change clocks to be optional

On Fri, Jan 19, 2018 at 6:06 AM, Lucas Stach wrote: > While the clocks were documented as required, the driver always treated them > as optional and there are existing Marvell Dove DTs, which would break if > changed to required. Accept reality and document the clocks as

Re: [PATCH RFC 6/9] drm: Add cgroup helper library

Hello, Matt. On Fri, Jan 19, 2018 at 05:51:38PM -0800, Matt Roper wrote: > Most DRM drivers will want to handle the CGROUP_SETPARAM ioctl by looking up a > driver-specific per-cgroup data structure (or allocating a new one) and > storing > the supplied parameter value into the data structure

[PATCH] gpu: ipu-cpmem: add 8-bit grayscale support to ipu_cpmem_set_image

Add the missing offset calculation for grayscale images. Since the IPU only supports capturing greyscale in raw passthrough mode, it is the same as 8-bit bayer formats. Signed-off-by: Philipp Zabel --- drivers/gpu/ipu-v3/ipu-cpmem.c | 1 + 1 file changed, 1 insertion(+)

Re: [PATCH RFC 8/9] drm/i915: Allow default context priority to be set via cgroup parameter

On Sat, Jan 20, 2018 at 10:40:19AM +, Chris Wilson wrote: > Quoting Chris Wilson (2018-01-20 09:36:10) > > Quoting Matt Roper (2018-01-20 01:51:40) > > > GPU contexts are usually created with "normal" priority as a starting > > > point and > > > then may be adjusted from their either via

[Bug 103443] [CI] igt@ - success - WARN - no modes for connector 76

https://bugs.freedesktop.org/show_bug.cgi?id=103443 Bug 103443 depends on bug 103369, which changed state. Bug 103369 Summary: [CI] igt@kms_* fail - igt-kms-WARNING: connector 76/eDP-1 has no modes https://bugs.freedesktop.org/show_bug.cgi?id=103369 What|Removed

[PATCH libdrm] tests: Add drm_set_cgrp_param

drm_set_cgrp_param is a simple tool to set DRM parameters associated with a cgroup. It is intended to be called at system initialization time (e.g., from a sysv-init script or systemd service) to configure graphics policy and resource management according to the wishes of the system integrator.

[PATCH] dt-bindings: display: stm32: add pixel clock mandatory property

Add the DPI/RGB input pixel clock in mandatory properties because it really offers a better preciseness for timing computations. Signed-off-by: Philippe Cornu --- Please apply "dt-bindings: display: stm32: correct clock-names in dsi panel example" before this patch.

[PATCH] dt-bindings: display: stm32: correct clock-names in dsi panel example

In the dsi panel example, clock names in the "clock-names" field have been swapped: * "pclk" (peripheral clock) is < 1 CLK_F469_DSI> on stm32f4 * "ref" (dsi phy pll ref clock) is <_hse> on stm32f4 Signed-off-by: Philippe Cornu ---

[PATCH] drm/bridge/synopsys: dsi: Add 1.31 version support

From: Philippe CORNU Add support for the Synopsys DesignWare MIPI DSI version 1.31 Two registers need to be updated/added for supporting 1.31: * PHY_TMR_CFG 0x9c (updated) 1.30 [31:24] phy_hs2lp_time [23:16] phy_lp2hs_time [14: 0] max_rd_time 1.31

[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 #12 from Harry Wentland --- Can you try blacklisting amdgpu and try S3 again? We've seen issues with S3 on 4.15 RCs outside of amdgpu where the system wouldn't come back from S3. It's fixed in more recent

[PATCH v18 10/10] drm/omapdrm: Use of_find_backlight helper

Replace of_find_backlight_by_node and of the code around it with of_find_backlight helper to avoid repetition of code. Signed-off-by: Meghana Madhyastha --- Changes in v18: -Fixed warnings resulting from passing device_node* to of_find_backlight. Fixed it by

Re: [PATCH] dt-bindings: display: stm32: correct clock-names in dsi panel example

On Mon, Jan 22, 2018 at 8:39 AM, Philippe CORNU wrote: > Hi Rob, > > On 01/22/2018 03:30 PM, Rob Herring wrote: >> On Sun, Jan 21, 2018 at 2:58 PM, Philippe Cornu >> wrote: >>> In the dsi panel example, clock names in the "clock-names" >>> field

[PATCH v18 09/10] drm/panel: Use of_find_backlight helper

Replace of_find_backlight_by_node and of the code around it with of_find_backlight helper to avoid repetition of code. Signed-off-by: Meghana Madhyastha --- Changes in v18: -Fixed warnings resulting from passing device_node* to of_find_backlight. Fixed it by

[PATCH v18 07/10] drm/panel: Use backlight_enable/disable helpers

Use backlight_enable/disable helpers instead of changing the property and calling backlight_update_status for cleaner and simpler code and also to avoid repetitions. Signed-off-by: Meghana Madhyastha --- drivers/gpu/drm/panel/panel-innolux-p079zca.c | 6 ++

[PATCH v18 08/10] drm/omapdrm: Use backlight_enable/disable helpers

Use backlight_enable/disable helpers instead of changing the property and calling backlight_update_status for cleaner and simpler code and also to avoid repetitions. Signed-off-by: Meghana Madhyastha --- drivers/gpu/drm/omapdrm/displays/panel-dpi.c | 11 ++-

[PATCH v18 06/10] drm/tinydrm: Call devres version of of_find_backlight

Call devm_of_find_backlight (the devres version) instead of of_find_backlight. Signed-off-by: Meghana Madhyastha --- Reviewed-by: Noralf Trønnes Reviewed-by: Sean Paul drivers/gpu/drm/tinydrm/mi0283qt.c | 2 +-

[PATCH v18 04/10] drm/tinydrm: Replace tinydrm_of_find_backlight with of_find_backlight

Remove tinydrm_of_find_backlight from tinydrm-helpers.c. We now have a generic of_find_backlight defined in backlight.c. Let the callers of tinydrm_of_find_backlight call of_find_backlight. Also, remove select BACKLIGHT_LCD_SUPPORT and select BACKLIGHT_CLASS_DEVICE from tinydrm/Kconfig as it is a

[PATCH v18 05/10] video: backlight: Add devres versions of of_find_backlight

Add devm_of_find_backlight and the corresponding release function because some drivers use devres versions of functions for acquiring device resources. Signed-off-by: Meghana Madhyastha --- Acked-by: Daniel Thompson Reviewed-by: Noralf

[PATCH v18 03/10] video: backlight: Add of_find_backlight helper in backlight.c

Add of_find_backlight, a helper function which is a generic version of tinydrm_of_find_backlight that can be used by other drivers to avoid repetition of code and simplify things. Signed-off-by: Meghana Madhyastha --- Acked-by: Daniel Thompson

[PATCH v18 02/10] drm/tinydrm: Convert tinydrm_enable/disable_backlight to backlight_enable/disable

Remove tinydrm_enable/disable_backlight and let the callers call the more generic backlight_enable/disable helpers Signed-off-by: Meghana Madhyastha --- Reviewed-by: Noralf Trønnes Reviewed-by: Sean Paul

[PATCH v18 00/10] Add backlight helper functions

Move drm helper functions from tinydrm-helpers to linux/backlight for ease of use by callers in other drivers. Changes in v18: -Fixed warnings resulting from passing device_node* to of_find_backlight. Fixed it by passing struct device* to of_find_backlight Meghana Madhyastha (10): video:

[PATCH v18 01/10] video: backlight: Add helpers to enable and disable backlight

Add helper functions backlight_enable and backlight_disable to enable/disable a backlight device. These helper functions can then be used by different drm and tinydrm drivers to avoid repetition of code and also to enforce a uniform and consistent way to enable/disable a backlight device.

Re: [PATCH] dt-bindings: display: stm32: correct clock-names in dsi panel example

Hi Rob, On 01/22/2018 03:30 PM, Rob Herring wrote: > On Sun, Jan 21, 2018 at 2:58 PM, Philippe Cornu wrote: >> In the dsi panel example, clock names in the "clock-names" >> field have been swapped: >> * "pclk" (peripheral clock) is < 1 CLK_F469_DSI> on stm32f4 >> * "ref"

Re: [PATCH] dt-bindings: display: stm32: correct clock-names in dsi panel example

On Sun, Jan 21, 2018 at 2:58 PM, Philippe Cornu wrote: > In the dsi panel example, clock names in the "clock-names" > field have been swapped: > * "pclk" (peripheral clock) is < 1 CLK_F469_DSI> on stm32f4 > * "ref" (dsi phy pll ref clock) is <_hse> on stm32f4 > >

Re: [PATCH v4 00/13] drm/sun4i: Support the Display Engine frontend

On Mon, Jan 22, 2018 at 10:25:14AM +0100, Maxime Ripard wrote: > Hi, > > This is a first serie to enable the display engine frontend. > > This hardware block is found in the first generation Display Engine from > Allwinner. Its role is to implement more advanced features that the > associated

[Bug 104730] VLC crashes on playback with "READ_ONLY without WC is disallowed"

https://bugs.freedesktop.org/show_bug.cgi?id=104730 Bug ID: 104730 Summary: VLC crashes on playback with "READ_ONLY without WC is disallowed" Product: Mesa Version: git Hardware: Other OS: All

[Bug 103915] Undertale crashes on startup (compiling shaders?)

https://bugs.freedesktop.org/show_bug.cgi?id=103915 --- Comment #9 from Alexander Schlarb --- BTW: I should also probably mention my hardware & software: * Radeon R9 M280X (BonaireXT) * Linux 4.14.0-3-amd64 * Debian unstable * Mesa 17.3.3 * DRM 3.19.0 * LLVM

  1   2   >