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

On Wed, Feb 07, 2018 at 09:32:35PM +, Pandiyan, Dhinakaran wrote: > > > > 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: > > > >

Re: [PATCH v7 1/6] base: power: runtime: Export pm_runtime_get/put_suppliers

Hi Vivek, On Wed, Feb 7, 2018 at 7:31 PM, Vivek Gautam wrote: > The device link allows the pm framework to tie the supplier and > consumer. So, whenever the consumer is powered-on the supplier > is powered-on first. > > There are however cases in which the consumer

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

On Mon, 12 Feb 2018 12:45:40 +0100 Gerd Hoffmann wrote: > Hi, > > > >(a) software rendering: client allocates shared memory buffer, renders > > >into it, then passes a file handle for that shmem block together > > >with some meta data (size, format, ...)

[Bug 105021] suspend / rx550 / extremely slow after 2nd thaw

https://bugs.freedesktop.org/show_bug.cgi?id=105021 --- Comment #7 from arne_woer...@yahoo.com --- 4.15.3-1-ARCH has that bug, too... -arne -- You are receiving this mail because: You are the assignee for the bug.___ dri-devel mailing list

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

On Mon, Feb 12, 2018 at 06:11:57PM +, Kieran Bingham wrote: > + adv7511->i2c_packet = i2c_new_secondary_device(i2c, "packet", > + ADV7511_PACKET_I2C_ADDR_DEFAULT); > + if (!adv7511->i2c_packet) { > + ret = -EINVAL; > + goto

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

Hi Ville, As per our last discussion, following points were discussed: 1. To suppress the aspect-ratio info from getblob ioctl to a user that does not support it: i. A new flag must be added to drm_blob_property to mark if the blob has mode data. ii. This flag must be set when the

Re: [RFC][PATCH 4/4 v2] drm_hwcomposer: Try to fallback if GLCompisition fails

On Wed, Jan 31, 2018 at 11:03 AM, John Stultz wrote: > On Wed, Jan 31, 2018 at 10:51 AM, Alexandru-Cosmin Gheorghe > wrote: >> It seems that we don't pass any explicit fences to the kernel for >> IN_FENCE_FD property. This particular

[Bug 105018] Kernel panic when waking up after screen goes blank.

https://bugs.freedesktop.org/show_bug.cgi?id=105018 --- Comment #7 from L.S.S. --- And I just crashed my system the same usual way. With those parameters set there are some additional outputs besides the usual ones. Feb 13 11:31:55 linuxsys kernel:

[Bug 105018] Kernel panic when waking up after screen goes blank.

https://bugs.freedesktop.org/show_bug.cgi?id=105018 --- Comment #6 from L.S.S. --- Created attachment 137308 --> https://bugs.freedesktop.org/attachment.cgi?id=137308=edit dmesg output with amdgpu.dc_log=1 and drm.debug=6, right after login. I'm not sure to what

Re: [PATCH] virgl: fix caps ioctl size check.

On Mon, Feb 12, 2018 at 4:26 PM, Dave Airlie wrote: > From: Dave Airlie > > The size check seems backwards, if userspace gives us a size > larger it is probably asking for a newer version of the caps, > so we just fill in the caps version we have at the

[PATCH] virgl: fix caps ioctl size check.

From: Dave Airlie The size check seems backwards, if userspace gives us a size larger it is probably asking for a newer version of the caps, so we just fill in the caps version we have at the smaller size, and it can work it out from there. Userspace will probably still need

Re: [PATCH 6/7] vulkan: Add new VK_MESA_query_timestamp extension

Quoting Keith Packard (2018-02-09 20:45:15) > This extension adds a single function to query the current GPU > timestamp, just like glGetInteger64v(GL_TIMESTAMP, ). This > function is needed to complete the implementation of > GOOGLE_display_timing, which needs to be able to coorelate GPU and CPU

Re: [PATCH 3/7] vulkan: Add EXT_acquire_xlib_display

Quoting Keith Packard (2018-02-09 20:45:12) > This extension adds the ability to borrow an X RandR output for > temporary use directly by a Vulkan application. For DRM, we use the > Linux resource leasing mechanism. > > Signed-off-by: Keith Packard > --- > configure.ac

[Bug 68857] [cypress] SNU OpenCL NAS Parallel Benchmarks don't work

https://bugs.freedesktop.org/show_bug.cgi?id=68857 Jan Vesely changed: What|Removed |Added Summary|SNU OpenCL NAS Parallel |[cypress] SNU

[Bug 105042] [LLVM Regression] Shadow of Mordor stucks at intro video

https://bugs.freedesktop.org/show_bug.cgi?id=105042 Andy Furniss changed: What|Removed |Added CC||adf.li...@gmail.com

[Bug 105042] [LLVM Regression] Shadow of Mordor stucks at intro video

https://bugs.freedesktop.org/show_bug.cgi?id=105042 --- Comment #3 from Bas Nieuwenhuizen --- There is a git mirror for LLVM: https://github.com/llvm-mirror/llvm wrt the nir crash I doubt that is due to LLVM, might be because we only enabled compute shaders for nir

Re: [Mesa-dev] [PATCH 1/7] vulkan: Add KHR_display extension to anv and radv using DRM

Emil Velikov writes: > A few top level comments: Thanks much for looking over this code. I realize it's a large amount of change and hence more work to review. > - using card/primary node and (missing) authentication > Current code opens the primary node when

Re: [PATCH 1/7] vulkan: Add KHR_display extension to anv and radv using DRM

Eric Engestrom writes: > copy/paste error: s/drm/display/ That's actually intentional -- any system which supports 'drm' can support the display backend as it's based on that. Maybe it should use a different test? (note that I haven't been using the autotools backend

Re: [PATCH hwc v2 3/6] drm_hwcomposer: Submit in-fence to DRM

On Wed, Sep 27, 2017 at 1:55 PM, Sean Paul wrote: > On Wed, Sep 27, 2017 at 7:58 AM, Robert Foss > wrote: >> Add support for in-fences through the IN_FENCE_FD property. In-fences signal >> when their associated buffer may be read by DRM/KMS. >>

[PATCH v3 5/5] drm: adv7511: Add support for i2c_new_secondary_device

From: Kieran Bingham 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 to override the default addresses so that

[PATCH v3 2/5] dt-bindings: adv7511: Add support for i2c_new_secondary_device

From: Kieran Bingham 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. Extend the device tree node bindings to be able to override the

[PATCH v3 4/5] media: adv7604: Add support for i2c_new_secondary_device

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 address and acts as a standard slave device on the I²C bus. Allow a device tree node to override the default addresses so that

[PATCH v3 3/5] [RFT] ARM: dts: wheat: Fix ADV7513 address usage

From: Kieran Bingham The r8a7792 Wheat board has two ADV7513 devices sharing a single i2c bus, however in low power mode the ADV7513 will reset it's slave maps to use the hardware defined default addresses. The ADV7511 driver was adapted to allow the two

[PATCH v3 0/5] Add support for i2c_new_secondary_device

From: Kieran Bingham Back in 2014, Jean-Michel provided patches [0] to implement a means of describing software defined I2C addresses for devices through the DT nodes. The patch to implement the function "i2c_new_secondary_device()" was integrated, but

[PATCH v3 1/5] dt-bindings: media: adv7604: Add support for i2c_new_secondary_device

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 address and acts as a standard slave device on the I²C bus. Extend the device tree node bindings to be able to override the

[PATCH v2 4/4] drm: NULL pointer dereference [null-pointer-deref] (CWE 476) problem

The Parfait (version 2.1.0) static code analysis tool found the following NULL pointer derefernce problem. - drivers/gpu/drm/drm_vblank.c Null pointer checks were added to return values from calls to drm_crtc_from_index(). There is a possibility, however minute, that crtc->index may not be found

[PATCH v2 2/4] drm: NULL pointer dereference [null-pointer-deref] (CWE 476) problem

The Parfait (version 2.1.0) static code analysis tool found the following NULL pointer derefernce problem. - drivers/gpu/drm/drm_dp_mst_topology.c The call to drm_dp_calculate_rad() in function drm_dp_port_setup_pdt() could result in a NULL pointer being returned to port->mstb due to a failure to

[Bug 92827] Tonga: No Sound over HDMI with connected AV receiver

https://bugs.freedesktop.org/show_bug.cgi?id=92827 --- Comment #12 from Harry Wentland --- Looks like the conversation steered away from audio. Please use a new ticket or comment on existing tickets dealing with wrong modes, such as

[PATCH v2 3/4] drm: NULL pointer dereference [null-pointer-deref] (CWE 476) problem

The Parfait (version 2.1.0) static code analysis tool found the following NULL pointer derefernce problem. - drivers/gpu/drm/drm_edid.c The call to drm_cvt_mode() in function drm_mode_std() for the HDTV hack resulted in the possibility of accessing a NULL pointer if drm_mode_std() returned NULL.

[PATCH v2 1/4] drm: NULL pointer dereference [null-pointer-deref] (CWE 476) problem

The Parfait (version 2.1.0) static code analysis tool found the following NULL pointer dereference problem. - drivers/gpu/drm/drm_drv.c Any calls to drm_minor_get_slot() could result in the return of a NULL pointer when an invalid DRM device type is encountered. 2 helper functions where added

[PATCH v2 0/4] Parfait changes

The following patch(s) are bugs found by the static compiler 'Parfait'. Care was taken to make sure false positive results were removed from this patchset. Parfait Overview https://labs.oracle.com/pls/apex/f?p=labs:49:P49_PROJECT_ID:13 v1: Initial release v2: - Split

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

On Tue, Feb 06, 2018 at 03:12:38PM +0100, Hans de Goede wrote: > 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 Reviewed-by: Ville Syrjälä

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

On Tue, Feb 06, 2018 at 03:12:37PM +0100, Hans de Goede wrote: > 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

[Bug 103736] Sudden system freezes, GPU fault detected

https://bugs.freedesktop.org/show_bug.cgi?id=103736 --- Comment #9 from Ernst Sjöstrand --- I get [ 133.978908] amdgpu :09:00.0: GPU fault detected: 147 0x00198802 [ 133.978911] amdgpu :09:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x0053 [ 133.978912] amdgpu

Re: [PATCH] drm/amdgpu: replace iova debugfs file with iomem (v2)

On 12/02/18 12:16 PM, Christian König wrote: Am 12.02.2018 um 17:40 schrieb Tom St Denis: On 09/02/18 01:44 PM, Christian König wrote: Am 09.02.2018 um 19:19 schrieb Tom St Denis: On 09/02/18 01:17 PM, Christian König wrote: Am 09.02.2018 um 18:28 schrieb Tom St Denis: On 09/02/18 12:27 PM,

Re: [PATCH 0/5] Fix deadlock on runtime suspend in DRM drivers

On Mon, Feb 12, 2018 at 4:45 AM, Lukas Wunner wrote: > On Mon, Feb 12, 2018 at 09:03:26AM +, Mike Lothian wrote: >> On 12 February 2018 at 03:39, Lukas Wunner wrote: >> > On Mon, Feb 12, 2018 at 12:35:51AM +, Mike Lothian wrote: >> > > I've not been able

Re: [Intel-gfx] [PATCH 2/5] drm: Allow determining if current task is output poll worker

On Mon, Feb 12, 2018 at 05:50:12PM +, Chris Wilson wrote: > Quoting Lyude Paul (2018-02-12 17:46:11) > > On Sun, 2018-02-11 at 10:38 +0100, Lukas Wunner wrote: > > > Introduce a helper to determine if the current task is an output poll > > > worker. > > > > > > This allows us to fix a

Re: [PATCH v2 3/5] [RFT] ARM: dts: wheat: Fix ADV7513 address usage

Hi Lars, Thanks for your review! On 12/02/18 18:24, Lars-Peter Clausen wrote: > On 02/12/2018 07:11 PM, Kieran Bingham wrote: > [...] >> +/* >> + * The adv75xx resets its addresses to defaults during low power power >> + * mode. Because we have two ADV7513 devices on the same bus, we

Re: [PATCH v2 3/5] [RFT] ARM: dts: wheat: Fix ADV7513 address usage

On 02/12/2018 07:11 PM, Kieran Bingham wrote: [...] > + /* > + * The adv75xx resets its addresses to defaults during low power power > + * mode. Because we have two ADV7513 devices on the same bus, we must > + * change both of them away from the defaults so that they do not > +

[Bug 105046] Screen resolution reset to 1368x768 when turning monitor off

https://bugs.freedesktop.org/show_bug.cgi?id=105046 --- Comment #5 from Michael Zapf --- Created attachment 137305 --> https://bugs.freedesktop.org/attachment.cgi?id=137305=edit dmesg output after turning the monitor back on The turn-off event occured at time [75.336273].

[PATCH v2 5/5] drm: adv7511: Add support for i2c_new_secondary_device

From: Kieran Bingham 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 to override the default addresses so that

[PATCH v2 1/5] dt-bindings: media: adv7604: Add support for i2c_new_secondary_device

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 address and acts as a standard slave device on the I²C bus. Extend the device tree node bindings to be able to override the

[PATCH v2 2/5] dt-bindings: adv7511: Add support for i2c_new_secondary_device

From: Kieran Bingham 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. Extend the device tree node bindings to be able to override the

[PATCH v2 3/5] [RFT] ARM: dts: wheat: Fix ADV7513 address usage

From: Kieran Bingham The r8a7792 Wheat board has two ADV7513 devices sharing a single i2c bus, however in low power mode the ADV7513 will reset it's slave maps to use the hardware defined default addresses. The ADV7511 driver was adapted to allow the two

[PATCH v2 0/5] Add support for i2c_new_secondary_device

From: Kieran Bingham Back in 2014, Jean-Michel provided patches [0] to implement a means of describing software defined I2C addresses for devices through the DT nodes. The patch to implement the function "i2c_new_secondary_device()" was integrated, but

[PATCH v2 4/5] media: adv7604: Add support for i2c_new_secondary_device

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 address and acts as a standard slave device on the I²C bus. Allow a device tree node to override the default addresses so that

Re: [Intel-gfx] [PATCH 2/5] drm: Allow determining if current task is output poll worker

Quoting Lyude Paul (2018-02-12 17:46:11) > On Sun, 2018-02-11 at 10:38 +0100, Lukas Wunner wrote: > > Introduce a helper to determine if the current task is an output poll > > worker. > > > > This allows us to fix a long-standing deadlock in several DRM drivers > > wherein the ->runtime_suspend

Re: [PATCH 2/5] drm: Allow determining if current task is output poll worker

On Sun, 2018-02-11 at 10:38 +0100, Lukas Wunner wrote: > Introduce a helper to determine if the current task is an output poll > worker. > > This allows us to fix a long-standing deadlock in several DRM drivers > wherein the ->runtime_suspend callback waits for the output poll worker > to finish

Re: [PATCH 0/5] Fix deadlock on runtime suspend in DRM drivers

This patchset is a no-brainer for me. I'm ashamed to say I think I might have seen this issue before, but polling gets used so rarely nowadays it slipped under the rug by accident. Anyway, for the whole series (except patch #2, which I will respond to with a short comment in just a moment):

[Bug 105042] [LLVM Regression] Shadow of Mordor stucks at intro video

https://bugs.freedesktop.org/show_bug.cgi?id=105042 --- Comment #2 from Gregor Münch --- Im using pre-compiled llvm binaries- thus I have no packages to try in between. I know how to do a bisect with git but I somehow fail to do the same with svn. Maybe solution is actually

Re: [Intel-gfx] [PATCH] drm/i915: Improve PSR activation timing

On Sat, Feb 10, 2018 at 09:43:59AM +, Chris Wilson wrote: > Quoting Andy Lutomirski (2018-02-09 17:55:38) > > On Fri, Feb 9, 2018 at 7:39 AM, Rodrigo Vivi wrote: > > > Rodrigo Vivi writes: > > > So, I move the hacked scheduled to 10s and forced

Re: [PATCH] drm/amdgpu: replace iova debugfs file with iomem (v2)

Am 12.02.2018 um 17:40 schrieb Tom St Denis: On 09/02/18 01:44 PM, Christian König wrote: Am 09.02.2018 um 19:19 schrieb Tom St Denis: On 09/02/18 01:17 PM, Christian König wrote: Am 09.02.2018 um 18:28 schrieb Tom St Denis: On 09/02/18 12:27 PM, Tom St Denis wrote: From: Christian König

Re: [PATCH] drm: Use idr_init_base(1) when using id==0 for invalid

On Mon, Feb 12, 2018 at 02:55:33PM +, Chris Wilson wrote: > Use the new idr_init_base() function to create an IDR that knows id==0 > is never allocated as it maps to an invalid identifier. By knowing that > id==0 is invalid, the IDR can start from id=1 instead avoiding the issue > of having to

Re: [PATCH 1/5] workqueue: Allow retrieval of current task's work struct

Hello, On Sun, Feb 11, 2018 at 10:38:28AM +0100, Lukas Wunner wrote: > Introduce a helper to retrieve the current task's work struct if it is > a workqueue worker. > > This allows us to fix a long-standing deadlock in several DRM drivers > wherein the ->runtime_suspend callback waits for a

[Bug 198745] Blank screen on RX 580 with AMDGPU Display Core enabled

https://bugzilla.kernel.org/show_bug.cgi?id=198745 --- Comment #10 from Kyle De'Vir (kyle.de...@mykolab.com) --- Ah. None ~ just your average HDMI to HDMI cable. -- You are receiving this mail because: You are watching the assignee of the bug. ___

[Bug 105036] Blank screen on RX 580 with AMDGPU Display Core enabled

https://bugs.freedesktop.org/show_bug.cgi?id=105036 --- Comment #5 from kyle.de...@mykolab.com --- Created attachment 137304 --> https://bugs.freedesktop.org/attachment.cgi?id=137304=edit journalctl output for drm with amdgpu.dc_log=1 and drm.debug=6 -- You are receiving this mail because:

[Bug 105036] Blank screen on RX 580 with AMDGPU Display Core enabled

https://bugs.freedesktop.org/show_bug.cgi?id=105036 --- Comment #4 from kyle.de...@mykolab.com --- Created attachment 137303 --> https://bugs.freedesktop.org/attachment.cgi?id=137303=edit journalctl output for amdgpu with amdgpu.dc_log=1 and drm.debug=6 -- You are receiving this mail because:

[Bug 198745] Blank screen on RX 580 with AMDGPU Display Core enabled

https://bugzilla.kernel.org/show_bug.cgi?id=198745 --- Comment #9 from Alex Deucher (alexdeuc...@gmail.com) --- (In reply to Kyle De'Vir from comment #8) > What do you mean by dongle? Wifi? A display dongle (e.g., DP to HDMI adapter). -- You are receiving this mail because: You are watching

[Bug 198745] Blank screen on RX 580 with AMDGPU Display Core enabled

https://bugzilla.kernel.org/show_bug.cgi?id=198745 --- Comment #8 from Kyle De'Vir (kyle.de...@mykolab.com) --- Created attachment 274131 --> https://bugzilla.kernel.org/attachment.cgi?id=274131=edit dmesg log with amdgpu.dc_log=1 and drm.debug=6 My monitor is an AOC I2379VHE. It's attached

[Bug 105046] Screen resolution reset to 1368x768 when turning monitor off

https://bugs.freedesktop.org/show_bug.cgi?id=105046 --- Comment #4 from Michael Zapf --- No problem, here's xrandr at first: - before: Screen 0: minimum 320 x 200, current 1920 x 1200, maximum 16384 x 16384 DisplayPort-0 disconnected (normal

[Bug 92827] Tonga: No Sound over HDMI with connected AV receiver

https://bugs.freedesktop.org/show_bug.cgi?id=92827 --- Comment #11 from Maximilian Böhm --- I feel your pain, I’m experiencing something similar here: RX 580 → HDMI @ FullHD → Marantz NR1504 → [EDID-Fake-Plug] RX 580 → DP @ UHD → Dell P2715Q. Sometimes, when I turn the monitor

Re: [PATCH] drm/amdgpu: replace iova debugfs file with iomem (v2)

On 09/02/18 01:44 PM, Christian König wrote: Am 09.02.2018 um 19:19 schrieb Tom St Denis: On 09/02/18 01:17 PM, Christian König wrote: Am 09.02.2018 um 18:28 schrieb Tom St Denis: On 09/02/18 12:27 PM, Tom St Denis wrote: From: Christian König Oops, I'll

[Bug 101483] A10-8780P (Carrizo) + R7 M260/M265 does not boot without any "workaround" parameter.

https://bugs.freedesktop.org/show_bug.cgi?id=101483 FFAB changed: What|Removed |Added Attachment #136521|0 |1 is obsolete|

Re: [Mesa-dev] [PATCH 1/7] vulkan: Add KHR_display extension to anv and radv using DRM

Hi Keith, A few top level comments: - using card/primary node and (missing) authentication Current code opens the primary node when VK_KHR_display is available. Thus running a platform=drm,x11,wayland build will fail, as the client is not authenticated with the X/WL server. - reuse "drm" as a

[Bug 101483] A10-8780P (Carrizo) + R7 M260/M265 does not boot without any "workaround" parameter.

https://bugs.freedesktop.org/show_bug.cgi?id=101483 --- Comment #41 from FFAB --- Created attachment 137301 --> https://bugs.freedesktop.org/attachment.cgi?id=137301=edit booting without additional kernel parameter -- You are receiving this mail because: You are the assignee

[Bug 101483] A10-8780P (Carrizo) + R7 M260/M265 does not boot without any "workaround" parameter.

https://bugs.freedesktop.org/show_bug.cgi?id=101483 --- Comment #40 from FFAB --- Upstream kernel test - kernel 4.16-rc1 Installation, on which upstream kernel was installed: ubuntu 16.04.3, kernel 4.13.0-32, updated 2018-02-12 1. booting without any workaround parameters 2.

[Bug 105046] Screen resolution reset to 1368x768 when turning monitor off

https://bugs.freedesktop.org/show_bug.cgi?id=105046 --- Comment #3 from Harry Wentland --- Can you attach a full dmesg log from boot until this issue occurs, with kernel options amdgpu.dc_log=1 and drm.debug=6? Can you also paste what 'xrandr' outputs before and after

Re: [PATCH] drm/pl111: Fix regression from fbdev CMA helper

Den 12.02.2018 16.53, skrev Linus Walleij: On Mon, Feb 12, 2018 at 3:01 PM, Noralf Trønnes wrote: Den 12.02.2018 14.42, skrev Noralf Trønnes: Den 12.02.2018 13.40, skrev Linus Walleij: drm_mode_config_reset(dev); -drm_fb_cma_fbdev_init(dev, 32, 0); +

[Bug 105018] Kernel panic when waking up after screen goes blank.

https://bugs.freedesktop.org/show_bug.cgi?id=105018 --- Comment #5 from Harry Wentland --- Can you attach a full dmesg log with amdgpu.dc_log=1 and drm.debug=6 passed as kernel options? -- You are receiving this mail because: You are the assignee for the

Re: [PATCH] drm/pl111: Fix regression from fbdev CMA helper

On Mon, Feb 12, 2018 at 3:01 PM, Noralf Trønnes wrote: > Den 12.02.2018 14.42, skrev Noralf Trønnes: >> Den 12.02.2018 13.40, skrev Linus Walleij: >>> drm_mode_config_reset(dev); >>> -drm_fb_cma_fbdev_init(dev, 32, 0); >>> +drm_fb_cma_fbdev_init(dev, 32, 1);

[Bug 198745] Blank screen on RX 580 with AMDGPU Display Core enabled

https://bugzilla.kernel.org/show_bug.cgi?id=198745 Harry Wentland (harry.wentl...@amd.com) changed: What|Removed |Added CC|

[Bug 105046] Screen resolution reset to 1368x768 when turning monitor off

https://bugs.freedesktop.org/show_bug.cgi?id=105046 --- Comment #2 from Michael Zapf --- I got 3 systems where this issue occurs: 1. Monitor HP LP2475w connected via HDMI through a Pioneer AV receiver (VSX-330) to an AMD Radeon RX480. (New DC was needed to get HDMI Audio.)

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

> > I was more thinking about a struct containing enough info to allow the > > proxy on the host side find the buffer, something like: > > > > struct { > >enum type { stdvga, virtio-cpu, ... } > >pcislot device; > >union { > > int stdvga_pcibar_offset; > >

Re: [PATCH 1/7] vulkan: Add KHR_display extension to anv and radv using DRM

On Friday, 2018-02-09 20:45:10 -0800, Keith Packard wrote: > This adds support for the KHR_display extension to the anv and radv > Vulkan drivers. The drivers now attempt to open the master DRM node > when the KHR_display extension is requested so that the common winsys > code can perform the

[Bug 105036] Blank screen on RX 580 with AMDGPU Display Core enabled

https://bugs.freedesktop.org/show_bug.cgi?id=105036 --- Comment #3 from Harry Wentland --- What monitor are you using? Please recapture the journalctl with these options for the Linux kernel: amdgpu.dc_log=1 drm.debug=6 -- You are receiving this mail because: You are

[Bug 105046] Screen resolution reset to 1368x768 when turning monitor off

https://bugs.freedesktop.org/show_bug.cgi?id=105046 --- Comment #1 from Harry Wentland --- What monitor do you use and is it connected via DisplayPort, HDMI, or DVI? -- You are receiving this mail because: You are the assignee for the

[PATCH] drm/amdgpu: replace iova debugfs file with iomem (v3)

From: Christian König This allows access to pages allocated through the driver with optional IOMMU mapping. v2: Fix number of bytes copied and add write method v3: drop check for kmap return Original-by: Christian König

[PATCH] drm: Use idr_init_base(1) when using id==0 for invalid

Use the new idr_init_base() function to create an IDR that knows id==0 is never allocated as it maps to an invalid identifier. By knowing that id==0 is invalid, the IDR can start from id=1 instead avoiding the issue of having to start each lookup from the zeroth leaf as id==0 is always unused (and

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

On 02/12/2018 03:27 PM, Gerd Hoffmann wrote: On Mon, Feb 12, 2018 at 03:00:24PM +0100, Tomeu Vizoso wrote: On 02/12/2018 12:52 PM, Gerd Hoffmann wrote: Hi, can we reach agreement on whether vsock should be involved in this? I think the best approach would be to have guest proxy and

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

On Mon, Feb 12, 2018 at 03:00:24PM +0100, Tomeu Vizoso wrote: > On 02/12/2018 12:52 PM, Gerd Hoffmann wrote: > >Hi, > > > > > can we reach agreement on whether vsock should be involved in this? > > > > I think the best approach would be to have guest proxy and host proxy > > use vsock for

Re: [PATCH] drm/pl111: Fix regression from fbdev CMA helper

Den 12.02.2018 14.42, skrev Noralf Trønnes: Den 12.02.2018 13.40, skrev Linus Walleij: Commit d18df744de1a ("drm/pl111: Use drm_fb_cma_fbdev_init/fini()") refactored the driver to use fbdev handling in the core, but mistakedly limited the number of maximum connections to 0. Predictably, zero

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

On 02/12/2018 12:52 PM, Gerd Hoffmann wrote: Hi, can we reach agreement on whether vsock should be involved in this? I think the best approach would be to have guest proxy and host proxy use vsock for the wayland protocol. Use a wayland protocol extension to reference the buffers in

Re: [PATCH] drm/pl111: Fix regression from fbdev CMA helper

Den 12.02.2018 13.40, skrev Linus Walleij: Commit d18df744de1a ("drm/pl111: Use drm_fb_cma_fbdev_init/fini()") refactored the driver to use fbdev handling in the core, but mistakedly limited the number of maximum connections to 0. Predictably, zero possible connections also gives zero

Re: [PATCH 0/5] Fix deadlock on runtime suspend in DRM drivers

On Sun, Feb 11, 2018 at 10:38:28AM +0100, Lukas Wunner wrote: > [...] > i915, malidp and msm "solved" this issue by not stopping the poll worker > on runtime suspend. But this results in the GPU bouncing back and forth > between D0 and D3 continuously. That's a total no-go for GPUs which >

[RFC PATCH gabbayo] drm/amdgpu: amdkfd_fence_ops can be static

Fixes: 447ed3ae9ceb ("drm/amdgpu: Add KFD eviction fence") Signed-off-by: Fengguang Wu --- amdgpu_amdkfd_fence.c |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/gpu/drm/amd/amdgpu/amdgpu_amdkfd_fence.c

[PATCH] drm/pl111: Fix regression from fbdev CMA helper

Commit d18df744de1a ("drm/pl111: Use drm_fb_cma_fbdev_init/fini()") refactored the driver to use fbdev handling in the core, but mistakedly limited the number of maximum connections to 0. Predictably, zero possible connections also gives zero framebuffers when using the system. So let's bump it

Applied "spi: kconfig: Remove AVR32 dep. from SPI_ATMEL" to the spi tree

The patch spi: kconfig: Remove AVR32 dep. from SPI_ATMEL has been applied to the spi tree at https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git All being well this means that it will be integrated into the linux-next tree (usually sometime in the next 24 hours) and sent to

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

Hi, > can we reach agreement on whether vsock should be involved in this? I think the best approach would be to have guest proxy and host proxy use vsock for the wayland protocol. Use a wayland protocol extension to reference the buffers in stdvga / ivshmem / virtio-gpu. Only the two proxies

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

Hi, > >(a) software rendering: client allocates shared memory buffer, renders > >into it, then passes a file handle for that shmem block together > >with some meta data (size, format, ...) to the wayland server. > > > >(b) gpu rendering: client opens a render node,

[Bug 105021] suspend / rx550 / extremely slow after 2nd thaw

https://bugs.freedesktop.org/show_bug.cgi?id=105021 --- Comment #6 from arne_woer...@yahoo.com --- FYI: neither (A) a new BIOS (Gigabyte F2A88XM-D3H, BIOS F10a 02/23/2016 (before it was F9)) nor (B) turning off IOMMU support in the BIOS nor (C) kernel parameters "intremap=off amd_iommu=off"

Re: Fwd: Re: [PATCHv5 0/3] drm/i915: add DisplayPort CEC-Tunneling-over-AUX support

Hi Ville, On 12/01/18 20:08, Hans Verkuil wrote: > On 01/12/2018 07:12 PM, Hans Verkuil wrote: >> On 01/12/2018 06:52 PM, Ville Syrjälä wrote: >>> On Fri, Jan 12, 2018 at 06:14:53PM +0100, Hans Verkuil wrote: On 01/12/2018 05:30 PM, Ville Syrjälä wrote: > On Fri, Jan 12, 2018 at

[PATCH 24/24] drm/omap: cleanup color space conversion

The setup code for color space conversion is a bit messy. This patch cleans it up. For some reason the TRM uses values in YCrCb order, which is also used in the current driver, whereas everywhere else it's YCbCr (which also matches YUV order). This patch changes the tables to use the common order

[PATCH 23/24] drm/omap: Allow HDMI audio setup even if we do not have video configured

From: Jyri Sarha Allow HDMI audio setup even if we do not have video configured. Audio will get configured at the same time with video if the video is configured soon enough. If it is not the audio DMA will timeout in couple of seconds and audio playback will be aborted.

[PATCH 13/24] drm/omap: remove leftover enums

A few enums are not used anywhere, so remove them. Signed-off-by: Tomi Valkeinen --- drivers/gpu/drm/omapdrm/dss/omapdss.h | 15 --- 1 file changed, 15 deletions(-) diff --git a/drivers/gpu/drm/omapdrm/dss/omapdss.h b/drivers/gpu/drm/omapdrm/dss/omapdss.h

[PATCH 22/24] drm/omap: fix maximum sizes

We define max width and height in mode_config to 2048. These maximums affect many things, which are independent and depend on platform. We need to do more fine grained checks in the code paths for each component, and so the maximum values in mode_config should just be "big enough" to cover all use

[PATCH 20/24] drm/omap: fix scaling limits for WB

WB has additional scaling limits when the output color format is one of the YUV formats. These limits are not handled at the moment, causing bad scaling and/or NULL dereference crash. This patchs adds the check so that dispc returns an error for bad scaling request. Signed-off-by: Tomi Valkeinen

[PATCH 17/24] drm/omap: fix WBDELAYCOUNT for HDMI

For HDMI, WBDELAYCOUNT starts counting at the start of vsync, not at the start of vfp. This patch adjusts the wbdelay for HDMI accordingly. Signed-off-by: Tomi Valkeinen --- drivers/gpu/drm/omapdrm/dss/dispc.c | 8 ++-- 1 file changed, 6 insertions(+), 2 deletions(-)

[PATCH 19/24] drm/omap: fix WB height with interlace

When using WB capture from interlaced source, we need to halve the picture heights correctly. Unfortunately the current dispc_ovl_setup_common() doesn't deal with interlace very neatly, so the end result is a bit messy. Signed-off-by: Tomi Valkeinen Acked-by: Benoit

[PATCH 15/24] drm/omap: Add pclk setting case when channel is DSS_WB

From: Benoit Parrot In dispc_set_ovl_common() we need to initialize pclk to a valid value when we use WB in capture mode (i.e. mem_2_mem is false). Otherwise dispc_ovl_calc_scaling() fails. Signed-off-by: Benoit Parrot Signed-off-by: Tomi Valkeinen

[PATCH 21/24] drm/omap: add writeback funcs to dispc_ops

Add writeback specific dispc functions to dispc_ops so that omapdrm can use them. Also move 'enum dss_writeback_channel' to the public omapdss.h for omapdrm. Signed-off-by: Tomi Valkeinen --- drivers/gpu/drm/omapdrm/dss/dispc.c | 19 +++

  1   2   >