Re: [PATCH] drm/bridge/synopsys: dsi: Add read feature

On 04.02.2018 22:31, Philippe Cornu wrote: > This patch adds the DCS/GENERIC DSI read feature. > > Signed-off-by: Philippe Cornu > --- Queued to drm-misc-next. -- Regards Andrzej ___ dri-devel mailing list

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

On 06.02.2018 09:42, Philippe Cornu wrote: > 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 > >

[Bug 105005] No image after downtime (RX460)

https://bugs.freedesktop.org/show_bug.cgi?id=105005 --- Comment #5 from Dmitry --- dc1 + hdmi. The problem remained -- You are receiving this mail because: You are the assignee for the bug.___ dri-devel mailing list

[git pull] drm for v4.16-rc1 (part 2 - fixes)

Hi Linus, Ben missed sending his tree, but he really didn't have much stuff in it, GP108 acceleration support is enabled by "secure boot" support, some clockgating work on Kepler, and bunch of fixes. The main bulk is regenerated firmware files, the change to them really isn't that large.

[PATCH 3/3] drm/radeon: only enable swiotlb path when need

swiotlb expands our card accessing range, but its path always is slower than ttm pool allocation. So add condition to use it. Change-Id: I1802645833155a9cd808913f863981173a82145f Signed-off-by: Chunming Zhou --- drivers/gpu/drm/radeon/radeon.h| 1 +

[PATCH 2/3] drm/amdgpu: only enable swiotlb alloc when need

get the max io mapping address of system memory to see if it is over our card accessing range. Change-Id: Ibc38dbd34a20af5b4a4b1ed154c14e1c58aa4c55 Signed-off-by: Chunming Zhou --- drivers/gpu/drm/amd/amdgpu/amdgpu.h | 1 + drivers/gpu/drm/amd/amdgpu/amdgpu_ttm.c | 6

[PATCH 1/3] drm: add func to get max iomem address

it will be used to check if the driver needs swiotlb Change-Id: Idbe47af8f12032d4803bb3d47273e807f19169c3 Signed-off-by: Chunming Zhou --- include/drm/drm_cache.h | 13 + 1 file changed, 13 insertions(+) diff --git a/include/drm/drm_cache.h

Re: [PATCH v3 5/8] drm: Handle aspect ratio info in atomic and legacy modeset paths

Hi Ville, I still have some queries regarding the handling of aspect ratio flags in getblob ioctl. Please find below my responses inline. On 2/1/2018 6:24 PM, Ville Syrjälä wrote: On Thu, Feb 01, 2018 at 04:35:22PM +0530, Nautiyal, Ankit K wrote: Hi Ville, Appreciate your time and the

[PATCH v2 2/2] amdgpu/dc/dml: Support clang option for stack alignment

DML uses the compiler option -mpreferred-stack-boundary=4 to configure a stack alignment of 16 bytes. Clang uses the option -mstack-alignment instead, which expects as parameter the alignment in bytes, and not a power of two like -mpreferred-stack-boundary. Probe for both compiler options and use

[PATCH v2 1/2] amdgpu/dc/dml: Consolidate redundant CFLAGS

Use subdir-ccflags instead of specifying the same flags for every source file. Signed-off-by: Matthias Kaehlcke Reviewed-by: Guenter Roeck --- Changes in v2: - added 'Reviewed-by: Guenter Roeck ' tag

Re: [PATCH 2/2] amdgpu/dc/dml: Support clang option for stack alignment

El Wed, Feb 07, 2018 at 05:34:44PM -0800 Guenter Roeck ha dit: > On Wed, Feb 7, 2018 at 5:21 PM, Matthias Kaehlcke wrote: > > DML uses the compiler option -mpreferred-stack-boundary=4 to configure > > a stack alignment of 16 bytes. Clang uses the option -mstack-alignment > >

[PATCH 1/2] amdgpu/dc/dml: Consolidate redundant CFLAGS

Use subdir-ccflags instead of specifying the same flags for every source file. Signed-off-by: Matthias Kaehlcke --- drivers/gpu/drm/amd/display/dc/dml/Makefile | 10 +- 1 file changed, 1 insertion(+), 9 deletions(-) diff --git

[PATCH 2/2] amdgpu/dc/dml: Support clang option for stack alignment

DML uses the compiler option -mpreferred-stack-boundary=4 to configure a stack alignment of 16 bytes. Clang uses the option -mstack-alignment instead, which expects as parameter the alignment in bytes, and not a power of two like -mpreferred-stack-boundary. Probe for both compiler options and use

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

Hi Archit, On 07/02/18 12:33, Kieran Bingham wrote: > Hi Archit, > > Thank you for your review, > >>>   unsigned int val; >>>   int ret; >>>   @@ -1153,24 +1151,35 @@ static int adv7511_probe(struct i2c_client *i2c, >>> const struct i2c_device_id *id) >>>   if (ret) >>>  

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

Hi Laurent, On 07/02/18 21:59, Laurent Pinchart wrote: > Hi Kieran, > > On Wednesday, 7 February 2018 17:14:09 EET Kieran Bingham wrote: >> On 29/01/18 10:26, Laurent Pinchart wrote: >>> On Monday, 22 January 2018 14:50:00 EET Kieran Bingham wrote: The ADV7511 has four 256-byte maps that

RE: [PATCH 1/1] drm: Add dirty_rects atomic blob property for drm_plane

Hi Lukasz, I hope you are doing great. I was busy with some other stuff but now will be working on page-flip damage. At this point I have high level understanding of what changes to make and before I start just wanted to confirm from you, whether you have made any progress to avoid duplicate

Re: [PATCH RFC v2 3/7] cgroup: Add interface to allow drivers to lookup process cgroup membership

Hello, On Thu, Feb 01, 2018 at 11:53:11AM -0800, Matt Roper wrote: > +/** > + * cgroup_for_driver_process - return the cgroup for a process > + * @pid: process to lookup cgroup for > + * > + * Returns the cgroup from the v2 hierarchy that a process belongs to. > + * This function is intended to

Re: [PATCH RFC v2 1/7] cgroup: Allow drivers to store data associated with a cgroup

Hello, On Thu, Feb 01, 2018 at 11:53:09AM -0800, Matt Roper wrote: > * Drivers may be built as modules (and unloaded/reloaded) which is not >something cgroup controllers support today. As discussed in the other subthread, this shouldn't be a concern. > * Drivers may wish to provide their

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

Hi Kieran, On Wednesday, 7 February 2018 17:14:09 EET Kieran Bingham wrote: > On 29/01/18 10:26, Laurent Pinchart wrote: > > On Monday, 22 January 2018 14:50:00 EET 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

Re: [Intel-gfx] [IGT PATCH RFC] tools: Introduce intel_cgroup tool

Hello, Forgot to respond to one point. On Thu, Feb 01, 2018 at 03:14:38PM -0800, Matt Roper wrote: > * The drivers that want to make use of this functionality may be built >as modules rather than compiled directly into the kernel. This is >important because the cgroups subsystem

Re: [PATCH] amdgpu/dc: Fix enum mismatch in calls to program_color_matrix()

On 2018-02-07 04:43 PM, Matthias Kaehlcke wrote: > The driver passes GRAPHICS_CSC_ADJUST_TYPE_SW of type enum > graphics_csc_adjust_type to program_color_matrix(), however the function > expects a parameter of type enum grph_color_adjust_option. Supposedly > the intention was to pass

[Bug 105005] No image after downtime (RX460)

https://bugs.freedesktop.org/show_bug.cgi?id=105005 --- Comment #4 from Dmitry --- Created attachment 137223 --> https://bugs.freedesktop.org/attachment.cgi?id=137223=edit Xorg log Attach Xorg log. DC then turned, I'll watch the reaction. -- You are receiving this mail

Re: [Intel-gfx] [IGT PATCH RFC] tools: Introduce intel_cgroup tool

Hello, Matt, Chris. On Thu, Feb 01, 2018 at 03:14:38PM -0800, Matt Roper wrote: > > Hmm. Could we not avoid drm_ioctl + well known param names and use a > > more generic tool to set cgroup attributes? Just feels wrong that a > > such a generic interface boils down to a driver specific ioctl. So,

[Bug 105005] No image after downtime (RX460)

https://bugs.freedesktop.org/show_bug.cgi?id=105005 --- Comment #3 from Dmitry --- Created attachment 137222 --> https://bugs.freedesktop.org/attachment.cgi?id=137222=edit dmesg Attach dmesg -- You are receiving this mail because: You are the assignee for the

[PATCH 2/2] drm/msm/mdp4: Return directly after a failed kzalloc() in mdp4_kms_init()

From: Markus Elfring Date: Wed, 7 Feb 2018 22:34:45 +0100 * Return directly after a call of the function "kzalloc" failed at the beginning. * Delete an initialisation and a check (for the local variable "kms") which became unnecessary with this refactoring.

[PATCH 1/2] drm/msm/mdp4: Delete an error message for a failed memory allocation in mdp4_kms_init()

From: Markus Elfring Date: Wed, 7 Feb 2018 22:22:28 +0100 Omit an extra message for a memory allocation failure in this function. This issue was detected by using the Coccinelle software. Signed-off-by: Markus Elfring ---

[PATCH 0/2] drm/msm/mdp4: Adjustments for mdp4_kms_init()

From: Markus Elfring Date: Wed, 7 Feb 2018 22:38:44 +0100 Two update suggestions were taken into account from static source code analysis. Markus Elfring (2): Delete an error message for a failed memory allocation Return directly after a failed kzalloc()

[PATCH] amdgpu/dc: Fix enum mismatch in calls to program_color_matrix()

The driver passes GRAPHICS_CSC_ADJUST_TYPE_SW of type enum graphics_csc_adjust_type to program_color_matrix(), however the function expects a parameter of type enum grph_color_adjust_option. Supposedly the intention was to pass GRPH_COLOR_MATRIX_SW, which has the same value as

Re: [RFC PATCH v2 1/5] dt-bindings: add bindings for USB physical connector

On Mon, Feb 05, 2018 at 10:06:35AM +0100, Andrzej Hajda wrote: > On 05.02.2018 07:08, Rob Herring wrote: > > On Wed, Jan 31, 2018 at 02:44:31PM +0100, Andrzej Hajda wrote: > >> These bindings allow to describe most known standard USB connectors > >> and it should be possible to extend it if

Re: [Intel-gfx] [PATCH 06/10] drm/tegra: Handle 64-bit return from drm_crtc_vblank_count()

On Wed, 2018-02-07 at 10:41 +0100, Thierry Reding wrote: > On Wed, Feb 07, 2018 at 01:41:18AM +, Pandiyan, Dhinakaran wrote: > > On Fri, 2018-02-02 at 21:12 -0800, Dhinakaran Pandiyan wrote: > > > 570e86963a51 ("drm: Widen vblank count to 64-bits [v3]") changed the > > > return type for

[PATCH] drm/msm/mdp5: Delete an error message for a failed memory allocation in two functions

From: Markus Elfring Date: Wed, 7 Feb 2018 21:50:07 +0100 Omit an extra message for a memory allocation failure in these functions. This issue was detected by using the Coccinelle software. Signed-off-by: Markus Elfring ---

Re: [PATCH] drm/amd/display: Remove extra pairs of parentheses in dce_calcs.c

On 2018-02-07 02:49 PM, Matthias Kaehlcke wrote: > The double parentheses are not needed. Removing them fixes multiple > warnings like this when building with clang: > > drivers/gpu/drm/amd/amdgpu/../display/dc/calcs/dce_calcs.c:617:42: > error: equality comparison with extraneous parentheses >

Re: [PATCH] drm/amd/powerplay: Remove extra pair of parentheses

On Wed, Feb 7, 2018 at 2:19 PM, Guenter Roeck wrote: > On Wed, Feb 7, 2018 at 11:10 AM, Matthias Kaehlcke wrote: >> The double parentheses are not needed. Removing them fixes the following >> warning when building with clang: >> >>

[PULL] drm-intel-next-fixes

Hi Dave, Here goes drm-intel-next-fixes-2018-02-07: Fix for pcode timeouts on BXT and GLK, cmdparser fixes and fixes for new vbt version on CFL and CNL. GVT contains vGPU reset enhancement, which refines vGPU reset flow and the support of virtual aperture read/write when x-no-mmap=on is set in

[Bug 105005] No image after downtime (RX460)

https://bugs.freedesktop.org/show_bug.cgi?id=105005 --- Comment #2 from Alex Deucher --- Does it work with DC enabled? -- You are receiving this mail because: You are the assignee for the bug.___ dri-devel mailing list

[Bug 105005] No image after downtime (RX460)

https://bugs.freedesktop.org/show_bug.cgi?id=105005 --- Comment #1 from Alex Deucher --- Please include your dmesg output and Xorg log if using X. -- You are receiving this mail because: You are the assignee for the bug.___

[PATCH] drm/tegra/fb: Delete an error message for a failed memory allocation in tegra_fbdev_create()

From: Markus Elfring Date: Wed, 7 Feb 2018 21:17:17 +0100 Omit an extra message for a memory allocation failure in this function. This issue was detected by using the Coccinelle software. Signed-off-by: Markus Elfring ---

[Bug 197925] [amdgpu_dc][carrizo] multiple monitor handling errors

https://bugzilla.kernel.org/show_bug.cgi?id=197925 --- Comment #12 from kwka...@gmx.com --- Still not fixed v4.15-11781-g413879a10b0b -- You are receiving this mail because: You are watching the assignee of the bug. ___ dri-devel mailing list

[PATCH] drm/amd/display: Remove extra pairs of parentheses in dce_calcs.c

The double parentheses are not needed. Removing them fixes multiple warnings like this when building with clang: drivers/gpu/drm/amd/amdgpu/../display/dc/calcs/dce_calcs.c:617:42: error: equality comparison with extraneous parentheses [-Werror,-Wparentheses-equality] if

[Bug 105005] No image after downtime (RX460)

https://bugs.freedesktop.org/show_bug.cgi?id=105005 Bug ID: 105005 Summary: No image after downtime (RX460) Product: DRI Version: XOrg git Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity:

Re: [PATCH 1/3] drm/panel: simple: Add ability to override typical timing

On Wed, Feb 07, 2018 at 11:41:49AM -0600, Rob Herring wrote: > On Tue, Feb 6, 2018 at 3:48 PM, Sean Paul wrote: > > On Tue, Feb 06, 2018 at 02:19:34PM -0600, Rob Herring wrote: > >> On Tue, Feb 6, 2018 at 10:56 AM, Sean Paul wrote: > >> > This patch

Re: [PATCH 3/3] drm/tegra: fb: Implement ->fb_mmap() callback

On 07.02.2018 18:45, Thierry Reding wrote: > From: Thierry Reding > > This fixes hangs with legacy applications that use the mmap() syscall on > the fbdev device to map framebuffer memory. The fbdev implementation for > mmap() creates a mapping that conflicts with DRM usage

[pull] amdgpu drm-next-4.16

Hi Dave, Just one fix this week for 4.16. This is on top of the pull request I sent last week. One of the fixes from last week got applied to the wrong asic by accident. The patch this week fixes that. The following changes since commit 7e24a3ea825e546487c3fc47f8cbf6512f6c9e8c: drm/amdgpu:

[PATCH] drm/amd/powerplay: Remove extra pair of parentheses

The double parentheses are not needed. Removing them fixes the following warning when building with clang: drivers/gpu/drm/amd/powerplay/smumgr/tonga_smumgr.c:419:29: error: equality comparison with extraneous parentheses [-Werror,-Wparentheses-equality] if ((data->vdd_gfx_control ==

Re: [PATCH] drm/amd/powerplay: Fix enum mismatch

On Wed, Feb 7, 2018 at 2:01 PM, Guenter Roeck wrote: > On Wed, Feb 7, 2018 at 10:58 AM, Matthias Kaehlcke wrote: >> In several locations the driver uses AMD_CG_STATE_UNGATE (type enum >> amd_clockgating_state) instead of AMD_PG_STATE_UNGATE (type enum >>

[PATCH] drm/amd/powerplay: Fix enum mismatch

In several locations the driver uses AMD_CG_STATE_UNGATE (type enum amd_clockgating_state) instead of AMD_PG_STATE_UNGATE (type enum amd_powergating_stat) and vice versa. Both constants have the same value, so this doesn't cause any problems, but we still want to pass the correct type. Fixing the

Re: Enabling i915 Panel Self Refresh by default on some devices ?

Hans de Goede writes: > Hi, > > On 06-02-18 00:14, Rodrigo Vivi wrote: >> >> Hi Hans, >> >> On Fri, Feb 02, 2018 at 09:55:32AM +, Hans de Goede wrote: >>> Hi, >>> >>> On 01-02-18 13:31, Hans de Goede wrote: Hi All, As you may have heard I've recently been

Re: [PATCH 0/5] prevent OOM triggered by TTM

Hi, On 02/07/2018 02:22 PM, Christian König wrote: Understood, but why is that? Well because customers requested it :) What we try to do here is having a parameter which says when less than x megabytes of memory are left then fail the allocation. This is basically to prevent buggy

Re: [PATCH] drm/nouveau: Make clock gate support conditional

Reviewed-by: Lyude Paul On Wed, 2018-02-07 at 18:40 +0100, Thierry Reding wrote: > From: Thierry Reding > > The recently introduced clock gate support breaks on Tegra chips because > no thermal support is enabled for those devices. Conditionalize the code

[Bug 104932] Hang when running X11/Wayland on GFX8/Polaris10/Ellesmere/Rx-480-8GiB (agd5f a5592a6df4f45a018b48f252ad1c498e683e9b9d, hwentland's DC-Patches-Jan-31-2018.mbox applied)

https://bugs.freedesktop.org/show_bug.cgi?id=104932 --- Comment #5 from Robin Kauffman --- (In reply to Michel Dänzer from comment #4) > Which versions of Mesa & LLVM are you using? LLVM & Clang 7.0 Git, LLVM commit e0c16f05e9fbc1dcd291814ceab9dbc5, Clang commit

[PATCH 2/3] drm/tegra: gem: Make __tegra_gem_mmap() available more widely

From: Thierry Reding This function allows mapping a GEM object into a virtual memory address space, which makes it useful outside of the GEM code. While at it, rename the function so it doesn't clash with the function that implements the DRM_TEGRA_GEM_MMAP IOCTL.

[PATCH 1/3] drm/tegra: gem: Reshuffle declarations

From: Thierry Reding Move declarations in the gem.h header file into the same order as the corresponding definitions in gem.c. Signed-off-by: Thierry Reding --- drivers/gpu/drm/tegra/gem.h | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff

[PATCH 3/3] drm/tegra: fb: Implement ->fb_mmap() callback

From: Thierry Reding This fixes hangs with legacy applications that use the mmap() syscall on the fbdev device to map framebuffer memory. The fbdev implementation for mmap() creates a mapping that conflicts with DRM usage and causes a hang when the memory is accessed through

Re: [PATCH 1/3] drm/panel: simple: Add ability to override typical timing

On Tue, Feb 6, 2018 at 3:48 PM, Sean Paul wrote: > On Tue, Feb 06, 2018 at 02:19:34PM -0600, Rob Herring wrote: >> On Tue, Feb 6, 2018 at 10:56 AM, Sean Paul wrote: >> > This patch adds the ability to override the typical display timing for a >> >

[PATCH] drm/nouveau: Make clock gate support conditional

From: Thierry Reding The recently introduced clock gate support breaks on Tegra chips because no thermal support is enabled for those devices. Conditionalize the code on the existence of thermal support to fix this. Fixes: b138eca661cc ("drm/nouveau: Add support for basic

[Bug 103142] R600g+sb: optimizer apparently stuck in an endless loop

https://bugs.freedesktop.org/show_bug.cgi?id=103142 Gert Wollny changed: What|Removed |Added QA Contact|dri-devel@lists.freedesktop

[Bug 103142] R600g+sb: optimizer apparently stuck in an endless loop

https://bugs.freedesktop.org/show_bug.cgi?id=103142 --- Comment #7 from Gert Wollny --- It seems sb is trying to create an operation that tries to use two distinct relative indices within the same instruction, this is forbidden and the scheduler gets stuck. from the post

[PATCH v2 5/5] arm64: dts: rockchip: Specify override mode for kevin panel

This patch adds an override mode for kevin devices. The mode increases both back porches to allow a pixel clock of 2kHz as opposed to the 'typical' value of 252750kHz. This is needed to avoid interference with the touch digitizer on these laptops. Changes in v2: - Wrap the timing in

[PATCH v2 1/5] dt-bindings: Add headings to simple-panel bindings

In preparation for a new subnode section in a follow-on patch, add explicit headings to the existings sections for simple-panel. Changes in v2: - Added Cc: Doug Anderson Cc: Eric Anholt Cc: Heiko Stuebner Cc: Jeffy Chen

[PATCH v2 0/5] drm/panel: simple: Add mode support to devicetree

Hey all, Here's a set which allows us to add an "override" mode to the simple panel dt node. The override mode can be used for devices for which the typical display timing is not sufficient, yet the overriding mode should not be applied across the entire platform. An example of this (and the

[PATCH v2 4/5] drm/panel: simple: Use display_timing for lq123p1jx31

Convert the sharp lq123p1jx31 from using a fixed mode to specifying a display timing with min/typ/max values. This allows us to capture the timings set forth in the datasheet as well as the additional values that we've cleared with the display vendor to avoid interference with the digitizer on the

[PATCH v2 2/5] dt-bindings: Add display-timing subnode to simple-panel

This patch adds a new subnode to simple-panel allowing us to override the typical timing expressed in the panel's display_timing. Changes in v2: - Split out the binding into a new patch (Rob) - display-timings is a new section (Rob) - Use the full display-timings subnode instead of picking the

[PATCH v2 3/5] drm/panel: simple: Add ability to override typical timing

This patch adds the ability to override the typical display timing for a given panel. This is useful for devices which have timing constraints that do not apply across the entire display driver (eg: to avoid crosstalk between panel and digitizer on certain laptops). The rules are as follows: -

Re: [PATCH] drm/fb-helper: Redo fb format<->fb_bitfield mapping

On Wed, Feb 07, 2018 at 05:08:30PM +, Eric Engestrom wrote: > On Wednesday, 2018-02-07 17:24:45 +0200, Ville Syrjala wrote: > > From: Ville Syrjälä > > > > Replace the switch statements that try to map between the fb format and > > the fb_bitfield infromation

[Bug 198713] AMD DC crashes when computing clocks/detecting freesync

https://bugzilla.kernel.org/show_bug.cgi?id=198713 --- Comment #3 from Jon (j...@moozaad.co.uk) --- (In reply to Mike Lothian from comment #2) > As a workaround try amdgpu.dc=0 Well spotted. Workaround has stopped the traces as you'd expect. It's also stopped the weird blue flicker I was getting

Re: [PATCH] drm/fb-helper: Redo fb format<->fb_bitfield mapping

On Wednesday, 2018-02-07 17:24:45 +0200, Ville Syrjala wrote: > From: Ville Syrjälä > > Replace the switch statements that try to map between the fb format and > the fb_bitfield infromation with a single table. > > Note that this changes the behaviour of

Re: nouveau 30bpp / deep color status

On Wed, Feb 07, 2018 at 06:28:42PM +0200, Ville Syrjälä wrote: > On Sun, Feb 04, 2018 at 06:50:45PM -0500, Ilia Mirkin wrote: > > In case anyone's curious about 30bpp framebuffer support, here's the > > current status: > > > > Kernel: > > > > Ben and I have switched the code to using a 256-based

[Bug 100784] Fullscreen fade transitions in starsector run at a few frames per second

https://bugs.freedesktop.org/show_bug.cgi?id=100784 --- Comment #4 from Jon --- Present in 18.0.0 too. Still drops to single figures for transitions from space station menu to solar map. Doesn't seem present from galactic map to solar map. -- You are receiving this mail

[Bug 196771] [AMDGPU] Scrambled video output during boot on WQHD monitor

https://bugzilla.kernel.org/show_bug.cgi?id=196771 Rokas Kupstys (rokups+kernel-b...@zoho.com) changed: What|Removed |Added Status|NEW |RESOLVED

Re: nouveau 30bpp / deep color status

On Sun, Feb 04, 2018 at 06:50:45PM -0500, Ilia Mirkin wrote: > In case anyone's curious about 30bpp framebuffer support, here's the > current status: > > Kernel: > > Ben and I have switched the code to using a 256-based LUT for Kepler+, > and I've also written a patch to cause the addfb ioctl to

[Bug 198713] AMD DC crashes when computing clocks/detecting freesync

https://bugzilla.kernel.org/show_bug.cgi?id=198713 Mike Lothian (m...@fireburn.co.uk) changed: What|Removed |Added CC||m...@fireburn.co.uk

[Bug 198713] AMD DC crashes when computing clocks/detecting freesync

https://bugzilla.kernel.org/show_bug.cgi?id=198713 --- Comment #1 from Jon (j...@moozaad.co.uk) --- Created attachment 274055 --> https://bugzilla.kernel.org/attachment.cgi?id=274055=edit kernel config from /boot -- You are receiving this mail because: You are watching the assignee of the

[Bug 198713] New: AMD DC crashes when computing clocks/detecting freesync

https://bugzilla.kernel.org/show_bug.cgi?id=198713 Bug ID: 198713 Summary: AMD DC crashes when computing clocks/detecting freesync Product: Drivers Version: 2.5 Kernel Version: 4.15.1-7 Hardware: x86-64

Re: [PATCH 1/2] media: adv7604: Add support for i2c_new_secondary_device

Hi Rob, On 29/01/18 20:08, Rob Herring wrote: > On Mon, Jan 22, 2018 at 12:49:56PM +, Kieran Bingham wrote: >> From: Jean-Michel Hautbois >> >> The ADV7604 has thirteen 256-byte maps that can be accessed via the main >> I²C ports. Each map has it own I²C

Re: [PATCH v3 1/3] drm/omap: Fail probe if irq registration fails

On 07/02/18 14:10, Jyri Sarha wrote: > Call to omap_drm_irq_install() may fail with an error code. In such a > case the driver probe should fail. > > Signed-off-by: Jyri Sarha > --- > drivers/gpu/drm/omapdrm/omap_drv.c | 4 ++-- > 1 file changed, 2 insertions(+), 2 deletions(-) >

Re: [PATCH 0/3] drm/panel: simple: Add mode support to devicetree

On Wed, Feb 07, 2018 at 09:16:22AM +, Eric Anholt wrote: > Sean Paul writes: > > > Hey all, > > Here's a set which allows us to add an "override" mode to the simple > > panel dt node. The override mode can be used for devices for which the > > typical display timing is

[PATCH] drm/fb-helper: Redo fb format<->fb_bitfield mapping

From: Ville Syrjälä Replace the switch statements that try to map between the fb format and the fb_bitfield infromation with a single table. Note that this changes the behaviour of drm_fb_helper_check_var() to return an error of the requested fb_bitfields don't

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

Hi Laurent, On 29/01/18 10:26, Laurent Pinchart wrote: > Hi Kieran, > > Thank you for the patch. Thanks for your review, > On Monday, 22 January 2018 14:50:00 EET 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

[GIT PULL] fbdev changes for v4.16

Hi Linus, Please pull fbdev changes for v4.16. There is nothing really major here (please see the signed tag description for details). Best regards, -- Bartlomiej Zolnierkiewicz Samsung R Institute Poland Samsung Electronics The following changes since commit

[Bug 104963] MSI MoBo A88XM-E35 GPU Trinity A8-5600K (Aruba HD7560D) Boot loop without radeon.dpm=0

https://bugs.freedesktop.org/show_bug.cgi?id=104963 --- Comment #2 from VF --- No, neither radeon.bapm=O nor radeon.bapm=1 help neither in K4.4.0-112 nor K4.15.1 -- You are receiving this mail because: You are the assignee for the

[drm-intel:drm-intel-next-queued 1/1] drivers/gpu//drm/i915/i915_pmu.c:473:18: error: 'struct dev_pm_info' has no member named 'suspended_jiffies'

tree: git://anongit.freedesktop.org/drm-intel drm-intel-next-queued head: 1fe699e30113ed6f6e853ff44710d256072ea627 commit: 1fe699e30113ed6f6e853ff44710d256072ea627 [1/1] drm/i915/pmu: Fix sleep under atomic in RC6 readout config: i386-randconfig-x019-201805 (attached as .config) compiler:

[PATCH libdrm] meson: use pkg-config to detect libatomic_ops

Signed-off-by: Eric Engestrom --- amdgpu/meson.build| 2 +- etnaviv/meson.build | 2 +- freedreno/meson.build | 2 +- intel/meson.build | 2 +- meson.build | 3 ++- nouveau/meson.build | 2 +- omap/meson.build | 2 +- radeon/meson.build|

[PATCH v3 2/3] drm/omap: Add get_ovl_name() and get_mgr_name() to dispc_ops

Add get_ovl_name() and get_mgr_name() to dispc_ops and get rid of adhoc names here and there in the omapdrm code. This moves the names of hardware entities to omapdss side where they have to be when new omapdss backend drivers are introduced. Signed-off-by: Jyri Sarha ---

[PATCH v3 1/3] drm/omap: Fail probe if irq registration fails

Call to omap_drm_irq_install() may fail with an error code. In such a case the driver probe should fail. Signed-off-by: Jyri Sarha --- drivers/gpu/drm/omapdrm/omap_drv.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/drivers/gpu/drm/omapdrm/omap_drv.c

[PATCH v3 3/3] drm/omap: Make omapdss API more generic

The new omapdss API is HW independent and cleans up some of the DSS5 specific hacks from the omapdrm side and gets rid off the DSS5 IRQ register bits and replace them with HW independent generic u64 based macros. The new macros make it more straight forward to implement the IRQ code for the future

[PATCH v3 0/3] drm/omap: Make omapdss API more generic + related patches

Since v2: - Simplify dispc_mgr_has_framedone() - dispc_hw_to_api_irq() and dispc_api_to_hw_irq() use new dispc_irq_bits[] - rename dispc_ops read_irqstatus() to read_and_clear_irqstatus() and remove clearmask - precalculate priv->irq_uf_mask in omap_drm_irq_install() and use it in

Re: [PATCH v2] drm/i915/pmu: Fix sleep under atomic in RC6 readout

On 2/6/2018 10:54 PM, Imre Deak wrote: Hi Rafael, On Tue, Feb 06, 2018 at 09:11:02PM +, Chris Wilson wrote: Quoting Tvrtko Ursulin (2018-02-06 18:33:11) From: Tvrtko Ursulin We are not allowed to call intel_runtime_pm_get from the PMU counter read callback

Re: [PATCH] drm: don't link DP aux i2c adapter to the hardware device node

On 05.02.2018 19:07, Thierry Reding wrote: > On Mon, Feb 05, 2018 at 06:39:05PM +0100, Lucas Stach wrote: >> Am Montag, den 05.02.2018, 18:33 +0100 schrieb Thierry Reding: >>> On Mon, Feb 05, 2018 at 05:11:30PM +0100, Thierry Reding wrote: On Wed, Apr 05, 2017 at 02:04:31PM +0200, Thierry

Re: [PATCH v3 2/3] drm/omap: Add get_ovl_name() and get_mgr_name() to dispc_ops

On 07/02/18 14:10, Jyri Sarha wrote: > Add get_ovl_name() and get_mgr_name() to dispc_ops and get rid of > adhoc names here and there in the omapdrm code. This moves the names > of hardware entities to omapdss side where they have to be when new > omapdss backend drivers are introduced. > >

Re: [PATCH 0/5] prevent OOM triggered by TTM

Understood, but why is that? Well because customers requested it :) What we try to do here is having a parameter which says when less than x megabytes of memory are left then fail the allocation. This is basically to prevent buggy applications which try to allocate as much memory as

Re: [PATCH 0/5] prevent OOM triggered by TTM

Hi, Roger. On 02/07/2018 09:25 AM, He, Roger wrote: Why should TTM be different in that aspect? It would be good to know your reasoning WRT this? Now, in TTM struct ttm_bo_device it already has member no_retry to indicate your option. If you prefer no OOM triggered by TTM, set it as

Re: [PATCH 17/17] drm/dp: Add drm_dp_link_choose() helper

On Mon, 05 Feb 2018, Thierry Reding wrote: > From: Thierry Reding > > This helper chooses an appropriate configuration, according to the > bitrate requirements of the video mode and the capabilities of the > DisplayPort sink. > > Signed-off-by:

[Bug 198669] Driver crash at radeon_ring_backup+0xd3/0x140 [radeon]

https://bugzilla.kernel.org/show_bug.cgi?id=198669 --- Comment #13 from ro...@beardandsandals.co.uk (ro...@beardandsandals.co.uk) --- You can ignore comment 11. I I thought the email reply had not worked. So I posted a revised version directly. Comment 10 is the correct one. -- You are

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

Hi Archit, Thank you for your review, On 29/01/18 04:11, Archit Taneja wrote: > Hi, > > On 01/22/2018 06:20 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

[PATCH] drm/bochs: make structure bochs_bo_driver static

From: Colin Ian King The structure bochs_bo_driver is local to the source and does not need to be in global scope, so make it static. Cleans up sparse warning: drivers/gpu/drm/bochs/bochs_mm.c:197:22: warning: symbol 'bochs_bo_driver' was not declared. Should it be

Re: [PATCH 2/2] drm/sun4i: Handle DRM_MODE_FLAG_**SYNC_POSITIVE correctly

On Wed, Jan 24, 2018 at 08:37:28PM +0100, Giulio Benetti wrote: > > > > Also, how was it tested? This seems quite weird that we haven't caught > > > > that one sooner, and I'm a bit worried about the possible regressions > > > > here. > > > > > > It sounds really strange to me too, > > > because

RE: [PATCH 0/5] prevent OOM triggered by TTM

Sure, will make it turn off as default and make the limit configurable. Thanks Roger(Hongbo.He) -Original Message- From: Christian König [mailto:ckoenig.leichtzumer...@gmail.com] Sent: Wednesday, February 07, 2018 4:41 PM To: He, Roger ; Thomas Hellstrom

[Bug 104989] [r600] [bisected] OpenGL applications can't render anything at all

https://bugs.freedesktop.org/show_bug.cgi?id=104989 Vlad Golovkin changed: What|Removed |Added Assignee|dri-devel@lists.freedesktop

Re: [PATCH 1/3] drm/panel: simple: Add ability to override typical timing

On Tue, Feb 06, 2018 at 02:19:34PM -0600, Rob Herring wrote: > On Tue, Feb 6, 2018 at 10:56 AM, Sean Paul wrote: > > This patch adds the ability to override the typical display timing for a > > given panel. This is useful for devices which have timing constraints > > that

Re: [PATCH v3 1/2] drm/virtio: Add window server support

On 02/06/2018 03:23 PM, Gerd Hoffmann wrote: Hi, Hmm? I'm assuming the wayland client (in the guest) talks to the wayland proxy, using the wayland protocol, like it would talk to a wayland display server. Buffers must be passed from client to server/proxy somehow, probably using fd

  1   2   >