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, Ja

[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 asso

[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 p

[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 Cc:

[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 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: And

[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 p

[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: And

[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: And

[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: And

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

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 m

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 th

[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:

[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||e.singularity

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

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 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. > > H

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 1

[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 interconne

[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 v

[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 of

[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)

[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&action=edit Renderdoc capture under DXVK -- You are receiving this mail because: You are the assignee for the bug._

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 > --- > drivers/gpu/drm/

[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, http://www.assignmenth

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 > > Su

[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

<    1   2