[PATCH] exynos-drm: Fix error messages to print flags and size

2016-10-06 22:09 GMT+09:00 Tobias Jakobi : > Hello, > > I think this patch was never picked up. So just a short 'ping' from my side. > Oops. one I missed. Will pick it up soon. Thanks, Inki Dae > With best wishes, > Tobias > > > Shuah Khan wrote: >> Fix exynos_drm_gem_create() error messages to

[PATCH 10/10] mm: replace access_process_vm() write parameter with gup_flags

Lorenzo Stoakes writes: > diff --git a/arch/powerpc/kernel/ptrace32.c b/arch/powerpc/kernel/ptrace32.c > index f52b7db3..010b7b3 100644 > --- a/arch/powerpc/kernel/ptrace32.c > +++ b/arch/powerpc/kernel/ptrace32.c > @@ -74,7 +74,7 @@ long compat_arch_ptrace(struct task_struct *child, >

the dp helper would try to enable the i2c channel for rockchip-edp

Hello, Recently, I want to use a eDP panel in my RK3288 platform, but I got the following message: [8.935918] i2c i2c-6: of_i2c: modalias failure on /dp at ff97/ports [8.936018] rockchip-drm display-subsystem: bound ff97.dp (ops rockchip_dp_component_ops

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

top.org/archives/dri-devel/attachments/20161019/911a6e74/attachment.html>

[Bug 98333] 4K @ 60Hz over HDMI 2.0 not working with AMDGPU-DAL

logs on request (not sure to log right now). Thanks! -- You are receiving this mail because: You are the assignee for the bug. -- next part -- An HTML attachment was scrubbed... URL: <https://lists.freedesktop.org/archives/dri-devel/attachments/20161019/e2623

[PATCH 2/2] dma-buf/fence-array: hold fences reference when creating an array

Am 19.10.2016 um 19:48 schrieb Gustavo Padovan: > From: Gustavo Padovan > > When creating fence arrays we were not holding references to the fences > in the array, however when destroy the array we were putting away a > reference to these fences. > > This patch hold the ref for all fences in the

[PATCH] reservation: fix reservation_object_wait_timeout_rcu result

From: Christian König Return one when the timeout is zero and we don't got any fences. Fixes "reservation: revert "wait only with non-zero timeout specified (v3)"". Signed-off-by: Christian König --- drivers/dma-buf/reservation.c | 2 +- 1 file changed, 1

[RESEND][GIT PULL] TDA998x I2C driver development updates

Sorry, my mistake - it was merged, and it's just that I seem to have accidentally rebased the branch, which is why the commits were still showing up in my tree. Sorry for the noise, please ignore. On Wed, Oct 19, 2016 at 05:37:18PM +0100, Russell King wrote: > David, > > Please incorporate the

[PATCH v2] drm/bridge: adv7511: Remove unused code blocks

Hi Laurent, On 10/19/2016 7:03 PM, Laurent Pinchart wrote: > Hi Jitendra, > > On Wednesday 19 Oct 2016 18:37:38 Sharma, Jitendra wrote: >> On 10/19/2016 5:21 PM, Laurent Pinchart wrote: >>> On Wednesday 19 Oct 2016 17:12:48 Jitendra Sharma wrote: Remove redundant condition check Remove

[PATCH 00/10] mm: adjust get_user_pages* functions to explicitly pass FOLL_* flags

On Wed 19-10-16 09:49:43, Dave Hansen wrote: > On 10/19/2016 02:07 AM, Michal Hocko wrote: > > On Wed 19-10-16 09:58:15, Lorenzo Stoakes wrote: > >> On Tue, Oct 18, 2016 at 05:30:50PM +0200, Michal Hocko wrote: > >>> I am wondering whether we can go further. E.g. it is not really clear to > >>> me

[PATCH v2] drm/bridge: adv7511: Remove unused code blocks

Hi., On 10/19/2016 6:37 PM, Sharma, Jitendra wrote: > Hi Laurent, > > > On 10/19/2016 5:21 PM, Laurent Pinchart wrote: >> Hi Jitendra, >> >> Thank you for the patch. >> >> On Wednesday 19 Oct 2016 17:12:48 Jitendra Sharma wrote: >>> Remove redundant condition check >>> Remove not necessary

Unix Device Memory Allocation project

On Wed, Oct 19, 2016 at 4:10 PM, Daniel Vetter wrote: > On Wed, Oct 19, 2016 at 03:15:08PM +0200, Marek Olšák wrote: >> On Oct 19, 2016 8:24 AM, "Daniel Vetter" wrote: >> > On Wed, Oct 19, 2016 at 1:40 AM, Marek Olšák wrote: >> > > - The producer-consumer interop API doesn't know about the

[PATCH v2] drm/bridge: adv7511: Remove unused code blocks

Hi Laurent, On 10/19/2016 5:21 PM, Laurent Pinchart wrote: > Hi Jitendra, > > Thank you for the patch. > > On Wednesday 19 Oct 2016 17:12:48 Jitendra Sharma wrote: >> Remove redundant condition check >> Remove not necessary if-else block for checking DT entry because else >> part will never be

exynos-drm: display manager fails to start without IOMMU problem

Hello Shuah, just a short note that more misleading comments about default allocation flags can be found in libdrm. https://cgit.freedesktop.org/mesa/drm/tree/exynos/exynos_drm.c See e.g. the comment for exynos_bo_create(). In my opinion, the whole approach to _set_ a bit to get non-contigious

[PATCH] drm: Fix LSPCON kernel-doc

On Wed, 19 Oct 2016, Ville Syrjälä wrote: > On Wed, Oct 19, 2016 at 03:08:04PM +0300, Jani Nikula wrote: >> Fix warnings on building htmldocs. >> >> v2: whitespace around '/' (Ville) >> >> Fixes: 056996b95686 ("drm: Helper for lspcon in drm_dp_dual_mode") >> Cc: Rodrigo Vivi >> Cc: Shashank

[PATCH] drm/msm: update uapi header license

The same file in libdrm is, as is the tradition with the rest of libdrm, etc, using an MIT license. To avoid complications in the future with sync'ing the uapi header to libdrm, lets fix the license mismatch now before there are any non-trivial commits from someone other than myself. Cc: Emil

[PATCH] drm: Fix LSPCON kernel-doc

On Wed, Oct 19, 2016 at 03:08:04PM +0300, Jani Nikula wrote: > Fix warnings on building htmldocs. > > v2: whitespace around '/' (Ville) > > Fixes: 056996b95686 ("drm: Helper for lspcon in drm_dp_dual_mode") > Cc: Rodrigo Vivi > Cc: Shashank Sharma > Cc: > Signed-off-by: Jani Nikula lgtm

[RESEND][GIT PULL] TDA998x I2C driver development updates

David, Please incorporate the latest TDA998x I2C driver development updates, which can be found at: git://git.armlinux.org.uk/~rmk/linux-arm.git drm-tda998x-devel with SHA1 df0bd1e8f3c508bf4c3445f94b12e38289b65f13. This was sent on the 9th September, and I was hoping that it was going to

[Intel-gfx] [PATCH] drm/i915: Add i915 perf infrastructure

> -- next part -- An HTML attachment was scrubbed... URL: <https://lists.freedesktop.org/archives/dri-devel/attachments/20161019/9f52acaf/attachment.html>

[Bug 98324] amd-staging-4.7: problems with unblanking displays when monitors are switched off

|Linux (All) -- You are receiving this mail because: You are the assignee for the bug. -- next part -- An HTML attachment was scrubbed... URL: <https://lists.freedesktop.org/archives/dri-devel/attachments/20161019/9c1beb3f/attachment-0001.html>

[PATCH 3/3] drm/fsl-dcu: disable outputs before unloading driver

Make sure that all outputs are disabled before unloading the DRM driver. Otherwise vblank handling is not shut down properly and warnings such as this appear: WARNING: CPU: 0 PID: 540 at drivers/gpu/drm/drm_irq.c:339 drm_vblank_cleanup+0x5c/0x94 Signed-off-by: Stefan Agner ---

[PATCH 2/3] drm/fsl-dcu: unload driver before disabling clocks

Use drm_put_dev to unload the driver before disabling clocks. Otherwise the driver might read a register during unload which leads to an external abort. Signed-off-by: Stefan Agner --- drivers/gpu/drm/fsl-dcu/fsl_dcu_drm_drv.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

[PATCH 1/3] drm/fb_cma_helper: do not free fbdev if there is none

If fbdev emulation is not in use (or not built-in), fb_helper.fbdev is NULL. Don't call calling drm_fbdev_cma_defio_fini in this case. Signed-off-by: Stefan Agner --- drivers/gpu/drm/drm_fb_cma_helper.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git

[PATCH 0/3] drm/fsl-dcu: fix driver remove/DRM unload

Hi All, The first patch is a better alternative to the previously posted patch ("drm/fsl-dcu: only init fbdev if required") as suggested by Daniel. The second and third are fix related issue uncovered during tests with bind/unbind: echo 40058000.dcu > /sys/bus/platform/drivers/fsl-dcu/unbind

[GIT PULL] Armada DRM fixes

David, Please incorporate the latest Armada DRM fixes fixes, which can be found at: git://git.armlinux.org.uk/~rmk/linux-arm.git drm-armada-fixes with SHA1 ea908ba8f73446dfbf87ff71f7cadb1994d2c5bb. One small fix for Armada, where the clock prepare/enable counts were going awry. This will

[PATCH] drm: rcar-du: Simplify and fix probe error handling

It isn't safe to call drm_dev_unregister() without first initializing mode setting with drm_mode_config_init(). This leads to a crash if either IO memory can't be remapped or vblank initialization fails. Fix this by reordering the initialization sequence. Move vblank initialization after the

[PATCH 8/8] drm: rcar-du: Initialize encoder's type based on the bridge's type

Set the type of the DRM encoder that models the hardware encoders (bridges) chain based on the type of the last bridge in the chain instead of hardcoding encoder compatible strings in the display driver. Signed-off-by: Laurent Pinchart ---

[PATCH 7/8] drm: rcar-du: Replace manual VGA DAC implementation with DRM bridge

Signed-off-by: Laurent Pinchart --- drivers/gpu/drm/rcar-du/Kconfig | 6 -- drivers/gpu/drm/rcar-du/Makefile | 5 +- drivers/gpu/drm/rcar-du/rcar_du_encoder.c | 52 drivers/gpu/drm/rcar-du/rcar_du_encoder.h | 2

[PATCH 6/8] drm: Set on-chip bridges' encoder type

Initialize the new drm_bridge::encoder_type field to the right value for all bridges that model on-SoC IP cores. Signed-off-by: Laurent Pinchart --- drivers/gpu/drm/exynos/exynos_drm_mic.c | 2 ++ drivers/gpu/drm/mediatek/mtk_hdmi.c | 2 ++

[PATCH 5/8] drm: bridge: Set bridges' encoder type

Initialize the new drm_bridge::encoder_type field to the right value for all external bridge drivers. Signed-off-by: Laurent Pinchart --- drivers/gpu/drm/bridge/adv7511/adv7511_drv.c | 1 + drivers/gpu/drm/bridge/analogix-anx78xx.c |

[PATCH 4/8] drm: Add encoder_type field to the drm_bridge structure

The drm_bridge object models on- or off-chip hardware encoders and provide an abstract control API to display drivers. In order to help display drivers creating the right kind of drm_encoder object, expose the type of the hardware encoder associated with each bridge. Signed-off-by: Laurent

[PATCH 3/8] drm: bridge: lvds-encoder: Add thine, thc63lvdm83d compatible string

The THC63LVDM83D is a transparent LVDS encoder. Unlike dumb LVDS encoders it can be controlled through a few pins (power down, LVDS swing, clock edge selection) and requires power supplies. However, on several boards where the device is used neither the control pins nor the power supply are

[PATCH 2/8] drm: bridge: vga-dac: Add adi,adv7123 compatible string

The ADV7123 is a transparent VGA DAC. Unlike dumb VGA DACs it can be controlled through a power save pin, and requires a power supply. However, on most boards where the device is used neither the power save signal nor the power supply are controllable. To avoid developing a separate

[PATCH 1/8] drm: bridge: Add LVDS encoder driver

The LVDS encoder driver is a DRM bridge driver that supports the parallel to LVDS encoders that don't require any configuration. The driver thus doesn't interact with the device, but creates an LVDS connector for the panel and exposes its size and timing based on information retrieved from DT.

[PATCH 0/8] R-Car DU: Use drm bridge API

Hello, (This time with the proper dri-devel mailing list address, sorry for the noise) This patch series replaces the custom external encoders support implementation in the R-Car DU driver with code based on the DRM bridge API. While the overall diffstat isn't impressive, the rcar-du-drm driver

[Bug 98324] amd-staging-4.7: problems with unblanking displays when monitors are switched off

-devel/attachments/20161019/88773a3e/attachment.html>

[PATCH v2] drm/bridge: adv7511: Remove unused code blocks

Remove redundant condition check Remove not necessary if-else block for checking DT entry because else part will never be picked as in absence of device node, probe will fail in initial stage only. Remove unused id->driver_data entries As id->driver_data is not used in driver source. So no need

[GIT PULL] drm/fsl-dcu: fixes for v4.9-rc2

Hi Dave, This are some fixes which I hoped to still get into v4.9. I used to test them here since about 2 weeks and Meng came around to test it on the second platform making use of this IP too, so they are well tested now. -- Stefan The following changes since commit

[PATCH v3 1/5] drm/fsl-dcu: enable TCON bypass mode by default

On 2016-10-19 02:35, Meng Yi wrote: >> >> Do not use encoder disable/enable callbacks to control bypass mode as this >> seems to mess with the signals not liked by displays. This also makes more >> sense since the encoder is already defined to be parallel RGB/LVDS at >> creation >> time. >> >>

exynos-drm: display manager fails to start without IOMMU problem

On 10/19/2016 10:23 AM, Tobias Jakobi wrote: > Hello Shuah, > > just a short note that more misleading comments about default allocation > flags can be found in libdrm. > > https://cgit.freedesktop.org/mesa/drm/tree/exynos/exynos_drm.c > > See e.g. the comment for exynos_bo_create(). > > In my

[PATCH] reservation: fix reservation_object_wait_timeout_rcu result

On Wed, Oct 19, 2016 at 1:59 PM, Christian König wrote: > From: Christian König > > Return one when the timeout is zero and we don't got any fences. > > Fixes "reservation: revert "wait only with non-zero timeout specified (v3)"". > > Signed-off-by: Christian König Reviewed-by: Alex Deucher

mm: fix cache mode tracking in vm_insert_mixed() breaks AMDGPU [was: Re: Latest testing with drm-next-4.9-wip and latest LLVM/mesa stack - Regression in PowerPlay/DPM on CIK?]

On 18 October 2016 at 23:53, Dan Williams wrote: > On Mon, Oct 17, 2016 at 8:48 PM, Dave Airlie wrote: > [..] Aren't there only 2 possibilities for this regression? 1/ a memtype entry was never made so track_pfn_insert() returns an uncached mapping 2/ a conflicting

[PATCH 2/2] dma-buf/fence-array: hold fences reference when creating an array

2016-10-19 Christian König : > Am 19.10.2016 um 19:48 schrieb Gustavo Padovan: > > From: Gustavo Padovan > > > > When creating fence arrays we were not holding references to the fences > > in the array, however when destroy the array we were putting away a > > reference to these fences. > > >

[Bug 178421] [regression] Radeon Oops on shutdown

https://bugzilla.kernel.org/show_bug.cgi?id=178421 Alex Deucher changed: What|Removed |Added CC||alexdeucher at gmail.com --- Comment #1

[PATCH v2] drm/bridge: adv7511: Remove unused code blocks

Hi Jitendra, On Wednesday 19 Oct 2016 18:37:38 Sharma, Jitendra wrote: > On 10/19/2016 5:21 PM, Laurent Pinchart wrote: > > On Wednesday 19 Oct 2016 17:12:48 Jitendra Sharma wrote: > >> Remove redundant condition check > >> Remove not necessary if-else block for checking DT entry because else >

[Bug 178421] New: [regression] Radeon Oops on shutdown

https://bugzilla.kernel.org/show_bug.cgi?id=178421 Bug ID: 178421 Summary: [regression] Radeon Oops on shutdown Product: Drivers Version: 2.5 Kernel Version: 4.9-rc1 Hardware: All OS: Linux Tree: Mainline

[PATCH] exynos-drm: Fix display manager failing to start without IOMMU problem

On 10/19/2016 08:16 AM, Inki Dae wrote: > Hi Shuah, > > 2016-10-13 8:11 GMT+09:00 Shuah Khan : >> Hi Inki, >> >> On 08/15/2016 10:40 PM, Inki Dae wrote: >> okay the very first commit that added IOMMU support introduced the code that rejects non-contig gem memory type without

[PATCH -next] drm/i915/gvt: fix return value check

From: Wei Yongjun In case of error, the function i915_gem_object_create() returns ERR_PTR() not NULL. The NULL test in the return value check should be replaced with IS_ERR(). Signed-off-by: Wei Yongjun --- drivers/gpu/drm/i915/gvt/cmd_parser.c | 8 1 file

Unix Device Memory Allocation project

On Wed, Oct 19, 2016 at 03:15:08PM +0200, Marek Olšák wrote: > On Oct 19, 2016 8:24 AM, "Daniel Vetter" wrote: > > On Wed, Oct 19, 2016 at 1:40 AM, Marek Olšák wrote: > > > - The producer-consumer interop API doesn't know about the metadata. > > > All you need to pass around is a buffer

[Bug 98322] QXL drm driver regression in 4.7

. -- next part -- An HTML attachment was scrubbed... URL: <https://lists.freedesktop.org/archives/dri-devel/attachments/20161019/504107ae/attachment.html>

[PATCH 9/9] gpu: ipu-v3: initially clear all interrupts

On Wed, Oct 19, 2016 at 12:07 AM, Philipp Zabel wrote: > If we want to stop resetting the IPU in the future, masking all > interrupts before registering the irq handlers will not be enough to > avoid spurious interrupts. We also have to clear them. > > Signed-off-by: Philipp Zabel Acked-by:

[PATCH 8/9] drm/imx: ipuv3-plane: add support for YUV 4:2:2 and 4:4:4, NV12, and NV16 formats

On Wed, Oct 19, 2016 at 12:07 AM, Philipp Zabel wrote: > Hook up support for DRM_FORMAT_YUV422, DRM_FORMAT_YVU422, > DRM_FORMAT_YUV444, DRM_FORMAT_YVU444, DRM_FORMAT_NV12, > and DRM_FORMAT_NV16. > > Signed-off-by: Philipp Zabel > --- > drivers/gpu/drm/imx/ipuv3-plane.c | 52 >

Unix Device Memory Allocation project

On 19/10/16 08:40 AM, Marek Olšák wrote: > > 1) DRI (producer: application; consumer: X server) > - The producer receives these flags: READ, EXPLICIT_FLUSH. The X > server will treat the shared "texture" as read-only. FWIW, no, the X server doesn't treat buffers shared with clients via DRI as

[PATCH 2/2] dma-buf/fence-array: hold fences reference when creating an array

From: Gustavo Padovan When creating fence arrays we were not holding references to the fences in the array, however when destroy the array we were putting away a reference to these fences. This patch hold the ref for all fences in the array when creating the

[PATCH 1/2] dma-buf/sync_file: hold reference to fence when creating sync_file

From: Gustavo Padovan fence referencing was out of balance. It was not taking any ref to the fence at creating time, but it was putting a reference when freeing the sync file. This patch fixes the balancing issue by getting a reference for the fence when

[PATCH 7/9] gpu: ipu-v3: add YUV 4:4:4 support

On Wed, Oct 19, 2016 at 12:07 AM, Philipp Zabel wrote: > The IDMAC does support reading and writing DRM_FORMAT_YUV444 and > DRM_FORMAT_YVU444. > > Signed-off-by: Philipp Zabel > --- > drivers/gpu/ipu-v3/ipu-common.c | 2 ++ > drivers/gpu/ipu-v3/ipu-cpmem.c | 17 + > 2 files

[PATCH 6/9] gpu: ipu-cpmem: Add missing YVU422 case to ipu_cpmem_set_yuv_planar

On Wed, Oct 19, 2016 at 12:07 AM, Philipp Zabel wrote: > ipu_cpmem_set_fmt is already prepared to handle DRM_FORMAT_YVU422. > > Signed-off-by: Philipp Zabel > --- > drivers/gpu/ipu-v3/ipu-cpmem.c | 5 + > 1 file changed, 5 insertions(+) > > diff --git a/drivers/gpu/ipu-v3/ipu-cpmem.c

[PATCH 5/9] drm/imx: ipuv3-plane: let drm_plane_state_to_ubo/vbo handle chroma subsampling other than 4:2:0

On Wed, Oct 19, 2016 at 12:07 AM, Philipp Zabel wrote: > To support 4:2:2 or 4:4:4 chroma subsampling, divide the x/y offsets in > drm_plane_state_to_ubo/vbo only if necessary for the given pixel format. > > Signed-off-by: Philipp Zabel > --- > drivers/gpu/drm/imx/ipuv3-plane.c | 27

Unix Device Memory Allocation project

iver can decide whether a linear layout is necessary or not. Marek -- next part -- An HTML attachment was scrubbed... URL: <https://lists.freedesktop.org/archives/dri-devel/attachments/20161019/7d9bf461/attachment.html>

[PATCH V2] gpu/drm/exynos/exynos_hdmi - Unmap region obtained by of_iomap

Free memory mapping, if hdmi_probe is not successful. Signed-off-by: Arvind Yadav --- drivers/gpu/drm/exynos/exynos_hdmi.c |5 + 1 file changed, 5 insertions(+) diff --git a/drivers/gpu/drm/exynos/exynos_hdmi.c b/drivers/gpu/drm/exynos/exynos_hdmi.c index 2275efe..ba28dec 100644 ---

[PATCH 4/9] drm/imx: ipuv3-plane: merge ipu_plane_atomic_set_base into atomic_update

On Wed, Oct 19, 2016 at 12:07 AM, Philipp Zabel wrote: > ipu_plane_atomic_set_base is called from ipu_plane_atomic_update in two > different places, depending on whether drm_atomic_crtc_needs_modeset is > true. Also depending on the same condition, this function does two > different things. >

[PATCH 3/9] drm/imx: ipuv3-plane: request modeset if plane offsets changed

On Wed, Oct 19, 2016 at 12:07 AM, Philipp Zabel wrote: > If the framebuffer pixel format is planar YUV and unchanged, but the U > or V plane offsets change, do not return an error, but request a modeset > instead. > > Signed-off-by: Philipp Zabel Acked-by: Liu Ying > --- >

[PATCH 2/9] drm/imx: ipuv3-plane: disable local alpha for planes without alpha channel

On Wed, Oct 19, 2016 at 12:07 AM, Philipp Zabel wrote: > Without this patch, after enabling the overlay plane with an RGBA > framebuffer, switching to a framebuffer without alpha channel would > cause the plane to vanish, since the pixel local alpha is constant > zero in that case. Disable local

Unix Device Memory Allocation project

gotiated between userspace driver developers for sharing of more complex allocations than 2D displayable surfaces. Marek > -Daniel > -- > Daniel Vetter > Software Engineer, Intel Corporation > +41 (0) 79 365 57 48 - http://blog.ffwll.ch -- next part -- An HTML attachment was scrubbed... URL: <https://lists.freedesktop.org/archives/dri-devel/attachments/20161019/f4e50c12/attachment-0001.html>

[PATCH 1/9] drm/imx: ipuv3-plane: make sure x/y offsets are even in case of chroma subsampling

On Wed, Oct 19, 2016 at 12:07 AM, Philipp Zabel wrote: > Odd x/y offsets are not allowed for chroma subsampled planar YUV > formats. > > Signed-off-by: Philipp Zabel > --- > drivers/gpu/drm/imx/ipuv3-plane.c | 8 > 1 file changed, 8 insertions(+) > > diff --git

[PATCH] drm: Fix LSPCON kernel-doc

Fix warnings on building htmldocs. v2: whitespace around '/' (Ville) Fixes: 056996b95686 ("drm: Helper for lspcon in drm_dp_dual_mode") Cc: Rodrigo Vivi Cc: Shashank Sharma Cc: Signed-off-by: Jani Nikula --- n.b. 056996b95686 ("drm: Helper for lspcon in drm_dp_dual_mode") has been merged

[Intel-gfx] [PATCH] drm: Fix LSPCON kernel-doc

On Wed, Oct 19, 2016 at 02:43:24PM +0300, Jani Nikula wrote: > Fix warnings on building htmldocs. > > Fixes: 056996b95686 ("drm: Helper for lspcon in drm_dp_dual_mode") > Cc: Rodrigo Vivi > Cc: Shashank Sharma > Cc: > Signed-off-by: Jani Nikula > > --- > > n.b. 056996b95686 ("drm: Helper

[PATCH v2] drm/bridge: adv7511: Remove unused code blocks

Hi Jitendra, Thank you for the patch. On Wednesday 19 Oct 2016 17:12:48 Jitendra Sharma wrote: > Remove redundant condition check > Remove not necessary if-else block for checking DT entry because else > part will never be picked as in absence of device node, probe will > fail in initial stage

[PATCH RFC 8/8] drm/i915: Add support for DP link training compliance

This patch adds support to handle automated DP compliance link training test requests. This patch has been tested with Unigraf DPR-120 DP Compliance device for testing Link Training Compliance. After we get a short pulse Compliance test request, test request values are read and hotplug uevent is

[PATCH RFC 7/8] drm/i915: Link Rate fallback on Link training failure

If link training at a link rate optimal for a particular mode fails during modeset's atomic commit phase, then we let the modeset complete and then retry. We save the link rate value at which link training failed and use a lower link rate to prune the modes during the next modeset, configure the

[PATCH RFC 6/8] drm/i915: Define the modeset retry work function

This work function gets scheduled on link training failure during the atomic commit of modeset. It should get executed after the current modeset is completed and send a hotplug uevent to notify the usersapce about change in the connector link property requesting link_train_retry Cc: Jani Nikula

[PATCH RFC 5/8] drm/i915; Add a function to return index of link rate

This is required to return the index of link rate into common_rates array. This gets used to retry the link training at lower link rate. Cc: Jani Nikula Cc: Daniel Vetter Cc: Ville Syrjala Signed-off-by: Manasi Navare --- drivers/gpu/drm/i915/intel_dp.c | 15 +++ 1 file changed,

[PATCH RFC 4/8] drm/i915: Change the placement of some static functions in intel_dp.c

From: "Navare, Manasi D" These static helper functions are required to be used during fallback link rate implemnetation so they need to be placed at the top of the file. v3: * Add cleanup to other patch (Mika Kahola) v2: * Dont move around functions declared in

[PATCH RFC 3/8] drm: Trigger a complete modeset if link_train_retry is set

The link_train_retry property of the connector needs to be checked to see if a full modeset is required. If this is set, then link train retry is requested possibly due to linktrain failure in the previous modeset. Hence we need to indicate connector status changed in order to trigger a full

[PATCH RFC 2/8] drm: Define a work struct for scheduling a uevent for modeset retry

This work struct will be used to schedule a uevent on a separate thread. This will be scheduled after a link train failure during modeset to indicate a modeset retry request. It will get executed after the current modeset is complete and all locks are released. This was required to avoid deadlock.

[PATCH RFC 1/8] drm: Add a link_train_retry field to drm_connector

This is a boolean that is set to true if link training fails during modeset in the atomic commit. This will be used to detect a change in the connector properties and to retrigger a full modeset so that the link can be retrained at lower link rate value. Cc: dri-devel at lists.freedesktop.org Cc:

[PATCH RFC 0/8] Hotplug Uevent on Link training failure on DP

These patches handle the DP link training failure during atomic modeset. A new connector property is defined to indicate if link training retry is requested on failure. If link training fails, we set this connector property and send a hotplug uevent that gets exceuted after the current modeset is

[PATCH v2] drm/arcpgu: Accommodate adv7511 switch to DRM bridge

On 10/19/2016 01:16 PM, Eugeniy Paltsev wrote: > ARC PGU driver starts crashing on initialization after > 'commit e12c2f645557 ("drm/i2c: adv7511: Convert to drm_bridge")' > This happenes because in "arcpgu_drm_hdmi_init" function we get pointer > of "drm_i2c_encoder_driver" structure, which

[PATCH] drm: Fix LSPCON kernel-doc

Fix warnings on building htmldocs. Fixes: 056996b95686 ("drm: Helper for lspcon in drm_dp_dual_mode") Cc: Rodrigo Vivi Cc: Shashank Sharma Cc: Signed-off-by: Jani Nikula --- n.b. 056996b95686 ("drm: Helper for lspcon in drm_dp_dual_mode") has been merged via drm-intel tree ---

[PATCH v2 5/9] of: Add vendor prefix for Netron DY

Desc: not available URL: <https://lists.freedesktop.org/archives/dri-devel/attachments/20161019/8e2680c2/attachment.sig>

[PATCH v4 1/1] drm/panel: simple: Add nvd9128 as a simple panel

thanks. Thierry -- next part -- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 801 bytes Desc: not available URL: <https://lists.freedesktop.org/archives/dri-devel/attachments/20161019/1f6d7174/attachment.sig>

[PATCH v4] drm/panel: simple: Add support for AUO t215hvn01

. Name: signature.asc Type: application/pgp-signature Size: 801 bytes Desc: not available URL: <https://lists.freedesktop.org/archives/dri-devel/attachments/20161019/2255e529/attachment-0001.sig>

Unix Device Memory Allocation project

On 19.10.2016 01:40, Marek Olšák wrote: > * We can build upon this idea. I think the worst thing to do would > be to add metadata handling to driver-agnostic userspace APIs. Really, > driver-agnostic APIs shouldn't know about that, because they can't > understand all the hw-specific

[PATCH v4 2/2] drm/panel: simple: add support for Sharp LQ150X1LG11 panels

g this with .bpc set to 6 and hope for the best (and fix it if somebody finds that it's broken). So no need to resend, just let me know what you think. Thierry -- next part -- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 801 bytes Desc: not available URL: <https://lists.freedesktop.org/archives/dri-devel/attachments/20161019/59630dac/attachment.sig>

[PATCH v4 2/2] drm/panel: simple: add support for Sharp LQ150X1LG11 panels

8, > + }, > + .bus_format = MEDIA_BUS_FMT_RGB565_1X16, This doesn't match the .bpc = 8 above. You'd usually use a .bpc = 6 for RGB565 panels. Thierry -- next part -- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 801 bytes Desc: not available URL: <https://lists.freedesktop.org/archives/dri-devel/attachments/20161019/d7f6d758/attachment.sig>

[Bug 178281] wine-staging apps freezes the machine with RX460

https://bugzilla.kernel.org/show_bug.cgi?id=178281 --- Comment #8 from fin4478 at hotmail.com --- I made my kernel slower by enabling debug and setting cpu timer from 300Hz to 250Hz. Now my desktop does not hang with TR 2013 and Heaven benchmarks although Heaven hangs when using 8x antialising

Unix Device Memory Allocation project

Am 19.10.2016 um 08:23 schrieb Daniel Vetter: > On Wed, Oct 19, 2016 at 1:40 AM, Marek Olšák wrote: >> - The producer-consumer interop API doesn't know about the metadata. >> All you need to pass around is a buffer handle. (KMS, DMABUF, etc.) >>* There was a note during the talk that DMABUF

[PATCH 1/2] drm: make is_lspcon_adaptor static

On Tue, 18 Oct 2016, "Sharma, Shashank" wrote: > Reviewed-by: Shashank Sharma Both pushed to drm-intel-next-queued, thanks for the review. RB, Jani. > > Regards > Shashank > -Original Message- > From: Nikula, Jani > Sent: Tuesday, October 18, 2016 4:52 PM > To: intel-gfx at

[PATCH] drm: fix sparse warnings on undeclared symbols in crc debugfs

On Tue, 18 Oct 2016, Chris Wilson wrote: > On Tue, Oct 18, 2016 at 02:28:35PM +0300, Jani Nikula wrote: >> Fixes sparse warnings: >> >> drivers/gpu/drm/drm_debugfs_crc.c:118:30: warning: symbol >> 'drm_crtc_crc_control_fops' was not declared. Should it be static? >> >>

[PATCH] drm/amd/powerplay: don't give up if DPM is already running

Hi Gražvydas, Sorry for so late response. I can reproduce this issue in gpu passthrough case. When we forced power off the VM or forced reset the VM without shutting down the Os, the rmmod will not be called. So dpm was still running. If we skipped the enable dpm tasks, some clock tables

[PATCH 10/10] drm/imx: ipuv3-plane: use drm_plane_helper_check_state, clipped coordinates

On Wed, Oct 19, 2016 at 12:21:17PM +0200, Philipp Zabel wrote: > Use drm_plane_helper_check_state to clip raw user coordinates to crtc > bounds. This checks for full plane coverage and scaling already, so > we can drop some custom checks. Use the clipped coordinates everywhere. > > Suggested-by:

[Bug 178281] wine-staging apps freezes the machine with RX460

https://bugzilla.kernel.org/show_bug.cgi?id=178281 --- Comment #7 from fin4478 at hotmail.com --- There is just boot traces in dmesg, journalctl and Xorg.0.log when my computer desktop hangs and checking with ssh. -- You are receiving this mail because: You are watching the assignee of the bug.

[PATCH 10/10] drm/imx: ipuv3-plane: use drm_plane_helper_check_state, clipped coordinates

Am Mittwoch, den 19.10.2016, 13:31 +0300 schrieb Ville Syrjälä: > On Wed, Oct 19, 2016 at 12:21:17PM +0200, Philipp Zabel wrote: > > Use drm_plane_helper_check_state to clip raw user coordinates to crtc > > bounds. This checks for full plane coverage and scaling already, so > > we can drop some

mm: fix cache mode tracking in vm_insert_mixed() breaks AMDGPU [was: Re: Latest testing with drm-next-4.9-wip and latest LLVM/mesa stack - Regression in PowerPlay/DPM on CIK?]

On Wed, Oct 19, 2016 at 8:42 AM, Dave Airlie wrote: > On 18 October 2016 at 23:53, Dan Williams wrote: >> On Mon, Oct 17, 2016 at 8:48 PM, Dave Airlie wrote: >> [..] > Aren't there only 2 possibilities for this regression? > > 1/ a memtype entry was never made so track_pfn_insert()

[PATCH 10/10] drm/imx: ipuv3-plane: use drm_plane_helper_check_state, clipped coordinates

Use drm_plane_helper_check_state to clip raw user coordinates to crtc bounds. This checks for full plane coverage and scaling already, so we can drop some custom checks. Use the clipped coordinates everywhere. Suggested-by: Ville Syrjälä Signed-off-by: Philipp Zabel ---

[PATCH 09/10] gpu: ipu-v3: initially clear all interrupts

If we want to stop resetting the IPU in the future, masking all interrupts before registering the irq handlers will not be enough to avoid spurious interrupts. We also have to clear them. Signed-off-by: Philipp Zabel Acked-by: Liu Ying --- drivers/gpu/ipu-v3/ipu-common.c | 5 - 1 file

[PATCH 08/10] drm/imx: ipuv3-plane: add support for YUV 4:2:2 and 4:4:4, NV12, and NV16 formats

Hook up support for DRM_FORMAT_YUV422, DRM_FORMAT_YVU422, DRM_FORMAT_YUV444, DRM_FORMAT_YVU444, DRM_FORMAT_NV12, and DRM_FORMAT_NV16. Signed-off-by: Philipp Zabel --- Changes since v1: - Make UBO/VBO swap for YVU formats more obvious in ipu_plane_atomic_update ---

[PATCH 07/10] gpu: ipu-v3: add YUV 4:4:4 support

The IDMAC does support reading and writing DRM_FORMAT_YUV444 and DRM_FORMAT_YVU444. Signed-off-by: Philipp Zabel Acked-by: Liu Ying --- Changes since v1: - Drop change to ipu_cpmem_set_yuv_planar, which has been removed --- drivers/gpu/ipu-v3/ipu-common.c | 2 ++

[PATCH 06/10] gpu: ipu-cpmem: remove unused ipu_cpmem_set_yuv_planar function

ipu_cpmem_set_yuv_planar_full is only used directly, remove the wrapper. Suggested-by: Liu Ying Signed-off-by: Philipp Zabel --- drivers/gpu/ipu-v3/ipu-cpmem.c | 36 include/video/imx-ipu-v3.h | 2 -- 2 files changed, 38 deletions(-) diff --git

[PATCH 05/10] drm/imx: ipuv3-plane: let drm_plane_state_to_ubo/vbo handle chroma subsampling other than 4:2:0

To support 4:2:2 or 4:4:4 chroma subsampling, divide the x/y offsets in drm_plane_state_to_ubo/vbo only if necessary for the given pixel format. Signed-off-by: Philipp Zabel --- drivers/gpu/drm/imx/ipuv3-plane.c | 27 ++- 1 file changed, 18 insertions(+), 9 deletions(-)

  1   2   >