[Bug 108260] [Regression?] [powerplay] Failed to retrieve minimum clocks. 4.19-rc6+

2019-01-23 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=108260 Martin Jørgensen changed: What|Removed |Added Resolution|FIXED |--- Status|RESOLVED

RE: [PATCH] drm/modes: Prevent division by zero htotal

2019-01-23 Thread Zhang, Tina
> -Original Message- > From: Daniel Vetter [mailto:daniel.vet...@ffwll.ch] On Behalf Of Daniel Vetter > Sent: Wednesday, January 23, 2019 6:56 PM > To: Zhang, Tina > Cc: intel-...@lists.freedesktop.org; dri-devel@lists.freedesktop.org; Adam > Jackson ; Dave Airlie ; Daniel Vetter > >

[Bug 107152] GPU fault detected: 146 / VM_CONTEXT1_PROTECTION_FAULT / ring gfx timeout

2019-01-23 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=107152 --- Comment #15 from Ida Wallace --- Thanks for letting us know about the duplicate bug of GPU fault and System crashes, so solution seekers can refer both references to understand the bug and try to solve it easily. Ida,

Re: [PATCH V2,4/8] drm/mediatek: fix the rate and divder of hdmi phy for MT2701

2019-01-23 Thread CK Hu
On Fri, 2019-01-18 at 20:59 +0800, Wangyan Wang wrote: > From: chunhui dai Describe something here. > > Fixes: 0fc721b2968e ("drm/mediatek: add hdmi driver for MT2701 and MT7623") > Signed-off-by: chunhui dai Any one who pass a patch should sign off it. Regards, CK > --- >

[Bug 109445] Graveyard Keeper: Lockup in under 5min of play.

2019-01-23 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=109445 --- Comment #2 from Mike Mestnik --- Created attachment 143217 --> https://bugs.freedesktop.org/attachment.cgi?id=143217=edit Renderdoc capture under DXVK -- You are receiving this mail because: You are the assignee for the

[v7 3/3] dt-bindings: msm/disp: Introduce interconnect bindings for MDSS on SDM845

2019-01-23 Thread Jayant Shekhar
Add interconnect properties such as interconnect provider specifier , the edge source and destination ports which are required by the interconnect API to configure interconnect path for MDSS. Changes in v2: - None Changes in v3: - Remove common property definitions (Rob Herring)

[v7 2/3] drm/msm/dpu: Integrate interconnect API in MDSS

2019-01-23 Thread Jayant Shekhar
The interconnect framework is designed to provide a standard kernel interface to control the settings of the interconnects on a SoC. The interconnect API uses a consumer/provider-based model, where the providers are the interconnect buses and the consumers could be various drivers. MDSS is one

[v7 1/3] drm/msm/dpu: clean up references of DPU custom bus scaling

2019-01-23 Thread Jayant Shekhar
Since the upstream interconnect bus framework has landed upstream, the existing references of custom bus scaling needs to be cleaned up. Changes in v2: - Fixed build error due to partial clean up Changes in v3: - Condense multiple lines into a single line (Sean Paul) Changes in

[v7 0/3] Use interconnect API in MDSS on SDM845

2019-01-23 Thread Jayant Shekhar
The interconnect API provides an interface for consumer drivers to express their bandwidth needs in the SoC. This data is aggregated and the on-chip interconnect hardware is configured to the appropriate power/performance profile. MDSS is one of the interconnect consumers which uses the

Re: drm/komeda: Off by one in komeda_fb_get_pixel_addr()

2019-01-23 Thread james qian wang (Arm Technology China)
On Wed, Jan 23, 2019 at 12:37:55PM +0300, Dan Carpenter wrote: > The > should be >= to avoid an off by one bug. > > Fixes: c46c24bb6b11 ("drm/komeda: Add komeda_framebuffer") > Signed-off-by: Dan Carpenter > --- > > I'm 98% sure this is correct, but please review it carefully because I'm > not

Re: [PATCH v4 1/2] drm: Add color management LUT validation helper (v4)

2019-01-23 Thread Matt Roper
On Sat, Jan 12, 2019 at 01:07:14PM +0100, Daniel Vetter wrote: > On Fri, Jan 11, 2019 at 02:27:00PM -0800, Matt Roper wrote: > > Dave, Daniel - any concerns if we merge this drm core patch through the > > Intel tree? The second patch in the series doesn't apply cleanly in > > drm-misc-next. > >

Re: [PATCH 2/2] drm/msm: Use DRM_DEV_INFO_RATELIMITED for shrinker messages

2019-01-23 Thread Rob Clark
On Mon, Jan 21, 2019 at 4:36 AM Jani Nikula wrote: > > On Fri, 18 Jan 2019, "Kristian H. Kristensen" wrote: > > Otherwise we get hard to track down "Purging: 123123 bytes" messages in > > the log. > > > > Signed-off-by: Kristian H. Kristensen > > --- > > drivers/gpu/drm/msm/msm_gem_shrinker.c

Re: [PATCH v4 0/9] mmu notifier provide context informations

2019-01-23 Thread Dan Williams
On Wed, Jan 23, 2019 at 3:05 PM Jerome Glisse wrote: > > On Wed, Jan 23, 2019 at 02:54:40PM -0800, Dan Williams wrote: > > On Wed, Jan 23, 2019 at 2:23 PM wrote: > > > > > > From: Jérôme Glisse > > > > > > Hi Andrew, i see that you still have my event patch in you queue [1]. > > > This patchset

[Bug 201497] [amdgpu]: '*ERROR* No EDID read' is back in 4.19

2019-01-23 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=201497 Elliot Thomas (e.singularity...@gmail.com) changed: What|Removed |Added CC|

[pull] amdgpu drm-fixes-5.0

2019-01-23 Thread Alex Deucher
Hi Dave, Daniel, Just a couple of fixes for 5.0: - Overclock fix for vega10 - Hybrid gfx laptop fix The following changes since commit 35dad45d5cad3c9ca8d6a338cbf668cd7ea86469: drm/amd/display: Detach backlight from stream (2019-01-16 17:11:47 -0500) are available in the Git repository at:

Re: [PATCH v4 0/9] mmu notifier provide context informations

2019-01-23 Thread Jerome Glisse
On Wed, Jan 23, 2019 at 02:54:40PM -0800, Dan Williams wrote: > On Wed, Jan 23, 2019 at 2:23 PM wrote: > > > > From: Jérôme Glisse > > > > Hi Andrew, i see that you still have my event patch in you queue [1]. > > This patchset replace that single patch and is broken down in further > > step so

Re: [PATCH v4 0/9] mmu notifier provide context informations

2019-01-23 Thread Dan Williams
On Wed, Jan 23, 2019 at 2:23 PM wrote: > > From: Jérôme Glisse > > Hi Andrew, i see that you still have my event patch in you queue [1]. > This patchset replace that single patch and is broken down in further > step so that it is easier to review and ascertain that no mistake were > made during

Re: [PATCH v4 9/9] RDMA/umem_odp: optimize out the case when a range is updated to read only

2019-01-23 Thread Jerome Glisse
On Wed, Jan 23, 2019 at 10:32:00PM +, Jason Gunthorpe wrote: > On Wed, Jan 23, 2019 at 05:23:15PM -0500, jgli...@redhat.com wrote: > > From: Jérôme Glisse > > > > When range of virtual address is updated read only and corresponding > > user ptr object are already read only it is pointless to

[PATCH v4 9/9] RDMA/umem_odp: optimize out the case when a range is updated to read only

2019-01-23 Thread jglisse
From: Jérôme Glisse When range of virtual address is updated read only and corresponding user ptr object are already read only it is pointless to do anything. Optimize this case out. Signed-off-by: Jérôme Glisse Cc: Christian König Cc: Jan Kara Cc: Felix Kuehling Cc: Jason Gunthorpe Cc:

[PATCH v4 8/9] gpu/drm/i915: optimize out the case when a range is updated to read only

2019-01-23 Thread jglisse
From: Jérôme Glisse When range of virtual address is updated read only and corresponding user ptr object are already read only it is pointless to do anything. Optimize this case out. Signed-off-by: Jérôme Glisse Cc: Christian König Cc: Jan Kara Cc: Felix Kuehling Cc: Jason Gunthorpe Cc:

[PATCH v4 7/9] gpu/drm/amdgpu: optimize out the case when a range is updated to read only

2019-01-23 Thread jglisse
From: Jérôme Glisse When range of virtual address is updated read only and corresponding user ptr object are already read only it is pointless to do anything. Optimize this case out. Signed-off-by: Jérôme Glisse Cc: Christian König Cc: Jan Kara Cc: Felix Kuehling Cc: Jason Gunthorpe Cc:

[PATCH v4 4/9] mm/mmu_notifier: pass down vma and reasons why mmu notifier is happening

2019-01-23 Thread jglisse
From: Jérôme Glisse CPU page table update can happens for many reasons, not only as a result of a syscall (munmap(), mprotect(), mremap(), madvise(), ...) but also as a result of kernel activities (memory compression, reclaim, migration, ...). Users of mmu notifier API track changes to the CPU

[PATCH v4 5/9] mm/mmu_notifier: mmu_notifier_range_update_to_read_only() helper

2019-01-23 Thread jglisse
From: Jérôme Glisse Helper to test if a range is updated to read only (it is still valid to read from the range). This is useful for device driver or anyone who wish to optimize out update when they know that they already have the range map read only. Signed-off-by: Jérôme Glisse Cc: Christian

[PATCH v4 6/9] gpu/drm/radeon: optimize out the case when a range is updated to read only

2019-01-23 Thread jglisse
From: Jérôme Glisse When range of virtual address is updated read only and corresponding user ptr object are already read only it is pointless to do anything. Optimize this case out. Signed-off-by: Jérôme Glisse Cc: Christian König Cc: Jan Kara Cc: Felix Kuehling Cc: Jason Gunthorpe Cc:

[PATCH v4 3/9] mm/mmu_notifier: use correct mmu_notifier events for each invalidation

2019-01-23 Thread jglisse
From: Jérôme Glisse This update each existing invalidation to use the correct mmu notifier event that represent what is happening to the CPU page table. See the patch which introduced the events to see the rational behind this. Signed-off-by: Jérôme Glisse Cc: Christian König Cc: Jan Kara

[PATCH v4 0/9] mmu notifier provide context informations

2019-01-23 Thread jglisse
From: Jérôme Glisse Hi Andrew, i see that you still have my event patch in you queue [1]. This patchset replace that single patch and is broken down in further step so that it is easier to review and ascertain that no mistake were made during mechanical changes. Here are the step: Patch 1 -

[PATCH v4 2/9] mm/mmu_notifier: contextual information for event triggering invalidation

2019-01-23 Thread jglisse
From: Jérôme Glisse CPU page table update can happens for many reasons, not only as a result of a syscall (munmap(), mprotect(), mremap(), madvise(), ...) but also as a result of kernel activities (memory compression, reclaim, migration, ...). Users of mmu notifier API track changes to the CPU

[PATCH v4 1/9] mm/mmu_notifier: contextual information for event enums

2019-01-23 Thread jglisse
From: Jérôme Glisse CPU page table update can happens for many reasons, not only as a result of a syscall (munmap(), mprotect(), mremap(), madvise(), ...) but also as a result of kernel activities (memory compression, reclaim, migration, ...). This patch introduce a set of enums that can be

Re: [PATCH] drm/bridge: sil_sii8620: depend on INPUT instead of selecting it.

2019-01-23 Thread Laurent Pinchart
Hello Dmity, On Wed, Jan 23, 2019 at 02:21:05PM -0800, Dmitry Torokhov wrote: > On Thu, Jan 24, 2019 at 12:17:35AM +0200, Laurent Pinchart wrote: > > On Wed, Jan 23, 2019 at 02:03:42PM -0800, Dmitry Torokhov wrote: > >> On Wed, Jan 23, 2019 at 09:45:56AM +0100, Lukas Wunner wrote: > >>> On Tue,

Re: [PATCH] drm/bridge: sil_sii8620: depend on INPUT instead of selecting it.

2019-01-23 Thread Laurent Pinchart
Hello Dmity, On Wed, Jan 23, 2019 at 02:03:42PM -0800, Dmitry Torokhov wrote: > On Wed, Jan 23, 2019 at 09:45:56AM +0100, Lukas Wunner wrote: > > On Tue, Jan 22, 2019 at 06:13:11AM -0800, Ronald Tschalär wrote: > >> commit d6abe6df706c66d803e6dd4fe98c1b6b7f125a56 (drm/bridge: > >> sil_sii8620: do

[Bug 109445] Graveyard Keeper: Lockup in under 5min of play.

2019-01-23 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=109445 Mike Mestnik changed: What|Removed |Added URL||https://store.steampowered.

[Bug 109445] Graveyard Keeper: Lockup in under 5min of play.

2019-01-23 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=109445 --- Comment #1 from Mike Mestnik --- Created attachment 143210 --> https://bugs.freedesktop.org/attachment.cgi?id=143210=edit ar file containing glxinfo and Xorg.log -- You are receiving this mail because: You are the assignee for the

[Bug 109445] Graveyard Keeper: Lockup in under 5min of play.

2019-01-23 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=109445 Bug ID: 109445 Summary: Graveyard Keeper: Lockup in under 5min of play. Product: DRI Version: unspecified Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW

[Bug 109444] Graveyard Keeper: Lockup in under 5min of play.

2019-01-23 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=109444 Bug ID: 109444 Summary: Graveyard Keeper: Lockup in under 5min of play. Product: DRI Version: unspecified Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW

[Bug 201497] [amdgpu]: '*ERROR* No EDID read' is back in 4.19

2019-01-23 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=201497 --- Comment #6 from Daniel Andersson (engyw...@gmail.com) --- Created attachment 280701 --> https://bugzilla.kernel.org/attachment.cgi?id=280701=edit 5.0-rc3 drm.debug=0x4 This is still an issue on 5.0-rc3. -- You are receiving this mail

[Bug 201497] [amdgpu]: '*ERROR* No EDID read' is back in 4.19

2019-01-23 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=201497 Daniel Andersson (engyw...@gmail.com) changed: What|Removed |Added Kernel Version|4.19|4.19 4.20 5.0-rc1

[Bug 105733] Amdgpu randomly hangs and only ssh works. Mouse cursor moves sometimes but does nothing. Keyboard stops working.

2019-01-23 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=105733 --- Comment #60 from l...@protonmail.ch --- dwagner, my problem persists even if I completely power the system down after shutting it down by holding down the power button and then turning the PSU completely off. I have not tried shutting it off

Re: [PATCH v2] xf86drm: Add drmIsMaster()

2019-01-23 Thread Christopher James Halse Rogers
On 24 January 2019 6:18:32 am NZDT, Emil Velikov wrote: >On Wed, 23 Jan 2019 at 04:39, Christopher James Halse Rogers > wrote: >> >> We can't use drmSetMaster to query whether or not a drm fd is master >> because it requires CAP_SYS_ADMIN, even if the fd *is* a master fd. >> >> Pick

[Bug 108916] polaris11 d3d9 rendering issue

2019-01-23 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=108916 --- Comment #1 from Axel Davy --- Hi, I just wanted to confirm the trace reproduces the issue, but it may not be a nine issue but a radeonsi llvm issue. The trace has no glitches on llvmpipe. -- You are receiving this mail because: You are

[Bug 105733] Amdgpu randomly hangs and only ssh works. Mouse cursor moves sometimes but does nothing. Keyboard stops working.

2019-01-23 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=105733 --- Comment #59 from dwagner --- I don't think your observations indicate a hardware defect. I have also a reproducible "hysteresis"-effect with regards to my RX460 GPU: When I experience the bug scenario I reported in

[Bug 105733] Amdgpu randomly hangs and only ssh works. Mouse cursor moves sometimes but does nothing. Keyboard stops working.

2019-01-23 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=105733 --- Comment #58 from krutoiles...@gmail.com --- The corruption suggestion is interesting. My RX580 does this and now it won't even boot on windows anymore, just crashes. On Wed, Jan 23, 2019, 12:44 PM l...@protonmail.ch changed bug 105733 >

[Bug 105733] Amdgpu randomly hangs and only ssh works. Mouse cursor moves sometimes but does nothing. Keyboard stops working.

2019-01-23 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=105733 l...@protonmail.ch changed: What|Removed |Added CC||l...@protonmail.ch --- Comment #57

[PATCH] staging: android: ion: Allocate from heap ID directly without mask

2019-01-23 Thread Andrew F. Davis
Previously the heap to allocate from was selected by a mask of allowed heap types. This may have been done as a primitive form of constraint solving, the first heap type that matched any set bit of the heap mask was allocated from, unless that heap was excluded by having its heap ID bit not set in

[Bug 108031] [Regression] amdgpu_device_ip_init failed on Bonaire XT

2019-01-23 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=108031 --- Comment #4 from Alex Deucher --- (In reply to Alex Deucher from comment #3) > Remove amdgpu.dpm=1 from your kernel command line. The default dpm > implementation changed in 4.19. and setting dpm=1 overrides that resulting in different

[Bug 108031] [Regression] amdgpu_device_ip_init failed on Bonaire XT

2019-01-23 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=108031 --- Comment #3 from Alex Deucher --- Remove amdgpu.dpm=1 from your kernel command line. The default dpm implementation changed in 4.19. -- You are receiving this mail because: You are the assignee for the

Re: [PATCH v3 2/4] drm/vc4: Report underrun errors

2019-01-23 Thread Eric Anholt
Paul Kocialkowski writes: > From: Boris Brezillon > > The DRM framework provides a generic way to report underrun errors. > Let's implement the necessary hooks to support it in the VC4 driver. > > Signed-off-by: Boris Brezillon > --- > Changes in v3: > - Generic underrun report function has

Re: [PATCH v3 1/4] drm/vc4: Wait for display list synchronization when completing commit

2019-01-23 Thread Eric Anholt
Paul Kocialkowski writes: > During an atomic commit, the HVS is configured with a display list > for the channel matching the associated CRTC. The Pixel Valve (CRTC) > and encoder are also configured for the new setup at that time. > While the Pixel Valve and encoder are reconfigured

Re: [PATCH v2] xf86drm: Add drmIsMaster()

2019-01-23 Thread Emil Velikov
On Wed, 23 Jan 2019 at 04:39, Christopher James Halse Rogers wrote: > > We can't use drmSetMaster to query whether or not a drm fd is master > because it requires CAP_SYS_ADMIN, even if the fd *is* a master fd. > > Pick DRM_IOCTL_MODE_ATTACHMODE as a long-deprecated ioctl that is > DRM_MASTER but

Re: [PATCH] drm/vkms: Fix flush_work() without INIT_WORK().

2019-01-23 Thread Shayenne Moura
> syzbot is hitting a lockdep warning [1] because flush_work() is called > without INIT_WORK() after kzalloc() at vkms_atomic_crtc_reset(). > > Commit 6c234fe37c57627a ("drm/vkms: Implement CRC debugfs API") added > INIT_WORK() to only vkms_atomic_crtc_duplicate_state() side. Assuming > that

Re: [PATCH 13/14] staging: android: ion: Do not sync CPU cache on map/unmap

2019-01-23 Thread Brian Starkey
Hi Andrew, On Wed, Jan 23, 2019 at 10:51:24AM -0600, Andrew F. Davis wrote: > On 1/22/19 11:33 AM, Sumit Semwal wrote: > > Hello everyone, > > > > Sincere apologies for chiming in a bit late here, but was off due to > > some health issues. > > > > Hope you are feeling better friend :) > >

Re: [PATCH 13/14] staging: android: ion: Do not sync CPU cache on map/unmap

2019-01-23 Thread Andrew F. Davis
On 1/22/19 9:23 PM, Sumit Semwal wrote: > Hello everyone, > > (Thanks to Dan for letting me know my last email got corrupted :/ - > resending it here) > Hmm, this one seems a bit messed up also (Thunderbird doesn't seem to like it at least). [snip] > - from dma-buf PoV, ION is an exporter of

Re: [PATCH] drm: Split out drm_probe_helper.h

2019-01-23 Thread Sam Ravnborg
Hi Daniel. On Thu, Jan 17, 2019 at 10:03:34PM +0100, Daniel Vetter wrote: > Having the probe helper stuff (which pretty much everyone needs) in > the drm_crtc_helper.h file (which atomic drivers should never need) is > confusing. Split them out. > > To make sure I actually achieved the goal here

Re: [PATCH 13/14] staging: android: ion: Do not sync CPU cache on map/unmap

2019-01-23 Thread Andrew F. Davis
On 1/22/19 11:33 AM, Sumit Semwal wrote: > Hello everyone, > > Sincere apologies for chiming in a bit late here, but was off due to > some health issues. > Hope you are feeling better friend :) Looks like this email was a bit broken and you replied again, the responses are a little different

Re: [Intel-wired-lan] [PATCH 1/3] treewide: Lift switch variables out of switches

2019-01-23 Thread Jeff Kirsher
On Wed, 2019-01-23 at 03:03 -0800, Kees Cook wrote: > Variables declared in a switch statement before any case statements > cannot be initialized, so move all instances out of the switches. > After this, future always-initialized stack variables will work > and not throw warnings like this: > >

Re: [PATCH] iommu/intel: quirk to disable DMAR for QM57 igfx

2019-01-23 Thread Joerg Roedel
On Wed, Jan 23, 2019 at 05:02:38PM +0200, Joonas Lahtinen wrote: > We have many reports where just having intel_iommu=on (and using the > system normally, without any virtualization stuff going on) will cause > unexplained GPU hangs. For those users, simply switching to > intel_iommu=igfx_off

Re: [Intel-gfx] [PATCH 14/15] drm/i915/tv: Fix >1024 modes on gen3

2019-01-23 Thread Ville Syrjälä
On Wed, Jan 23, 2019 at 03:49:02PM +0200, Imre Deak wrote: > On Mon, Nov 12, 2018 at 06:59:59PM +0200, Ville Syrjala wrote: > > From: Ville Syrjälä > > > > On gen3 we must disable the TV encoder vertical filter for >1024 > > pixel wide sources. Once that's done all we can is try to center > >

[Bug 108031] [Regression] amdgpu_device_ip_init failed on Bonaire XT

2019-01-23 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=108031 --- Comment #2 from Alexander Schlarb --- Created attachment 143205 --> https://bugs.freedesktop.org/attachment.cgi?id=143205=edit 4.19.0 Debian kernal boot log (external screen working) I can reproduce this with 00:01.0 VGA compatible

[PATCH 3/4] drm/sun4i: dsi: Add burst support

2019-01-23 Thread Maxime Ripard
From: Konstantin Sudakov The current driver doesn't support the DSI burst operation mode. Let's add the needed quirks to make it work. Signed-off-by: Konstantin Sudakov Signed-off-by: Maxime Ripard --- drivers/gpu/drm/sun4i/sun6i_mipi_dsi.c | 178 +++--- 1 file changed,

Re: [Freedreno] [PATCH v4 3/3] drm/msm/dpu: add display port support in DPU

2019-01-23 Thread Sean Paul
On Mon, Dec 17, 2018 at 02:35:05PM -0800, Jeykumar Sankaran wrote: > Add display port support in DPU by creating hooks > for DP encoder enumeration and encoder mode > initialization. > > This change is based on the SDM845 Display port > driver changes[1]. > > changes in v2: > - rebase on [2]

[PATCH 0/4] drm/sun4i: dsi: Add burst mode support

2019-01-23 Thread Maxime Ripard
Hi, Here is a series implementing the burst mode support for DSI. It's been tested on an A33 board with the panel supported on the 4th patch, which should remove all quirks due to a different SoC from the equation. Let me know what you think, Maxime Konstantin Sudakov (2): drm/sun4i: dsi:

[PATCH 4/4] drm/panel: Add Rondo RB070D30 panel

2019-01-23 Thread Maxime Ripard
From: Konstantin Sudakov The Rondo RB070D30 panel is a MIPI-DSI panel based on a Fitipower EK79007 controller and a 1024x600 panel. Signed-off-by: Konstantin Sudakov Signed-off-by: Maxime Ripard --- drivers/gpu/drm/panel/Kconfig| 9 +- drivers/gpu/drm/panel/Makefile

[PATCH 2/4] drm/sun4i: dsi: Change the start delay calculation

2019-01-23 Thread Maxime Ripard
The current calculation for the video start delay in the current DSI driver is that it is the total vertical size, minus the backporch and sync length, plus 1. However, the Allwinner code has it as the active vertical size, plus the back porch and the sync length. This doesn't make any difference

[PATCH 1/4] drm/sun4i: dsi: Restrict DSI tcon clock divider

2019-01-23 Thread Maxime Ripard
The current code allows the TCON clock divider to have a range between 4 and 127 when feeding the DSI controller. The only display supported so far had a display clock rate that ended up using a divider of 4, but testing with other displays show that only 4 seems to be functional. This also

RE: [Intel-gfx] [PATCH 1/3] treewide: Lift switch variables out of switches

2019-01-23 Thread Jani Nikula
On Wed, 23 Jan 2019, Edwin Zimmerman wrote: > On Wed, 23 Jan 2019, Jani Nikula wrote: >> On Wed, 23 Jan 2019, Greg KH wrote: >> > On Wed, Jan 23, 2019 at 03:03:47AM -0800, Kees Cook wrote: >> >> Variables declared in a switch statement before any case statements >> >> cannot be initialized, so

Re: [PATCH] iommu/intel: quirk to disable DMAR for QM57 igfx

2019-01-23 Thread Joonas Lahtinen
Quoting Joerg Roedel (2019-01-22 18:51:35) > On Tue, Jan 22, 2019 at 04:48:26PM +0200, Joonas Lahtinen wrote: > > According to our IOMMU folks there exists some desire to be able to assign > > the iGFX device aka have intel_iommu=on instead of intel_iommu=igfx_off > > due to how the devices might

Re: [PATCHv2 0/7] drm/bridge: tc358767: small fixes

2019-01-23 Thread A H
Hi Tomi, śr., 23 sty 2019, 13:52: Tomi Valkeinen napisał(a): > Hi Andrzej, > > On 09/01/19 12:12, Andrzej Hajda wrote: > > On 09.01.2019 10:51, Lucas Stach wrote: > >> Am Mittwoch, den 09.01.2019, 11:12 +0200 schrieb Tomi Valkeinen: > >>> Hi Andrzej, > >>> > >>> On 09/01/19 10:22, Andrzej Hajda

Re: [Intel-gfx] [PATCH 1/3] treewide: Lift switch variables out of switches

2019-01-23 Thread Jani Nikula
On Wed, 23 Jan 2019, Jani Nikula wrote: > On Wed, 23 Jan 2019, Greg KH wrote: >> On Wed, Jan 23, 2019 at 03:03:47AM -0800, Kees Cook wrote: >>> Variables declared in a switch statement before any case statements >>> cannot be initialized, so move all instances out of the switches. >>> After

Re: [Intel-gfx] [PATCH 1/3] treewide: Lift switch variables out of switches

2019-01-23 Thread Jani Nikula
On Wed, 23 Jan 2019, Greg KH wrote: > On Wed, Jan 23, 2019 at 03:03:47AM -0800, Kees Cook wrote: >> Variables declared in a switch statement before any case statements >> cannot be initialized, so move all instances out of the switches. >> After this, future always-initialized stack variables

Re: [PATCH 2/5] drm/tegra: vic: Load firmware on demand

2019-01-23 Thread Thierry Reding
On Wed, Jan 23, 2019 at 03:47:45PM +0300, Dmitry Osipenko wrote: > 23.01.2019 12:39, Thierry Reding пишет: > > From: Thierry Reding > > > > Loading the firmware requires an allocation of IOVA space to make sure > > that the VIC's Falcon microcontroller can read the firmware if address > >

Re: [PATCH AUTOSEL 4.20 034/117] drm/amdgpu: Correct get_crtc_scanoutpos behavior when vpos >= vtotal

2019-01-23 Thread Sasha Levin
On Wed, Jan 09, 2019 at 10:20:49AM +0100, Michel Dänzer wrote: On 2019-01-08 8:25 p.m., Sasha Levin wrote: From: Nicholas Kazlauskas [ Upstream commit 520f08df45fbe300ed650da786a74093d658b7e1 ] When variable refresh rate is active [...] Variable refresh rate (FreeSync) support is only

Re: [PATCH 4/5] drm/tegra: Restrict IOVA space to DMA mask

2019-01-23 Thread Thierry Reding
On Wed, Jan 23, 2019 at 04:41:44PM +0300, Dmitry Osipenko wrote: > 23.01.2019 12:39, Thierry Reding пишет: > > From: Thierry Reding > > > > On Tegra186 and later, the ARM SMMU provides an input address space that > > is 48 bits wide. However, memory clients can only address up to 40 bits. > > If

Re: [Intel-gfx] [PATCH 15/15] drm/i915/tv: Filter out >1024 wide modes that would need vertical scaling on gen3

2019-01-23 Thread Imre Deak
On Mon, Nov 12, 2018 at 07:00:00PM +0200, Ville Syrjala wrote: > From: Ville Syrjälä > > Since gen3 can't handle >1024 wide sources with vertical scaling > let's not advertize such modes in the mode list. Less tempetation > to the user to try out things that won't work. > > Signed-off-by: Ville

Re: [Intel-gfx] [PATCH 14/15] drm/i915/tv: Fix >1024 modes on gen3

2019-01-23 Thread Imre Deak
On Mon, Nov 12, 2018 at 06:59:59PM +0200, Ville Syrjala wrote: > From: Ville Syrjälä > > On gen3 we must disable the TV encoder vertical filter for >1024 > pixel wide sources. Once that's done all we can is try to center > the image on the screen. Naturally the TV mode vertical resolution > must

[PATCH] drm/tegra: vic: Do not clear driver data

2019-01-23 Thread Thierry Reding
From: Thierry Reding Upon driver failure, the driver core will take care of clearing the driver data, so there's no need to do so explicitly in the driver. Signed-off-by: Thierry Reding --- drivers/gpu/drm/tegra/vic.c | 1 - 1 file changed, 1 deletion(-) diff --git

Re: [PATCH 4/4] drm/imx: only send commit done event when all state has been applied

2019-01-23 Thread Daniel Vetter
On Wed, Jan 23, 2019 at 12:35:02PM +0100, Philipp Zabel wrote: > On Fri, 2018-10-05 at 17:11 +0200, Philipp Zabel wrote: > > On Fri, 2018-09-14 at 18:59 +0200, Lucas Stach wrote: > > > Currently there is a small race window where we could manage to arm the > > > vblank event from atomic flush, but

Re: [PATCHv2 0/7] drm/bridge: tc358767: small fixes

2019-01-23 Thread Tomi Valkeinen
Hi Andrzej, On 09/01/19 12:12, Andrzej Hajda wrote: > On 09.01.2019 10:51, Lucas Stach wrote: >> Am Mittwoch, den 09.01.2019, 11:12 +0200 schrieb Tomi Valkeinen: >>> Hi Andrzej, >>> >>> On 09/01/19 10:22, Andrzej Hajda wrote: Hi Tomi, On 03.01.2019 12:59, Tomi Valkeinen wrote:

Re: [PATCH 1/3] treewide: Lift switch variables out of switches

2019-01-23 Thread Greg KH
On Wed, Jan 23, 2019 at 03:03:47AM -0800, Kees Cook wrote: > Variables declared in a switch statement before any case statements > cannot be initialized, so move all instances out of the switches. > After this, future always-initialized stack variables will work > and not throw warnings like this:

Re: [PATCH 4/4] drm/imx: only send commit done event when all state has been applied

2019-01-23 Thread Philipp Zabel
On Fri, 2018-10-05 at 17:11 +0200, Philipp Zabel wrote: > On Fri, 2018-09-14 at 18:59 +0200, Lucas Stach wrote: > > Currently there is a small race window where we could manage to arm the > > vblank event from atomic flush, but programming the hardware was too close > > to the frame end, so the

[PATCH] gpu: host1x: Represent host1x bus devices in debugfs

2019-01-23 Thread Thierry Reding
From: Thierry Reding This new debugfs file represents the state of host1x bus devices, specifying the list of subdevices and marking which ones have successfully registered. Signed-off-by: Thierry Reding --- drivers/gpu/host1x/bus.c | 35 +++ 1 file changed, 35

Re: [PATCH libdrm 1/2] xf86drm: fallback to MODALIAS for OF less platform devices

2019-01-23 Thread Emil Velikov
On Wed, 23 Jan 2019 at 11:04, Eric Engestrom wrote: > > On Wednesday, 2019-01-23 10:45:17 +, Emil Velikov wrote: > > From: Emil Velikov > > > > Some devices can lack OF data or it may not be available in the uevent > > file. Fallback to the MODALIAS data in those cases. > > > > We strip any

[Bug 201795] [Regression] Wrong 4k resolution detected with DisplayPort to HDMI adapter on amdgpu

2019-01-23 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=201795 tempel.jul...@gmail.com changed: What|Removed |Added CC||tempel.jul...@gmail.com ---

[v1] drm/msm: Remove clock and bandwidth votes in mdss pm suspend

2019-01-23 Thread Jayant Shekhar
MDSS PM suspend is dependent on runtime suspend for disabling clocks and removing bandwidth votes. In case of pm_suspend triggered, dpm_prepare hold a refcount on power usage of device and hence runtime suspend is never triggered during pm_suspend. As runtime suspend is not triggered, clocks and

Re: [PATCH] video/fbdev: refactor video= cmdline parsing

2019-01-23 Thread Jani Nikula
On Wed, 23 Jan 2019, Daniel Vetter wrote: > On Wed, Jan 23, 2019 at 11:38:17AM +0200, Jani Nikula wrote: >> Make the video_setup() function slightly easier to read by removing the >> repeated checks for !global. Remove the misleading return value comment >> while at it. >> >> I'm slightly

Re: [PATCH libdrm 1/2] xf86drm: fallback to MODALIAS for OF less platform devices

2019-01-23 Thread Eric Engestrom
On Wednesday, 2019-01-23 10:45:17 +, Emil Velikov wrote: > From: Emil Velikov > > Some devices can lack OF data or it may not be available in the uevent > file. Fallback to the MODALIAS data in those cases. > > We strip any leading "MODALIAS=.*:" thus the resulting information is >

[PULL] drm-misc-next

2019-01-23 Thread Maxime Ripard
Hi Dave, Daniel, Here is the PR for drm-misc-next for this week. Let me know if there's anything wrong. Thanks! Maxime drm-misc-next-2019-01-23: drm-misc-next for 5.1: UAPI Changes: - Addition of the Allwinner tiled format modifier Cross-subsystem Changes: Core Changes: - dma-buf

Re: [PATCH v2] xf86drm: Add drmIsMaster()

2019-01-23 Thread Daniel Vetter
On Wed, Jan 23, 2019 at 03:38:45PM +1100, Christopher James Halse Rogers wrote: > We can't use drmSetMaster to query whether or not a drm fd is master > because it requires CAP_SYS_ADMIN, even if the fd *is* a master fd. > > Pick DRM_IOCTL_MODE_ATTACHMODE as a long-deprecated ioctl that is >

Re: [PATCH] video/fbdev: refactor video= cmdline parsing

2019-01-23 Thread Daniel Vetter
On Wed, Jan 23, 2019 at 11:38:17AM +0200, Jani Nikula wrote: > Make the video_setup() function slightly easier to read by removing the > repeated checks for !global. Remove the misleading return value comment > while at it. > > I'm slightly hesitant to change any of this, but here goes anyway,

Re: [PATCH] drm/modes: Prevent division by zero htotal

2019-01-23 Thread Daniel Vetter
On Wed, Jan 23, 2019 at 03:28:59PM +0800, Tina Zhang wrote: > This patch prevents division by zero htotal. How did you manage to get here with htotal == 0? This needs backtraces (or if this is just about static checkers, a mention of that). -Daniel > > Signed-off-by: Tina Zhang > Cc: Adam

Re: [PATCH 01/11] drm: Add devm_drm_dev_init/register

2019-01-23 Thread Noralf Trønnes
Den 22.01.2019 20.30, skrev Daniel Vetter: > On Tue, Jan 22, 2019 at 8:07 PM Noralf Trønnes wrote: >> >> >> >> Den 22.01.2019 10.32, skrev Daniel Vetter: >>> On Mon, Jan 21, 2019 at 01:21:46PM +0100, Noralf Trønnes wrote: Den 21.01.2019 10.55, skrev Daniel Vetter: > On Mon,

Re: [igt-dev] [PATCH] drm/doc: Make igts for cross-driver stuff mandatory

2019-01-23 Thread Daniel Vetter
On Wed, Jan 23, 2019 at 12:03:40PM +0200, Jani Nikula wrote: > On Tue, 22 Jan 2019, "Wentland, Harry" wrote: > > Would it make sense to append something like ", if such a test can be > > reasonably made using IGT for the target HW." to make it clear to > > contributors that in cases like the one

Re: [igt-dev] [PATCH] drm/doc: Make igts for cross-driver stuff mandatory

2019-01-23 Thread Daniel Vetter
On Wed, Jan 23, 2019 at 12:11:36PM +0200, Jani Nikula wrote: > On Wed, 23 Jan 2019, Daniel Stone wrote: > > If it helps, maybe we could draw up a list somewhere (README in igt? > > wiki?) of which tests seem to pass generically across a few drivers, > > which ones are expected to pass, which ones

Re: [igt-dev] [PATCH] drm/doc: Make igts for cross-driver stuff mandatory

2019-01-23 Thread Daniel Vetter
On Wed, Jan 23, 2019 at 09:40:34AM +, Brian Starkey wrote: > On Tue, Jan 22, 2019 at 08:19:10PM +0100, Daniel Vetter wrote: > > On Tue, Jan 22, 2019 at 8:00 PM Wentland, Harry > > wrote: > > > On 2019-01-16 11:39 a.m., Daniel Vetter wrote: > > > > Compared to the RFC[1] no changes to the

[PATCH libdrm 2/2] xf85drm: de-duplicate drmParse{Platform.Host1x}{Bus, Device}Info

2019-01-23 Thread Emil Velikov
From: Emil Velikov The functions are virtually identical, fold them up. Signed-off-by: Emil Velikov --- xf86drm.c | 98 +-- 1 file changed, 15 insertions(+), 83 deletions(-) diff --git a/xf86drm.c b/xf86drm.c index 374734eb..18c9693a 100644

[PATCH libdrm 1/2] xf86drm: fallback to MODALIAS for OF less platform devices

2019-01-23 Thread Emil Velikov
From: Emil Velikov Some devices can lack OF data or it may not be available in the uevent file. Fallback to the MODALIAS data in those cases. We strip any leading "MODALIAS=.*:" thus the resulting information is compatible with existing code in Mesa. Signed-off-by: Emil Velikov --- xf86drm.c

Re: [PATCH] gpu: ipu-v3: pre: don't trigger update if buffer address doesn't change

2019-01-23 Thread Philipp Zabel
On Mon, 2019-01-07 at 12:58 +0100, Lucas Stach wrote: > Am Freitag, den 21.12.2018, 12:11 +0100 schrieb Philipp Zabel: > > Hi Lucas, > > > > > On Wed, Dec 19, 2018 at 4:40 PM Lucas Stach > > > wrote: > > > > > > On a NOP double buffer update where current buffer address is the same > > > as

Re: [PATCH 13/15] drm/i915/tv: Generate better pipe timings for TV encoder

2019-01-23 Thread Imre Deak
On Tue, Jan 22, 2019 at 07:34:55PM +0200, Ville Syrjälä wrote: > On Tue, Jan 22, 2019 at 07:22:24PM +0200, Imre Deak wrote: > > On Mon, Nov 12, 2018 at 06:59:58PM +0200, Ville Syrjala wrote: > > > From: Ville Syrjälä > > > > > > To make vblank timestamps work better with the TV encoder let's > >

[PATCH] drm/rockchip: rgb: update SPDX license identifier

2019-01-23 Thread Sandy Huang
update SPDX License Identifier from GPL-2.0+ to GPL-2.0 and drop some GPL text. Signed-off-by: Sandy Huang --- drivers/gpu/drm/rockchip/rockchip_rgb.c | 11 +-- drivers/gpu/drm/rockchip/rockchip_rgb.h | 11 +-- 2 files changed, 2 insertions(+), 20 deletions(-) diff --git

Re: [igt-dev] [PATCH] drm/doc: Make igts for cross-driver stuff mandatory

2019-01-23 Thread Jani Nikula
On Wed, 23 Jan 2019, Daniel Stone wrote: > If it helps, maybe we could draw up a list somewhere (README in igt? > wiki?) of which tests seem to pass generically across a few drivers, > which ones are expected to pass, which ones don't but really should, > etc. I'm currently running on imx-drm

Re: [igt-dev] [PATCH] drm/doc: Make igts for cross-driver stuff mandatory

2019-01-23 Thread Daniel Stone
Hi, On Tue, 22 Jan 2019 at 19:42, Wentland, Harry wrote: > On 2019-01-22 2:19 p.m., Daniel Vetter wrote: > > I'd say we'll shrug these cases off as "can't be reasonable tested, > > won't have an igt". First driver team with hw that can be validated > > gets to fill the gaps :-) In practice still

Re: [igt-dev] [PATCH] drm/doc: Make igts for cross-driver stuff mandatory

2019-01-23 Thread Jani Nikula
On Tue, 22 Jan 2019, "Wentland, Harry" wrote: > Would it make sense to append something like ", if such a test can be > reasonably made using IGT for the target HW." to make it clear to > contributors that in cases like the one discussed this is at the > reviewers discretion? I think the

  1   2   >