Re: [RFC PATCH 1/3] atmel-hlcdc: add support for 8-bit color lookup table mode

Le Sat, 17 Jun 2017 00:46:12 +0200, Peter Rosin a écrit : > Hm, it's probably too late to do it here. Planes have already been > enabled and the engine may have started to fetch data and do the > composition. You could do that in ->update_plane() [1], and make it

[Bug 101189] Latest git fails to compile with radeon

https://bugs.freedesktop.org/show_bug.cgi?id=101189 --- Comment #16 from Pavel Vinogradov --- try current git, the patchset was applied there smoothly. (In reply to Benji Wiebe from comment #15) > With this patch https://patchwork.freedesktop.org/patch/158696/ the build

[Bug 101189] Latest git fails to compile with radeon

https://bugs.freedesktop.org/show_bug.cgi?id=101189 Benji Wiebe changed: What|Removed |Added Resolution|FIXED |---

Re: [PATCH 5/5] amdgpu: use drm sync objects for shared semaphores (v5)

> team which seem to make a lot of sense to upstream as well: > > 1. An IOCTL to reset a sync object to it's initial state. E.g. reset the > fence the sync objects wraps back to NULL. > > 2. The ability to merge multiple sync objects into one. Essentially the same > thing we have for the sync

[PATCH] libdrm: add drm syncobj create/destroy/import/export

From: Dave Airlie These ioctls are now in drm next so add the first set of libdrm APIs. Signed-off-by: Dave Airlie --- include/drm/drm.h | 26 ++ xf86drm.c | 81 +++ xf86drm.h

[Bug 101473] (SI) latest stable & cant boot - Invalid PCI ROM header structure: expecting 0xaa55, got 0x0000

https://bugs.freedesktop.org/show_bug.cgi?id=101473 qmaster...@gmail.com changed: What|Removed |Added Priority|medium |high -- You are receiving this

[Bug 101473] (SI) latest stable & cant boot - Invalid PCI ROM header structure: expecting 0xaa55, got 0x0000

https://bugs.freedesktop.org/show_bug.cgi?id=101473 Bug ID: 101473 Summary: (SI) latest stable & cant boot - Invalid PCI ROM header structure: expecting 0xaa55, got 0x Product: DRI Version: unspecified Hardware: x86-64

[Bug 93826] 2560x1440 @144Hz graphic glitches and bad refresh rate

https://bugs.freedesktop.org/show_bug.cgi?id=93826 --- Comment #69 from withoutaface --- (In reply to iuno from comment #59) > > @withoutaface: You have to rebuild your kernel. ... I rebuild my kernel 4.10.0-22 (ubuntu 17.04) and patched radeon driver (atombios_crtc.c) void

Re: [Freedreno] [PATCH] fixup! drm/msm: Separate locking of buffer resources from struct_mutex

On Fri, Jun 16, 2017 at 5:32 PM, wrote: > Hi Rob, > > This looks good to me! > > Just one nit: msm_gem_vunmap becomes very shrinker specific as it holds the > msm_obj->lock with the shrinker class. Should we have the caller i.e. > msm_gem_shrinker_vmap hold it instead?

Re: [PATCH v3 09/14] drm/i915: add compute_config for YCBCR outputs

Hi Shashank, [auto build test ERROR on drm-intel/for-linux-next] [also build test ERROR on next-20170616] [cannot apply to drm/drm-next v4.12-rc5] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url: https://github.com/0day-ci/linux/commits

[Bug 93727] [Regression] [r600g] Core profile is 3.2 instead of 3.3 in Big Endian PPC

https://bugs.freedesktop.org/show_bug.cgi?id=93727 --- Comment #4 from erhar...@mailbox.org --- Seems it has not been fixed up to now. $ glxinfo | grep -i opengl OpenGL vendor string: X.Org OpenGL renderer string: Gallium 0.4 on AMD CEDAR (DRM 2.49.0 / 4.10.17-gentoo) OpenGL core profile version

[PATCH] drm/i915: fix noderef.cocci warnings

drivers/gpu/drm/i915/i915_gem_execbuffer.c:1224:54-60: ERROR: application of sizeof to pointer sizeof when applied to a pointer typed expression gives the size of the pointer Generated by: scripts/coccinelle/misc/noderef.cocci Signed-off-by: Fengguang Wu ---

[drm-intel:for-linux-next 8/14] drivers/gpu/drm/i915/i915_gem_execbuffer.c:1224:54-60: ERROR: application of sizeof to pointer

tree: git://anongit.freedesktop.org/drm-intel for-linux-next head: 95ff7c7dd7098860bc131c7dec0ad76ca61e796a commit: 2889caa9232109afc8881f29a2205abeb5709d0c [8/14] drm/i915: Eliminate lots of iterations over the execobjects array coccinelle warnings: (new ones prefixed by >>) >>

Re: [PATCH v3 04/14] drm/edid: parse YCBCR 420 videomodes from EDID

Hi Shashank, [auto build test WARNING on drm-intel/for-linux-next] [also build test WARNING on v4.12-rc5 next-20170616] [cannot apply to drm/drm-next] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url: https://github.com/0day-ci/linux

[Bug 101189] Latest git fails to compile with radeon

https://bugs.freedesktop.org/show_bug.cgi?id=101189 Pavel Vinogradov changed: What|Removed |Added Status|REOPENED|RESOLVED

[PATCH 41/44] powerpc/cell: clean up fixed mapping dma_ops initialization

By the time cell_pci_dma_dev_setup calls cell_dma_dev_setup no device can have the fixed map_ops set yet as it's only set by the set_dma_mask method. So move the setup for the fixed case to be only called in that place instead of indirecting through cell_dma_dev_setup. Signed-off-by: Christoph

[PATCH 44/44] powerpc: merge __dma_set_mask into dma_set_mask

Signed-off-by: Christoph Hellwig --- arch/powerpc/include/asm/dma-mapping.h | 1 - arch/powerpc/kernel/dma.c | 13 - 2 files changed, 4 insertions(+), 10 deletions(-) diff --git a/arch/powerpc/include/asm/dma-mapping.h

[PATCH 42/44] powerpc/cell: use the dma_supported method for ops switching

Besides removing the last instance of the set_dma_mask method this also reduced the code duplication. Signed-off-by: Christoph Hellwig --- arch/powerpc/platforms/cell/iommu.c | 25 + 1 file changed, 9 insertions(+), 16 deletions(-) diff --git

[PATCH 43/44] dma-mapping: remove the set_dma_mask method

Signed-off-by: Christoph Hellwig --- arch/powerpc/kernel/dma.c | 4 include/linux/dma-mapping.h | 6 -- 2 files changed, 10 deletions(-) diff --git a/arch/powerpc/kernel/dma.c b/arch/powerpc/kernel/dma.c index 41c749586bd2..466c9f07b288 100644 ---

[PATCH 35/44] x86: remove arch specific dma_supported implementation

And instead wire it up as method for all the dma_map_ops instances. Note that this also means the arch specific check will be fully instead of partially applied in the AMD iommu driver. Signed-off-by: Christoph Hellwig --- arch/x86/include/asm/dma-mapping.h | 3 ---

[PATCH 39/44] xen-swiotlb: remove xen_swiotlb_set_dma_mask

This just duplicates the generic implementation. Signed-off-by: Christoph Hellwig --- drivers/xen/swiotlb-xen.c | 12 1 file changed, 12 deletions(-) diff --git a/drivers/xen/swiotlb-xen.c b/drivers/xen/swiotlb-xen.c index c3a04b2d7532..82fc54f8eb77 100644 ---

[PATCH 32/44] hexagon: remove the unused dma_is_consistent prototype

Signed-off-by: Christoph Hellwig --- arch/hexagon/include/asm/dma-mapping.h | 1 - 1 file changed, 1 deletion(-) diff --git a/arch/hexagon/include/asm/dma-mapping.h b/arch/hexagon/include/asm/dma-mapping.h index 9c15cb5271a6..463dbc18f853 100644 ---

[PATCH 40/44] tile: remove dma_supported and mapping_error methods

These just duplicate the default behavior if no method is provided. Signed-off-by: Christoph Hellwig --- arch/tile/kernel/pci-dma.c | 30 -- 1 file changed, 30 deletions(-) diff --git a/arch/tile/kernel/pci-dma.c b/arch/tile/kernel/pci-dma.c index

[PATCH 38/44] arm: implement ->dma_supported instead of ->set_dma_mask

Same behavior, less code duplication. Signed-off-by: Christoph Hellwig --- arch/arm/common/dmabounce.c | 7 +++ 1 file changed, 3 insertions(+), 4 deletions(-) diff --git a/arch/arm/common/dmabounce.c b/arch/arm/common/dmabounce.c index 6ecd5be5d37e..9a92de63426f 100644 ---

[PATCH 37/44] mips/loongson64: implement ->dma_supported instead of ->set_dma_mask

Same behavior, less code duplication. Signed-off-by: Christoph Hellwig --- arch/mips/loongson64/common/dma-swiotlb.c | 19 +-- 1 file changed, 5 insertions(+), 14 deletions(-) diff --git a/arch/mips/loongson64/common/dma-swiotlb.c

[PATCH 36/44] dma-mapping: remove HAVE_ARCH_DMA_SUPPORTED

Signed-off-by: Christoph Hellwig --- include/linux/dma-mapping.h | 2 -- 1 file changed, 2 deletions(-) diff --git a/include/linux/dma-mapping.h b/include/linux/dma-mapping.h index a57875309bfd..3e5908656226 100644 --- a/include/linux/dma-mapping.h +++ b/include/linux/dma-mapping.h

[PATCH 34/44] arm: remove arch specific dma_supported implementation

And instead wire it up as method for all the dma_map_ops instances. Note that the code seems a little fishy for dmabounce and iommu, but for now I'd like to preserve the existing behavior 1:1. Signed-off-by: Christoph Hellwig --- arch/arm/common/dmabounce.c| 1 +

[PATCH 33/44] openrisc: remove arch-specific dma_supported implementation

This implementation is simply bogus - openrisc only has a simple direct mapped DMA implementation and thus doesn't care about the address. Signed-off-by: Christoph Hellwig --- arch/openrisc/include/asm/dma-mapping.h | 7 --- 1 file changed, 7 deletions(-) diff --git

[PATCH 28/44] sparc: remove arch specific dma_supported implementations

Usually dma_supported decisions are done by the dma_map_ops instance. Switch sparc to that model by providing a ->dma_supported instance for sbus that always returns false, and implementations tailored to the sun4u and sun4v cases for sparc64, and leave it unimplemented for PCI on sparc32, which

[PATCH 30/44] dma-virt: remove dma_supported and mapping_error methods

These just duplicate the default behavior if no method is provided. Signed-off-by: Christoph Hellwig --- lib/dma-virt.c | 12 1 file changed, 12 deletions(-) diff --git a/lib/dma-virt.c b/lib/dma-virt.c index dcd4df1f7174..5c4f11329721 100644 --- a/lib/dma-virt.c +++

[PATCH 31/44] hexagon: remove arch-specific dma_supported implementation

This implementation is simply bogus - hexagon only has a simple direct mapped DMA implementation and thus doesn't care about the address. Signed-off-by: Christoph Hellwig Acked-by: Richard Kuo --- arch/hexagon/include/asm/dma-mapping.h | 2 --

[PATCH 29/44] dma-noop: remove dma_supported and mapping_error methods

These just duplicate the default behavior if no method is provided. Signed-off-by: Christoph Hellwig --- lib/dma-noop.c | 12 1 file changed, 12 deletions(-) diff --git a/lib/dma-noop.c b/lib/dma-noop.c index de26c8b68f34..643a074f139d 100644 --- a/lib/dma-noop.c +++

[PATCH 25/44] arm: implement ->mapping_error

DMA_ERROR_CODE is going to go away, so don't rely on it. Signed-off-by: Christoph Hellwig --- arch/arm/common/dmabounce.c| 13 +--- arch/arm/include/asm/dma-iommu.h | 2 ++ arch/arm/include/asm/dma-mapping.h | 1 - arch/arm/mm/dma-mapping.c | 41

[PATCH 27/44] sparc: remove leon_dma_ops

We can just use pci32_dma_ops directly. Signed-off-by: Christoph Hellwig Acked-by: David S. Miller --- arch/sparc/include/asm/dma-mapping.h | 3 +-- arch/sparc/kernel/ioport.c | 5 + 2 files changed, 2 insertions(+), 6 deletions(-) diff --git

[PATCH 22/44] x86/pci-nommu: implement ->mapping_error

DMA_ERROR_CODE is going to go away, so don't rely on it. Signed-off-by: Christoph Hellwig --- arch/x86/kernel/pci-nommu.c | 10 +- 1 file changed, 9 insertions(+), 1 deletion(-) diff --git a/arch/x86/kernel/pci-nommu.c b/arch/x86/kernel/pci-nommu.c index

[PATCH 26/44] dma-mapping: remove DMA_ERROR_CODE

And update the documentation - dma_mapping_error has been supported everywhere for a long time. Signed-off-by: Christoph Hellwig --- Documentation/DMA-API-HOWTO.txt | 31 +-- include/linux/dma-mapping.h | 5 - 2 files changed, 5 insertions(+),

[PATCH 24/44] x86: remove DMA_ERROR_CODE

All dma_map_ops instances now handle their errors through ->mapping_error. Signed-off-by: Christoph Hellwig --- arch/x86/include/asm/dma-mapping.h | 2 -- 1 file changed, 2 deletions(-) diff --git a/arch/x86/include/asm/dma-mapping.h b/arch/x86/include/asm/dma-mapping.h index

[PATCH 23/44] x86/calgary: implement ->mapping_error

DMA_ERROR_CODE is going to go away, so don't rely on it. Signed-off-by: Christoph Hellwig --- arch/x86/kernel/pci-calgary_64.c | 24 1 file changed, 16 insertions(+), 8 deletions(-) diff --git a/arch/x86/kernel/pci-calgary_64.c

[PATCH 20/44] sparc: implement ->mapping_error

DMA_ERROR_CODE is going to go away, so don't rely on it. Signed-off-by: Christoph Hellwig Acked-by: David S. Miller --- arch/sparc/include/asm/dma-mapping.h | 2 -- arch/sparc/kernel/iommu.c| 12 +--- arch/sparc/kernel/iommu_common.h |

[PATCH 21/44] powerpc: implement ->mapping_error

DMA_ERROR_CODE is going to go away, so don't rely on it. Instead define a ->mapping_error method for all IOMMU based dma operation instances. The direct ops don't ever return an error and don't need a ->mapping_error method. Signed-off-by: Christoph Hellwig Acked-by: Michael

[PATCH 19/44] s390: implement ->mapping_error

s390 can also use noop_dma_ops, and while that currently does not return errors it will so in the future. Implementing the mapping_error method is the proper way to have per-ops error conditions. Signed-off-by: Christoph Hellwig Acked-by: Gerald Schaefer

[PATCH 16/44] arm64: remove DMA_ERROR_CODE

The dma alloc interface returns an error by return NULL, and the mapping interfaces rely on the mapping_error method, which the dummy ops already implement correctly. Thus remove the DMA_ERROR_CODE define. Signed-off-by: Christoph Hellwig Reviewed-by: Robin Murphy

[PATCH 15/44] xtensa: remove DMA_ERROR_CODE

xtensa already implements the mapping_error method for its only dma_map_ops instance. Signed-off-by: Christoph Hellwig --- arch/xtensa/include/asm/dma-mapping.h | 2 -- 1 file changed, 2 deletions(-) diff --git a/arch/xtensa/include/asm/dma-mapping.h

[PATCH 18/44] iommu/amd: implement ->mapping_error

DMA_ERROR_CODE is going to go away, so don't rely on it. Signed-off-by: Christoph Hellwig --- drivers/iommu/amd_iommu.c | 18 +- 1 file changed, 13 insertions(+), 5 deletions(-) diff --git a/drivers/iommu/amd_iommu.c b/drivers/iommu/amd_iommu.c index

[PATCH 17/44] hexagon: switch to use ->mapping_error for error reporting

Signed-off-by: Christoph Hellwig Acked-by: Richard Kuo --- arch/hexagon/include/asm/dma-mapping.h | 2 -- arch/hexagon/kernel/dma.c | 12 +--- arch/hexagon/kernel/hexagon_ksyms.c| 1 - 3 files changed, 9 insertions(+), 6 deletions(-)

[PATCH 14/44] sh: remove DMA_ERROR_CODE

sh does not return errors for dma_map_page. Signed-off-by: Christoph Hellwig --- arch/sh/include/asm/dma-mapping.h | 2 -- 1 file changed, 2 deletions(-) diff --git a/arch/sh/include/asm/dma-mapping.h b/arch/sh/include/asm/dma-mapping.h index d99008af5f73..9b06be07db4d 100644 ---

[PATCH 12/44] microblaze: remove DMA_ERROR_CODE

microblaze does not return errors for dma_map_page. Signed-off-by: Christoph Hellwig --- arch/microblaze/include/asm/dma-mapping.h | 2 -- 1 file changed, 2 deletions(-) diff --git a/arch/microblaze/include/asm/dma-mapping.h b/arch/microblaze/include/asm/dma-mapping.h index

[PATCH 13/44] openrisc: remove DMA_ERROR_CODE

openrisc does not return errors for dma_map_page. Signed-off-by: Christoph Hellwig --- arch/openrisc/include/asm/dma-mapping.h | 2 -- 1 file changed, 2 deletions(-) diff --git a/arch/openrisc/include/asm/dma-mapping.h b/arch/openrisc/include/asm/dma-mapping.h index

[PATCH 08/44] xen-swiotlb: implement ->mapping_error

DMA_ERROR_CODE is going to go away, so don't rely on it. Signed-off-by: Christoph Hellwig Reviewed-by: Konrad Rzeszutek Wilk --- drivers/xen/swiotlb-xen.c | 12 ++-- 1 file changed, 10 insertions(+), 2 deletions(-) diff --git

[PATCH 10/44] ia64: remove DMA_ERROR_CODE

All ia64 dma_mapping_ops instances already have a mapping_error member. Signed-off-by: Christoph Hellwig --- arch/ia64/include/asm/dma-mapping.h | 2 -- 1 file changed, 2 deletions(-) diff --git a/arch/ia64/include/asm/dma-mapping.h b/arch/ia64/include/asm/dma-mapping.h index

[PATCH 11/44] m32r: remove DMA_ERROR_CODE

dma-noop is the only dma_mapping_ops instance for m32r and does not return errors. Signed-off-by: Christoph Hellwig --- arch/m32r/include/asm/dma-mapping.h | 2 -- 1 file changed, 2 deletions(-) diff --git a/arch/m32r/include/asm/dma-mapping.h

[PATCH 07/44] xen-swiotlb: consolidate xen_swiotlb_dma_ops

ARM and x86 had duplicated versions of the dma_ops structure, the only difference is that x86 hasn't wired up the set_dma_mask, mmap, and get_sgtable ops yet. On x86 all of them are identical to the generic version, so they aren't needed but harmless. All the symbols used only for

[PATCH 01/44] firmware/ivc: use dma_mapping_error

DMA_ERROR_CODE is not supposed to be used by drivers. Signed-off-by: Christoph Hellwig Acked-by: Thierry Reding --- drivers/firmware/tegra/ivc.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/drivers/firmware/tegra/ivc.c

[PATCH 02/44] ibmveth: properly unwind on init errors

That way the driver doesn't have to rely on DMA_ERROR_CODE, which is not a public API and going away. Signed-off-by: Christoph Hellwig Acked-by: David S. Miller --- drivers/net/ethernet/ibm/ibmveth.c | 159 + 1 file changed,

[PATCH 06/44] iommu/dma: don't rely on DMA_ERROR_CODE

DMA_ERROR_CODE is not a public API and will go away soon. dma dma-iommu driver already implements a proper ->mapping_error method, so it's only using the value internally. Add a new local define using the value that arm64 which is the only current user of dma-iommu. Signed-off-by: Christoph

[PATCH 09/44] c6x: remove DMA_ERROR_CODE

Signed-off-by: Christoph Hellwig --- arch/c6x/include/asm/dma-mapping.h | 5 - 1 file changed, 5 deletions(-) diff --git a/arch/c6x/include/asm/dma-mapping.h b/arch/c6x/include/asm/dma-mapping.h index aca9f755e4f8..05daf1038111 100644 --- a/arch/c6x/include/asm/dma-mapping.h

[PATCH 05/44] drm/armada: don't abuse DMA_ERROR_CODE

dev_addr isn't even a dma_addr_t, and DMA_ERROR_CODE has never been a valid driver API. Add a bool mapped flag instead. Signed-off-by: Christoph Hellwig --- drivers/gpu/drm/armada/armada_fb.c | 2 +- drivers/gpu/drm/armada/armada_gem.c | 5 ++---

[PATCH 04/44] drm/exynos: don't use DMA_ERROR_CODE

DMA_ERROR_CODE already isn't a valid API to user for drivers and will go away soon. exynos_drm_fb_dma_addr uses it a an error return when the passed in index is invalid, but the callers never check for it but instead pass the address straight to the hardware. Add a WARN_ON instead and just

[PATCH 03/44] dmaengine: ioat: don't use DMA_ERROR_CODE

DMA_ERROR_CODE is not a public API and will go away. Instead properly unwind based on the loop counter. Signed-off-by: Christoph Hellwig Acked-by: Dave Jiang Acked-By: Vinod Koul --- drivers/dma/ioat/init.c | 24

clean up and modularize arch dma_mapping interface V2

Hi all, for a while we have a generic implementation of the dma mapping routines that call into per-arch or per-device operations. But right now there still are various bits in the interfaces where don't clearly operate on these ops. This series tries to clean up a lot of those (but not all

Re: [PATCH 2/2] drm/vc4: Add get/set tiling ioctls.

Daniel Stone writes: > On 13 June 2017 at 16:49, Eric Anholt wrote: >> Daniel Stone writes: >>> I posted a DRI3 v1.1 patch series which can advertise and also transit >>> modifiers directly under X11, and have also typed up the

[Bug 97820] [BDW BYT SKL HSW IVB]Regression] [GPU Hang] with gem_reset_stats ban- and reset-stats- subtests

https://bugs.freedesktop.org/show_bug.cgi?id=97820 --- Comment #9 from Michel Thierry --- (In reply to Jari Tahvanainen from comment #8) > If this requires the change on test then should one change the component to > IGT instead of DRM/Intel? Hi, Antonio modified the

Re: [PATCH] drm: hdlcd: Update PM code to save/restore console.

Den 16.06.2017 15.53, skrev Liviu Dudau: Update the PM code to suspend/resume the fbdev_cma console. Signed-off-by: Liviu Dudau --- drivers/gpu/drm/arm/hdlcd_drv.c | 11 ++- 1 file changed, 10 insertions(+), 1 deletion(-) diff --git

Re: [RFC PATCH 1/3] atmel-hlcdc: add support for 8-bit color lookup table mode

Hi Peter, On Fri, 16 Jun 2017 17:54:04 +0200 Peter Rosin wrote: > On 2017-06-16 12:01, Boris Brezillon wrote: > > Hi Peter, > > > > On Fri, 16 Jun 2017 11:12:25 +0200 > > Peter Rosin wrote: > > > >> All layers of chips support this, the only variable is

Re: [PATCH 1/7] drm/bridge: Support hotplugging panel-bridge.

Archit Taneja writes: > On 06/16/2017 02:11 AM, Eric Anholt wrote: >> If the panel-bridge is being set up after the drm_mode_config_reset(), >> then the connector's state would never get initialized, and we'd >> dereference the NULL in the hotplug path. We also need to

[Bug 101387] amdgpu display corruption and hang on AMD A10-9620P

https://bugs.freedesktop.org/show_bug.cgi?id=101387 --- Comment #19 from Carlo Caione --- Those patches do not solve the issue but I noticed that the visual corruption at boot is not reproducible on the latest linus master. I bisected and found out that the commit solving the

[PATCH] fixup! drm/msm: Separate locking of buffer resources from struct_mutex

--- Ok, 2nd fixup to handle vmap shrinking. drivers/gpu/drm/msm/msm_gem.c | 44 +++ 1 file changed, 36 insertions(+), 8 deletions(-) diff --git a/drivers/gpu/drm/msm/msm_gem.c b/drivers/gpu/drm/msm/msm_gem.c index f5d1f84..3190e05 100644 ---

[GIT PULL] fbdev fixes for v4.12-rc6

Hi Linus, Please pull fbdev fixes for v4.12-rc6. Best regards, -- Bartlomiej Zolnierkiewicz Samsung R Institute Poland Samsung Electronics The following changes since commit 32c1431eea4881a6b17bd7c639315010aeefa452: Linux 4.12-rc5 (2017-06-11 16:48:20 -0700) are available in the git

[PATCH v2] drm/mediatek: separate color module to fixup error memory reallocation

Previous patch (c5f228ef6c drm/mediatek: add *driver_data for different hardware settings) calls devm_kfree() and then devm_kzalloc() to reallocate color module data structure. But this reallocation cannnot guarantee the new address is unchanged, but the caller will use the old address, which is

Re: [PATCH] drm/mediatek: fixup error memory reallocation

On Wed, 2017-06-14 at 09:19 +0800, CK Hu wrote: > On Mon, 2017-06-12 at 15:15 +0800, YT Shen wrote: > > Previous patch (c5f228ef6c drm/mediatek: add *driver_data for different > > hardware settings) calls devm_kfree() and then devm_kzalloc() to > > reallocate color module data structure. But this

[PATCH] drm: hdlcd: Update PM code to save/restore console.

Update the PM code to suspend/resume the fbdev_cma console. Signed-off-by: Liviu Dudau --- drivers/gpu/drm/arm/hdlcd_drv.c | 11 ++- 1 file changed, 10 insertions(+), 1 deletion(-) diff --git a/drivers/gpu/drm/arm/hdlcd_drv.c b/drivers/gpu/drm/arm/hdlcd_drv.c index

[PATCH] drm/arm: hdlcd: Use CMA helper for plane buffer address calculation

CMA has gained a recent helper function for calculating the start of the plane buffer's physical address. Use that instead of the hand rolled version. Signed-off-by: Liviu Dudau --- drivers/gpu/drm/arm/hdlcd_crtc.c | 9 + 1 file changed, 1 insertion(+), 8

[PATCH] drm/arm: mali-dp: Use CMA helper for plane buffer address calculation

CMA has gained a recent helper function for calculating the start of a plane buffer's physical address. Use that instead of the hand rolled version. Cc: Brian Starkey Signed-off-by: Liviu Dudau --- drivers/gpu/drm/arm/malidp_planes.c | 12

Re: [RFC PATCH 1/3] atmel-hlcdc: add support for 8-bit color lookup table mode

Hi Peter, On Fri, 16 Jun 2017 11:12:25 +0200 Peter Rosin wrote: > All layers of chips support this, the only variable is the base address > of the lookup table in the register map. > > Signed-off-by: Peter Rosin > --- >

Re: [PATCH 2/2] drm/vc4: Add get/set tiling ioctls.

On 13 June 2017 at 16:49, Eric Anholt wrote: > Daniel Stone writes: >> I posted a DRI3 v1.1 patch series which can advertise and also transit >> modifiers directly under X11, and have also typed up the support for >> Wayland which is working just fine with

[drm:drm-next 16/16] drivers/gpu//drm/i915/intel_dp.c:1551:12: error: 'rate_to_index' defined but not used

tree: git://people.freedesktop.org/~airlied/linux.git drm-next head: 925344ccc91d7a7fd84cab2dece1c34bbd86fd8c commit: 925344ccc91d7a7fd84cab2dece1c34bbd86fd8c [16/16] BackMerge tag 'v4.12-rc5' into drm-next config: x86_64-randconfig-it0-06161413 (attached as .config) compiler: gcc-4.9 (Debian

Re: [PATCH 33/44] openrisc: remove arch-specific dma_supported implementation

On Fri, Jun 09, 2017 at 02:20:42PM +0200, Geert Uytterhoeven wrote: > Hi Christoph, > > On Thu, Jun 8, 2017 at 3:25 PM, Christoph Hellwig wrote: > > This implementation is simply bogus - hexagon only has a simple > > openrisc? Yeah. ___

Re: [PATCH 28/44] sparc: remove arch specific dma_supported implementations

On Fri, Jun 09, 2017 at 12:22:48AM +1000, Julian Calaby wrote: > I'm guessing there's a few places that have DMA ops but DMA isn't > actually supported. Why not have a common method for this, maybe > "dma_not_supported"? It's not common at all. Except for sbus all dma API user first call

Re: [PATCH 06/44] iommu/dma: don't rely on DMA_ERROR_CODE

On Thu, Jun 08, 2017 at 02:59:07PM +0100, Robin Murphy wrote: > Hi Christoph, > > On 08/06/17 14:25, Christoph Hellwig wrote: > > DMA_ERROR_CODE is not a public API and will go away soon. dma dma-iommu > > driver already implements a proper ->mapping_error method, so it's only > > using the

Re: [PATCH 27/44] sparc: remove leon_dma_ops

On Mon, Jun 12, 2017 at 10:06:26AM +0200, Andreas Larsson wrote: > Yes, it is needed. LEON systems are AMBA bus based. The common case here is > DMA over AMBA buses. Some LEON systems have PCI bridges, but in general > CONFIG_PCI is not a given. Ok, and even for AMBA we use the pci ops, so I'll

Re: [PATCH 25/44] arm: implement ->mapping_error

On Thu, Jun 08, 2017 at 03:43:14PM +0100, Russell King - ARM Linux wrote: > BOn Thu, Jun 08, 2017 at 03:25:50PM +0200, Christoph Hellwig wrote: > > +static int dmabounce_mapping_error(struct device *dev, dma_addr_t dma_addr) > > +{ > > + if (dev->archdata.dmabounce) > > + return 0; >

[PATCH v2] drm/vc4: Send a VBLANK event when disabling a CRTC

VBLANK events are missed when the CRTC is being disabled because the driver does not wait till the end of the frame before stopping the HVS and PV blocks. In this case, we should explicitly issue a VBLANK event if there's one waiting. Signed-off-by: Boris Brezillon

Re: [PATCH 5/5] amdgpu: use drm sync objects for shared semaphores (v5)

Am 15.06.2017 um 05:59 schrieb Dave Airlie: On 1 June 2017 at 11:06, Dave Airlie wrote: From: Dave Airlie This creates a new command submission chunk for amdgpu to add in and out sync objects around the submission. Sync objects are managed via the drm

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

Hi Dave, The following changes since commit 2ea659a9ef488125eb46da6eb571de5eae5c43f6: Linux 4.12-rc1 (2017-05-13 13:19:49 -0700) are available in the git repository at: git://anongit.freedesktop.org/tegra/linux tags/drm/tegra/for-4.13-rc1 for you to fetch changes up to

[PATCH] drm/exynos: dsi: do not try to find bridge

It doesn't need to try to find a bridge if bridge node doesn't exist. Signed-off-by: Inki Dae --- drivers/gpu/drm/exynos/exynos_drm_dsi.c | 8 +--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/drivers/gpu/drm/exynos/exynos_drm_dsi.c

Re: [PATCH 2/7] drm/vc4: Fix vblank handling

On Thu, 15 Jun 2017 16:30:58 -0700 Eric Anholt wrote: > Boris Brezillon writes: > > > There are two problems related to VBLANK handling in the current CRTC > > driver: > > > > * VBLANK events are missed when the CRTC is being disabled

Re: [PATCH 3/7] drm/vc4: Mimic drm_atomic_helper_commit() behavior

On Thu, 15 Jun 2017 16:33:11 -0700 Eric Anholt wrote: > Eric Anholt writes: > > > [ Unknown signature status ] > > Boris Brezillon writes: > > > >> On Tue, 06 Jun 2017 13:27:09 -0700 > >> Eric Anholt

Re: [PATCH] bridge: Fix panel-bridge error return on !panel.

On 06/15/2017 11:24 PM, Eric Anholt wrote: ERR_PTR() needs a negative errno argument. Thanks, I'll queue it to drm-misc-next-fixes once it's opened. Archit Signed-off-by: Eric Anholt --- drivers/gpu/drm/bridge/panel.c | 2 +- 1 file changed, 1 insertion(+), 1

Re: R7-250X: Vulkan: Doom lockups.

Hi Mike, On 16 June 2017 at 05:48, Mike Mestnik wrote: > I can tell by the 2 color(green and violet) rendering that this driver > is experimental. Attached is kern.log from some testing I've done. > You might be interested in the following bug report. It's the first hit