[PATCH v5 4/4] drm/rockchip: support dp training outside dp firmware

DP firmware uses fixed phy config values to do training, but some boards need to adjust these values to fit for their unique hardware design. So get phy config values from dts and use software link training instead of relying on firmware, if software training fail, keep firmware training as a

[RFC 14/24] drm/lima: add MMU related functions

From: Lima Project Developers Signed-off-by: Qiang Yu Signed-off-by: Marek Vasut Signed-off-by: Heiko Stuebner --- drivers/gpu/drm/lima/lima_mmu.c | 154

[PATCH v5 3/4] phy: rockchip-typec: support variable phy config value

the phy config values used to fix in dp firmware, but some boards need change these values to do training and get the better eye diagram result. So support that in phy driver. Signed-off-by: Chris Zhong Signed-off-by: Lin Huang --- Changes in v2: -

[PATCH v5 1/4] drm/rockchip: add transfer function for cdn-dp

From: Chris Zhong We may support training outside firmware, so we need support dpcd read/write to get the message or do some setting with display. Signed-off-by: Chris Zhong Signed-off-by: Lin Huang Reviewed-by: Sean Paul

[RFC 08/24] drm/lima: add lima core driver

From: Lima Project Developers Signed-off-by: Qiang Yu Signed-off-by: Heiko Stuebner Signed-off-by: Erico Nunes --- drivers/gpu/drm/lima/lima_drv.c | 466

Re: [PATCH 1/2] ARM: dts: Restructure Vexpress motherboard includes

Hi Linus, On 17/05/18 10:04, Linus Walleij wrote: > On Wed, May 9, 2018 at 6:44 PM, Sudeep Holla wrote: > >> Please copy me and Lorenzo also in future. >> Applied now(with typo in hierarchy fixed), thanks. > > Sure thing, sorry I didn't realize you were working actively

Re: [RFC 07/24] drm/lima: add mali 4xx GPU hardware regs

Sorry, I'm preparing RFC for lima driver, this mail is send by accident. Will resend a formal one latter. Regards, Qiang On Fri, May 18, 2018 at 11:16 AM, Qiang Yu wrote: > From: Lima Project Developers > > Signed-off-by: Qiang Yu

Re: [PATCH v6 1/4] drm/bridge: add support for sn65dsi86 bridge driver

On 2018-05-16 12:56, Andrzej Hajda wrote: I suppose you wanted to respond on the list, so I have added back all recipients. On 16.05.2018 06:39, spa...@codeaurora.org wrote: On 2018-05-15 19:23, Andrzej Hajda wrote: On 15.05.2018 07:52, Sandeep Panda wrote: Add support for TI's sn65dsi86

[RFC 13/24] drm/lima: add PP related functions

From: Lima Project Developers PP is a processor used for OpenGL fragment shader processing. Signed-off-by: Qiang Yu Signed-off-by: Heiko Stuebner --- drivers/gpu/drm/lima/lima_pp.c | 418 +

Re: [PATCH] efi/fb: Convert PCI bus address to resource if translated by the bridge

On 17 May 2018 at 16:55, Peter Jones wrote: > On Thu, May 17, 2018 at 09:22:23AM -0400, Sinan Kaya wrote: >> A host bridge is allowed to remap BAR addresses using _TRA attribute in >> _CRS windows. >> >> pci_bus :00: root bus resource [mem 0x8010010-0x8011fff

Re: [PATCH 19/24] drm/armada: Move GEM BO to drm_framebuffer

On Thu, May 17, 2018 at 02:15:40PM +0100, Daniel Stone wrote: > Hi Russell, > > On 30 March 2018 at 15:11, Daniel Stone wrote: > > Since drm_framebuffer can now store GEM objects directly, place them > > there rather than in our own subclass. As this makes the framebuffer

Re: [GIT PULL] TDA998x I2C driver CEC support

Hi David, I don't see this in what I presume is your tree yet - do you have some concern about merging this series? Thanks. On Tue, Apr 24, 2018 at 10:54:56AM +0100, Russell King wrote: > David, > > Please incorporate support for TDA998x I2C driver CEC, which can be > found at: > >

Re: [PATCH V1 2/5] backlight: qcom-wled: Add support for WLED4 peripheral

On 2018-05-17 18:01, Rob Herring wrote: On Thu, May 17, 2018 at 4:47 AM, wrote: On 2018-05-08 15:55, kgu...@codeaurora.org wrote: On 2018-05-07 21:50, Bjorn Andersson wrote: On Thu 03 May 02:57 PDT 2018, Kiran Gunda wrote: WLED4 peripheral is present on some PMICs

DRM Inquiry

Hi All, Good day! I’ve been doing some PTN3460 programming under Linux using C/C++ and I have some questions regarding on setting the brightness level to my display device. The display device with PTN3460 is connected in DP (display port) to my computer. Only needs a DisplayPort native AUX

KASAN: use-after-free Read in vgacon_invert_region

We report the crash: "KASAN: use-after-free Read in vgacon_invert_region" This crash was found in v4.17-rc3. Specifically, memory access (read operation) is invalid, and it is detected by KASAN. C repro code: https://kiwi.cs.purdue.edu/static/alexkkid-fuzzer/repro-ba6c1.c kernel config:

[PATCH v5 2/4] Documentation: bindings: add phy_config for Rockchip USB Type-C PHY

If want to do training outside DP Firmware, need phy voltage swing and pre_emphasis value. Signed-off-by: Lin Huang --- Changes in v2: - None Changes in v3: - modify property description and add this property to Example Change in v4: - None Change in v5: - None

[RFC 09/24] drm/lima: add GPU device functions

From: Lima Project Developers Signed-off-by: Qiang Yu Signed-off-by: Simon Shields Signed-off-by: Heiko Stuebner --- drivers/gpu/drm/lima/lima_device.c | 407 +

Re: [RFC PATCH] efi/fb: Convert PCI bus address to resource if translated by the bridge

On 5/17/2018 6:17 AM, Robin Murphy wrote: >> +    } >> + > > Is this not pretty much just pcibios_bus_to_resource()? > Agreed, let me convert the code to use pcibios_bus_to_resource() API. I wasn't aware of its existence. > Robin. -- Sinan Kaya Qualcomm Datacenter Technologies, Inc. as an

Re: [PATCH v2 0/3] Expanding the basic vkms features

On Wed, May 16, 2018 at 08:55:06PM -0300, Rodrigo Siqueira wrote: > This series of patches add a centralized initialization mechanism, a > single CRTC with a plane, an encoder, and extra module information. > > Changes in v2: > - Remove unused definitions > - Improve file names > - Improve

[RFC 07/24] drm/lima: add mali 4xx GPU hardware regs

From: Lima Project Developers Signed-off-by: Qiang Yu Signed-off-by: Heiko Stuebner --- drivers/gpu/drm/lima/lima_regs.h | 304 +++ 1 file changed, 304 insertions(+) create mode 100644

Re: [RFC PATCH 04/10] devfreq: rk3399_dmc / rockchip: pm_domains: Register notify to DMC driver.

Hi, As I already commented[1], I think that it is not proper in order to pass the devfreq instance to power_domain driver by separate defined function (rockchip_pm_register_dmcfreq_notifier()). [1] https://patchwork.kernel.org/patch/10349571/ Maybe, you could check the 'OF graph[1]' or 'device

Re: [PATCH 2/2] drm/tegra: Acquire a reference to the IOVA cache

On 23.04.2018 09:57, Thierry Reding wrote: > From: Thierry Reding > > The IOVA API uses a memory cache to allocate IOVA nodes from. To make > sure that this cache is available, obtain a reference to it and release > the reference when the cache is no longer needed. > > On

Re: [PATCH v5 4/4] drm/rockchip: support dp training outside dp firmware

+ Kishon On Thursday, May 17, 2018 09:51 PM, Sean Paul wrote: On Thu, May 17, 2018 at 05:18:00PM +0800, Lin Huang wrote: DP firmware uses fixed phy config values to do training, but some boards need to adjust these values to fit for their unique hardware design. So get phy config values from

Re: [PATCH V1 2/5] backlight: qcom-wled: Add support for WLED4 peripheral

On 2018-05-08 15:55, kgu...@codeaurora.org wrote: On 2018-05-07 21:50, Bjorn Andersson wrote: On Thu 03 May 02:57 PDT 2018, Kiran Gunda wrote: WLED4 peripheral is present on some PMICs like pmi8998 and pm660l. It has a different register map and also configurations are different. Add support

Re: [PATCH 2/5] drm: rcar-du: lvds: Add R8A77995 support

On Wed, May 16, 2018 at 11:59:32AM +0300, Sergei Shtylyov wrote: > Hello! > > On 5/16/2018 10:54 AM, Simon Horman wrote: > > > > Add support for the R-Car D3 (R8A77995) SoC to the LVDS encoder driver. > > > > > > Signed-off-by: Ulrich Hecht > > > --- > > >

[PATCH] efi/fb: Convert PCI bus address to resource if translated by the bridge

A host bridge is allowed to remap BAR addresses using _TRA attribute in _CRS windows. pci_bus :00: root bus resource [mem 0x8010010-0x8011fff window] (bus address [0x0010-0x1fff]) pci :02:00.0: reg 0x10: [mem 0x8011e00-0x8011eff] When a VGA device is behind such

[RFC 10/24] drm/lima: add PMU related functions

From: Lima Project Developers Signed-off-by: Qiang Yu Signed-off-by: Heiko Stuebner --- drivers/gpu/drm/lima/lima_pmu.c | 85 + drivers/gpu/drm/lima/lima_pmu.h | 30 2 files

Re: [PATCH 08/24] drm/mtk: Promote impossible internal error to WARN_ON

On Thu, 2018-05-17 at 16:55 +0200, Thierry Reding wrote: > On Thu, May 17, 2018 at 09:58:19AM -0400, Sean Paul wrote: > > On Fri, Mar 30, 2018 at 03:11:22PM +0100, Daniel Stone wrote: > > > A FB with no object is something we should be shouting very loudly > > > about, not quietly logging as

[PATCH v7 1/5] drm: mali-dp: Add support for writeback on DP550/DP650

Mali-DP display processors are able to write the composition result to a memory buffer via the SE. Add entry points in the HAL for enabling/disabling this feature, and implement support for it on DP650 and DP550. DP500 acts differently and so is omitted from this change. Changes since v3: - Fix

[PATCH v7 4/5] drm/mali-dp: Add RGB writeback formats for DP500.

Annotate the pixel format matrix for DP500 with the memory-write flag for formats that are supported by the SE memwrite engine. Signed-off-by: Liviu Dudau --- drivers/gpu/drm/arm/malidp_hw.c | 10 +- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git

[PATCH v7 0/5] drm/mali-dp: Add support for memory writeback engine

Hi, Updating the Mali DP memory writeback engine support series to match the latest generic writeback connector support posted here [1]. As the generic patches look ready to be merged into drm-misc-next, I'm sending the updated Mali DP driver as well. Changelog: - v7: Added support for DP500

[PATCH v7 5/5] drm: mali-dp: Add writeback connector

From: Brian Starkey Mali-DP has a memory writeback engine which can be used to write the composition result to a memory buffer. Expose this functionality as a DRM writeback connector on supported hardware. Changes since v1: Daniel Vetter: - Don't require a modeset when

[PATCH v7 3/5] drm/mali-dp: Add writeback support for DP500.

Mali DP500 behaves differently from the rest of the Mali DP IP, in that it does not have a one-shot mode and keeps writing the content of the current frame to the provided memory area until stopped. As a way of emulating the one-shot behaviour, we are going to use the CVAL interrupt that is being

[PATCH v7 2/5] drm: mali-dp: Add RGB writeback formats for DP550/DP650

From: Brian Starkey Add a layer bit for the SE memory-write, and add it to the pixel format matrix for DP550/DP650. Signed-off-by: Brian Starkey [rebased and fixed conflicts] Signed-off-by: Mihail Atanassov Signed-off-by:

Re: [PATCH v5 4/4] drm/rockchip: support dp training outside dp firmware

Am Freitag, 18. Mai 2018, 03:45:46 CEST schrieb Brian Norris: > On Thu, May 17, 2018 at 6:41 PM, hl wrote: > > On Thursday, May 17, 2018 09:51 PM, Sean Paul wrote: > >> On Thu, May 17, 2018 at 05:18:00PM +0800, Lin Huang wrote: > >>> DP firmware uses fixed phy config values

Re: [PATCH v4 3/3] ARM: dts: sun7i: Add support for the Ainol AW1 tablet

On Mon, May 14, 2018 at 10:36:08PM +0200, Paul Kocialkowski wrote: > > > + backlight: backlight { > > > + compatible = "pwm-backlight"; > > > + pwms = < 0 5 PWM_POLARITY_INVERTED>; > > > + brightness-levels = < 0 1 1 1 1 2 2 2 > > > +

Re: [RFC] remoting KMS

On 05/17/2018 11:40 PM, Daniel Vetter wrote: On Thu, May 17, 2018 at 11:18 PM, Thomas Hellstrom wrote: On 05/17/2018 09:20 PM, Daniel Vetter wrote: On Thu, May 17, 2018 at 8:23 PM, Thomas Hellstrom wrote: Hi! I'm currently working on a remoting KMS

[Bug 106561] ./libdrm_macros.h:26:5: error: 'HAVE_VISIBILITY' is not defined, evaluates to 0 [-Werror,-Wundef]

https://bugs.freedesktop.org/show_bug.cgi?id=106561 Bug ID: 106561 Summary: ./libdrm_macros.h:26:5: error: 'HAVE_VISIBILITY' is not defined, evaluates to 0 [-Werror,-Wundef] Product: DRI Version: DRI git Hardware: x86-64

[PATCH] drm/v3d: Checking for NULL vs IS_ERR()

The v3d_fence_create() only returns error pointers on error. It never returns NULL. Fixes: 57692c94dcbe ("drm/v3d: Introduce a new DRM driver for Broadcom V3D V3.x+") Signed-off-by: Dan Carpenter diff --git a/drivers/gpu/drm/v3d/v3d_sched.c

Re: [PATCH 10/24] drm/mtk: mtk_drm_fb -> drm_framebuffer

On Fri, 2018-03-30 at 22:11 +0800, Daniel Stone wrote: > Now that mtk_drm_fb is an empty wrapper around drm_framebuffer, we can > just delete it. > Reviewed-by: CK Hu > Signed-off-by: Daniel Stone > Cc: CK Hu > Cc: Philipp Zabel

[PATCH] drm/exynos: fimc: signedness bug in fimc_setup_clocks()

"id" needs to be signed for the error handling to work. Fixes: 7a2d5c77c558 ("drm/exynos: fimc: Convert driver to IPP v2 core API") Signed-off-by: Dan Carpenter diff --git a/drivers/gpu/drm/exynos/exynos_drm_fimc.c b/drivers/gpu/drm/exynos/exynos_drm_fimc.c index

Re: [PATCH 09/24] drm/mtk: Move GEM BO to drm_framebuffer

On Fri, 2018-03-30 at 22:11 +0800, Daniel Stone wrote: > Since drm_framebuffer can now store GEM objects directly, place them > there rather than in our own subclass. As this makes the framebuffer > create_handle and destroy functions the same as the GEM framebuffer > helper, we can reuse those. >

Re: [PATCH 2/3] drm/scheduler: Don't call wait_event_killable for signaled process.

On 2018-05-17 09:05 PM, Andrey Grodzovsky wrote: > On 05/17/2018 10:48 AM, Michel Dänzer wrote: >> On 2018-05-17 01:18 PM, Andrey Grodzovsky wrote: >>> Hi Michele and others, I am trying to implement the approach bellow to >>> resolve AMDGPU's hang when commands are stuck in pipe during process

Re: [PATCH 3/4] drm/i915: Limit searching for PIN_HIGH

Quoting Chris Wilson (2018-05-13 10:50:09) > To no surprise (since we've flip-flopped over the use of PIN_HIGH a few > times), doing a search by address over a pathologically fragmented > address space is exceeding slow. To protect ourselves from nearly > unbounded latency (think searching a

Re: [PATCH libdrm] Always pass O_CLOEXEC when opening DRM file descriptors

Am 18.05.2018 um 11:17 schrieb Michel Dänzer: From: Michel Dänzer Signed-off-by: Michel Dänzer Reviewed-by: Christian König --- xf86drm.c | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git

Re: DRM Inquiry

On Thu, 17 May 2018, John Sledge wrote: > I’ve been doing some PTN3460 programming under Linux using C/C++ and I > have some questions regarding on setting the brightness level to my > display device. > > The display device with PTN3460 is connected in DP (display port) to

Re: [PATCH v2 12/26] drm/sun4i: Add support for multiple DW HDMI PHY clock parents

On Fri, May 18, 2018 at 03:15:22PM +0530, Jagan Teki wrote: > From: Jernej Skrabec > > Some SoCs with DW HDMI have multiple possible clock parents, like A64 > and R40. > > Expand HDMI PHY clock driver to support second clock parent. > > Signed-off-by: Jernej Skrabec

Re: [PATCH] drm/panel: simple: fix data type in KEO TX31D200VM0BAA timings

On Thu, Apr 19, 2018 at 11:20:03PM +0200, Stefan Agner wrote: > All values in a struct struct timing_entry (every entry in > struct display_timing) require an integer. Choose the closest > safe integer of 32. > > This avoids a warning seen with clang: >

Re: [PATCH v2] gpu: host1x: Fix compiler errors by converting to dma_addr_t

On Wed, May 16, 2018 at 12:22:04PM +0200, Emil Goode wrote: > The compiler is complaining with the following errors: > > drivers/gpu/host1x/cdma.c:94:48: error: > passing argument 3 of ‘dma_alloc_wc’ from incompatible pointer type > [-Werror=incompatible-pointer-types] > >

Re: [PATCH 2/3] drm/scheduler: Don't call wait_event_killable for signaled process.

Anyway, the kernel can't rely on userspace using O_CLOEXEC. If the flush callback being called from multiple processes is an issue, maybe the flush callback isn't appropriate after all. Userspace could also grab a reference just by opening /proc/$pid/fd/*. The idea is just that when any

Re: [PATCH 4/4] drm/i915: Pin the ring high

Quoting Chris Wilson (2018-05-13 10:50:10) > If we can use an unmappable ring, try to pin it out of the mappable > aperture. This simple layout preference is to try and keep the mappable > aperture reserved and available to handle GGTT mmapping requests from > userspace without causing evictions

Re: [PATCH 3/4] drm/i915: Limit searching for PIN_HIGH

Quoting Joonas Lahtinen (2018-05-18 11:05:36) > Quoting Chris Wilson (2018-05-13 10:50:09) > > To no surprise (since we've flip-flopped over the use of PIN_HIGH a few > > times), doing a search by address over a pathologically fragmented > > address space is exceeding slow. To protect ourselves

Re: [PATCH] drm/panel: simple: AUO P320HVN03 uses SPWG data ordering

On Wed, Apr 11, 2018 at 05:27:41PM +0200, Lucas Stach wrote: > The patch adding support for the AUO P320HVN03 panel was written against a > preliminary datasheet, which specified JEIDA data ordering. Testing with > real hardware has shown that the actually used data ordering is SPWG. > > Fixes:

Re: [PATCH v7 3/5] drm/mali-dp: Add writeback support for DP500.

On Fri, May 18, 2018 at 09:56:20AM +0100, Brian Starkey wrote: > Hi Liviu, > > On Fri, May 18, 2018 at 09:24:21AM +0100, Liviu Dudau wrote: > > Mali DP500 behaves differently from the rest of the Mali DP IP, > > in that it does not have a one-shot mode and keeps writing the > > content of the

Re: [PATCH 3/4] drm/i915: Limit searching for PIN_HIGH

Quoting Chris Wilson (2018-05-18 13:07:16) > Quoting Joonas Lahtinen (2018-05-18 11:05:36) > > Quoting Chris Wilson (2018-05-13 10:50:09) > > > To no surprise (since we've flip-flopped over the use of PIN_HIGH a few > > > times), doing a search by address over a pathologically fragmented > > >

Re: [PATCH] efi/fb: Convert PCI bus address to resource if translated by the bridge

On 17/05/18 14:22, Sinan Kaya wrote: A host bridge is allowed to remap BAR addresses using _TRA attribute in _CRS windows. pci_bus :00: root bus resource [mem 0x8010010-0x8011fff window] (bus address [0x0010-0x1fff]) pci :02:00.0: reg 0x10: [mem

Re: [PATCH 1/4] drm/mm: Reject over-sized allocation requests early

Quoting Chris Wilson (2018-05-13 10:50:07) > As we keep an rbtree of available holes sorted by their size, we can > very easily determine if there is any hole large enough that might > satisfy the allocation request. This helps when dealing with a highly > fragmented address space and a request

Re: [PATCH v4 2/2] drm/panel: Add device_link from panel device to drm device

On 26.04.2018 10:07, Jyri Sarha wrote: > Add device_link from panel device (supplier) to drm device (consumer) > when drm_panel_attach() is called. This patch should protect the > master drm driver if an attached panel driver unbinds while it is in > use. The device_link should make sure the drm

Re: [PATCH v7 3/5] drm/mali-dp: Add writeback support for DP500.

Hi Liviu, On Fri, May 18, 2018 at 09:24:21AM +0100, Liviu Dudau wrote: Mali DP500 behaves differently from the rest of the Mali DP IP, in that it does not have a one-shot mode and keeps writing the content of the current frame to the provided memory area until stopped. As a way of emulating the

[PATCH libdrm] Always pass O_CLOEXEC when opening DRM file descriptors

From: Michel Dänzer Signed-off-by: Michel Dänzer --- xf86drm.c | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/xf86drm.c b/xf86drm.c index 3a9d0ed2..c09437b0 100644 --- a/xf86drm.c +++ b/xf86drm.c @@ -405,7 +405,7 @@

Re: [PATCH v2 00/26] arm64: allwinner: Add A64 DE2 HDMI support

On Fri, May 18, 2018 at 03:15:10PM +0530, Jagan Teki wrote: > Allwinner A64 has display engine pipeline like other Allwinner SOC's > A83T/H3/H5. > > A64 behaviour similar to Allwinner A83T where > Mixer0 => TCON0 => LVDS/RGB/MIPI-DSI > Mixer1 => TCON1 => HDMI > as per Display System Block

Re: [PATCH 2/4] drm/mm: Add a search-by-address variant to only inspect a single hole

Quoting Chris Wilson (2018-05-13 10:50:08) > Searching for an available hole by address is slow, as there no > guarantee that a hole will be available and so we must walk over all > nodes in the rbtree before we determine the search was futile. In many > cases, the caller doesn't strictly care for

RE: [PATCH v3 28/40] drm/i915: Handle HDCP2.2 downstream topology change

>-Original Message- >From: dri-devel [mailto:dri-devel-boun...@lists.freedesktop.org] On Behalf Of >Ramalingam C >Sent: Tuesday, April 3, 2018 7:28 PM >To: intel-...@lists.freedesktop.org; dri-devel@lists.freedesktop.org; >seanp...@chromium.org; dan...@ffwll.ch; ch...@chris-wilson.co.uk;

Re: [PATCH 7/7] gpu: host1x: Track client version

On 05/17/2018 06:34 PM, Thierry Reding wrote: From: Thierry Reding Userspace needs to know the version of the interface implemented by a client so it can create the proper command streams. Allow individual drivers to store this version along with the client so that it can

Re: [PATCH V1 2/5] backlight: qcom-wled: Add support for WLED4 peripheral

On Thu, May 17, 2018 at 10:10 AM, wrote: > On 2018-05-17 18:01, Rob Herring wrote: >> >> On Thu, May 17, 2018 at 4:47 AM, wrote: >>> >>> On 2018-05-08 15:55, kgu...@codeaurora.org wrote: On 2018-05-07 21:50, Bjorn Andersson wrote:

[radeon-alex:drm-next-4.18-wip 80/108] ERROR: "__divdi3" [drivers/gpu/drm/amd/amdgpu/amdgpu.ko] undefined!

tree: git://people.freedesktop.org/~agd5f/linux.git drm-next-4.18-wip head: 404af8e5236fe7eb64d91bf708bd7aa81815d14e commit: a21ddec61c5ed30b58eea3268ad3e0c69452ebfe [80/108] drm/amd/display: fix 31_32_fixpt shift functions config: i386-allmodconfig (attached as .config) compiler: gcc-7

[Bug 106548] Failed GfxDrv_DriverAcceptanceQuery.GL_GPU_FREQ_OVERRIDE_MDAPI

https://bugs.freedesktop.org/show_bug.cgi?id=106548 --- Comment #5 from Francesco Balestrieri --- Additional comment from Kishore in the duplicate bug #106549: "I have tried on default kernel version on ubuntu 18.04 is 4.15-rc20. and also on the drm-tip, i can

[Bug 104817] [Raven][GALLIUM_DDEBUG] system crashes/freezes randomly every few minutes/hours

https://bugs.freedesktop.org/show_bug.cgi?id=104817 --- Comment #5 from Justin Mitzel --- I am also having this problem. Ryzen 2500u on kernel 4.16-DRM-next. Many hangs that require a reboot to fix. -- You are receiving this mail because: You are the assignee for the

[Bug 104817] [Raven][GALLIUM_DDEBUG] system crashes/freezes randomly every few minutes/hours

https://bugs.freedesktop.org/show_bug.cgi?id=104817 --- Comment #6 from Justin Mitzel --- Although it also seems very likely that this is a Kernel driver issue. -- You are receiving this mail because: You are the assignee for the

Re: [PATCH 7/7] gpu: host1x: Track client version

On Fri, May 18, 2018 at 03:21:11PM +0300, Mikko Perttunen wrote: > On 05/17/2018 06:34 PM, Thierry Reding wrote: > > From: Thierry Reding > > > > Userspace needs to know the version of the interface implemented by a > > client so it can create the proper command streams.

[PATCH v2 3/5] mfd: cros-ec: Introduce CEC commands and events definitions.

The EC can expose a CEC bus, this patch adds the CEC related definitions needed by the cros-ec-cec driver. Having a 16 byte mkbp event size makes it possible to send CEC messages from the EC to the AP directly inside the mkbp event instead of first doing a notification and then a read.

Re: [PATCH v2 2/5] drm/i915: hdmi: add CEC notifier to intel_hdmi

On Fri, May 18, 2018 at 03:05:01PM +0200, Neil Armstrong wrote: > This patchs adds the cec_notifier feature to the intel_hdmi part > of the i915 DRM driver. It uses the HDMI DRM connector name to differentiate > between each HDMI ports. > The changes will allow the i915 HDMI code to notify EDID

Re: [PATCH 2/3] drm/scheduler: Don't call wait_event_killable for signaled process.

Am 18.05.2018 um 16:44 schrieb Michel Dänzer: On 2018-05-18 11:42 AM, Christian König wrote: Anyway, the kernel can't rely on userspace using O_CLOEXEC. If the flush callback being called from multiple processes is an issue, maybe the flush callback isn't appropriate after all. Userspace could

Re: [PATCH 2/3] drm/scheduler: Don't call wait_event_killable for signaled process.

On 05/18/2018 10:50 AM, Christian König wrote: Am 18.05.2018 um 16:44 schrieb Michel Dänzer: On 2018-05-18 11:42 AM, Christian König wrote: Anyway, the kernel can't rely on userspace using O_CLOEXEC. If the flush callback being called from multiple processes is an issue, maybe the flush

[Bug 106561] ./libdrm_macros.h:26:5: error: 'HAVE_VISIBILITY' is not defined, evaluates to 0 [-Werror,-Wundef]

https://bugs.freedesktop.org/show_bug.cgi?id=106561 --- Comment #1 from Eric Engestrom --- Hi Tomasz, I found this file; is that what you used to configure and compile libdrm? https://abf.io/openmandriva/libdrm/blob/master/libdrm.spec You seem to be using autotools,

RE: [PATCH v3 37/40] drm/i915: Implement the HDCP2.2 support for DP

>-Original Message- >From: dri-devel [mailto:dri-devel-boun...@lists.freedesktop.org] On Behalf Of >Ramalingam C >Sent: Tuesday, April 3, 2018 7:28 PM >To: intel-...@lists.freedesktop.org; dri-devel@lists.freedesktop.org; >seanp...@chromium.org; dan...@ffwll.ch; ch...@chris-wilson.co.uk;

Re: [PATCH v2 3/5] mfd: cros-ec: Introduce CEC commands and events definitions.

Hi Neil, 2018-05-18 15:05 GMT+02:00 Neil Armstrong : > The EC can expose a CEC bus, this patch adds the CEC related definitions > needed by the cros-ec-cec driver. > Having a 16 byte mkbp event size makes it possible to send CEC > messages from the EC to the AP directly

RE: [Intel-gfx] [PATCH v3 38/40] drm/i915: Implement the HDCP2.2 support for HDMI

>-Original Message- >From: Intel-gfx [mailto:intel-gfx-boun...@lists.freedesktop.org] On Behalf Of >Ramalingam C >Sent: Tuesday, April 3, 2018 7:28 PM >To: intel-...@lists.freedesktop.org; dri-devel@lists.freedesktop.org; >seanp...@chromium.org; dan...@ffwll.ch; ch...@chris-wilson.co.uk;

Re: [Intel-gfx] [PATCH v3 30/40] drm/i915: Initialize HDCP2.2 and its MEI interface

On Friday 18 May 2018 06:03 PM, Shankar, Uma wrote: -Original Message- From: Intel-gfx [mailto:intel-gfx-boun...@lists.freedesktop.org] On Behalf Of Ramalingam C Sent: Tuesday, April 3, 2018 7:28 PM To: intel-...@lists.freedesktop.org; dri-devel@lists.freedesktop.org;

RE: [Intel-gfx] [PATCH v3 39/40] drm/i915: Add HDCP2.2 support for DP connectors

>-Original Message- >From: Intel-gfx [mailto:intel-gfx-boun...@lists.freedesktop.org] On Behalf Of >Ramalingam C >Sent: Tuesday, April 3, 2018 7:28 PM >To: intel-...@lists.freedesktop.org; dri-devel@lists.freedesktop.org; >seanp...@chromium.org; dan...@ffwll.ch; ch...@chris-wilson.co.uk;

[PATCH] drm/nouveau/kms/nv50-: fix drm-get-put.cocci warnings

From: kbuild test robot Use drm_*_get() and drm_*_put() helpers instead of drm_*_reference() and drm_*_unreference() helpers. Generated by: scripts/coccinelle/api/drm-get-put.cocci Fixes: 30ed49b55b6e ("drm/nouveau/kms/nv50-: move code underneath dispnv50/")

Re: [PATCH v2 12/26] drm/sun4i: Add support for multiple DW HDMI PHY clock parents

On Fri, May 18, 2018 at 04:46:41PM +0200, Jernej Škrabec wrote: > > And this is a bit sloppy, since if phy_clk_num == 3, you won't try to > > lookup pll-2 either. > > It is highly unlikely this will be higher than 2, at least for this HDMI PHY, > since it has only 1 bit reserved for parent

Re: [PATCH 0/2] gpu: ipu-v3: csi: add RGB565 support

On Thu, 2018-05-03 at 18:29 +0200, Jan Luebbe wrote: > This series adds support to capture in RGB565 format on the parallel bus > by using the bayer (generic) mode instead. > > It also contains a small cleanup patch to pass on error codes from > mbus_code_to_bus_cfg in fill_csi_bus_cfg and

Re: [PATCH v5 3/4] phy: rockchip-typec: support variable phy config value

Hi, Am Donnerstag, 17. Mai 2018, 11:17:59 CEST schrieb Lin Huang: > the phy config values used to fix in dp firmware, but some boards > need change these values to do training and get the better eye diagram > result. So support that in phy driver. > > Signed-off-by: Chris Zhong

RE: [Intel-gfx] [PATCH v3 40/40] drm/i915: Add HDCP2.2 support for HDMI connectors

>-Original Message- >From: Intel-gfx [mailto:intel-gfx-boun...@lists.freedesktop.org] On Behalf Of >Ramalingam C >Sent: Tuesday, April 3, 2018 7:28 PM >To: intel-...@lists.freedesktop.org; dri-devel@lists.freedesktop.org; >seanp...@chromium.org; dan...@ffwll.ch; ch...@chris-wilson.co.uk;

[PATCH libdrm v2 1/3] amdgpu: Take lock before removing devices from fd_tab hash table.

Close the file descriptors under lock as well. v2: close fds after removing from hash table Signed-off-by: Jan Vesely --- amdgpu/amdgpu_device.c | 11 +++ 1 file changed, 7 insertions(+), 4 deletions(-) diff --git a/amdgpu/amdgpu_device.c

[PATCH libdrm 2/3] amdgpu/util_hash_table: Add helper function to count the number of entries in hash table

Analogous to the mesa commit of the same name. Signed-off-by: Jan Vesely --- amdgpu/util_hash_table.c | 12 amdgpu/util_hash_table.h | 2 ++ 2 files changed, 14 insertions(+) diff --git a/amdgpu/util_hash_table.c b/amdgpu/util_hash_table.c index

[PATCH libdrm 3/3] amdgpu: Destroy fd_hash table when the last device is removed.

Fixes memory leak on module unload. Analogous to mesa commit of the same name. Signed-off-by: Jan Vesely --- amdgpu/amdgpu_device.c | 4 1 file changed, 4 insertions(+) diff --git a/amdgpu/amdgpu_device.c b/amdgpu/amdgpu_device.c index e23dd3b3..34ac95b8 100644 ---

[PATCH v8 2/3] drm: writeback: Add out-fences for writeback connectors

From: Brian Starkey Add the WRITEBACK_OUT_FENCE_PTR property to writeback connectors, to enable userspace to get a fence which will signal once the writeback is complete. It is not allowed to request an out-fence without a framebuffer attached to the connector. A timeline

Re: [PATCH v5 4/4] drm/rockchip: support dp training outside dp firmware

On Fri, May 18, 2018 at 10:52:17AM +0200, Heiko Stuebner wrote: > Am Freitag, 18. Mai 2018, 03:45:46 CEST schrieb Brian Norris: > > On Thu, May 17, 2018 at 6:41 PM, hl wrote: > > > On Thursday, May 17, 2018 09:51 PM, Sean Paul wrote: > > >> On Thu, May 17, 2018 at 05:18:00PM

Re: [PATCH v2 1/5] media: cec-notifier: Get notifier by device and connector name

On Fri, May 18, 2018 at 03:05:00PM +0200, Neil Armstrong wrote: > In non device-tree world, we can need to get the notifier by the driver > name directly and eventually defer probe if not yet created. > > This patch adds a variant of the get function by using the device name > instead and will

RE: [PATCH v3 35/40] drm/i915: Check HDCP 1.4 and 2.2 link on CP_IRQ

>-Original Message- >From: dri-devel [mailto:dri-devel-boun...@lists.freedesktop.org] On Behalf Of >Ramalingam C >Sent: Tuesday, April 3, 2018 7:28 PM >To: intel-...@lists.freedesktop.org; dri-devel@lists.freedesktop.org; >seanp...@chromium.org; dan...@ffwll.ch; ch...@chris-wilson.co.uk;

Re: [PATCH] gpu: ipu-csi: add rgb/bgr888 24bit support to mbus_code_to_bus_cfg

On Wed, 2018-05-02 at 14:52 +0200, Michael Grzeschik wrote: > The 24bit RGB format configuration is currently missing, we add > it now. > > Signed-off-by: Michael Grzeschik Applied to imx-drm/next. regards Philipp ___

Re: [PATCH v5 2/4] Documentation: bindings: add phy_config for Rockchip USB Type-C PHY

Am Donnerstag, 17. Mai 2018, 11:17:58 CEST schrieb Lin Huang: > If want to do training outside DP Firmware, need phy voltage swing > and pre_emphasis value. > > Signed-off-by: Lin Huang > --- > Changes in v2: > - None > Changes in v3: > - modify property description and add

Re: [PATCH v5 4/4] drm/rockchip: support dp training outside dp firmware

Am Freitag, 18. Mai 2018, 17:36:56 CEST schrieb Sean Paul: > On Fri, May 18, 2018 at 10:52:17AM +0200, Heiko Stuebner wrote: > > Am Freitag, 18. Mai 2018, 03:45:46 CEST schrieb Brian Norris: > > > On Thu, May 17, 2018 at 6:41 PM, hl wrote: > > > > On Thursday, May 17, 2018

Re: [PATCH v5 2/4] Documentation: bindings: add phy_config for Rockchip USB Type-C PHY

On Thu, May 17, 2018 at 05:17:58PM +0800, Lin Huang wrote: > If want to do training outside DP Firmware, need phy voltage swing > and pre_emphasis value. "dt-bindings: phy: ..." for the subject please. > > Signed-off-by: Lin Huang > --- > Changes in v2: > - None > Changes

Re: [PATCH v4 2/2] drm/panel: Add device_link from panel device to drm device

On 18/05/18 14:51, Andrzej Hajda wrote: > On 26.04.2018 10:07, Jyri Sarha wrote: >> Add device_link from panel device (supplier) to drm device (consumer) >> when drm_panel_attach() is called. This patch should protect the >> master drm driver if an attached panel driver unbinds while it is in >>

Re: [PATCH v2 0/5] Add ChromeOS EC CEC Support

Hi Neil, 2018-05-18 15:04 GMT+02:00 Neil Armstrong : > Hi All, > > The new Google "Fizz" Intel-based ChromeOS device is gaining CEC support > through it's Embedded Controller, to enable the Linux CEC Core to communicate > with it and get the CEC Physical Address from the

RE: [Intel-gfx] [PATCH v3 30/40] drm/i915: Initialize HDCP2.2 and its MEI interface

>-Original Message- >From: Intel-gfx [mailto:intel-gfx-boun...@lists.freedesktop.org] On Behalf Of >Ramalingam C >Sent: Tuesday, April 3, 2018 7:28 PM >To: intel-...@lists.freedesktop.org; dri-devel@lists.freedesktop.org; >seanp...@chromium.org; dan...@ffwll.ch; ch...@chris-wilson.co.uk;

RE: [Intel-gfx] [PATCH v3 33/40] drm/i915: Enable HDCP1.4 incase of HDCP2.2 failure

>-Original Message- >From: Intel-gfx [mailto:intel-gfx-boun...@lists.freedesktop.org] On Behalf Of >Ramalingam C >Sent: Tuesday, April 3, 2018 7:28 PM >To: intel-...@lists.freedesktop.org; dri-devel@lists.freedesktop.org; >seanp...@chromium.org; dan...@ffwll.ch; ch...@chris-wilson.co.uk;

  1   2   >