Re: [RFC resend] arm64: mt8173: Fix Acer Chromebooks mmsys probe problem

Hi, On Thu, 2017-10-19 at 16:54 +0200, Philipp Zabel wrote: > Hi Laurent, > > On Thu, 2017-10-19 at 16:39 +0300, Laurent Pinchart wrote: > > Hi Philipp, > > > > On Thursday, 19 October 2017 16:01:54 EEST Philipp Zabel wrote: > > > On Thu, 2017-10-19 at 13:26 +0200, Matthias Brugger wrote: > > >

Re: [PATCH v2 00/11] drm/exynos: TV path improvements

Hi Andrzej, Merged. And regarding below patch 9, I will try to contact HW guy to ask for why the difference happens. [PATCH v2 09/11] drm/exynos/hdmi: quirk for support mode timings conversion Thanks, Inki Dae 2017년 09월 29일 19:05에 Andrzej Hajda 이(가) 쓴 글: > Hi all, > > This patchset does two

Re: [PATCH v3] drm: exynos: Add driver for HDMI audio interface

Hi Sylwester, 2017년 09월 26일 23:17에 Sylwester Nawrocki 이(가) 쓴 글: > The hdmi-codec interface added in this patch is required to properly > support HDMI audio. Currently the audio part of the SoC internal > HDMI transmitter is configured with fixed values, which makes HDMI > audio working by

Re: [pull] amdgpu dc drm-next-4.15-dc

Am 22.10.2017 23:48, schrieb Dieter Nützel: Am 21.10.2017 23:22, schrieb Alex Deucher: Hi Dave, Last batch of new stuff for DC. Highlights: - Fix some memory leaks - S3 fixes - Hotplug fixes - Fix some CX multi-display issues - MST fixes - DML updates from the hw team - Various code cleanups -

[Bug 103408] [bisected] frames dropped during video replay due to "add hardware_planes_only to list of affected planes"

https://bugs.freedesktop.org/show_bug.cgi?id=103408 Bug ID: 103408 Summary: [bisected] frames dropped during video replay due to "add hardware_planes_only to list of affected planes" Product: DRI Version: DRI git Hardware:

Re: [PATCH v2 0/2] qxl: fix wayland display flicker

On 19 October 2017 at 16:21, Gerd Hoffmann wrote: > > > Gerd Hoffmann (2): > drm/qxl: replace QXL_INFO with DRM_DEBUG_DRIVER > qxl: alloc & use shadow for dumb buffers > Reviewed-by: Dave Airlie for both, we probably need to cc stable on the second

Re: [pull] amdgpu dc drm-next-4.15-dc

Am 21.10.2017 23:22, schrieb Alex Deucher: Hi Dave, Last batch of new stuff for DC. Highlights: - Fix some memory leaks - S3 fixes - Hotplug fixes - Fix some CX multi-display issues - MST fixes - DML updates from the hw team - Various code cleanups - Misc bug fixes Now this tree has the same

[PATCH v2] gpu/drm/bridge/sii9234: Use common error handling code in sii9234_writebm()

From: Markus Elfring Date: Sun, 22 Oct 2017 21:50:51 +0200 * Add a jump target so that a bit of exception handling can be better reused at the end of this function. This issue was detected by using the Coccinelle software. * Adjust condition checks.

[PATCH] gpu/drm/bridge/sii9234: Use common error handling code in sii9234_writebm()

From: Markus Elfring Date: Sun, 22 Oct 2017 21:21:44 +0200 * Add a jump target so that a bit of exception handling can be better reused at the end of this function. This issue was detected by using the Coccinelle software. * Adjust condition checks.

Re: Enabling peer to peer device transactions for PCIe devices

On 22/10/17 12:13 AM, Petrosyan, Ludwig wrote: > But at first sight it has to be simple: > The PCIe Write transactions are address routed, so if in the packet header > the other endpoint address is written the TLP has to be routed (by PCIe > Switch to the endpoint), the DMA reading from the end

Re: No /dev/fb0 created for omapdrm in current Linux next

* Tomi Valkeinen [171019 23:13]: > On 19/10/17 19:30, Tony Lindgren wrote: > > Hi Tomi, > > > > Looks like omapdrm won't show anything with current Linux next based > > on my test with 900: > > > > modprobe twl4030_keypad > > modprobe tsc2005 > > modprobe omapdss > >

Re: Enabling peer to peer device transactions for PCIe devices

Hi Ludwig, P2P transactions are still *very* experimental at the moment and take a lot of expertise to get working in a general setup. It will definitely require changes to the kernel, including the drivers of all the devices you are trying to make talk to eachother. If you're up for it you

Re: [RFC resend 3/4] arm64: dts: mt8173: Fix drm subsystem

On 10/20/2017 11:16 AM, CK Hu wrote: > Hi, Matthias: > > On Thu, 2017-10-19 at 13:26 +0200, Matthias Brugger wrote: >> DRM subysystem and clock driver shared the same compatible mmsys. >> This stopped does not work, as only the first driver for a compatible >> gets probed. We change the

[PATCH v3] display: panel: Add Mitsubishi aa070mc01 display support (800x480)

This commit adds support for Mitsubishi aa070mc01 TFT panel working with 8 bit ISP mode (pin 19 "mode" HIGH for 20 pin TFT connector). Signed-off-by: Lukasz Majewski --- Changes for v2: - Place the code sorted alphabetically - Add missing ./Documentation/devicetree/binding/display

[PATCH] display: panel: Add Tianma tm070rvhg71 display support (800x480)

Signed-off-by: Lukasz Majewski --- .../bindings/display/panel/tianma,tm070rvhg71.txt | 7 ++ drivers/gpu/drm/panel/panel-simple.c | 27 ++ 2 files changed, 34 insertions(+) create mode 100644

Re: Enabling peer to peer device transactions for PCIe devices

Hello Logan Thank You very much for respond. Could be I have done is stupid... But at first sight it has to be simple: The PCIe Write transactions are address routed, so if in the packet header the other endpoint address is written the TLP has to be routed (by PCIe Switch to the endpoint), the

[PATCH v5 3/5] Documentation: Add device tree binding for Goldfish FB driver

From: Aleksandar Markovic Add documentation for DT binding of Goldfish FB driver. The compatible string used by OS for binding the driver is "google,goldfish-fb". Signed-off-by: Miodrag Dinic Signed-off-by: Goran Ferenc

Re: Enabling peer to peer device transactions for PCIe devices

Dear Linux kernel group my name is Ludwig Petrosyan I am working in DESY (Germany) we are responsible for the control system of  all accelerators in DESY. For a 7-8 years we have switched to MTCA.4 systems and using PCIe as a central Bus. I am mostly responsible for the Linux drivers of the

[Bug 101978] [bisected] war thunder performance reduced by ~28%

https://bugs.freedesktop.org/show_bug.cgi?id=101978 Justin changed: What|Removed |Added Version|git |17.2

RFC: Add drm_dev_suspend/resume() ?

Hi, I've spent some time in the fbdev emulation code and discovered a recurring pattern around suspend/resume. Should we add some more helpers :-) struct drm_device {     /**      * @suspend_state:      *      * Atomic state when suspended.      * Set by drm_dev_suspend(), cleared by

[Bug 103317] Tearing in WQHD, but not in FHD

https://bugs.freedesktop.org/show_bug.cgi?id=103317 --- Comment #6 from Torsten Kessler --- The new display engine (amdgpu.dc=1) definitely helps. It nearly eliminates the flickering during videos or browsing. It has no effect on 3D applications, for example 0ad. There seems

[Bug 103404] HDMI Audio with RX Vega not working on drm-next-4.15-dc (device listed as unconnected)

https://bugs.freedesktop.org/show_bug.cgi?id=103404 --- Comment #3 from randomsa...@gmail.com --- Created attachment 134993 --> https://bugs.freedesktop.org/attachment.cgi?id=134993=edit cat /proc/asound/card0/eld#0.* -- You are receiving this mail because: You are the assignee for the

[Bug 103404] HDMI Audio with RX Vega not working on drm-next-4.15-dc (device listed as unconnected)

https://bugs.freedesktop.org/show_bug.cgi?id=103404 --- Comment #2 from randomsa...@gmail.com --- Created attachment 134992 --> https://bugs.freedesktop.org/attachment.cgi?id=134992=edit Parsed edid output for the monitor, connected via DP. -- You are receiving this mail because: You are the

[Bug 103404] HDMI Audio with RX Vega not working on drm-next-4.15-dc (device listed as unconnected)

https://bugs.freedesktop.org/show_bug.cgi?id=103404 --- Comment #1 from randomsa...@gmail.com --- Created attachment 134991 --> https://bugs.freedesktop.org/attachment.cgi?id=134991=edit Parsed edid output for the receiver. -- You are receiving this mail because: You are the assignee for the

[Bug 103404] HDMI Audio with RX Vega not working on drm-next-4.15-dc (device listed as unconnected)

https://bugs.freedesktop.org/show_bug.cgi?id=103404 Bug ID: 103404 Summary: HDMI Audio with RX Vega not working on drm-next-4.15-dc (device listed as unconnected) Product: DRI Version: unspecified Hardware: x86-64 (AMD64)

[Bug 103403] something going on across the gpu DAC and monitor.

https://bugs.freedesktop.org/show_bug.cgi?id=103403 Bug ID: 103403 Summary: something going on across the gpu DAC and monitor. Product: DRI Version: XOrg git Hardware: x86 (IA32) URL:

[Bug 100666] amdgpu coolers never stoping linux

https://bugs.freedesktop.org/show_bug.cgi?id=100666 --- Comment #6 from Dimitrios Liappis --- Lucas, the Asus RX-550 (and apparently cards from all manufacturers for this chipset) doesn't have any fan control. See my comment here:

[Bug 97556] amdgpu fan behavior doesn't match windows

https://bugs.freedesktop.org/show_bug.cgi?id=97556 --- Comment #7 from Dimitrios Liappis --- To close the loop with my issue here, it appears that the Asus Radeon RX-550 doesn't have any PWM control. The fan speed is constant and can't be changed in Windows using the

Re: [PATCH v4] drm/amd/powerplay: Remove unnecessary cast on void pointer

Hi Harsha, [auto build test ERROR on v4.14-rc3] [cannot apply to drm/drm-next next-20171018] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url:

[Bug 103397] [regression, bisected] broken geometry in almost every game

https://bugs.freedesktop.org/show_bug.cgi?id=103397 --- Comment #1 from Christoph Haag --- Bug 103389 bisected to the same commit. -- You are receiving this mail because: You are the assignee for the bug.___ dri-devel mailing