Russell King - ARM Linux writes:
> On Tue, Apr 11, 2017 at 02:00:21PM -0700, Eric Anholt wrote:
>> Russell King - ARM Linux writes:
>>
>> > On Tue, Apr 11, 2017 at 09:06:31AM -0700, Eric Anholt wrote:
>> >> Russell King - ARM Linux
The reflects the purpose of the function better.
Signed-off-by: Laurent Pinchart
---
drivers/gpu/drm/omapdrm/omap_drv.h| 4 ++--
drivers/gpu/drm/omapdrm/omap_fb.c | 6 ++---
drivers/gpu/drm/omapdrm/omap_fbdev.c | 9
To ensure that neither the GEM object nor the DRM device goes away while
a GEM object exported through dma-buf is still accessible, take a
reference to both the GEM object and the DRM device at export time. The
dma-buf release handler already releases the GEM object (which resulted
in a refcount
The omap_gem_cpu_sync() function operates at a page level, while the
omap_gem_dma_sync() function operates at a buffer level. Rename them to
omap_gem_cpu_sync_page() and omap_gem_dma_sync_buffer() respectively to
avoid confusion.
Signed-off-by: Laurent Pinchart
The fields, variables and functions deal with DMA addresses, name them
accordingly. The omap_gem_get_paddr() and omap_gem_put_paddr() will be
addressed differently separately.
Signed-off-by: Laurent Pinchart
---
drivers/gpu/drm/omapdrm/omap_drv.h| 6
This makes the function more readable.
Signed-off-by: Laurent Pinchart
---
drivers/gpu/drm/omapdrm/omap_gem.c | 43 +++---
1 file changed, 21 insertions(+), 22 deletions(-)
diff --git a/drivers/gpu/drm/omapdrm/omap_gem.c
Hello,
This patch series updates and extends the previously posted "[PATCH 1/7]
omapdrm: Fix GEM objects DMA unmapping" series.
Compared to v1, the series now includes an extra cleanup (06/10), a cache
handling performance improvement (09/10) and a dmabuf refcount fix (10/10).
Memory leaks have
The field contains DMA addresses, clarify that by renaming it.
Signed-off-by: Laurent Pinchart
---
drivers/gpu/drm/omapdrm/omap_gem.c | 22 +++---
1 file changed, 11 insertions(+), 11 deletions(-)
diff --git
Both coherent (uncached) and non-coherent (cached) buffers can have
their pages mapped to the device through the DMA mapping API. Make sure
to unmap any mapped page when freeing a buffer, regardless of its type.
Signed-off-by: Laurent Pinchart
---
The display engine only reads from memory, there's no need to use
bidirectional DMA mappings. Use DMA_TO_DEVICE instead.
Signed-off-by: Laurent Pinchart
---
drivers/gpu/drm/omapdrm/omap_gem.c| 11 +--
drivers/gpu/drm/omapdrm/omap_gem_dmabuf.c |
The function is always called with the remap argument set to true.
Hardcode that behaviour and remove it.
Signed-off-by: Laurent Pinchart
---
drivers/gpu/drm/omapdrm/omap_drv.h| 3 +--
drivers/gpu/drm/omapdrm/omap_fb.c | 2 +-
The is_cache_coherent() function currently returns true when the mapping
is not cache-coherent. This isn't a bug as such as the callers interpret
cache-coherent as meaning that the driver has to handle the coherency
manually, but it is nonetheless very confusing. Fix it and add a bit
more
On 20 April 2017 at 19:13, Marek Szyprowski wrote:
> Dear all,
>
> This is an updated proposal for extending EXYNOS DRM API with generic support
> for hardware modules, which can be used for processing image data from the
> one memory buffer to another. Typical
On Tue, Apr 18, 2017 at 12:11:57PM -0700, Eric Anholt wrote:
> Cygnus has V3D 2.6 instead of 2.1, and doesn't use the VC4 display
> modules. The V3D can be uniquely identified by the IDENT[01]
> registers, and there's nothing to key off of for the display change
> other than the lack of DT nodes
https://bugs.freedesktop.org/show_bug.cgi?id=100742
Bug ID: 100742
Summary: dpm auto doesn't clock the GPU high enough for SteamVR
apps
Product: DRI
Version: unspecified
Hardware: Other
OS: All
On Thu, Apr 20, 2017 at 10:11 PM, Sean Paul wrote:
> Hi Dave,
> A few fixes for you to pick up. The driver changes are trivial, and the
> maintainer change was necessitated by the sti fix. The headliner here is the
> dma_buf_ops rename, since it touches so many drivers.
Hi Dave,
A few fixes for you to pick up. The driver changes are trivial, and the
maintainer change was necessitated by the sti fix. The headliner here is the
dma_buf_ops rename, since it touches so many drivers. Everything looks sane and
builds with that change, so it shouldn't cause problems.
On Fri, Apr 21, 2017 at 12:33:59AM +0300, Laurent Pinchart wrote:
> To ensure that neither the GEM object nor the DRM device goes away while
> a GEM object exported through dma-buf is still accessible, take a
> reference to both the GEM object and the DRM device at export time. The
> dma-buf
While reading drm_for_each_connector_iter, I noticed a mention to
drm_connector_begin which doesn't exist. It should be
drm_connector_get.
Signed-off-by: Gabriel Krisman Bertazi
---
include/drm/drm_connector.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff
Include instead of relative path from include/drm, then
remove the -Iinclude/drm compiler flag.
Signed-off-by: Masahiro Yamada
---
drivers/gpu/drm/msm/msm_fbdev.c | 2 +-
drivers/gpu/drm/nouveau/Kbuild| 1 -
drivers/gpu/drm/nouveau/nouveau_drm.c |
Include instead of relative path from include/drm, then
remove the -Iinclude/drm compiler flag.
Signed-off-by: Masahiro Yamada
---
drivers/gpu/drm/vmwgfx/Makefile | 3 ---
drivers/gpu/drm/vmwgfx/vmwgfx_cmdbuf.c | 2 +-
Hi everyone,
Sorry for the late reply. My university exams are in progress and will keep
me busy till 27th April.
First of all, I would like to clear the air a little bit; I do have a
knowledge of C/C++ but the knowledge and understanding is only limited to
pursuing undergraduate level Computer
With the include directives under include/drm/ fixed, this flag is
no longer needed.
Signed-off-by: Masahiro Yamada
---
drivers/gpu/drm/vgem/Makefile | 1 -
1 file changed, 1 deletion(-)
diff --git a/drivers/gpu/drm/vgem/Makefile b/drivers/gpu/drm/vgem/Makefile
On Thu, Apr 20, 2017 at 10:25:01AM +0200, Arnd Bergmann wrote:
> On Thu, Apr 20, 2017 at 9:02 AM, Mikko Perttunen wrote:
> > I think we have a "policy" on Tegra that the DMA API will never allocate
> > using the IOMMU (Thierry can elaborate on this), which is why I wrote the
> >
With the include directives under include/drm/ fixed, this flag is
no longer needed.
Signed-off-by: Masahiro Yamada
---
drivers/gpu/drm/savage/Makefile | 1 -
1 file changed, 1 deletion(-)
diff --git a/drivers/gpu/drm/savage/Makefile
Include instead of relative path from include/drm, then
remove the -Iinclude/drm compiler flag.
Signed-off-by: Masahiro Yamada
---
drivers/gpu/drm/radeon/Makefile | 2 +-
drivers/gpu/drm/radeon/btc_dpm.c | 2 +-
drivers/gpu/drm/radeon/ci_dpm.c |
Include instead of relative path from include/drm, then
remove the -Iinclude/drm compiler flag.
Signed-off-by: Masahiro Yamada
---
drivers/gpu/drm/hisilicon/hibmc/Makefile| 1 -
drivers/gpu/drm/hisilicon/hibmc/hibmc_ttm.c | 2 +-
2 files changed, 1
Include instead of relative path from include/drm, then
remove the -Iinclude/drm compiler flag.
Signed-off-by: Masahiro Yamada
---
drivers/gpu/drm/bridge/Makefile| 2 --
drivers/gpu/drm/bridge/nxp-ptn3460.c | 10 +-
With the include directives under include/drm/ fixed, this flag is
no longer needed.
Signed-off-by: Masahiro Yamada
---
drivers/gpu/drm/r128/Makefile | 1 -
1 file changed, 1 deletion(-)
diff --git a/drivers/gpu/drm/r128/Makefile b/drivers/gpu/drm/r128/Makefile
With the include directives under include/drm/ fixed, this flag is
no longer needed.
Signed-off-by: Masahiro Yamada
---
drivers/gpu/drm/i2c/Makefile | 2 --
1 file changed, 2 deletions(-)
diff --git a/drivers/gpu/drm/i2c/Makefile b/drivers/gpu/drm/i2c/Makefile
Include instead of relative path from include/drm, then
remove the -Iinclude/drm compiler flag.
The fixes of include/drm/ttm/*.h will help driver Makefiles drop
-Iinclude/drm flag.
Signed-off-by: Masahiro Yamada
---
drivers/gpu/drm/ttm/Makefile | 1 -
Include instead of relative path from include/drm, then
remove the -Iinclude/drm compiler flag.
Signed-off-by: Masahiro Yamada
---
drivers/gpu/drm/virtio/Makefile | 2 --
drivers/gpu/drm/virtio/virtgpu_debugfs.c | 2 +-
On 20.04.2017 11:25, Arnd Bergmann wrote:
On Thu, Apr 20, 2017 at 9:02 AM, Mikko Perttunen wrote:
On 19.04.2017 21:24, Arnd Bergmann wrote:
When dma_addr_t and phys_addr_t are not the same size, we get a warning
from the dma_alloc_wc function:
drivers/gpu/host1x/cdma.c: In
Include instead of relative path from include/drm, then
remove the -Iinclude/drm compiler flag.
Signed-off-by: Masahiro Yamada
---
drivers/gpu/drm/amd/amdgpu/Makefile | 2 +-
drivers/gpu/drm/amd/amdgpu/amdgpu.h | 10 +-
With the include directives under include/drm/ fixed, this flag is
no longer needed.
Signed-off-by: Masahiro Yamada
---
drivers/gpu/drm/udl/Makefile | 3 ---
1 file changed, 3 deletions(-)
diff --git a/drivers/gpu/drm/udl/Makefile b/drivers/gpu/drm/udl/Makefile
Include instead of relative path from include/drm, then
remove the -Iinclude/drm compiler flag.
Signed-off-by: Masahiro Yamada
---
drivers/gpu/drm/qxl/Makefile | 2 --
drivers/gpu/drm/qxl/qxl_debugfs.c | 2 +-
drivers/gpu/drm/qxl/qxl_display.c | 2 +-
In several instances the driver passes an 'enum pipe' value to a
function expecting an 'enum transcoder' and viceversa. Since PIPE_x and
TRANSCODER_x have the same values this doesn't cause functional
problems. Still it is incorrect and causes clang to generate warnings
like this:
On Tue, Apr 18, 2017 at 05:40:36PM +0900, Hoegeun Kwon wrote:
> This patch add the panel device tree node for s6e3hf2 display
> controller to TM2e dts.
>
> Signed-off-by: Hoegeun Kwon
> Reviewed-by: Andrzej Hajda
> ---
>
On 20.04.2017 13:02, Arnd Bergmann wrote:
On Thu, Apr 20, 2017 at 11:44 AM, Mikko Perttunen wrote:
On 20.04.2017 11:25, Arnd Bergmann wrote:
On Thu, Apr 20, 2017 at 9:02 AM, Mikko Perttunen wrote:
On 19.04.2017 21:24, Arnd Bergmann wrote:
I don't think
Many Makefiles needed to add -Iinclude/drm as an include path,
but the right thing to do is to include headers in the form
#include
This series fixes the source files, then rip off -Iinclude/drm flags.
Masahiro Yamada (28):
drm/ttm: fix include notation and remove -Iinclude/drm flag
Include instead of relative path from include/drm, then
remove the -Iinclude/drm compiler flag.
Signed-off-by: Masahiro Yamada
---
drivers/gpu/drm/cirrus/Makefile | 1 -
drivers/gpu/drm/cirrus/cirrus_ttm.c | 2 +-
2 files changed, 1 insertion(+), 2
Include instead of relative path from include/drm, then
remove the -Iinclude/drm compiler flag.
Signed-off-by: Masahiro Yamada
---
drivers/gpu/drm/bochs/Makefile | 1 -
drivers/gpu/drm/bochs/bochs.h | 4 ++--
2 files changed, 2 insertions(+), 3 deletions(-)
With the include directives under include/drm/ fixed, this flag is
no longer needed.
Signed-off-by: Masahiro Yamada
---
drivers/gpu/drm/i810/Makefile | 1 -
1 file changed, 1 deletion(-)
diff --git a/drivers/gpu/drm/i810/Makefile b/drivers/gpu/drm/i810/Makefile
Include instead of relative path from include/drm, then
remove the -Iinclude/drm compiler flag.
Signed-off-by: Masahiro Yamada
---
drivers/gpu/drm/tilcdc/Makefile | 1 -
drivers/gpu/drm/tilcdc/tilcdc_drv.c | 2 +-
2 files changed, 1 insertion(+), 2
Include instead of relative path from include/drm, then
remove the -Iinclude/drm compiler flag.
Signed-off-by: Masahiro Yamada
---
drivers/gpu/drm/ast/Makefile | 2 --
drivers/gpu/drm/ast/ast_ttm.c | 2 +-
2 files changed, 1 insertion(+), 3 deletions(-)
diff
With the include directives under include/drm/ fixed, this flag is
no longer needed.
Signed-off-by: Masahiro Yamada
---
drivers/gpu/drm/mga/Makefile | 1 -
1 file changed, 1 deletion(-)
diff --git a/drivers/gpu/drm/mga/Makefile b/drivers/gpu/drm/mga/Makefile
Include instead of relative path from include/drm, then
remove the -Iinclude/drm compiler flag.
While we are here, use <...> instead of "..." for include/linux/*.h
headers too.
Signed-off-by: Masahiro Yamada
---
drivers/gpu/drm/vc4/Makefile| 2 --
Ah, had to forget something :)
Reviewed-by: Mikko Perttunen
On 19.04.2017 21:24, Arnd Bergmann wrote:
When IOMMU_IOVA is not built-in but host1x is, we get a link error:
drivers/gpu/host1x/dev.o: In function `host1x_remove':
dev.c:(.text.host1x_remove+0x50): undefined
Include instead of relative path from include/drm, then
remove the -Iinclude/drm compiler flag.
Signed-off-by: Masahiro Yamada
---
drivers/gpu/drm/mgag200/Makefile | 1 -
drivers/gpu/drm/mgag200/mgag200_ttm.c | 2 +-
2 files changed, 1 insertion(+), 2
With the include directives under include/drm/ fixed, this flag is
no longer needed.
Signed-off-by: Masahiro Yamada
---
drivers/gpu/drm/gma500/Makefile | 1 -
1 file changed, 1 deletion(-)
diff --git a/drivers/gpu/drm/gma500/Makefile
https://bugs.freedesktop.org/show_bug.cgi?id=100745
Bug ID: 100745
Summary: amdgpu fails to wake up DisplayPort DELL monitors with
'clock recovery failed'
Product: DRI
Version: unspecified
Hardware: Other
On Thu, Apr 20, 2017 at 9:36 AM, Maxime Ripard
wrote:
> Hi Rob,
>
> On Thu, Apr 20, 2017 at 09:02:53AM -0500, Rob Herring wrote:
>> On Sun, Apr 16, 2017 at 08:08:40PM +0800, Icenowy Zheng wrote:
>> > diff --git a/include/dt-bindings/clock/sun8i-de2.h
>> >
Hi
If you want I work with a Allwinner A20 (my board are derived from
OlinuXino-Micro-A20), and I will interest with LVDS function.
I use your patch but I have nothing to display on my screen.
You can see my work on
https://github.com/Philippe12/linux-sunxi/tree/sun7i-A20-lvds
My hardware is
With the include directives under include/drm/ fixed, this flag is
no longer needed.
Signed-off-by: Masahiro Yamada
---
drivers/gpu/drm/tdfx/Makefile | 1 -
1 file changed, 1 deletion(-)
diff --git a/drivers/gpu/drm/tdfx/Makefile b/drivers/gpu/drm/tdfx/Makefile
https://bugs.freedesktop.org/show_bug.cgi?id=100058
--- Comment #11 from Edward O'Callaghan ---
(In reply to Adam Wolk from comment #10)
> > Do the patches in bug 99387 help?
>
> This is a machine I use for work unfortunately I can't fiddle with it more.
>
>
https://bugs.freedesktop.org/show_bug.cgi?id=100695
--- Comment #4 from Michel Dänzer ---
Bug 100681 was fixed by LLVM SVN r300791, how about this?
--
You are receiving this mail because:
You are the assignee for the bug.___
https://bugs.freedesktop.org/show_bug.cgi?id=100745
--- Comment #2 from mr.nuke...@gmail.com ---
Created attachment 130957
--> https://bugs.freedesktop.org/attachment.cgi?id=130957=edit
log around the time the problem happens (with excessive debug info)
--
You are receiving this mail because:
https://bugs.freedesktop.org/show_bug.cgi?id=100745
--- Comment #1 from Edward O'Callaghan ---
OK, I had a short look into this,
So it seems that we have that,
amdgpu_atombios_dp_aux_transfer() calls amdgpu_atombios_dp_process_aux_chan()
which has either a
On Thu, Apr 20, 2017 at 10:58 PM, Emil Velikov
wrote:
> On 18 April 2017 at 20:38, Daniel Vetter wrote:
> > On Tue, Apr 18, 2017 at 02:27:14PM -0400, Rob Clark wrote:
> >> On Tue, Apr 18, 2017 at 1:32 PM, Emil Velikov
>
Hi Masahiro,
On 20.04.2017 11:56, Masahiro Yamada wrote:
> Include instead of relative path from include/drm, then
> remove the -Iinclude/drm compiler flag.
>
> Signed-off-by: Masahiro Yamada
> ---
>
> drivers/gpu/drm/bridge/Makefile| 2 --
>
Hi all,
After merging the drm-misc tree, today's linux-next build (x86_64
allmodconfig) failed like this:
drivers/tee/tee_shm.c:87:2: error: unknown field 'kmap_atomic' specified in
initializer
.kmap_atomic = tee_shm_op_kmap_atomic,
^
drivers/tee/tee_shm.c:87:17: error: initialization from
ls)
for this purpose?
TODO:
- convert remaining Exynos DRM IPP drivers (FIMC, GScaller)
- remove Exynos DRM IPP subsystem
- (optional) provide virtual V4L2 mem2mem device on top of Exynos PP
framework
Patches were tested on Exynos 4412-based Odroid U3 board, on top of Linux
next-20170420 kernel.
roject of mine, using such an
API for an Exynos renderer backend for the mpv media player.
With best wishes,
Tobias
>>> Open questions:
>>> - How to expose pp capabilities and supported formats? Currently this is
>>> done with a drm_exynos_pp_get structure and DRM_IOCTL_E
Hi Logan,
Thanks for the patch.
On 20 April 2017 at 13:21, Daniel Vetter wrote:
> On Wed, Apr 19, 2017 at 01:36:10PM -0600, Logan Gunthorpe wrote:
>> Seeing the kunmap_atomic dma_buf_ops share the same name with a macro
>> in highmem.h, the former can be aliased if any dma-buf
ers:
> http://www.spinics.net/lists/dri-devel/msg137380.html
> - Is it okay to use DRM objects and properties API
> (DRM_IOCTL_MODE_GETPROPERTY and DRM_IOCTL_MODE_OBJ_GETPROPERTIES ioctls)
> for this purpose?
>
> TODO:
> - convert remaining Exynos DRM IPP drivers (FIMC, GScaller)
&
We expected to end with "timeout_ms" set to zero, but it's a post-op so
the current code ends with -1. Let's fix this by changing it to a
pre-op.
Fixes: 21898816831f ("drm/mediatek: add dsi transfer function")
Signed-off-by: Dan Carpenter
diff --git
Hi Dan,
On Thu, 2017-04-20 at 13:24 +0300, Dan Carpenter wrote:
> We expected to end with "timeout_ms" set to zero, but it's a post-op so
> the current code ends with -1. Let's fix this by changing it to a
> pre-op.
>
> Fixes: 21898816831f ("drm/mediatek: add dsi transfer function")
>
I'll send a v2 that does that.
regards,
dan carpenter
___
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
On Thu, Apr 20, 2017 at 11:49 AM, Russell King - ARM Linux
wrote:
> On Thu, Apr 20, 2017 at 10:25:01AM +0200, Arnd Bergmann wrote:
>> On Thu, Apr 20, 2017 at 9:02 AM, Mikko Perttunen wrote:
>> > I think we have a "policy" on Tegra that the DMA API will
RM IPP drivers (FIMC, GScaller)
- remove Exynos DRM IPP subsystem
- (optional) provide virtual V4L2 mem2mem device on top of Exynos PP framework
Patches were tested on Exynos 4412-based Odroid U3 board, on top of Linux
next-20170420 kernel.
Best regards
Marek Szyprowski
Samsung R Institute Po
Add a DRM_MODE_PROP_VENDOR flag, which allows to create DRM properties
for vendor, custom DRM objects. This allows to create OBJECT type properties,
which were reserved only for ATOMIC mode sets. This flag is also checked
in drm_object_property_get_value() function to let userspace to get
default
Make drm_mode_object_add() and drm_mode_object_unregister() functions
public, so the drivers can register their own DRM objects to the core.
Those objects can be queried by generic DRM_IOCTL_MODE_OBJ_GETPROPERTIES
ioctl.
Signed-off-by: Marek Szyprowski
---
The omapdrm driver uses a custom API to synchronize with the SGX GPU.
This is unusable as such in the mainline kernel as the API is only
partially implemented and requires additional out-of-tree patches.
Furthermore, as no SGX driver is available in the mainline kernel, the
API can't be considered
On Tue, Apr 18, 2017 at 06:47:56PM +0800, Icenowy Zheng wrote:
> >> + /* Get the physical address of the buffer in memory */
> >> + gem = drm_fb_cma_get_gem_obj(fb, 0);
> >> +
> >> + DRM_DEBUG_DRIVER("Using GEM @ %pad\n", >paddr);
> >> +
> >> + /* Compute the start of the displayed memory */
>
Am 19.04.2017 um 21:14 schrieb Dave Airlie:
On 20 April 2017 at 04:42, Dave Airlie wrote:
On 19 April 2017 at 22:07, Christian König wrote:
Am 13.04.2017 um 03:41 schrieb Dave Airlie:
Okay I've taken Chris's suggestions to heart and reworked
On Wed, 19 Apr 2017, Arnd Bergmann wrote:
> On Wed, Apr 19, 2017 at 10:21 PM, Laurent Pinchart
> wrote:
>>>
>>> This adds a dependency like we have for the other panel drivers.
>>
>> I believe the dependency should be made optional. DPI panels
On Thu, Apr 20, 2017 at 11:44 AM, Mikko Perttunen wrote:
> On 20.04.2017 11:25, Arnd Bergmann wrote:
>> On Thu, Apr 20, 2017 at 9:02 AM, Mikko Perttunen wrote:
>>> On 19.04.2017 21:24, Arnd Bergmann wrote:
>>
>> I don't think this can be a per-platform policy.
>
On Wed, Apr 19, 2017 at 01:36:10PM -0600, Logan Gunthorpe wrote:
> Seeing the kunmap_atomic dma_buf_ops share the same name with a macro
> in highmem.h, the former can be aliased if any dma-buf user includes
> that header.
>
> I'm personally trying to include highmem.h inside scatterlist.h and
Hi All,
On 2017-04-20 09:51, Daniel Vetter wrote:
On Wed, Apr 19, 2017 at 01:36:10PM -0600, Logan Gunthorpe wrote:
Seeing the kunmap_atomic dma_buf_ops share the same name with a macro
in highmem.h, the former can be aliased if any dma-buf user includes
that header.
I'm personally trying to
Hi Rob,
On Thu, Apr 20, 2017 at 09:02:53AM -0500, Rob Herring wrote:
> On Sun, Apr 16, 2017 at 08:08:40PM +0800, Icenowy Zheng wrote:
> > diff --git a/include/dt-bindings/clock/sun8i-de2.h
> > b/include/dt-bindings/clock/sun8i-de2.h
> > new file mode 100644
> > index ..982c6d18c75b
>
On Tue, 04 Apr 2017, Manasi Navare wrote:
> From: "Navare, Manasi D"
>
> Display stream compression is supported on DP 1.4 DP
> devices. This patch adds the corersponding DPCD
> register definitions for DSC.
>
> v4:
> * Add DSC Enable DPCD
https://bugs.freedesktop.org/show_bug.cgi?id=100712
--- Comment #6 from Julien Isorce ---
Created attachment 130947
--> https://bugs.freedesktop.org/attachment.cgi?id=130947=edit
dmesg_W9000_with_custom_fence_debug.log
--
You are receiving this mail because:
You are
https://bugs.freedesktop.org/show_bug.cgi?id=100712
Julien Isorce changed:
What|Removed |Added
Summary|ring 0 stalled after|ring 0 stalled
https://bugs.freedesktop.org/show_bug.cgi?id=100712
--- Comment #7 from Julien Isorce ---
I made 2 apitrace using Zach's test mentioned here
https://bugs.freedesktop.org/show_bug.cgi?id=100465#c24 . This test is also
good to reproduce this ring 0 stalled issue.
1:
On Wed, 19 Apr 2017, clinton.a.tay...@intel.com wrote:
> From: Clint Taylor
>
> Adding DPCD register definitions from the DP 1.3 specification for CEC
> over AUX support.
>
> Signed-off-by: Clint Taylor
Literally all DPCD macros in the
From: Clint Taylor
Adding DPCD register definitions from the DP 1.3 specification for CEC
over AUX support.
V2: Add DP_ prefix to all defines.
Reviewed-by: Jani Nikula
Signed-off-by: Clint Taylor
---
https://bugs.freedesktop.org/show_bug.cgi?id=93341
--- Comment #27 from Julien Isorce ---
About your comment #26, do you get similar logs than those attached ? i.e. ring
N stalled then gpu softreset then freeze which requires reboot ?
Can you try
On Tue, Apr 18, 2017 at 07:05:12PM +0800, Icenowy Zheng wrote:
> >> @@ -56,7 +55,7 @@ static void sun4i_crtc_atomic_flush(struct drm_crtc
> >*crtc,
> >>
> >>DRM_DEBUG_DRIVER("Committing plane changes\n");
> >>
> >> - sun4i_backend_commit(scrtc->backend);
> >> +
On Sun, Apr 16, 2017 at 08:08:40PM +0800, Icenowy Zheng wrote:
> The "Display Engine 2.0" in Allwinner newer SoCs contains a clock
> management unit for its subunits, like the DE CCU in A80.
>
> Add a sunxi-ng style driver for it.
>
> Signed-off-by: Icenowy Zheng
> ---
>
https://bugs.freedesktop.org/show_bug.cgi?id=100681
jdr...@gmail.com changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
On Sun, Apr 16, 2017 at 08:08:39PM +0800, Icenowy Zheng wrote:
> Allwinner "Display Engine 2.0" contains some clock controls in it.
>
> In order to add them as clock drivers, we need a device tree binding.
> Add the binding here.
>
> Signed-off-by: Icenowy Zheng
> ---
> Changes
On Sun, Apr 16, 2017 at 08:08:41PM +0800, Icenowy Zheng wrote:
> Allwinner V3s SoC have a display engine which have a different pipeline
> with older SoCs.
>
> Add document for it (new compatibles and the new "mixer" part).
>
> Signed-off-by: Icenowy Zheng
> ---
> Changes in
https://bugs.freedesktop.org/show_bug.cgi?id=100306
--- Comment #19 from MirceaKitsune ---
llvm 4.0.0 is now in openSUSE Tumbleweed: I have preformed a 'zypper dup',
installed it, and restarted. Now it's time to see if this really makes the
freeze go away.
From: Clint Taylor
Adding DPCD register definitions from the DP 1.3 specification for CEC
over AUX support.
V2: Add DP_ prefix to all defines.
V3: missed prefixes from the ESI1 defines
Cc: Jani Nikula
Reviewed-by: Jani Nikula
On Wed, Apr 19, 2017 at 11:06 PM, Hans Verkuil wrote:
> On 19/04/17 18:59, Arnd Bergmann wrote:
>> When the media subsystem is built as a loadable module, a built-in
>> This adds a Kconfig dependency to enforce the HDMI driver to also
>> be a loadable module in this case.
>
>
On Tue, Apr 18, 2017 at 05:40:34PM +0900, Hoegeun Kwon wrote:
> The samsung s6e3hf2 panel is a 5.65" 1600x2560 AMOLED panel connected
> using MIPI-DSI interfaces.
>
> The s6e3hf2 is add to samsung,s6e3ha2.txt binding because it is a
> panel similar to the s6e3ha2. So add the compatible string and
On 18.04.2017 17:48, Rob Clark wrote:
On Fri, Apr 14, 2017 at 1:04 PM, Raghav Jajodia
wrote:
Hi there
I am Raghav Jajodia, an Engineering student from India. While going through
the X.org foundation, I felt that X.org is a great community for new Open
Source
Hi Marek,
Thanks!
On 20 April 2017 at 13:36, Marek Szyprowski wrote:
> Hi All,
>
> On 2017-04-20 09:51, Daniel Vetter wrote:
>>
>> On Wed, Apr 19, 2017 at 01:36:10PM -0600, Logan Gunthorpe wrote:
>>>
>>> Seeing the kunmap_atomic dma_buf_ops share the same name with a
On Thu, Apr 20, 2017 at 9:02 AM, Mikko Perttunen wrote:
> On 19.04.2017 21:24, Arnd Bergmann wrote:
>>
>> When dma_addr_t and phys_addr_t are not the same size, we get a warning
>> from the dma_alloc_wc function:
>>
>> drivers/gpu/host1x/cdma.c: In function
On 18 April 2017 at 20:38, Daniel Vetter wrote:
> On Tue, Apr 18, 2017 at 02:27:14PM -0400, Rob Clark wrote:
>> On Tue, Apr 18, 2017 at 1:32 PM, Emil Velikov
>> wrote:
>> > On 18 April 2017 at 16:48, Rob Clark wrote:
>> >> On Fri,
1 - 100 of 106 matches
Mail list logo