DVI output on i.MX51 EVP board not working?

Hello, I can't get the DVI output to work on a i.MX51 EVP board (babbage). There seems to be no signal at all. The board is running the mainline kernel 4.11.0-rc4 as of a day ago (89970a0). - The connector and cable works. u-boot (v2016.07-rc2) shows a penguin at boot. However while the Linux

[radeon-alex:drm-next-4.12 202/315] ERROR: "soc15_grbm_select" [drivers/gpu/drm/amd/amdgpu/amdgpu.ko] undefined!

tree: git://people.freedesktop.org/~agd5f/linux.git drm-next-4.12 head: 60508d3df2d2052881190ac82802a12cabcef53c commit: b1023571479020e9e9c15a51b43bf8e15406952b [202/315] drm/amdgpu: implement GFX 9.0 support (v2) config: x86_64-randconfig-s2-03311121 (attached as .config) compiler: gcc-4.4

[Bug 99784] AMD 7470m When VGA plugged into laptop, only one monitor working at a time

https://bugs.freedesktop.org/show_bug.cgi?id=99784 --- Comment #10 from lazane...@gmail.com --- Created attachment 130604 --> https://bugs.freedesktop.org/attachment.cgi?id=130604=edit xrandr outputs for radeon and fglrx Also there are a lot differences in xrandr outputs for fglrx and radeon,

[PATCH libdrm 1/3] exynos: fix type-punned pointer build warning

As like the commit ecc2a097294d ("xf86drm: Fix type-punned pointer build warning"), this fixes following build warning. exynos_drm.c: In function 'exynos_handle_event': exynos_drm.c:420:15: warning: dereferencing type-punned pointer will break strict-aliasing rules [-Wstrict-aliasing]

[PATCH libdrm 2/3] exynos/fimg2d: remove unused-function build warning

The function g2d_reset() is not anymore used after the commit e3c97d1a2473 ("exynos/fimg2d: add g2d_validate_xyz() functions"), so it should be removed. Signed-off-by: Seung-Woo Kim --- exynos/exynos_fimg2d.c | 14 -- 1 files changed, 0 insertions(+), 14

[PATCH libdrm 3/3] tests/exynos: remove unused-function build warning

The function g2d_blend_test() is blocked to call because of feature unsafety. This patch blocks with proper feature name and also blocks the function itself to remove build warning. Signed-off-by: Seung-Woo Kim --- tests/exynos/exynos_fimg2d_test.c |4 +++- 1 files

[PATCH libdrm 0/3] remove build warnings for exynos

For exynos module for libdrm, there are some build warnings, so this patch series remove them. Seung-Woo Kim (3): exynos: fix type-punned pointer build warning exynos/fimg2d: remove unused-function build warning tests/exynos: remove unused-function build warning exynos/exynos_drm.c

[Bug 99784] AMD 7470m When VGA plugged into laptop, only one monitor working at a time

https://bugs.freedesktop.org/show_bug.cgi?id=99784 --- Comment #9 from lazane...@gmail.com --- I changed resolution to 1280x768, and it disabled both internal monitor and VGA. After message box timed out and reverted resolution to 1366x768, VGA is now off and HDMI and internal are on. -- You

[Bug 99784] AMD 7470m When VGA plugged into laptop, only one monitor working at a time

https://bugs.freedesktop.org/show_bug.cgi?id=99784 --- Comment #8 from Michel Dänzer --- I wonder if at least some of the issues could be related to the internal panel's horizontal resolution of 1366... Does setting a lower resolution on the internal panel make any

[Bug 194949] Amdgpu: RX 460 idle temp is 45C

https://bugzilla.kernel.org/show_bug.cgi?id=194949 --- Comment #5 from fin4...@hotmail.com --- I cloned and tested agd5f/linux/?h=drm-next-4.12-wip kernel today and temperature still raises to 45C after boot. Sysfs power control interface does not help. Works ok with kernel 4.11-rc4 from

[Bug 99784] AMD 7470m When VGA plugged into laptop, only one monitor working at a time

https://bugs.freedesktop.org/show_bug.cgi?id=99784 --- Comment #7 from lazane...@gmail.com --- Problem persists with kernel 4.11.rc4. I also made imgur post with relevant screenshots and explanations http://imgur.com/a/3kwiq -- You are receiving this mail because: You are the assignee for the

[Bug 100465] Hard lockup with radeonsi driver on FirePro W600, W9000 and W9100

https://bugs.freedesktop.org/show_bug.cgi?id=100465 --- Comment #3 from Michel Dänzer --- Doesn't seem to happen with my Tonga after 30 minutes. One thing to keep in mind is that FurMark is designed to stress the GPU. Do the systems you're testing on have appropriate power

[PATCH v5 0/5] Adding driver-private objects to atomic state

Changes in this version: Included the 5 left over patches. Patches 1 and 5 have changed, so I have removed Maarten's R-B for patch 5. 1/5: Added NULL checks 5/5: Fixed vcpi slot accounting when atomic_release() is called multiple times within an atomic_check() This series

Heavy artifacts during hw accelerated playback of wmv files

Hi, with versions newer than libdrm-2.4.66 I have heavy artifacts during hw accelerated playback of wmv files vaapi/vdpau tested with gstreamer- 0.10 and ffmpeg based mpv. Bisect result: db138b9ba12a0de5d6140832c0679c2418e3e7e0 is the first bad commit commit

[PATCH] drivers: gpu: drm: dr_fb_cma_helper: Fix kerneldoc comments

Remove the description for the non-existing 'num_crtc' to fix the build warning: ./drivers/gpu/drm/drm_fb_cma_helper.c:557: warning: Excess function parameter 'num_crtc' description in 'drm_fbdev_cma_init'. Signed-off-by: Tamara Diaconita ---

[PATCH v5 3/5] drm/dp: Add DP MST helpers to atomically find and release vcpi slots

From: "Pandiyan, Dhinakaran" drm_dp_atomic_find_vcpi_slots() should be called from ->atomic_check() to check there are sufficient vcpi slots for a mode and to add that to the state. This should be followed by a call to drm_dp_mst_allocate_vcpi() in

[PATCH v5 2/5] drm/dp: Introduce MST topology state to track available link bandwidth

From: "Pandiyan, Dhinakaran" Link bandwidth is shared between multiple display streams in DP MST configurations. The DP MST topology manager structure maintains the shared link bandwidth for a primary link directly connected to the GPU. For atomic modesetting

Re: [PATCH 1/6] virtio: wrap find_vqs

On 2017年03月30日 04:48, Michael S. Tsirkin wrote: We are going to add more parameters to find_vqs, let's wrap the call so we don't need to tweak all drivers every time. Signed-off-by: Michael S. Tsirkin --- A quick glance and it looks ok, but what the benefit of this series,

Re: [Intel-gfx] [PATCH] Revert unrelated part of "drm: simplify the locking in the GETCRTC ioctl"

On Thu, 2017-03-30 at 09:36 +0200, Maarten Lankhorst wrote: > Op 28-03-17 om 09:01 schreef Daniel Vetter: > > > > diff --git a/drivers/gpu/drm/i915/intel_display.c > > b/drivers/gpu/drm/i915/intel_display.c > > index 68cded453882..43dbad62786e 100644 > > ---

i915 Invert backlight brightness

lspci -n 00:02.0 0300: 8086:0f31 (rev 0e) lspci -nn 00:02.0 VGA compatible controller [0300]: Intel Corporation Atom Processor Z36xxx/Z37xxx Series Graphics & Display [8086:0f31] (rev 0e)___ dri-devel mailing list dri-devel@lists.freedesktop.org

[PATCH v5 4/5] drm: Connector helper function to release resources

From: "Pandiyan, Dhinakaran" Having an ->atomic_release callback is useful to release shared resources that get allocated in compute_config(). This function is expected to be called in the atomic_check() phase before new resources are acquired. v4: Document that

Re: [PATCHv5 07/11] s5p-cec: add cec-notifier support, move out of staging

On Wed, Mar 29, 2017 at 04:15:39PM +0200, Hans Verkuil wrote: > From: Hans Verkuil > > By using the CEC notifier framework there is no longer any reason > to manually set the physical address. This was the one blocking > issue that prevented this driver from going out of

RE: [PATCH] drm/amdgpu/virt: fix spelling mistake: "hypervior" -> "hypervisor"

> > From: Colin Ian King > > trivial fix to spelling mistake in DRM_ERROR error message > > Signed-off-by: Colin Ian King > --- > drivers/gpu/drm/amd/amdgpu/mxgpu_vi.c | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git

[PATCH] drivers: gpu: drm: i915L intel_lpe_audio: Fix kerneldoc comments

Add description for existing parameter 'pipe' to fix the build warning: ./drivers/gpu/drm/i915/intel_lpe_audio.c:342: warning: No description found for parameter 'pipe'. Signed-off-by: Tamara Diaconita --- drivers/gpu/drm/i915/intel_lpe_audio.c | 1 + 1 file changed,

Re: [PATCHv5 04/11] exynos_hdmi: add CEC notifier support

On Wed, Mar 29, 2017 at 04:15:36PM +0200, Hans Verkuil wrote: > + cec_notifier_set_phys_addr(hdata->notifier, > +cec_get_edid_phys_addr(edid)); This pattern causes problems - can we have the notifier taking the EDID please, and stubs in cec-notifier.h to stub

Re: [PATCH 1/6] virtio: wrap find_vqs

On Wed, 29 Mar 2017 23:48:44 +0300 "Michael S. Tsirkin" wrote: > We are going to add more parameters to find_vqs, let's wrap the call so > we don't need to tweak all drivers every time. > > Signed-off-by: Michael S. Tsirkin > --- > drivers/block/virtio_blk.c

Re: linux-next: Tree for Mar 30

On Thu, 2017-03-30 at 16:55 +1100, Stephen Rothwell wrote: > Hi all, > > Changes since 20170329: > > Undropped tree: xen-tip > > The vfs tree gained a conflict against Linus' tree. > > The drm tree gained conflicts against the drm-intel-fixes tree. > > The mailbox tree lost its build failure.

Re: [PATCHv5 00/11] video/exynos/sti/cec: add CEC notifier & use in drivers

On Thu, Mar 30, 2017 at 09:47:00AM +0200, Daniel Vetter wrote: > On Wed, Mar 29, 2017 at 09:59:34PM +0200, Hans Verkuil wrote: > > Hi Daniel, > > > > On 29/03/17 19:47, Daniel Vetter wrote: > > > On Wed, Mar 29, 2017 at 04:15:32PM +0200, Hans Verkuil wrote: > > >> From: Hans Verkuil

Re: [PATCHv5 06/11] s5p-cec.txt: document the HDMI controller phandle

On Wed, Mar 29, 2017 at 04:15:38PM +0200, Hans Verkuil wrote: > From: Hans Verkuil > > Update the bindings documenting the new hdmi phandle. > > Signed-off-by: Hans Verkuil > CC: linux-samsung-...@vger.kernel.org > CC: devicet...@vger.kernel.org

[PATCH v5 1/5] drm: Add driver-private objects to atomic state

From: "Pandiyan, Dhinakaran" It is necessary to track states for objects other than connector, crtc and plane for atomic modesets. But adding objects like DP MST link bandwidth to drm_atomic_state would mean that a non-core object will be modified by the core

Re: [PATCH 1/2] drm/bridge: ti-tfp410: support hpd via gpio

Hi, On 03/30/2017 11:49 AM, Archit Taneja wrote: On 03/28/2017 07:02 PM, Jyri Sarha wrote: On 03/27/17 08:58, Archit Taneja wrote: Hi, On 03/07/2017 03:21 AM, Christopher Spinrath wrote: Hi Fabio, On 03/06/2017 10:46 PM, Fabio Estevam wrote: Hi Christopher, On Mon, Mar 6, 2017 at 6:40

Re: DRM: Component framework API support

Hi Eugeniy, On 30-03-2017 13:05, Eugeniy Paltsev wrote: > Hi, > > I am trying to add support of new component framework API in ARC PGU driver. > The point is that for now we have ARC PGU driver which works with adv7511 > encoder. Both of them don't support component framework API. I had to add

Re: [PATCHv5 04/11] exynos_hdmi: add CEC notifier support

On Wed, Mar 29, 2017 at 04:15:36PM +0200, Hans Verkuil wrote: > From: Hans Verkuil > > Implement the CEC notifier support to allow CEC drivers to > be informed when there is a new physical address. > > Signed-off-by: Hans Verkuil > Tested-by:

Re: [PATCHv5 05/11] ARM: dts: exynos: add HDMI controller phandle to exynos4.dtsi

On Wed, Mar 29, 2017 at 04:15:37PM +0200, Hans Verkuil wrote: > From: Hans Verkuil > > Add the new hdmi phandle to exynos4.dtsi. This phandle is needed by the > s5p-cec driver to initialize the CEC notifier framework. > > Tested with my Odroid U3. > > Signed-off-by:

[PATCH] megachips-stdpxxxx-ge-b850v3-fw: Fix drm bridge initialization

Reordering of the device nodes based on unit address resulted in ge_b850v3_lvds_attach() being called before ge_b850v3_lvds_ptr->stdp4028_i2c was populated. This patch moves the drm bridge initialization from ge_b850v3_lvds_init() to stdp4028_ge_b850v3_fw_probe() ensuring that

Re: [PATCHv5 11/11] arm: sti: update sti-cec for CEC notifier support

Hi Benjamin On 03/30/2017 09:41 AM, Benjamin Gaignard wrote: > + Patrice for sti DT In order to be coherent with all previous STi DT patches, can you update the commit message with "ARM: dts: STiH410: update sti-cec for CEC notifier support" Thanks Patrice > > 2017-03-29 16:15 GMT+02:00

[PATCH v5 5/5] drm/dp: Track MST link bandwidth

From: "Pandiyan, Dhinakaran" Use the added helpers to track MST link bandwidth for atomic modesets. Link bw is acquired in the ->atomic_check() phase when CRTCs are being enabled with drm_atomic_find_vcpi_slots() instead of drm_find_vcpi_slots(). Similarly, link bw

RE: [PATCH 1/6] virtio: wrap find_vqs

> -Original Message- > From: Michael S. Tsirkin [mailto:m...@redhat.com] > Sent: Thursday, March 30, 2017 4:49 AM > Subject: [PATCH 1/6] virtio: wrap find_vqs > > We are going to add more parameters to find_vqs, let's wrap the call so > we don't need to tweak all drivers every time. > >

[Bug 100465] Hard lockup with radeonsi driver on FirePro W600, W9000 and W9100

https://bugs.freedesktop.org/show_bug.cgi?id=100465 Michel Dänzer changed: What|Removed |Added Attachment #130563|text/x-log |text/plain

Re: [PATCH 4/6] drm/amdgpu: drop alpha support

On 30/03/17 10:09 PM, Alex Deucher wrote: > On Thu, Mar 30, 2017 at 2:39 AM, Michel Dänzer wrote: >> On 29/03/17 09:55 PM, Christian König wrote: >>> From: Christian König >>> >>> We will probably never see this combination. >>> >>> Signed-off-by:

Re: [RFC PATCH xserver] modesetting: re-set the crtc's mode when link-status goes BAD

On Thu, Mar 30, 2017 at 05:37:55PM -0700, Eric Anholt wrote: > Martin Peres writes: > > > On 26/01/17 14:37, Martin Peres wrote: > >> Despite all the careful planing of the kernel, a link may become > >> insufficient to handle the currently-set mode. At this point,

Re: [PATCH] drm/vc4: Allocate the right amount of space for boot-time CRTC state.

Daniel Vetter writes: > On Tue, Mar 28, 2017 at 01:13:43PM -0700, Eric Anholt wrote: >> Without this, the first modeset would dereference past the allocation >> when trying to free the mm node. >> >> Signed-off-by: Eric Anholt >> Tested-by: Stefan Wahren

Re: [RFC PATCH xserver] modesetting: re-set the crtc's mode when link-status goes BAD

Martin Peres writes: > On 26/01/17 14:37, Martin Peres wrote: >> Despite all the careful planing of the kernel, a link may become >> insufficient to handle the currently-set mode. At this point, the >> kernel should mark this particular configuration as being broken

[PATCH v4 2/2] drm/pl111: Initial drm/kms driver for pl111

From: Tom Cooksey This is a modesetting driver for the pl111 CLCD display controller found on various ARM platforms such as the Versatile Express. The driver has only been tested on the bcm911360_entphn platform so far, with PRIME-based buffer sharing between vc4 and clcd.

[PATCH v4 1/2] video: ARM CLCD: Move registers to a separate header.

We'd like to reuse these register definitions for the DRM CLCD driver, but there's a bunch of fbdev-specific code in the current header. Signed-off-by: Eric Anholt --- include/linux/amba/clcd-regs.h | 76 ++ include/linux/amba/clcd.h

Re: [PATCH libdrm] configure.ac: bring back pthread-stubs check

On Thursday, 2017-03-30 18:01:12 +0100, Emil Velikov wrote: > Accidentally removed with earlier commit. Although rather than simply > adding the check for all platforms, use the same heuristics as we do in > mesa. > > Namely: pthread-stubs is a thing only for BSD platforms. Everyone else > should

Re: [PATCH v4 6/6] drm/omap: Implement CTM property for CRTC using OVL managers CPR matrix

Hi Jyri, Thank you for the patch. On Friday 24 Mar 2017 16:47:56 Jyri Sarha wrote: > Implement CTM color management property for OMAP CRTC using DSS > overlay manager's Color Phase Rotation matrix. The CPR matrix does not > exactly match the CTM property documentation. On DSS the CPR matrix is >

Re: [PATCH v4 4/6] drm/omap: Remove the obsolete #define omap_plane _omap_plane hack

Hi Jyri, Thank you for the patch. On Friday 24 Mar 2017 16:47:54 Jyri Sarha wrote: > Remove the obsolete "#define omap_plane _omap_plane" hack and other > related hacks to get around the enum omap_plane colliding with struct > omap_plane. > > Signed-off-by: Jyri Sarha

Re: [PATCH v4 3/6] drm/omap: Fix one ugly indentation style break left by coccinelle

Hi Jyri, Thank you for the patch. On Friday 24 Mar 2017 16:47:53 Jyri Sarha wrote: > Fix one ugly indentation style break left by the previous coccilnelle > patch. > > Signed-off-by: Jyri Sarha Acked-by: Laurent Pinchart > --- >

Re: [PATCH v4 2/6] drm/omap: Rename enum omap_plane to enum omap_plane_id

Hi Jyri, On Friday 24 Mar 2017 16:47:52 Jyri Sarha wrote: > The enum omap_plane conflicted with the same struct name for omapdrm > plane private data. This rename should solve the conflict. > > The rename was implement with this very simple coccinelle patch: > > @@ > @@

[pull] radeon and amdgpu drm-next-4.12

Hi Dave, New stuff for 4.12: - Preliminary vega10 support - Support for multi-level page tables - GPU sensor stuff for mesa - job tracing improvements - PRT support for sparse buffers - Additional SR-IOV improvements - ttm improvements - misc bug fixes and code cleanups The following changes

Re: [PATCH v4 1/6] drm/omap: Get rid of DRM_OMAP_NUM_CRTCS config option

Hi Jyri, Thank you for the patch. On Friday 24 Mar 2017 16:47:51 Jyri Sarha wrote: > Allocate one CRTC for each connected output and get rid of > DRM_OMAP_NUM_CRTCS config option. We still can not create more CRTCs > than we have DSS display managers. We also reserve one overlay per > CRTC for

Re: [PATCH v3 2/2] drm/pl111: Initial drm/kms driver for pl111

Eric Anholt writes: > From: Tom Cooksey > > This is a modesetting driver for the pl111 CLCD display controller > found on various ARM platforms such as the Versatile Express. The > driver has only been tested on the bcm911360_entphn platform so far, > with

Re: [PATCH] drm: Fix locking gotcha in page_flip ioctl

Reviewed-by: Harry Wentland Harry On 2017-03-30 04:48 PM, Daniel Vetter wrote: We want to lock the primary plane, not the cursor (which might be optional). Real bad case of copy-paste fail, unfortunately our CI didn't catch that because i915 does have a cursor plane.

[PATCH] drm: Fix locking gotcha in page_flip ioctl

We want to lock the primary plane, not the cursor (which might be optional). Real bad case of copy-paste fail, unfortunately our CI didn't catch that because i915 does have a cursor plane. Cc: Eric Anholt Reported-by: Eric Anholt Fixes: 29dc0d1de182 ("drm: Roll

[PATCH v3 2/2] drm/pl111: Initial drm/kms driver for pl111

From: Tom Cooksey This is a modesetting driver for the pl111 CLCD display controller found on various ARM platforms such as the Versatile Express. The driver has only been tested on the bcm911360_entphn platform so far, with PRIME-based buffer sharing between vc4 and clcd.

[PATCH v3 1/2] video: ARM CLCD: Move registers to a separate header.

We'd like to reuse these register definitions for the DRM CLCD driver, but there's a bunch of fbdev-specific code in the current header. Signed-off-by: Eric Anholt --- include/linux/amba/clcd-regs.h | 76 ++ include/linux/amba/clcd.h

Re: [PATCH 2/2] drm/amdgpu: Avoid overflows/divide-by-zero in latency_watermark calculations.

On Wed, Mar 29, 2017 at 4:09 PM, Mario Kleiner wrote: > At dot clocks > approx. 250 Mhz, some of these calcs will overflow and > cause miscalculation of latency watermarks, and for some overflows also > divide-by-zero driver crash ("divide error: [#1] PREEMPT SMP"

Re: [Intel-gfx] [PATCH] drm/vblank: drop the mode argument from drm_calc_vbltimestamp_from_scanoutpos

On Thu, Mar 30, 2017 at 04:41:57PM +0300, Ville Syrjälä wrote: > On Thu, Mar 30, 2017 at 03:27:57PM +0200, Daniel Vetter wrote: > > On Thu, Mar 30, 2017 at 2:03 PM, Ville Syrjälä > > wrote: > > > On Wed, Mar 22, 2017 at 09:56:12PM +0100, Daniel Vetter wrote: > > >>

Re: [PATCH] drm: Clear e after kfree in drm_mode_page_flip_ioctl

On Thu, Mar 30, 2017 at 10:26:24AM -0400, Harry Wentland wrote: > Reviewed-by: Harry Wentland Thanks for the quick review, pushed to drm-misc. -Daniel > > On 2017-03-30 09:32 AM, Daniel Vetter wrote: > > With the explicit retry loop static analyzers get confused by the

[PATCH libdrm] configure.ac: bring back pthread-stubs check

Accidentally removed with earlier commit. Although rather than simply adding the check for all platforms, use the same heuristics as we do in mesa. Namely: pthread-stubs is a thing only for BSD platforms. Everyone else should have lightweight pthread API in their C runtime library. Fixes:

Re: [PATCH] drm: Clear e after kfree in drm_mode_page_flip_ioctl

Reviewed-by: Harry Wentland On 2017-03-30 09:32 AM, Daniel Vetter wrote: With the explicit retry loop static analyzers get confused by the control flow and believe that e could be accessed after kfree. That's not possible, but it's non-obvious, so let's clear it to

Re: [PATCH 1/6] virtio: wrap find_vqs

On Thu, Mar 30, 2017 at 02:00:08PM +0800, Jason Wang wrote: > > > On 2017年03月30日 04:48, Michael S. Tsirkin wrote: > > We are going to add more parameters to find_vqs, let's wrap the call so > > we don't need to tweak all drivers every time. > > > > Signed-off-by: Michael S.

[Bug 100395] DC, Powerplay, Tonga, top screen flicker with current amd-staging-4.9

https://bugs.freedesktop.org/show_bug.cgi?id=100395 --- Comment #6 from Harry Wentland --- Thanks, Andy, for the report and taking the time to bisect. Jordan from my team spotted the bug as well and is working on a solution. If you're curious about the cause of this...

Re: [PATCH] drm: Convert cmpxchg(bool) back to a two step operation

On Thu, Mar 30, 2017 at 03:08:32PM +0100, Chris Wilson wrote: > ARM v6 (at least) only allows cmpxchg on 32bit variables which doesn't > always include the bool type. > > drivers/built-in.o: In function `vblank_disable_and_save': > imx-ocotp.c:(.text+0xb45e8): undefined reference to

[PATCH] drm: Convert cmpxchg(bool) back to a two step operation

ARM v6 (at least) only allows cmpxchg on 32bit variables which doesn't always include the bool type. drivers/built-in.o: In function `vblank_disable_and_save': imx-ocotp.c:(.text+0xb45e8): undefined reference to `__bad_cmpxchg' Makefile:986: recipe for target 'vmlinux' failed Reported-by: kbuild

Re: [Intel-gfx] [PATCH] drm/vblank: drop the mode argument from drm_calc_vbltimestamp_from_scanoutpos

On Thu, Mar 30, 2017 at 03:27:57PM +0200, Daniel Vetter wrote: > On Thu, Mar 30, 2017 at 2:03 PM, Ville Syrjälä > wrote: > > On Wed, Mar 22, 2017 at 09:56:12PM +0100, Daniel Vetter wrote: > >> If we restrict this helper to only kms drivers (which is the case) we >

[PATCH] drm: Clear e after kfree in drm_mode_page_flip_ioctl

With the explicit retry loop static analyzers get confused by the control flow and believe that e could be accessed after kfree. That's not possible, but it's non-obvious, so let's clear it to NULL. We already cleared e = NULL at the top of the function, so this is all in line. Cc: Julia Lawall

[PATCH] dim: Add apply-pull command

I'm getting real lazy, let's start scripting this. Very rough draft, but adds a Link: (patchwork tracks pull requests too, maybe we'll start CI-ing them too), and sob line. In the future we might add more checks here ... Signed-off-by: Daniel Vetter --- dim | 34

Re: [Intel-gfx] [PATCH] drm/vblank: drop the mode argument from drm_calc_vbltimestamp_from_scanoutpos

On Thu, Mar 30, 2017 at 2:03 PM, Ville Syrjälä wrote: > On Wed, Mar 22, 2017 at 09:56:12PM +0100, Daniel Vetter wrote: >> If we restrict this helper to only kms drivers (which is the case) we >> can look up the correct mode easily ourselves. But it's a bit tricky:

Re: [PATCH 4/6] drm/amdgpu: drop alpha support

Am 30.03.2017 um 15:09 schrieb Alex Deucher: On Thu, Mar 30, 2017 at 2:39 AM, Michel Dänzer wrote: On 29/03/17 09:55 PM, Christian König wrote: From: Christian König We will probably never see this combination. Signed-off-by: Christian König

Re: [PATCH 4/6] drm/amdgpu: drop alpha support

On Thu, Mar 30, 2017 at 2:39 AM, Michel Dänzer wrote: > On 29/03/17 09:55 PM, Christian König wrote: >> From: Christian König >> >> We will probably never see this combination. >> >> Signed-off-by: Christian König >> --- >>

[Bug 100465] Hard lockup with radeonsi driver on FirePro W600, W9000 and W9100

https://bugs.freedesktop.org/show_bug.cgi?id=100465 --- Comment #2 from Julien Isorce --- Created attachment 130569 --> https://bugs.freedesktop.org/attachment.cgi?id=130569=edit Same result with amdgpu using a 4.10 kernel -- You are receiving this mail because: You

DRM: Component framework API support

Hi, I am trying to add support of new component framework API in ARC PGU driver. The point is that for now we have ARC PGU driver which works with adv7511 encoder. Both of them don't support component framework API. I had to add support of component framework based dw_hdmi encoder to ARC PGU

Re: [Intel-gfx] [PATCH] drm/vblank: drop the mode argument from drm_calc_vbltimestamp_from_scanoutpos

On Wed, Mar 22, 2017 at 09:56:12PM +0100, Daniel Vetter wrote: > If we restrict this helper to only kms drivers (which is the case) we > can look up the correct mode easily ourselves. But it's a bit tricky: > > - All legacy drivers look at crtc->hwmode. But that is update already > at the

[PATCHv4 25/29] drm/omap: displays: panel-dpi: Support for handling backlight devices

From: Peter Ujfalusi The associated backlight device can be configured via DT by providing the phandle to the device. If the backlight device is configured, the driver can manage the backligt along with the panel's power state, iow it can turn on the backlight when the

[PATCHv4 18/29] drm/omap: remove unused dispc_wb_enable & dispc_wb_is_enabled

Remove two unused WB functions. Signed-off-by: Tomi Valkeinen Reviewed-by: Laurent Pinchart --- drivers/gpu/drm/omapdrm/dss/dispc.c | 10 -- drivers/gpu/drm/omapdrm/dss/dss.h | 2 -- 2 files changed, 12 deletions(-) diff

[PATCHv4 21/29] drm/omap: dss: Support for detecting display stack readiness

From: Peter Ujfalusi When omapdss is loaded (all core components are in place) create a list of devices used in the display graph. This list later can be used by omapdrm via the omapdss_stack_is_ready() function to check that these components are loaded. Based on this

[PATCHv4 11/29] drm/omap: display: don't use dsi_get_pixel_size()

display.c uses dsi_get_pixel_size() which is implemented in the DSI driver, and we won't have that in the omapdss-base module, to which we want to move display.c This patch changes display.c not to use dsi_get_pixel_size(). The call can be replaced with a simple check for OMAP_DSS_DSI_FMT_RGB565.

[PATCHv4 26/29] drm/omap: dispc: improve debug print of display flags

Instead of printing 0/1 for display flags like vsync high/low, use a tri-state print (-1/0/1) to indicate the "undefined" state. Signed-off-by: Tomi Valkeinen --- drivers/gpu/drm/omapdrm/dss/dispc.c | 20 +++- 1 file changed, 15 insertions(+), 5

[PATCHv4 19/29] drm/omap: fix replication logic

DSS uses "replication logic" to convert color components from smaller bit widths to bigger bit widths. Without replication logic, the color component would be shifted and the least significant bits would be left at 0, whereas with replication logic, the least significat bits will be filled with

[PATCHv4 16/29] drm/omap: use dispc_ops

Change omapdrm to get dispc_ops and use that to call the dispc functions instead or direct function calls. The change is very straightforward. The only problem was in omap_crtc_init() which calls pipe2vbl(crtc), and at that point of time the crtc->dev link, which is used to get the dispc_ops,

[PATCHv4 23/29] drm/omap: display: Add displays in sorted order to the panel_list

From: Peter Ujfalusi Keep the panel_list ordered according to aliases. The DRM connectors will be created following the panel_list. By keeping the list ordered the DRM connectors will be created in the same order regardless of the driver probe order. Signed-off-by: Peter

[PATCHv4 24/29] drm/omap: poll only connectors where the connect/disconnect can be checked

From: Peter Ujfalusi When the connector associated detect callback is not provided, we can not detect if the display is connected or disconnected. These displays do not support hot plug, they are always connected. Let DRM know that connectors w/o detect callback should not

[PATCHv4 22/29] drm/omap: Use omapdss_stack_is_ready() to check that the display stack is up

From: Peter Ujfalusi Instead of 'guessing' based on aliases of the status of the DSS drivers, use the new interface to check that all needed drivers are loaded. In this way we can be sure that all needed drivers are loaded so it is safe to continue the probing of omapdrm.

[PATCHv4 29/29] drm/omap: fix crash on module unload

When unloading omapdrm we get a NULL pointer deref in omap_drm_irq_uninstall(). This is caused by: 967dd48417874dd25491a4e933648f394a64f70f ("drm: remove drm_vblank_no_hw_counter assignment from driver code") We shut down all the crtcs at unload time before calling omap_drm_irq_uninstall, so the

[PATCHv4 28/29] drm/omap: use drm_atomic_helper_shutdown()

Use drm_atomic_helper_shutdown() to ensure that all crtcs are disabled when unloading the driver. Signed-off-by: Tomi Valkeinen --- drivers/gpu/drm/omapdrm/omap_drv.c | 2 ++ 1 file changed, 2 insertions(+) diff --git a/drivers/gpu/drm/omapdrm/omap_drv.c

[PATCHv4 06/29] drm/omap: Add support for render nodes

From: Hemant Hariyani Add support for render nodes in omap driver and allow required ioctls to be accessible via render nodes. This enables unprivileged clients to allocate resources like GEM buffers for rendering their content into. Mode setting (KMS ioctls) is not

[PATCHv4 20/29] drm/omap: dss: Functions to check components in the display/output list

From: Peter Ujfalusi The functions can be used to check a component (by it's of_node) if it is part of the omapdss display or output list. If the component is found, it means that the driver is loaded. Signed-off-by: Peter Ujfalusi Signed-off-by:

[PATCHv4 10/29] drm/omap: output: use dev_err instead of DSSERR

We don't have omapdss's custom error printing functions in the common omapdss-base module, to which we want to move output.c. This patch changes output.c to use dev_err instead of DSSERR so that it doesn't depend on DSSERR. Signed-off-by: Tomi Valkeinen Acked-by: Laurent

[PATCHv4 27/29] drm/omap: fix display SYNC/DE flags

At the moment VSYNC/HSYNC/DE high/low flags set by the panel/encoder drivers get lost when the videotimings are translated to DRM's videomode, as DRM's mode does not have corresponding flags. DRM has bus-flags for this purpose, and while it lacks a few flags at the moment, it should be used here.

[PATCHv4 17/29] drm/omap: remove all EXPORT_SYMBOLs from dispc.c

omapdrm now uses dispc_ops instead of direct function calls so we can remove all EXPORT_SYMBOLs from dispc. Most of the functions can also be made static, but a few are used outside dispc.c. Signed-off-by: Tomi Valkeinen --- drivers/gpu/drm/omapdrm/dss/dispc.c | 84

[PATCHv4 15/29] drm/omap: fill dispc_ops

This patch changes the current omapdss driver to fill a dispc_ops struct and set it to omapdss-base. Signed-off-by: Tomi Valkeinen --- drivers/gpu/drm/omapdrm/dss/dispc.c | 40 + 1 file changed, 40 insertions(+) diff --git

[PATCHv4 12/29] drm/omap: move display, dss-of, output to omapdss-base

This patch moves the common parts of omapdss to omapdss-base so that both the current omapdss driver and the new omapdss6 driver can use them. Signed-off-by: Tomi Valkeinen --- drivers/gpu/drm/omapdrm/dss/Makefile | 6 +++--- drivers/gpu/drm/omapdrm/dss/display.c | 2 --

[PATCHv4 13/29] drm/omap: move dispc related dss-feat funcs to dispc

omapdrm still uses a few non-dispc functions: dss_feat_get_num_mgrs(), dss_feat_get_num_ovls() and dss_feat_get_supported_color_modes(). We want to provide omapdrm a single dispc_ops function pointer struct so that omapdrm will use either the current omapdss or the new omapdss6 driver depending

[PATCHv4 03/29] drm/omap: remove divider constraint from hsdiv

The driver only uses even dividers for hsdiv when pclk >= 100MHz, as odd dividers can create uneven duty cycle. However, while this holds true for some dividers like DISPC's LCK and PCK dividers, it is not actually true for hsdiv. hsdiv always produces even duty cycle, so the constraint can be

[PATCHv4 09/29] drm/omap: move dss_initialized to omapdss-base

omapdss_is_initialized() is used to find out if omapdss has been probed successfully. This patch moves the related code to the common omapdss-base module, so that the same support will be there for both omapdss and omapdss6. Signed-off-by: Tomi Valkeinen ---

[PATCHv4 14/29] drm/omap: add dispc_ops

We want to change the dispc API from plain functions to a struct with functions pointers, so that omapdrm can call either omapdss or omapdss6 depending on the platform. This patch adds 'struct dispc_ops' and adds functions to omapdss-base to set and get the ops. Signed-off-by: Tomi Valkeinen

[PATCHv4 07/29] drm/omap: fix HDMI sync polarities

While implementing writeback support, odd behavior of WBDELAYCOUNT was observed with the combination of WB capture and HDMI. The result of the debugging was that the HDMI sync polarities are not set correctly. The current code sets the sync polarities going from HDMI WP to DISPC according to the

[PATCHv4 01/29] drm/omap: work-around for errata i886

DRA7 errata i886 (FPDLink PLL Unlocks With Certain SoC PLL M/N Values) says that FPDLink is sensitive to jitter on the vout clock, and that low PLL M and N values result in more jitter than high M and N values. This patch implements a workaround for the problem by changing the PLL setup to search

  1   2   >