[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 #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

[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

[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 102009] [clover, amdgcn] Blender crashes when compiling OpenCL kernel

https://bugs.freedesktop.org/show_bug.cgi?id=102009 Jan Vesely changed: What|Removed |Added Summary|Blender crashes when|[clover, amdgcn]

[Bug 106571] Stoney [Radeon R5 Graphics] [1002:98E4] hangs on hibernate

https://bugs.freedesktop.org/show_bug.cgi?id=106571 Bug ID: 106571 Summary: Stoney [Radeon R5 Graphics] [1002:98E4] hangs on hibernate Product: DRI Version: unspecified Hardware: x86-64 (AMD64) OS: Linux

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

On Freitag, 18. Mai 2018 09:14:36 CEST Maxime Ripard wrote: > On Mon, May 14, 2018 at 10:36:08PM +0200, Paul Kocialkowski wrote: > > > > + backlight: backlight { > > > > + compatible = "pwm-backlight"; > > > > + pwms = < 0 5 PWM_POLARITY_INVERTED>; > > > > +

[GIT PULL] drm/tegra: Changes for v4.18-rc1

Hi Dave, The following changes since commit 60cc43fc888428bb2f18f08997432d426a243338: Linux 4.17-rc1 (2018-04-15 18:24:20 -0700) are available in the Git repository at: git://anongit.freedesktop.org/tegra/linux tags/drm/tegra/for-4.18-rc1 for you to fetch changes up to

Re: [PATCH v2] drm/tegra: Add kerneldoc for UAPI

On Sat, May 19, 2018 at 01:28:17AM +0300, Dmitry Osipenko wrote: > On 19.05.2018 01:24, Thierry Reding wrote: > > On Sat, May 19, 2018 at 01:18:05AM +0300, Dmitry Osipenko wrote: > >> On 19.05.2018 01:13, Thierry Reding wrote: > >>> On Fri, May 18, 2018 at 11:58:19PM +0200, Thierry Reding wrote: >

Re: [PATCH v2] drm/tegra: Add kerneldoc for UAPI

On Sat, May 19, 2018 at 01:18:05AM +0300, Dmitry Osipenko wrote: > On 19.05.2018 01:13, Thierry Reding wrote: > > On Fri, May 18, 2018 at 11:58:19PM +0200, Thierry Reding wrote: > >> On Sat, May 19, 2018 at 12:42:22AM +0300, Dmitry Osipenko wrote: > >>> On 18.05.2018 23:33, Thierry Reding wrote: >

Re: [PATCH v2] drm/tegra: Add kerneldoc for UAPI

On Fri, May 18, 2018 at 11:58:19PM +0200, Thierry Reding wrote: > On Sat, May 19, 2018 at 12:42:22AM +0300, Dmitry Osipenko wrote: > > On 18.05.2018 23:33, Thierry Reding wrote: > > > From: Thierry Reding > > > > > > Document the userspace ABI with kerneldoc to provide some

[radeon-alex:amd-staging-drm-next 114/468] sound/soc//amd/raven/pci-acp3x.c:58:8: error: implicit declaration of function 'pci_enable_msi'; did you mean 'pci_enable_sriov'?

Hi Maruthi, FYI, the error/warning still remains. tree: git://people.freedesktop.org/~agd5f/linux.git amd-staging-drm-next head: e92fc21bcb298e0dc2823c7910961c7587de12e5 commit: 2a6630b1095609b26a205b7c537594f3cde99c0a [114/468] ASoC: AMD: enable ACP3x drivers build config: sh-allmodconfig

Re: [PATCH 7/7] drm/tegra: Add kerneldoc for UAPI

On Sat, May 19, 2018 at 12:07:15AM +0300, Dmitry Osipenko wrote: > On 18.05.2018 23:12, Thierry Reding wrote: > > On Fri, May 18, 2018 at 08:19:55PM +0300, Dmitry Osipenko wrote: > >> On 17.05.2018 18:41, Thierry Reding wrote: > >>> From: Thierry Reding > >>> > >>> Document

Re: [PATCH v2] drm/tegra: Add kerneldoc for UAPI

On Sat, May 19, 2018 at 12:42:22AM +0300, Dmitry Osipenko wrote: > On 18.05.2018 23:33, Thierry Reding wrote: > > From: Thierry Reding > > > > Document the userspace ABI with kerneldoc to provide some information on > > how to use it. > > > > v2: > > - keep GEM object

[Bug 106441] Totem video playback stuttering and graphical artifacts

https://bugs.freedesktop.org/show_bug.cgi?id=106441 --- Comment #1 from Richard B. Kreckel --- I can reproduce this: Totem 3.26 is basically unable to play MPEG-4 or H.264 Videos on AMD graphics cards using Mesa 18.0.3. It hangs, lags, and uses almost all available CPU

[PATCH 15/16] iommu: Gracefully allow drivers to not attach to a default domain

Provide individual device drivers the chance to gracefully refuse to attach a device to the default domain. If the attach_device op returns -ENOTSUPP don't print a error message and don't set group->domain but still return success from iommu_group_add_dev(). This allows all the usual APIs to work

[PATCH 13/16] drm/msm/a5xx: Support per-instance pagetables

Add support for per-instance pagetables for 5XX targets. Create a support buffer for preemption to hold the SMMU pagetable information for a preempted ring, enable TTBR1 to support split pagetables and add the necessary PM4 commands to trigger a pagetable switch at the beginning of a user command.

[PATCH 14/16] drm/msm: Support per-instance address spaces

Create a per-instance address spaces when a new DRM file instance is opened assuming the target supports it and the underlying infrastructure exists. If the operation is unsupported fall back quietly to use the global pagetable. Signed-off-by: Jordan Crouse ---

[PATCH 16/16] iommu/arm-smmu: Add list of devices to opt out of DMA domains

Add a list of compatible strings for devices that wish to opt out of attaching to a DMA domain. This is for devices that prefer to manage their own IOMMU space for any number of reasons. Returning -ENOTSUPP for attach device will filter down and force arch_setup_dma_ops() to not set up the iommu

[PATCH 09/16] drm/msm/gpu: Support using split page tables for kernel buffer objects

arm-smmu based targets can support split pagetables (TTBR0/TTBR1). This is most useful for implementing per-instance pagetables so that the "user" pagetable can be swapped out while the "kernel" or "global" pagetable remains entact. if the target specifies a global virtual memory range then try

[PATCH 07/16] drm/msm/gpu: Enable 64 bit mode by default

A5XX GPUs can be run in either 32 or 64 bit mode. The GPU registers and the microcode use 64 bit virtual addressing in either case but the upper 32 bits are ignored if the GPU is in 32 bit mode. There is no performance disadvantage to remaining in 64 bit mode even if we are only generating 32 bit

[PATCH 04/16] iommu: sva: Add support for private PASIDs

Some older SMMU implementations that do not have a fully featured hardware PASID features have alternate workarounds for using multiple pagetables. For example, MSM GPUs have logic to automatically switch the user pagetable from hardware by writing the context bank directly. Support private

[PATCH 12/16] drm/msm: Add support for per-instance address spaces

Add a function to allocate a new pasid from a existing MMU domain and create a per-instance address space. Signed-off-by: Jordan Crouse --- drivers/gpu/drm/msm/msm_drv.h | 3 +++ drivers/gpu/drm/msm/msm_gem_vma.c | 37 +-- 2 files

[PATCH 11/16] drm/msm: Add support for iommu-sva PASIDs

The IOMMU core can support creating multiple pagetables for a specific domai and making them available to a client driver that has the means to manage the pagetable itself. PASIDs are unique indexes to a software created pagetable with the same format and characteristics as the parent IOMMU

[PATCH 06/16] iommu: arm-smmu: Add side-band function for specific PASID callbacks

Just allowing a client driver to create and manage a a private PASID isn't interesting if the client driver doesn't have enough information about the pagetable to be able to use it. Add a side band function for arm-smmu that lets the client device register pasid operations to pass the relevant

[PATCH 08/16] drm/msm: Pass the MMU domain index in struct msm_file_private

Pass the index of the MMU domain in struct msm_file_private instead of assuming gpu->id throughout the submit path. This clears the way to change ctx->aspace to a per-instance pagetable. Signed-off-by: Jordan Crouse --- drivers/gpu/drm/msm/msm_drv.c| 16

[PATCH 10/16] drm/msm: Add msm_mmu features

Add a few simple support functions to support a bitmask of features that a specific MMU implementation supports. The first feature will be per-instance pagetables coming in the following patch. Signed-off-by: Jordan Crouse --- drivers/gpu/drm/msm/msm_mmu.h | 13

[RFC v2 00/16] Private PASID and per-instance pagetables

This is v2 of a patchset of changes to implmeent private PASID support for arm-smmu-v2 targets and implement per-instance pagetables for MSM GPUs. Per-instance pagetables allow the target GPU driver to create and manage an individual pagetable for each file descriptor instance and switch between

[PATCH 01/16] iommu: Add DOMAIN_ATTR_SPLIT_TABLES

Add a new domain attribute to enable split pagetable support for devices devices that support it. Signed-off-by: Jordan Crouse --- include/linux/iommu.h | 1 + 1 file changed, 1 insertion(+) diff --git a/include/linux/iommu.h b/include/linux/iommu.h index

[PATCH 05/16] iommu: arm-smmu: Add support for private PASIDs

Add support for allocating and populating pagetables indexed by private PASIDs. Each new PASID is allocated a pagetable with the same parameters and format as the parent domain. Signed-off-by: Jordan Crouse --- drivers/iommu/arm-smmu.c | 154

[PATCH 02/16] iommu/arm-smmu: Add split pagetable support for arm-smmu-v2

Add support for a split pagetable (TTBR0/TTBR1) scheme for arm-smmu-v2. If split pagetables are enabled, create a pagetable for TTBR1 and set up the sign extension bit so that all IOVAs with that bit set are mapped and translated from the TTBR1 pagetable. Signed-off-by: Jordan Crouse

[PATCH 03/16] iommu/io-pgtable-arm: Remove ttbr[1] from io_pgtbl_cfg

Now that we have a working example of an ARM driver that implements split pagetables completely in the client driver it is apparent that we don't need to store an extra ttbr value in the io_pgtbl_cfg struct that will never get used. Signed-off-by: Jordan Crouse ---

[radeon-alex:drm-next-4.18-wip 44/78] drivers/gpu/drm/amd/amdgpu/soc15.c:680:3-24: duplicated argument to & or | (fwd)

Lines 680 and 682 contain the same constant. julia -- Forwarded message -- Date: Sat, 19 May 2018 04:22:09 +0800 From: kbuild test robot To: kbu...@01.org Cc: Julia Lawall Subject: [radeon-alex:drm-next-4.18-wip 44/78]

[PATCH v2] drm/tegra: Add kerneldoc for UAPI

From: Thierry Reding Document the userspace ABI with kerneldoc to provide some information on how to use it. v2: - keep GEM object creation flags for ABI compatibility - fix typo in struct drm_tegra_syncpt_incr kerneldoc - fix typos in struct drm_tegra_submit kerneldoc -

Re: [PATCH 7/7] drm/tegra: Add kerneldoc for UAPI

On Fri, May 18, 2018 at 08:19:55PM +0300, Dmitry Osipenko wrote: > On 17.05.2018 18:41, Thierry Reding wrote: > > From: Thierry Reding > > > > Document the userspace ABI with kerneldoc to provide some information on > > how to use it. > > > > Signed-off-by: Thierry Reding

[PATCH libdrm] xf86drm: Be sure to closedir before return

removed in commit bb45ce4e3ac751315bfd7fbfd9e1425bf515ec0d Adding it back as it is still needed in the case where we don't find a match. Signed-off-by: Kevin Strasser --- xf86drm.c | 2 ++ 1 file changed, 2 insertions(+) diff --git a/xf86drm.c b/xf86drm.c index

[Bug 86351] HDMI audio garbled output on Radeon R9 280X

https://bugzilla.kernel.org/show_bug.cgi?id=86351 --- Comment #31 from Christian Birchinger (jo...@netswarm.net) --- Because you've referenced bug 101900 and the bug has been marked as fixed there, i've just retested my system with my now old Radeon R9 280X and Kernel 4.16.7 Audio over HDMI

[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 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 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] 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 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: [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;

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;

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 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 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: [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 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: [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 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] 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 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;

[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 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 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 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

[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

[PATCH v8 1/3] drm: Add writeback connector type

From: Brian Starkey Writeback connectors represent writeback engines which can write the CRTC output to a memory framebuffer. Add a writeback connector type and related support functions. Drivers should initialize a writeback connector with drm_writeback_connector_init()

[PATCH v8 0/3] drm: Introduce writeback connectors

Hi, This is v8 of the writeback connector series. v7 got flagged by the kbuild bot as not being correctly bisectable, so I went and fix that. For anyone that wants a refresh on what changed in v6, the series can be found here [2]. The only change in v7 is that the userspace capabilities patch

[PATCH v8 3/3] drm: writeback: Add client capability for exposing writeback connectors

Due to the fact that writeback connectors behave in a special way in DRM (they always report being disconnected) we might confuse some userspace. Add a client capability for writeback connectors that will filter them out for clients that don't understand the capability. Re-requested-by: Sean Paul

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

Re: [PATCH v2 5/5] media: platform: Add Chrome OS EC CEC driver

Hi Neil, 2018-05-18 15:05 GMT+02:00 Neil Armstrong : > The Chrome OS Embedded Controller can expose a CEC bus, this patch add the A minor nit, there is a "consensus" on tell cros-ec as "ChromeOS Embedded Controller" or "ChromeOS EC". Yes, I know that you can see in the

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

[Bug 106175] amdgpu.dc=1 shows performance issues with Xorg compositors when moving windows

https://bugs.freedesktop.org/show_bug.cgi?id=106175 --- Comment #12 from tempel.jul...@gmail.com --- Latest drm-next-4.18-wip aa1bce17d841a362d40da940487e13affe4c7b3b still shows the same behavior. I'd be happy if more users would comment on this, since it makes use of amdgpu.dc totally

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

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 also grab a reference just by

Re: [PATCH v2 1/3] drm/mtk: Remove impossible internal error

On Fri, May 18, 2018 at 02:47:03PM +0100, Daniel Stone wrote: > We cannot create a framebuffer with no objects, so there's no point > testing for it. > > v2: Remove the error entirely. (Sean, CK, Thierry) > > Signed-off-by: Daniel Stone > Cc: Sean Paul

Re: [PATCH v2 16/26] dt-bindings: clock: sun50i-a64-ccu: Add PLL_VIDEO[0-1] macros

On Fri, May 18, 2018 at 03:15:26PM +0530, Jagan Teki wrote: > Allwinner A64 has two clock parents PLL_VIDEO0 and PLL_VIDEO1. > > Include these macros on dt-bindings so-that the same can be > used while defining CCU clock phadles. > > Signed-off-by: Jagan Teki > --- >

[GIT PULL] etnaviv-next for 4.18

Hi Dave, nothing really big in etnaviv land this time. GC7000 support is still slowly cooking but not ready at this time. So what we have for this cycle is a bit of spring cleaning with removal of unused register logging code and getting rid of the license text in favor of SPDX, a few smaller

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

[PATCH v2 3/3] drm/mtk: mtk_drm_fb -> drm_framebuffer

Now that mtk_drm_fb is an empty wrapper around drm_framebuffer, we can just delete it. Signed-off-by: Daniel Stone Reviewed-by: CK Hu Reviewed-by: Thierry Reding Reviewed-by: Sean Paul Cc: Philipp Zabel

[PATCH v2 1/3] drm/mtk: Remove impossible internal error

We cannot create a framebuffer with no objects, so there's no point testing for it. v2: Remove the error entirely. (Sean, CK, Thierry) Signed-off-by: Daniel Stone Cc: Sean Paul Cc: Thierry Reding Cc: CK Hu

[PATCH v2 2/3] drm/mtk: Move GEM BO to drm_framebuffer

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. Signed-off-by: Daniel Stone

Re: [PATCH v2 4/5] mfd: cros_ec_dev: Add CEC sub-device registration

2018-05-18 15:05 GMT+02:00 Neil Armstrong : > The EC can expose a CEC bus, thus add the cros-ec-cec MFD sub-device > when the CEC feature bit is present. > > Signed-off-by: Neil Armstrong > --- > drivers/mfd/cros_ec_dev.c | 16 >

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 hwc] drm_hwcomposer: Support assigning planes in ValidateDisplay

On Thu, May 17, 2018 at 6:25 PM, Stefan Schake wrote: > Hey Rob, > > On Fri, May 18, 2018 at 12:08 AM, Rob Herring wrote: >> In order to assign planes to layers in ValidateDisplay, testing >> compositing with a DRM atomic modeset test is needed as

[PATCH v2 5/5] media: platform: Add Chrome OS EC CEC driver

The Chrome OS Embedded Controller can expose a CEC bus, this patch add the driver for such feature of the Embedded Controller. This driver is part of the cros-ec MFD and will be add as a sub-device when the feature bit is exposed by the EC. The controller will only handle a single logical

[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.

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

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 and HPD changes to an eventual CEC adapter. Signed-off-by: Neil Armstrong

[PATCH v2 4/5] mfd: cros_ec_dev: Add CEC sub-device registration

The EC can expose a CEC bus, thus add the cros-ec-cec MFD sub-device when the CEC feature bit is present. Signed-off-by: Neil Armstrong --- drivers/mfd/cros_ec_dev.c | 16 1 file changed, 16 insertions(+) diff --git a/drivers/mfd/cros_ec_dev.c

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

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 not create a notifier if not yet created. But the i915 driver exposes at

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

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 correct HDMI Connector, the following must be added/changed: - Add the CEC sub-device

RE: [Intel-gfx] [PATCH v3 34/40] drm/i915: hdcp_check_link only on CP_IRQ

>-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: [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: [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;

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

On 05/18/2018 03:39 PM, Thierry Reding wrote: 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

RE: [Intel-gfx] [PATCH v3 32/40] drm/i915: Enable superior HDCP ver that is capable

>-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: [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.

RE: [Intel-gfx] [PATCH v3 31/40] drm/i915: Schedule hdcp_check_link in _intel_hdcp_enable

>-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

>-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: [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:

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 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.

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 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: [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 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] 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: >

  1   2   >