Re: [PATCH] drm: Add optional COLOR_ENCODING and COLOR_RANGE properties to drm_plane

On Tue, Feb 06, 2018 at 07:08:34PM +0100, Hans Verkuil wrote: > On 02/06/2018 06:58 PM, Ville Syrjälä wrote: > > On Mon, Jun 12, 2017 at 12:10:04AM +0300, Jyri Sarha wrote: > >> Add a standard optional properties to support different non RGB color > >> encodings in DRM planes. COLOR_ENCODING

[Bug 100105] Make Theano OpenCL support work on Clover and RadeonSI

https://bugs.freedesktop.org/show_bug.cgi?id=100105 Bug 100105 depends on bug 100212, which changed state. Bug 100212 Summary: Implement vload_* and vstore_* to make Theano/libgpuarray working https://bugs.freedesktop.org/show_bug.cgi?id=100212 What|Removed

[Bug 100212] Implement vload_* and vstore_* to make Theano/libgpuarray working

https://bugs.freedesktop.org/show_bug.cgi?id=100212 Jan Vesely changed: What|Removed |Added Resolution|--- |FIXED

[Bug 104194] HDMI with RX460 not working on linux 4.15-rc2 with DC enabled and linux-amd-staging-drm-next

https://bugs.freedesktop.org/show_bug.cgi?id=104194 --- Comment #3 from saunders...@wright.edu --- I am having this issue as well on 4.15.1 without DC enabled (as well as DC enabled) on a RX 460. Will try the cable replug on GPU side (didn't work on monitor side.) -- You are receiving this mail

[Bug 104194] HDMI with RX460 not working on linux 4.15-rc2 with DC enabled and linux-amd-staging-drm-next

https://bugs.freedesktop.org/show_bug.cgi?id=104194 --- Comment #4 from saunders...@wright.edu --- Unplugging and replugging the cable on the GPU side causes the monitor to be detected without DC enabled. (Haven't checked with DC.) -- You are receiving this mail because: You are the assignee

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

https://bugzilla.kernel.org/show_bug.cgi?id=198669 --- Comment #7 from ro...@beardandsandals.co.uk (ro...@beardandsandals.co.uk) --- The original point I made in the bug report was that this bug is not about the mechanical hardware glitch. It as about the driver being in what is obviously a

Re: Questions on page flips and atomic modeset

On Tue, Feb 06, 2018 at 11:59:37AM +0200, Oleksandr Andrushchenko wrote: > Hello, Ville! > > Thank you very much for such a comprehensive answer. > > Please see inline > > > On 02/05/2018 06:47 PM, Ville Syrjälä wrote: > > On Mon, Feb 05, 2018 at 06:03:25PM +0200, Oleksandr Andrushchenko

[PATCH 3/3] 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. Cc: Doug Anderson Cc:

Re: Atomic driver and old remove FB behavior

Op 06-02-18 om 15:43 schreef Oleksandr Andrushchenko: > Hello, Maarten! > > > On 02/01/2018 12:13 PM, Oleksandr Andrushchenko wrote: >> On 02/01/2018 12:04 PM, Maarten Lankhorst wrote: >>> Op 01-02-18 om 08:08 schreef Oleksandr Andrushchenko: Hi, all! I am working on a

Re: [PATCH] drm: Add optional COLOR_ENCODING and COLOR_RANGE properties to drm_plane

On 02/06/2018 06:58 PM, Ville Syrjälä wrote: > On Mon, Jun 12, 2017 at 12:10:04AM +0300, Jyri Sarha wrote: >> Add a standard optional properties to support different non RGB color >> encodings in DRM planes. COLOR_ENCODING select the supported non RGB >> color encoding, for instance ITU-R BT.709

[Bug 99553] Tracker bug for runnning OpenCL applications on Clover

https://bugs.freedesktop.org/show_bug.cgi?id=99553 Bug 99553 depends on bug 100212, which changed state. Bug 100212 Summary: Implement vload_* and vstore_* to make Theano/libgpuarray working https://bugs.freedesktop.org/show_bug.cgi?id=100212 What|Removed

Re: [PATCH] drm: Add optional COLOR_ENCODING and COLOR_RANGE properties to drm_plane

On Mon, Jun 12, 2017 at 12:10:04AM +0300, Jyri Sarha wrote: > Add a standard optional properties to support different non RGB color > encodings in DRM planes. COLOR_ENCODING select the supported non RGB > color encoding, for instance ITU-R BT.709 YCbCr. COLOR_RANGE selects > the value ranges

Re: [PATCH] drm: Add optional COLOR_ENCODING and COLOR_RANGE properties to drm_plane

On Tue, Feb 06, 2018 at 08:16:56PM +0200, Jyri Sarha wrote: > > I have not been following the subject for half a year now. Just let me > know if I can do something to help land this patch, e.g. rebase and > resend it. I guess I can just pick it up and repost along with my i915 stuff. I can just

[Bug 102423] kwin segfaults when Alt+Tabbing with windows thumbnails on AMDGPU

https://bugs.freedesktop.org/show_bug.cgi?id=102423 --- Comment #6 from pmarget...@gmail.com --- Plasma updated to 5.12 today, and I no longer can reproduce this bug. I guess this was on their end afterall. -- You are receiving this mail because: You are the assignee for the

[PATCH 5/5 v3] drm/pl111: Support multiple endpoints on the CLCD

The Versatile PL110 implementations use multiple endpoints: from the PL111 port, the lines are routed through a PLD, and from there forked so the same lines go to a VGA DAC and an external TFT panel connector. This is discrete wireing so there is no way to turn of one output, i.e. this is really

[PATCH 4/5 v3] drm/pl111: Support variants with broken VBLANK

The early Integrator CLCD synthesized in the Integrator CP and IM-PD1 FPGAs are broken: their vertical and next base interrupts are not functional. Support these variants by simply disabling the use of the vblank interrupt on these variants. Reviewed-by: Eric Anholt

[PATCH 3/5 v3] drm/pl111: Support variants with broken clock divider

The early Integrator CLCD synthesized in the Integrator CP and IM-PD1 FPGAs are broken: their clock dividers do not work properly. Support disabling the clock divider and drive the clock directly from the parent under these circumstances. Reviewed-by: Eric Anholt Signed-off-by:

[PATCH 2/5 v3] drm/pl111: Handle the Versatile RGB/BGR565 mode

The ARM Versatile series can do RGB/BGR565 with an external "PLD" (Programmable Logical Device). However the CLCD does not have control bits for this, so it needs to be set into the ordinary 16BPP mode, then the RGB/BGR565 handling of the pixel data is handled by configuring the PLD through the

[PATCH libdrm] drm: Fix 32-bit drmSyncobjWait.

Otherwise we get an EFAULT, at least on a 64-bit kernel. Fixes: 2048a9e7 "drm: add drmSyncobjWait wrapper" --- xf86drm.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/xf86drm.c b/xf86drm.c index 74b4e230..1e87610b 100644 --- a/xf86drm.c +++ b/xf86drm.c @@ -4271,7 +4271,7 @@

Re: [PATCH 0/4] tree-wide: fix comparison to bitshift when dealing with a mask

> I found two more using "git grep 'define.*0x[0-9a-f]* < '": I added '[0-9]\+' at the end of the regex to reduce the number of false positives... > drivers/net/can/m_can/m_can.c:#define RXFC_FWM_MASK (0x7f < > RXFC_FWM_SHIFT) > drivers/usb/gadget/udc/goku_udc.h:#define INT_EPnNAK(n) >

Re: [PATCH libdrm] drm: Fix 32-bit drmSyncobjWait.

Am 06.02.2018 um 11:23 schrieb Bas Nieuwenhuizen: Otherwise we get an EFAULT, at least on a 64-bit kernel. Fixes: 2048a9e7 "drm: add drmSyncobjWait wrapper" Reviewed-by: Christian König --- xf86drm.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff

Re: [PATCH 1/2] fbdev: don't select I2C directly

On Fri, Feb 2, 2018 at 12:59 PM, Arnd Bergmann wrote: > On Fri, Feb 2, 2018 at 1:21 AM, Randy Dunlap wrote: >> b. DRM configuration is a mess. You shouldn't want to follow their model. :) > > Right, that should also be fixed, so DRM no longer includes I2C

Re: [PATCH 4/5 v2] drm/pl111: Support variants with broken VBLANK

On Sun, Feb 4, 2018 at 12:44 AM, Eric Anholt wrote: > Linus Walleij writes: > >> The early Integrator CLCD synthesized in the Integrator CP and >> IM-PD1 FPGAs are broken: their vertical and next base interrupts >> are not functional. Support these

Re: Questions on page flips and atomic modeset

Hello, Ville! Thank you very much for such a comprehensive answer. Please see inline On 02/05/2018 06:47 PM, Ville Syrjälä wrote: On Mon, Feb 05, 2018 at 06:03:25PM +0200, Oleksandr Andrushchenko wrote: Hello, I have a DRM driver which implements display protocol for Xen [1] and this

[PATCH 1/5 v3] drm/pl111: Properly detect the ARM PL110 variants

With a bit of refactoring we can contain the variant data for the strange PL110 versions that is feature-incomplete PL110 for the ARM Integrator/CP and somewhere inbetween PL110 and PL111 for the ARM Versatile AB and Versatile PB. We also accomodate for the custom duct-taped RGB565/BGR565 support

Re: [PATCH v3 1/7] drm/panel: simple: add support for Ampire AM-800480AYTZQW-00H

Hi Jagan, On Sun, 2018-02-04 at 23:19 +0530, Jagan Teki wrote: > This adds support for the Ampire AM-800480AYTZQW-00H 7.0" WGA LCD, > which can be supported by the simple panel driver. > > Signed-off-by: Jagan Teki > Reviewed-by: Rob Herring > --- >

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

Nice work, but a few comments. First of all you need to reorder the patches. Adding the exceptions to the restrictions should come first, then the restriction itself. Otherwise we might break a setup in between the patches and that is bad for bisecting. Then make all values configurable,

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

Move the new call out of ttm_mem_global_reserve() and into ttm_page_alloc.c or ttm_page_alloc_dma.c (but keep it in ttm_memory.c). ttm_mem_global_reserve() is called for each page allocated and si_mem_available() is a bit to heavy for that. Good idea! Agree with you completely,

[PATCH v4 3/6] drm/tegra: Let core take care of normalizing the zpos

Instead of re-implementing the drm_atomic_helper_check() locally with just adding drm_atomic_normalize_zpos() into it, set the drm_mode_config->normalize_zpos. Signed-off-by: Peter Ujfalusi CC: Thierry Reding Acked-by: Daniel Vetter

[PATCH v4 2/6] drm/exynos: Let core take care of normalizing the zpos

Instead of re-implementing the drm_atomic_helper_check() locally with just adding drm_atomic_normalize_zpos() into it, set the drm_mode_config->normalize_zpos. Signed-off-by: Peter Ujfalusi CC: Inki Dae CC: Joonyoung Shim

[PATCH v4 4/6] drm/sti: Let core take care of normalizing the zpos

Instead of re-implementing the drm_atomic_helper_check() locally with just adding drm_atomic_normalize_zpos() into it, set the drm_mode_config->normalize_zpos. Note: the drm_atomic_helper_check() now includes if (state->legacy_cursor_update) state->async_update =

[PATCH v4 0/6] drm: zpos normalization cleanup and omapdrm to use it

Hi, Changes since v3: - Moved the new normalize_zpos bool to be around another bools - Extended the commit message for sti that the drm_atomic_helper_check() is going to ask for async_update due to the legacy cursor usage. Changes since v2: - Fixed commit messages

[PATCH v4 1/6] drm: Add drm_mode_config->normalize_zpos boolean

Instead of drivers duplicating the drm_atomic_helper_check() code to be able to normalize the zpos they can use the normalize_zpos flag to let the drm core to do it. Signed-off-by: Peter Ujfalusi --- drivers/gpu/drm/drm_atomic_helper.c | 11 +++

[PATCH v4 6/6] drm/omap: Use normalized zpos for plane placement

Planes with identical zpos value will result undefined behavior: disappearing planes, screen flickering and it is not supported by the hardware. Use normalized zpos to make sure that we don't encounter invalid configuration. Signed-off-by: Peter Ujfalusi CC: Tomi

[PATCH v4 5/6] drm: rcar-du: Let core take care of normalizing the zpos

Set the drm_mode_config->normalize_zpos and call drm_atomic_helper_check() from rcar_du_atomic_check() instead of re implementing the function locally. Signed-off-by: Peter Ujfalusi CC: Laurent Pinchart Acked-by: Daniel Vetter

[PATCH 3/3] drm/pl111: Use max memory bandwidth for resolution

We were previously selecting 1024x768 and 32BPP as the default set-up for the PL111 consumers. This does not work on elder systems: the device tree bindings support a property "max-memory-bandwidth" in bytes/second that states that if you exceed this the memory bus will saturate. The result is

[PATCH 2/3] drm/pl111: Make the default BPP a per-variant variable

The PL110, Integrator and Versatile boards strongly prefer to use 16 BPP even if other modes are supported, both to keep down memory consumption and also to easier find a good match to supported resolutions with consideration taken to the memory bandwidth of the platforms. Signed-off-by: Linus

[PATCH 1/3] drm: simple_kms_helper: Add mode_valid() callback support

The PL111 needs to filter valid modes based on memory bandwidth. I guess it is a pretty simple operation, so we can still claim the DRM KMS helper pipeline is simple after adding this (optional) vtable callback. Signed-off-by: Linus Walleij ---

[PATCH 0/3] Bandwidth limitation on PL111, take 2

I had to add a hook into the simple KMS helper to be able to gate off too high bandwidths on the PL111. Let me know what you think. This solution is inspired by the OMAPDRM commit a7631c4b9846 "drm/omap: Filter displays mode based on bandwidth limit" by Peter Ujfalusi. I'm not super-happy that

Re: [PATCH v3 03/20] kconfig: Remove leftover references to AVR32 symbol

On Mon, Feb 05, 2018 at 08:05:39PM +0100, Ulf Magnusson wrote: > The AVR32 symbol was removed in commit 26202873bb51 ("avr32: remove > support for AVR32 architecture"). Remove the remaining references to it > from the Kconfig files. > drivers/spi/Kconfig | 2 +- >

[PATCH] drm/amd/powerplay: delete some dead code

We deleted some code in e154162ef75d ("drm/amd/powerplay: refine pp code for raven") but there were a few related bits that were missed. Let's delete them as well. Signed-off-by: Dan Carpenter diff --git a/drivers/gpu/drm/amd/powerplay/inc/hwmgr.h

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

On 02/05/2018 05:03 PM, Gerd Hoffmann wrote: On Mon, Feb 05, 2018 at 03:46:17PM +0100, Tomeu Vizoso wrote: On 02/05/2018 01:20 PM, Gerd Hoffmann wrote: Hi, Why not use virtio-vsock to run the wayland protocol? I don't like the idea to duplicate something with very simliar functionality

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

[Bug 104216] Firefox quirks (black and/or white squares)

https://bugs.freedesktop.org/show_bug.cgi?id=104216 --- Comment #15 from Germano Massullo --- I am trying to build Mesa 17.0.5 but I had no success, even passing the older llvm to the old compiler. I had not the time to go deeper and check what happened to the build

[Bug 100979] Radeon r4 on a6-6310(BEEMA) APU hard lockup on hibernate and on second resume from suspend

https://bugs.freedesktop.org/show_bug.cgi?id=100979 --- Comment #12 from Przemek --- The valid mailing list post, when it comes to messages "swiotlb buffer is full" and "swiotlb: coherent allocation failed", is: https://lkml.org/lkml/2018/1/10/132. Thanks to Alex Deucher

[Bug 104082] amdgpu 0000:07:00.0: swiotlb buffer is full (sz: 2097152 bytes)

https://bugs.freedesktop.org/show_bug.cgi?id=104082 --- Comment #14 from Przemek --- Yes, sorry, my bad. Wrong copy-paste action here. Thanks Alex. -- You are receiving this mail because: You are the assignee for the bug.___

[PATCH 0/2] GPU-DRM-TILCDC: Adjustments for seven function implementations

From: Markus Elfring Date: Tue, 6 Feb 2018 22:17: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 in seven functions Use common error handling

[PATCH 2/2] drm/tilcdc: panel: Use common error handling code in of_get_panel_info()

From: Markus Elfring Date: Tue, 6 Feb 2018 22:10:11 +0100 Add a jump target so that a bit of exception handling can be better reused at the end of this function. Signed-off-by: Markus Elfring ---

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

https://bugzilla.kernel.org/show_bug.cgi?id=198669 --- Comment #9 from ro...@beardandsandals.co.uk (ro...@beardandsandals.co.uk) --- I think we have to agree to differ on this one. You seem to be focussing on the software interface between the GPU and the driver. What follows is my personal

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

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 since the former can sleep,

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

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 do not apply across the entire display driver (eg: to avoid >

Re: [PATCH] drm: Add optional COLOR_ENCODING and COLOR_RANGE properties to drm_plane

I have not been following the subject for half a year now. Just let me know if I can do something to help land this patch, e.g. rebase and resend it. On 02/06/18 20:08, Hans Verkuil wrote: > On 02/06/2018 06:58 PM, Ville Syrjälä wrote: >> On Mon, Jun 12, 2017 at 12:10:04AM +0300, Jyri Sarha

[Bug 104082] amdgpu 0000:07:00.0: swiotlb buffer is full (sz: 2097152 bytes)

https://bugs.freedesktop.org/show_bug.cgi?id=104082 --- Comment #13 from Alex Deucher --- https://lkml.org/lkml/2018/1/10/132 -- You are receiving this mail because: You are the assignee for the bug.___ dri-devel mailing list

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

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 since the former can sleep, and the latter is running under IRQ > context. > > To workaround this, we record the

[PATCH 1/2] drm/tilcdc: Delete an error message for a failed memory allocation in seven functions

From: Markus Elfring Date: Tue, 6 Feb 2018 21:51:15 +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/powerplay: delete some dead code

On Tue, Feb 6, 2018 at 7:35 AM, Dan Carpenter wrote: > We deleted some code in e154162ef75d ("drm/amd/powerplay: refine pp code > for raven") but there were a few related bits that were missed. Let's > delete them as well. > > Signed-off-by: Dan Carpenter

[PATCH] configure/Makefile.am: use pkg-config to discover libatomic_ops

From: Thomas Petazzoni The configure script currently tests the availability of libatomic_ops by checking the presence of atomic_ops.h. While this is good enough as an availability test, it is not sufficient as on some platforms, libatomic_ops provides an

[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 #1 from Alex Deucher --- Does booting with radeon.bapm=0 or radeon.bapm=1 on the kernel command line in grub help? -- You are receiving this mail because: You are the assignee for the

Re: Atomic driver and old remove FB behavior

Hello, Maarten! On 02/01/2018 12:13 PM, Oleksandr Andrushchenko wrote: On 02/01/2018 12:04 PM, Maarten Lankhorst wrote: Op 01-02-18 om 08:08 schreef Oleksandr Andrushchenko: Hi, all! I am working on a para-virtualized frontend DRM driver for Xen [1] which implements display device I/O

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

On Tue, Feb 06, 2018 at 04:04:10PM +, Chris Wilson wrote: > Quoting Tvrtko Ursulin (2018-02-06 14:31:07) > > +static u64 read_rc6_residency(struct drm_i915_private *i915) > > +{ > > + u64 val; > > + > > + val = intel_rc6_residency_ns(i915, IS_VALLEYVIEW(i915) ? > > +

[PATCH 1/3] 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: -

[PATCH 2/3] 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 0/3] 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

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

https://bugzilla.kernel.org/show_bug.cgi?id=198669 --- Comment #8 from Christian König (christian.koe...@amd.com) --- (In reply to ro...@beardandsandals.co.uk from comment #7) > The original point I made in the bug report was that this bug is not about > the mechanical hardware glitch. It as

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

On Mon, 5 Feb 2018 17:03:22 +0100 Gerd Hoffmann wrote: > On Mon, Feb 05, 2018 at 03:46:17PM +0100, Tomeu Vizoso wrote: > > On 02/05/2018 01:20 PM, Gerd Hoffmann wrote: > > >Hi, > > > > > Hmm. I allways assumed the wayland client allocates the buffers, not > the

Thinkpad X1 Carbon 3rd - Reducing the compressed framebuffer size

Hi! I'm periodically getting following message in dmesg on Lenovo Thinkpad X1 Carbon 3rd generation: [drm] Reducing the compressed framebuffer size. This may lead to less power savings than a non-reduced-size. Try to increase stolen memory size if available in BIOS. In BIOS I already set GPU

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

Quoting Tvrtko Ursulin (2018-02-06 14:31:07) > +static u64 read_rc6_residency(struct drm_i915_private *i915) > +{ > + u64 val; > + > + val = intel_rc6_residency_ns(i915, IS_VALLEYVIEW(i915) ? > + VLV_GT_RENDER_RC6 : > GEN6_GT_GFX_RC6); > +

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

On 06/02/2018 16:10, Imre Deak wrote: On Tue, Feb 06, 2018 at 04:04:10PM +, Chris Wilson wrote: Quoting Tvrtko Ursulin (2018-02-06 14:31:07) +static u64 read_rc6_residency(struct drm_i915_private *i915) +{ + u64 val; + + val = intel_rc6_residency_ns(i915, IS_VALLEYVIEW(i915) ?

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

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 drm_crtc_vblank_count() to u64. This could cause > potential problems if the return value is used in arithmetic operations > with a 32-bit

[radeon-alex:amd-staging-drm-next 1/3] drivers/gpu/drm/amd/amdgpu/../powerplay/hwmgr/rv_hwmgr.c:1067:3: error: 'const struct pp_hwmgr_func' has no member named 'set_mmhub_powergating_by_smu'

tree: git://people.freedesktop.org/~agd5f/linux.git amd-staging-drm-next head: 987aae1f47ba0fe5a320d013d2bf97b5f9922761 commit: 6bea4fd090e45704decd1abf47431ad1c1e56977 [1/3] drm/amd/powerplay: implement set_mmhub_powergating_by_smu for Raven config: ia64-allmodconfig (attached as .config)

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

On Tue, Feb 06, 2018 at 03:23:02PM +0100, Gerd Hoffmann wrote: > > Creation of shareable buffer by guest > > - > > > > 1. Client requests virtio driver to create a buffer suitable for sharing > > with host (DRM_VIRTGPU_RESOURCE_CREATE) > > client

[radeon-alex:amd-staging-drm-next 85/381] sound/soc//amd/raven/acp3x-pcm-dma.c:246:10: error: implicit declaration of function 'page_to_phys'; did you mean 'page_to_pfn'?

Hi Maruthi, FYI, the error/warning still remains. tree: git://people.freedesktop.org/~agd5f/linux.git amd-staging-drm-next head: 987aae1f47ba0fe5a320d013d2bf97b5f9922761 commit: 4ab7d004f9ff2e877caa267887360e1804b4edcf [85/381] ASoC: AMD: enable ACP3x drivers build config: tile-allyesconfig

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

This driver creates DRM encoder and connector for ZynqMP DisplayPort. Signed-off-by: Hyun Kwon Acked-by: Daniel Vetter --- v2 - Change the SPDX identifier format - Split drm properties into a separate patch --- --- drivers/gpu/drm/xlnx/zynqmp_dp.c

[PATCH v5 3/5] drm: xlnx: DRM KMS driver for Xilinx ZynqMP DP subsystem display

Xilinx ZynqMP has a hardened display pipeline. The pipeline can be logically partitioned into 2 parts: display controller and DisplayPort encoder / transmitter. This driver handles the display controller part of the pipeline that handles buffer management and blending. Signed-off-by: Hyun Kwon

[PATCH v5 2/5] dt-bindings: display: xlnx: Add ZynqMP DP subsystem bindings

This add a dt binding for ZynqMP DP subsystem. Signed-off-by: Hyun Kwon Reviewed-by: Rob Herring --- v4 - Specify phy related descriptions - Specify dma related descriptions - Remove ports - Remove child nodes for layers - Update the example accordingly v2

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

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, hardened pipeline can also interact with soft logics in FPGA. The Xilinx DRM KMS module is to integrate

[PATCH v5 5/5] drm: xlnx: ZynqMP DP subsystem DRM KMS driver

This is a wrapper around the ZynqMP Display and DisplayPort drivers. Signed-off-by: Hyun Kwon Acked-by: Daniel Vetter --- v4 - Use the newly added xlnx pipeline calls to initialize drm device v2 - Change the SPDX identifier format --- ---

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

Hi, Roger, On 02/06/2018 10:04 AM, Roger He wrote: currently ttm code has no any allocation limit. So it allows pages allocatation unlimited until OOM. Because if swap space is full of swapped pages and then system memory will be filled up with ttm pages. and then any memory allocation request

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

From: Tvrtko Ursulin We are not allowed to call intel_runtime_pm_get from the PMU counter read callback since the former can sleep, and the latter is running under IRQ context. To workaround this, we start our timer when we detect that we have failed to obtain a

Re: [PATCH v3 03/20] kconfig: Remove leftover references to AVR32 symbol

On Mon, Feb 5, 2018 at 8:05 PM, Ulf Magnusson wrote: > The AVR32 symbol was removed in commit 26202873bb51 ("avr32: remove > support for AVR32 architecture"). Remove the remaining references to it > from the Kconfig files. > > Signed-off-by: Ulf Magnusson

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

On 02/07/2018 02:09 AM, Michael S. Tsirkin wrote: On Tue, Feb 06, 2018 at 03:23:02PM +0100, Gerd Hoffmann wrote: Creation of shareable buffer by guest - 1. Client requests virtio driver to create a buffer suitable for sharing with host

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

From: Tvrtko Ursulin We are not allowed to call intel_runtime_pm_get from the PMU counter read callback since the former can sleep, and the latter is running under IRQ context. To workaround this, we record the last known RC6 and while runtime suspended estimate its

[PATCH v2] Documentation/ABI: add sysfs interface for s6e63m0 lcd driver

Document sysfs attributes of s6e63m0 lcd panel driver by looking through git logs and reading code. Signed-off-by: Aishwarya Pant --- Changes in v2: - Update contact information Documentation/ABI/testing/sysfs-class-lcd-s6e63m0 | 27 +++ 1 file changed,

[PATCH v4 3/3] drm/i915: Fix DSI panels with v1 MIPI sequences without a DEASSERT sequence v3

So far models of the Dell Venue 8 Pro, with a panel with MIPI panel index = 3, one of which has been kindly provided to me by Jan Brummer, where not working with the i915 driver, giving a black screen on the first modeset. The problem with at least these Dells is that their VBT defines a MIPI

[PATCH] video: fbdev: vermilion: use 64-bit arithmetic instead of 32-bit

Cast _pitch_ to u64 in order to give the compiler complete information about the proper arithmetic to use. Notice that this variable is being used in a context that expects an expression of type u64 (64 bits, unsigned). The expression pitch * var->yres_virtual is currently being evaluated using

[PATCH v4 1/3] drm/i915: Add intel_bios_cleanup() function

Add an intel_bios_cleanup() function to act as counterpart of intel_bios_init() and move the cleanup of vbt related resources there, putting it in the same file as the allocation. Signed-off-by: Hans de Goede --- drivers/gpu/drm/i915/i915_drv.c | 14 +-

Re: [PATCH v3 03/20] kconfig: Remove leftover references to AVR32 symbol

On Tue, Feb 6, 2018 at 1:08 PM, Mark Brown wrote: > On Mon, Feb 05, 2018 at 08:05:39PM +0100, Ulf Magnusson wrote: >> The AVR32 symbol was removed in commit 26202873bb51 ("avr32: remove >> support for AVR32 architecture"). Remove the remaining references to it >> from the

[PATCH v4 2/3] drm/i915: Free memdup-ed DSI VBT data structures on driver_unload

Make intel_bios_cleanup function free the DSI VBT data structures which are memdup-ed by parse_mipi_config() and parse_mipi_sequence(). Signed-off-by: Hans de Goede --- drivers/gpu/drm/i915/intel_bios.c | 6 ++ 1 file changed, 6 insertions(+) diff --git

[PATCH] video: console: kconfig: Remove AVR32 dep. from VGA_CONSOLE

The AVR32 symbol was removed in commit 26202873bb51 ("avr32: remove support for AVR32 architecture"). Signed-off-by: Ulf Magnusson --- drivers/video/console/Kconfig | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/video/console/Kconfig

[PATCH] spi: kconfig: Remove AVR32 dep. from SPI_ATMEL

The AVR32 symbol was removed in commit 26202873bb51 ("avr32: remove support for AVR32 architecture"). Signed-off-by: Ulf Magnusson --- drivers/spi/Kconfig | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/spi/Kconfig b/drivers/spi/Kconfig index

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

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

Re: [PATCH 0/4] tree-wide: fix comparison to bitshift when dealing with a mask

Hi Wolfram, On Mon, Feb 5, 2018 at 9:09 PM, Wolfram Sang wrote: > In one Renesas driver, I found a typo which turned an intended bit shift > ('<<') > into a comparison ('<'). Because this is a subtle issue, I looked tree wide > for > similar patterns. This

[PATCH v2 0/3] backlight: document sysfs interfaces

Patchset contains documentation of the sysfs interfaces for the following five backlight drivers- 1) lm3639 2) adp5520 3) adp8860 It was compiled from data sheets, reading code and git history logs. In v2 of the patches, documentation for lp8788 and lp855x devices was dropped as the attributes

[PATCH 5/5] drm/ttm: add input parameter allow_allo_anyway for ttm_bo_evict_mm

if true for it, allocate TTM pages regardless of zone global memory account limit. that is for another special case: suspend. doesn't care the zone global memory account limit for this case. Signed-off-by: Roger He --- drivers/gpu/drm/amd/amdgpu/amdgpu_debugfs.c | 2 +-

Re: [PATCH v1 2/2] drm/panel: otm8009a: Add support for the optional power-supply

Reviewed-by: Yannick Fertré On 02/05/2018 10:45 AM, Philippe Cornu wrote: > Add support for the optional power-supply. > > Note: A "dummy regulator" is returned by devm_regulator_get() > if the optional regulator is not present in the device tree, > simplifying the source

[Bug 102389] Random black screen on RX 470, HDMI 4k-60Hz

https://bugs.freedesktop.org/show_bug.cgi?id=102389 --- Comment #9 from jeremi.jasin...@gmail.com --- I still have this problem, on linux 4.15 on KDE Neon with dc enabled. So I bought DP to HDMI active converter, which supports 4k 60hz. While using this converter and the same HDMI cable,

[PATCH 0/5] prevent OOM triggered by TTM

currently ttm code has no any allocation limit. So it allows pages allocatation unlimited until OOM. Because if swap space is full of swapped pages and then system memory will be filled up with ttm pages. and then any memory allocation request will trigger OOM. the following patches is for

[PATCH 2/5] drm/ttm: keep original behavior except with flag no_retry

set the no_retry flag in struct ttm_mem_global and init it after ttm_mem_global_init Signed-off-by: Roger He --- drivers/gpu/drm/amd/amdgpu/amdgpu_ttm.c | 8 +--- drivers/gpu/drm/ttm/ttm_memory.c| 3 +++ include/drm/ttm/ttm_memory.h| 3 +++ 3 files

[PATCH 1/5] drm/ttm: check if the free swap space is under limit 256MB

for avoid OOM. if free swap space is less than 256MB, reject the TTM page allocation. Otherwise, swap space will be full of swapped pages and then system memory will be filled up with ttm pages. and then any memory allocation request will trigger OOM. to cover two cases: a. If total swap space >

[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 #23 from Bong Cosca --- Created attachment 137183 --> https://bugs.freedesktop.org/attachment.cgi?id=137183=edit Video BIOS Attached video BIOS may also prove useful in isolating this bug in the graphics

  1   2   >