dri-devel July 2018

dri-devel@lists.freedesktop.org

277 participants
1883 discussions

[Bug 107045] [4.18rc2] RX470 dGPU on hybrid laptop freezes screen after use
by bugzilla-daemon＠freedesktop.org 06 Oct '18

06 Oct '18

https://bugs.freedesktop.org/show_bug.cgi?id=107045 Bug ID: 107045 Summary: [4.18rc2] RX470 dGPU on hybrid laptop freezes screen after use Product: DRI Version: DRI git Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: critical Priority: medium Component: DRM/AMDgpu Assignee: dri-devel(a)lists.freedesktop.org Reporter: taijian(a)posteo.de Created attachment 140343 --> https://bugs.freedesktop.org/attachment.cgi?id=140343&action=edit full dmesg output via 'journalctl -kb -1' With kernel 4.18rc dpm on my hybrid laptop is finally working (thanks again to everyone who helped out getting it this far - see bug #104064, bug #106597 and bug #105760). However, it is still not actually usable, because any activation of the dGPU leads to a system freeze shortly thereafter. It does not really matter HOW the dGPU is triggered - be it running a graphical application via DRI_PRIME=1 or just querying #lshw. The dGPU activates and then tries to power down again, but that seems to be problematic as the (graphical) system will invariable freeze and become unresponsive. The best I have been able to reconstruct from the journal is that whenever the dGPU is called, it will first do this: [drm] PCIE GART of 256M enabled (table at 0x000000F400000000). followed by a bunch of this: amdgpu: [powerplay] failed to send message 62 ret is 0 amdgpu: [powerplay] last message was failed ret is 0 amdgpu: [powerplay] failed to send message 18f ret is 0 and then finally: [drm] UVD and UVD ENC initialized successfully. [drm] VCE initialized successfully. [drm] Cannot find any crtc or sizes amdgpu 0000:01:00.0: GPU pci config reset Sometimes, this will work more than once, sometimes the first invocation after boot will crash. This seems to be somewhat random. However, the crash will always come in the "[powerplay] ...failed to send message 18f ret is 0" phase. Any ideas how to tackle that or extract some more usable error message from my system? -- You are receiving this mail because: You are the assignee for the bug.

1 27

[RFC v4 00/18] vb2: Handle user cache hints, allow drivers to choose cache coherency
by Sakari Ailus 05 Oct '18

05 Oct '18

Hello, This is a rebased and partially reworked version of the vb2 cache hints support patch series posted by first myself, then Laurent and then myself again. I'm still posting this as RFC primarily because more testing and driver changes will be needed. In particular, a lot of platform drivers assume non-coherent memory but are not properly labelled as such. Please see the end of the message for detailed changes. This set unifies the cache coherency hint flags and corrects cache management in videobuf2 dma-contig and dma-sg memtype implementation. The support for non-coherent memory is completed: support for MMAP buffers is added and begin_cpu_access and end_cpu_access functions are added to DMA ops. Comments are welcome. changes since RFC v3: - Document V4L2_BUF_FLAG_NO_CACHE_SYNC flag behaviour for QBUF and DQBUF for CAPTURE and OUTPUT buffers. - Set queue dma_attrs DMA_ATTR_NON_CONSISTENT flag for omap3isp. - Put dma_sgt in vb2_dc_buf in order to avoid allocating and releasing it separately. It's generally needed anyway. - Buffer preparation DMA direction is generally DMA_TO_DEVICE for both CAPTURE and OUTPUT buffers: V4L2 does not guarantee that the user space could not write to capture buffers as well. Documentation/DMA-API.txt: - Before reading values that have been written by DMA from the device (use the DMA_FROM_DEVICE direction) - After writing values that will be written to the device using DMA (use the DMA_TO_DEVICE) direction - before *and* after handing memory to the device if the memory is DMA_BIDIRECTIONAL Cache maintenance can also be skipped for OUTPUT buffers in buffer finish as the hardware did not write to the buffer. changes since RFC v2: - Nicer looking tests for the need for syncing. - Also set DMA attributes for USERPTR buffers. - Unconditionally assign buf->attrs for MMAP buffers. - Don't call vb2_dc_get_base_sgt() until buf->dev is set. - Provide {begin,end}_cpu_access() dmabuf ops for cache management. - Make similar changes to dma-sg memops to support DMA attributes. Sakari Ailus (13): vb2: Rename confusingly named internal buffer preparation functions vb2: Move buffer cache synchronisation to prepare from queue vb2: Move cache synchronisation from buffer done to dqbuf handler v4l: Unify cache management hint buffer flags vb2: Anticipate queue specific DMA attributes for USERPTR buffers vb2: dma-contig: Assign DMA attrs for a buffer unconditionally vb2: dma-contig: Remove redundant sgt_base field vb2: dma-contig: Don't warn on failure in obtaining scatterlist vb2: dma-contig: Move vb2_dc_get_base_sgt() up vb2: dma-contig: Fix DMA attribute and cache management vb2: dma-contig: Add WARN_ON_ONCE() to check for potential bugs vb2: dma-sg: Let drivers decide DMA attrs of MMAP and USERPTR bufs vb2: Improve struct vb2_mem_ops documentation; alloc and put are for MMAP Samu Onkalo (1): vb2: Don't sync cache for a buffer if so requested Documentation/media/uapi/v4l/buffer.rst | 24 ++-- .../media/uapi/v4l/vidioc-prepare-buf.rst | 5 +- drivers/media/v4l2-core/videobuf2-core.c | 129 ++++++++++++++------- drivers/media/v4l2-core/videobuf2-dma-contig.c | 120 ++++++++++++------- drivers/media/v4l2-core/videobuf2-dma-sg.c | 47 ++++++-- drivers/media/v4l2-core/videobuf2-v4l2.c | 14 ++- drivers/media/v4l2-core/videobuf2-vmalloc.c | 3 +- include/media/videobuf2-core.h | 46 +++++--- include/trace/events/v4l2.h | 3 +- include/uapi/linux/videodev2.h | 7 +- 10 files changed, 263 insertions(+), 135 deletions(-) -- Regards, Sakari Sakari Ailus (17): vb2: Rename confusingly named internal buffer preparation functions vb2: Move buffer cache synchronisation to prepare from queue vb2: Move cache synchronisation from buffer done to dqbuf handler v4l: Unify cache management hint buffer flags vb2: Anticipate queue specific DMA attributes for USERPTR buffers vb2: dma-contig: Assign DMA attrs for a buffer unconditionally vb2: dma-contig: Remove redundant sgt_base field vb2: dma-contig: Don't warn on failure in obtaining scatterlist vb2: dma-contig: Allocate sgt as part of struct vb2_dc_buf vb2: dma-contig: Fix DMA attribute and cache management vb2: dma-contig: Add WARN_ON_ONCE() to check for potential bugs vb2: dma-sg: Let drivers decide DMA attrs of MMAP and USERPTR bufs vb2: Improve struct vb2_mem_ops documentation; alloc and put are for MMAP vb2: Dma direction is always DMA_TO_DEVICE in buffer preparation vb2: Do sync plane cache only for CAPTURE buffers in finish memop docs-rst: Document precise V4L2_BUF_FLAG_NO_CACHE_SYNC flag behaviour v4l: Use non-consistent DMA mappings for hardware that deserves it Samu Onkalo (1): vb2: Don't sync cache for a buffer if so requested Documentation/media/uapi/v4l/buffer.rst | 45 +++-- .../media/uapi/v4l/vidioc-prepare-buf.rst | 5 +- drivers/media/platform/omap3isp/ispvideo.c | 1 + drivers/media/v4l2-core/videobuf2-core.c | 122 ++++++++----- drivers/media/v4l2-core/videobuf2-dma-contig.c | 191 ++++++++++++--------- drivers/media/v4l2-core/videobuf2-dma-sg.c | 85 ++++++--- drivers/media/v4l2-core/videobuf2-v4l2.c | 14 +- drivers/media/v4l2-core/videobuf2-vmalloc.c | 3 +- include/media/videobuf2-core.h | 46 +++-- include/trace/events/v4l2.h | 3 +- include/uapi/linux/videodev2.h | 7 +- 11 files changed, 338 insertions(+), 184 deletions(-) -- 2.7.4

5 26

[Bug 103791] Tearing after screen wakeup/on
by bugzilla-daemon＠freedesktop.org 04 Oct '18

04 Oct '18

https://bugs.freedesktop.org/show_bug.cgi?id=103791 Bug ID: 103791 Summary: Tearing after screen wakeup/on Product: DRI Version: XOrg git Hardware: Other OS: All Status: NEW Severity: normal Priority: medium Component: DRM/AMDgpu Assignee: dri-devel(a)lists.freedesktop.org Reporter: denisgolovan(a)yandex.ru Hi Sometimes after screen wakeup/turning on I start to experience tearing. Tear free mode works fine before sleep/turning display off. My hardware is XFX Radeon RX580. Software: kernel-4.13.13+ck1, xorg-1.19.5, xf86-video-amdgpu (git 3a4f7422913093ed9e26b73ecd7f9e773478cb1e), libdrm-2.4.88 See dmesg, Xorg.0.log, xorg.conf attached. -- You are receiving this mail because: You are the assignee for the bug.

1 23

[Bug 101739] An issue with alpha-to-coverage handling is causing Arma 3 64-bit Linux port to render trees incorrectly
by bugzilla-daemon＠freedesktop.org 04 Oct '18

04 Oct '18

https://bugs.freedesktop.org/show_bug.cgi?id=101739 Bug ID: 101739 Summary: An issue with alpha-to-coverage handling is causing Arma 3 64-bit Linux port to render trees incorrectly Product: Mesa Version: git Hardware: Other OS: All Status: NEW Severity: normal Priority: medium Component: Drivers/Gallium/radeonsi Assignee: dri-devel(a)lists.freedesktop.org Reporter: krystian.galaj(a)vpltd.com QA Contact: dri-devel(a)lists.freedesktop.org The game is sometimes rendering trees. It has multiple tree mesh models, and when the tree gets close, the game is switching between different LODs/models by rendering both models overlapping on a grid of pixels, as if checkerboard, pixels of old LOD in black fields of it, new one in white. As long as it’s doing that using single-sampled buffers as render targets, all is fine. However in higher quality modes, the game switches to multisampled buffers. When using multisampled buffers, if ATOC is turned on in settings, the game is using alpha-to-coverage technique without polygon sorting to make sure that the grass is rendered correctly. At the same time it’s using depth test and depth write to fill up the depth buffer. In the same execution of fragment shader it sets the output color and alpha value, and the depth buffer value, and it expects the alpha value to cause the color value to end up only in some samples of multisampled texture, and - the important bit - the depth value to end up only in the corresponding samples of the depth buffer. This technique works on DX11 on Windows, on all drivers on Mac OS X, and on NVidia drivers on Linux, but on Mesa Radeonsi drivers on Linux it makes the rendering go bad, rendering most of the tree pixels white until the LOD transition ends. The white is visible on the screen because it is the initial color of the multisampled render target, and for some reason this color is allowed to leak through, which means that in some cases the depth buffer value is set, when the corresponding color buffer value isn’t. Both depth and color buffer have the same number of samples (8), and were created with fixedSamples = true in OpenGL call. It looks as if the depth buffer values in case of Mesa Radeonsi driver were: - correctly not written when the depth test fails for the fragment shader, - correctly written to all samples of the depth buffer when alpha coverage directs the draw to fill them all, but - INCORRECTLY assigned not only to those samples to which alpha coverage directed the fragment output color, but either to all the samples in depth buffer, or to samples in depth buffer that don’t correspond to the samples in color attachment buffer. We encountered the same issue in 2015 in fglrx drivers, contacted AMD team about it, and received confirmation that it is a bug, and that it was fixed. Unfortunately, shortly after that fglrx drivers went out of use. The issue can be easily reproduced in Arma 3 by: - launching Arma 3 game, - switching to High quality or higher to turn on multisampled buffers, - enabling ATOC (alpha to coverage) in Video settings, or making sure it's enabled, - launching first level of Drawdown 2035 campaign, ie. starting a new campaign, bypassing optional tutorial, and observing as the main character walks into the base, the bushes flicker white from time to time as they get closer. The issue is present in Mesa 17.2.0-devel from padoka PPA, on at least Radeon R7 260X/360. -- You are receiving this mail because: You are the assignee for the bug.

1 18

[RFC 0/3] Add Colorspace connector property interface
by Uma Shankar 27 Sep '18

27 Sep '18

This patch series creates a new connector property to program colorspace to sink devices. Modern sink devices support more than 1 type of colorspace like 601, 709, BT2020 etc. This helps to switch based on content type which is to be displayed. The decision lies with compositors as to in which scenarios, a particular colorspace will be picked. This will be helpful mostly to switch to higher gamut colorspaces like BT2020 when the media content is encoded as BT2020. Thereby giving a good visual experience to users. The expectation from userspace is that it should parse the EDID and get supported colorspaces. Use this property and switch to the one supported. Kernel will not give the supported colorspaces since this is panel dependant and our curremt property infrastructure is not supporting it. Have tested this using xrandr by using below command: xrandr --output HDMI2 --set "Colorspace" "BT2020_rgb" Please provide comments on this current approach. This is just an RFC to get some feedback. Will refine the series based on inputs and feedback. Uma Shankar (3): drm: Add colorspace property drm/i915: Attach colorspace property and enable modeset drm/i915: Set colorspace by enabling Infoframe drivers/gpu/drm/drm_atomic.c | 4 ++++ drivers/gpu/drm/drm_connector.c | 31 +++++++++++++++++++++++++++++++ drivers/gpu/drm/i915/intel_atomic.c | 1 + drivers/gpu/drm/i915/intel_hdmi.c | 5 +++++ include/drm/drm_connector.h | 7 +++++++ include/drm/drm_mode_config.h | 6 ++++++ include/uapi/drm/drm_mode.h | 11 +++++++++++ 7 files changed, 65 insertions(+) -- 1.9.1

5 11

[PATCH 0/5] Add CDTech 4.3" and 7" to panel-simple
by Giulio Benetti 27 Sep '18

27 Sep '18

Add CDTech 4.3" S043WQ26H-CT7 support Add CDTech 7" S070WV95-CT16 support Giulio Benetti (5): dt-bindings: Add vendor prefix for CDTech(H.K.) Electronics Limited drm/panel: add panel CDTech S070WV95-CT16 to panel-simple dt-bindings: Add CDTech S070WV95-CT16 panel bindings drm/panel: add panel CDTech S043WQ26H-CT7 to panel-simple dt-bindings: Add CDTech S043WQ26H-CT7 panel bindings .../display/panel/cdtech,s043wq26h-ct7.txt | 12 ++++ .../display/panel/cdtech,s070wv95-ct16.txt | 12 ++++ .../devicetree/bindings/vendor-prefixes.txt | 1 + drivers/gpu/drm/panel/panel-simple.c | 55 +++++++++++++++++++ 4 files changed, 80 insertions(+) create mode 100644 Documentation/devicetree/bindings/display/panel/cdtech,s043wq26h-ct7.txt create mode 100644 Documentation/devicetree/bindings/display/panel/cdtech,s070wv95-ct16.txt -- 2.17.1

3 10

[PATCH v3 00/11] drm/cma-helper: Remove drm_fbdev_cma* functions
by Noralf Trønnes 27 Sep '18

27 Sep '18

These are the remaining patches not applied due to missing review and: - arm/hdlcd and rcar-du have started to use drm_fbdev_cma_set_suspend_unlocked() since last, so I have added patches converting them to drm_mode_config_helper_suspend/resume(). - tinydrm has gained a new driver ili9225 Noralf. Noralf Trønnes (11): drm/arc: Use drm_fb_cma_fbdev_init/fini() drm/arm/hdlcd: Use drm_mode_config_helper_suspend/resume() drm/arm/hdlcd: Use drm_fb_cma_fbdev_init/fini() drm/hisilicon/kirin: Use drm_fb_cma_fbdev_init/fini() drm/meson: Use drm_fb_cma_fbdev_init/fini() drm/mxsfb: Use drm_fb_cma_fbdev_init/fini() drm/rcar-du: Use drm_mode_config_helper_suspend/resume() drm/rcar-du: Use drm_fb_cma_fbdev_init/fini() drm/fsl-dcu: Use drm_fb_cma_fbdev_init/fini() drm/tinydrm: Use drm_fb_cma_fbdev_init_with_funcs/fini() drm/cma-helper: Remove drm_fbdev_cma* functions Documentation/gpu/todo.rst | 5 - drivers/gpu/drm/arc/arcpgu.h | 4 - drivers/gpu/drm/arc/arcpgu_drv.c | 36 ++---- drivers/gpu/drm/arm/hdlcd_drv.c | 62 ++-------- drivers/gpu/drm/arm/hdlcd_drv.h | 2 - drivers/gpu/drm/drm_fb_cma_helper.c | 158 ------------------------ drivers/gpu/drm/fsl-dcu/fsl_dcu_drm_drv.c | 26 +--- drivers/gpu/drm/fsl-dcu/fsl_dcu_drm_drv.h | 1 - drivers/gpu/drm/hisilicon/kirin/kirin_drm_drv.c | 35 +----- drivers/gpu/drm/hisilicon/kirin/kirin_drm_drv.h | 4 - drivers/gpu/drm/meson/meson_drv.c | 20 +-- drivers/gpu/drm/meson/meson_drv.h | 1 - drivers/gpu/drm/mxsfb/mxsfb_drv.c | 21 +--- drivers/gpu/drm/mxsfb/mxsfb_drv.h | 1 - drivers/gpu/drm/rcar-du/rcar_du_drv.c | 34 +---- drivers/gpu/drm/rcar-du/rcar_du_drv.h | 3 - drivers/gpu/drm/rcar-du/rcar_du_kms.c | 20 +-- drivers/gpu/drm/tinydrm/core/tinydrm-core.c | 37 +----- drivers/gpu/drm/tinydrm/ili9225.c | 3 +- drivers/gpu/drm/tinydrm/mi0283qt.c | 3 +- drivers/gpu/drm/tinydrm/st7586.c | 3 +- include/drm/drm_fb_cma_helper.h | 28 +---- include/drm/tinydrm/tinydrm.h | 3 - 23 files changed, 61 insertions(+), 449 deletions(-) -- 2.14.2

3 16

[PATCH v2 00/22] drm/cma-helper: Remove drm_fbdev_cma* functions
by Noralf Trønnes 27 Sep '18

27 Sep '18

This patchset adds drm_fb_cma_fbdev_init/fini() functions that replaces drm_fbdev_cma_init/fini(). The reason for doing so is to get rid of struct drm_fbdev_cma and it's wrapper functions. The final piece will happen when tinydrm moves away from the cma helper and we can remove the struct. Note: Patches 19-22 depends on patchset: [v3] drm: Add simple modeset suspend/resume helpers Noralf. Changes since version 1: - Fix NULL pointer dereference in drm_fbdev_cma_create() (Benjamin) - sti: Remove unused private variable (Benjamin) - stm: Remove duplicate ldev assignment (Philippe) - tilcdc: Rebase on: 'drm/tilcdc: Use drm_gem_cma_print_info()' Noralf Trønnes (22): drm/gem-fb-helper: drm_gem_fbdev_fb_create() make funcs optional drm/cma-helper: Add drm_fb_cma_fbdev_init/fini() drm/arc: Use drm_fb_cma_fbdev_init/fini() drm/arm/hdlcd: Use drm_fb_cma_fbdev_init/fini() drm/atmel-hlcdc: Use drm_fb_cma_fbdev_init/fini() drm/hisilicon/kirin: Use drm_fb_cma_fbdev_init/fini() drm/imx: Use drm_fb_cma_fbdev_init/fini() drm/meson: Use drm_fb_cma_fbdev_init/fini() drm/mxsfb: Use drm_fb_cma_fbdev_init/fini() drm/pl111: Use drm_fb_cma_fbdev_init/fini() drm/rcar-du: Use drm_fb_cma_fbdev_init/fini() drm/sti: Use drm_fb_cma_fbdev_init/fini() drm/stm: Use drm_fb_cma_fbdev_init/fini() drm/sun4i: Use drm_fb_cma_fbdev_init/fini() drm/tilcdc: Use drm_fb_cma_fbdev_init/fini() drm/tve200: Use drm_fb_cma_fbdev_init/fini() drm/vc4: Use drm_fb_cma_fbdev_init/fini() drm/zte: Use drm_fb_cma_fbdev_init/fini() drm/arm/mali: Use drm_fb_cma_fbdev_init/fini() drm/fsl-dcu: Use drm_fb_cma_fbdev_init/fini() drm/tinydrm: Use drm_fb_cma_fbdev_init_with_funcs/fini() drm/cma-helper: Remove drm_fbdev_cma* functions Documentation/gpu/todo.rst | 5 - drivers/gpu/drm/arc/arcpgu.h | 4 - drivers/gpu/drm/arc/arcpgu_drv.c | 36 +---- drivers/gpu/drm/arm/hdlcd_drv.c | 37 +---- drivers/gpu/drm/arm/hdlcd_drv.h | 1 - drivers/gpu/drm/arm/malidp_drv.c | 39 +---- drivers/gpu/drm/arm/malidp_drv.h | 1 - drivers/gpu/drm/atmel-hlcdc/atmel_hlcdc_dc.c | 26 +--- drivers/gpu/drm/atmel-hlcdc/atmel_hlcdc_dc.h | 2 +- drivers/gpu/drm/drm_fb_cma_helper.c | 191 +++++++++--------------- drivers/gpu/drm/drm_gem_framebuffer_helper.c | 6 +- drivers/gpu/drm/fsl-dcu/fsl_dcu_drm_drv.c | 26 +--- drivers/gpu/drm/fsl-dcu/fsl_dcu_drm_drv.h | 1 - drivers/gpu/drm/hisilicon/kirin/kirin_drm_drv.c | 35 +---- drivers/gpu/drm/hisilicon/kirin/kirin_drm_drv.h | 4 - drivers/gpu/drm/imx/imx-drm-core.c | 33 +--- drivers/gpu/drm/imx/imx-drm.h | 1 - drivers/gpu/drm/meson/meson_drv.c | 20 +-- drivers/gpu/drm/meson/meson_drv.h | 1 - drivers/gpu/drm/mxsfb/mxsfb_drv.c | 21 +-- drivers/gpu/drm/mxsfb/mxsfb_drv.h | 1 - drivers/gpu/drm/pl111/pl111_drm.h | 1 - drivers/gpu/drm/pl111/pl111_drv.c | 16 +- drivers/gpu/drm/rcar-du/rcar_du_drv.c | 13 +- drivers/gpu/drm/rcar-du/rcar_du_drv.h | 2 - drivers/gpu/drm/rcar-du/rcar_du_kms.c | 20 +-- drivers/gpu/drm/sti/sti_drv.c | 27 +--- drivers/gpu/drm/sti/sti_drv.h | 1 - drivers/gpu/drm/stm/drv.c | 38 +---- drivers/gpu/drm/stm/ltdc.h | 1 - drivers/gpu/drm/sun4i/sun4i_drv.c | 14 +- drivers/gpu/drm/sun4i/sun4i_drv.h | 2 - drivers/gpu/drm/sun4i/sun4i_framebuffer.c | 18 +-- drivers/gpu/drm/sun4i/sun4i_framebuffer.h | 2 +- drivers/gpu/drm/tilcdc/tilcdc_drv.c | 26 +--- drivers/gpu/drm/tilcdc/tilcdc_drv.h | 2 - drivers/gpu/drm/tinydrm/core/tinydrm-core.c | 37 +---- drivers/gpu/drm/tinydrm/mi0283qt.c | 3 +- drivers/gpu/drm/tinydrm/st7586.c | 3 +- drivers/gpu/drm/tve200/tve200_drm.h | 1 - drivers/gpu/drm/tve200/tve200_drv.c | 16 +- drivers/gpu/drm/vc4/vc4_drv.c | 13 +- drivers/gpu/drm/vc4/vc4_drv.h | 2 - drivers/gpu/drm/vc4/vc4_kms.c | 18 +-- drivers/gpu/drm/zte/zx_drm_drv.c | 48 +----- include/drm/drm_fb_cma_helper.h | 29 +--- include/drm/tinydrm/tinydrm.h | 3 - 47 files changed, 198 insertions(+), 649 deletions(-) -- 2.14.2

6 37

[PATCH 1/2] drm/panel: seiko-43wvf1g: Switch to SPDX identifier
by Fabio Estevam 27 Sep '18

27 Sep '18

From: Fabio Estevam <fabio.estevam(a)nxp.com> Adopt the SPDX license identifier headers to ease license compliance management. Signed-off-by: Fabio Estevam <fabio.estevam(a)nxp.com> --- drivers/gpu/drm/panel/panel-seiko-43wvf1g.c | 5 +---- 1 file changed, 1 insertion(+), 4 deletions(-) diff --git a/drivers/gpu/drm/panel/panel-seiko-43wvf1g.c b/drivers/gpu/drm/panel/panel-seiko-43wvf1g.c index 75f9253..70654f9 100644 --- a/drivers/gpu/drm/panel/panel-seiko-43wvf1g.c +++ b/drivers/gpu/drm/panel/panel-seiko-43wvf1g.c @@ -1,12 +1,9 @@ +// SPDX-License-Identifier: GPL-2.0 /* * Copyright (C) 2017 NXP Semiconductors. * Author: Marco Franchi <marco.franchi(a)nxp.com> * * Based on Panel Simple driver by Thierry Reding <treding(a)nvidia.com> - * - * This program is free software; you can redistribute it and/or - * modify it under the terms of the GNU General Public License version - * 2 as published by the Free Software Foundation. */ #include <linux/backlight.h> -- 2.7.4

2 3

[PATCH v5 0/9] Add TOSHIBA TC358764 DSI/LVDS bridge driver
by Andrzej Hajda 27 Sep '18

27 Sep '18

Hi, This is continuation of Maciej patchset. I took it over since he can't work on it in near future. I have removed panel patches as they are already merged (thanks Thierry), but I have added fix for timings to allow refresh rate 60Hz. I have addressed all comments from reviewers - thanks Inki, thanks me :) All changes are described in the patches. Regards Andrzej Andrzej Hajda (6): dt-bindings: tc358754: add DT bindings drm/bridge: tc358764: Add DSI to LVDS bridge driver ARM: dts: exynos5250: add DSI node ARM: dts: exynos5250-arndale: add DSI and panel nodes drm/panel: simple: fix BOE/HV070WSA-100 timings dt-bindings: exynos_dsim: update of graph bindings Maciej Purski (3): drm/exynos: rename bridge_node to in_bridge_node drm/exynos: move connector creation to attach callback drm/exynos: enable out_bridge in exynos_dsi_enable .../display/bridge/toshiba,tc358764.txt | 35 ++ .../bindings/display/exynos/exynos_dsim.txt | 25 +- arch/arm/boot/dts/exynos5250-arndale.dts | 61 +++ arch/arm/boot/dts/exynos5250.dtsi | 21 + drivers/gpu/drm/bridge/Kconfig | 8 + drivers/gpu/drm/bridge/Makefile | 1 + drivers/gpu/drm/bridge/tc358764.c | 499 ++++++++++++++++++ drivers/gpu/drm/exynos/exynos_drm_dsi.c | 104 ++-- drivers/gpu/drm/panel/panel-simple.c | 14 +- 9 files changed, 701 insertions(+), 67 deletions(-) create mode 100644 Documentation/devicetree/bindings/display/bridge/toshiba,tc358764.txt create mode 100644 drivers/gpu/drm/bridge/tc358764.c -- 2.18.0

6 26

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

dri-devel July 2018