On Tue, Jun 27, 2017 at 7:59 AM, Daniel Vetter wrote:
>
> Thanks to Liviu's help I realized that I fumbled the locking rework
> completely.
> This one here should be better, but somehow I'm having a real bad day today
> and
> I spent all day typing shit code, and then making it worse.
>
> This h
https://bugs.freedesktop.org/show_bug.cgi?id=101594
--- Comment #2 from Luke A. Guest ---
Number of platforms 1
Platform Name Clover
Platform Vendor Mesa
Platform Version
https://bugs.freedesktop.org/show_bug.cgi?id=101561
Nick Sarnie changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://bugs.freedesktop.org/show_bug.cgi?id=101584
--- Comment #1 from Christoph Haag ---
Created attachment 132290
--> https://bugs.freedesktop.org/attachment.cgi?id=132290&action=edit
without X
Thanks to a tip from tom stellard I tried it without X (after exiting sddm).
I've tried to star
When the AMDGPU_GEM_CREATE_CPU_ACCESS_REQUIRED flag is given by userspace,
it should only be treated as a hint to initially place a BO somewhere CPU
accessible, rather than having a permanent effect on BO placement.
Instead of the flag being set in stone at BO creation, set the flag when a
page fa
Allow specifying a limit on visible VRAM via a module parameter. This is
helpful for testing performance under visible VRAM pressure.
v2: Add cast to 64-bit (Christian König)
Signed-off-by: John Brooks
Reviewed-by: Michel Dänzer
Reviewed-by: Christian König
---
drivers/gpu/drm/amd/amdgpu/amdg
Changes in this version:
- Dropped former patch 1 ("Separate placements and busy placements") as it was
no longer necessary
- Dropped former patch 4 ("Don't force BOs into visible VRAM if they can go to
GTT instead") as it was unnecessary and had too many side effects (Thanks
Christian)
- Dro
The BO move throttling code is designed to allow VRAM to fill quickly if it
is relatively empty. However, this does not take into account situations
where the visible VRAM is smaller than total VRAM, and total VRAM may not
be close to full but the visible VRAM segment is under pressure. In such
sit
There is no need for page faults to force BOs into visible VRAM if it's
full, and the time it takes to do so is great enough to cause noticeable
stuttering. Add GTT as a possible placement so that if visible VRAM is
full, page faults move BOs to GTT instead of evicting other BOs from VRAM.
Signed-
Signed-off-by: John Brooks
---
drivers/gpu/drm/amd/amdgpu/amdgpu.h| 3 +++
drivers/gpu/drm/amd/amdgpu/amdgpu_cs.c | 5 +
drivers/gpu/drm/amd/amdgpu/amdgpu_object.c | 2 ++
3 files changed, 10 insertions(+)
diff --git a/drivers/gpu/drm/amd/amdgpu/amdgpu.h
b/drivers/gpu/drm/amd/am
On 06/19/2017 09:58 PM, Philippe CORNU wrote:
Add the panel-bridge support for both panels & bridges (used by DSI host &
HDMI/LVDS bridges).
Reviewed-by: Archit Taneja
Signed-off-by: Philippe CORNU
---
drivers/gpu/drm/stm/Kconfig | 2 +-
drivers/gpu/drm/stm/ltdc.c | 211 ---
Hi Jean-Francois,
As you noted, the Xilinx DRM driver in Xilinx tree is missing many mainline
features including the atomic mode setting and needs some restructuring. Please
feel free to send patches to Xilinx git-dev, but note that we are also
developing / cleaning up the driver internally at
On Tue, Jun 27, 2017 at 10:51 PM, Jeff Kirsher
wrote:
> This was submitted and accepted into David Miller's net-next tree. I can
> see if Dave can pull it into his net tree. DOes stable need to pick this
> up as well?
Nah if it landed somewhere at least I'm happy, we can carry the fixup
for a w
On 06/19/2017 09:58 PM, Philippe CORNU wrote:
Add a Synopsys Designware MIPI DSI host DRM bridge driver, based on the
Rockchip version from rockchip/dw-mipi-dsi.c with phy & bridge APIs.
Signed-off-by: Philippe CORNU
---
drivers/gpu/drm/bridge/synopsys/Kconfig | 6 +
drivers/gpu/dr
On Wed, Jun 28, 2017 at 12:16:20AM +0300, Laurent Pinchart wrote:
> The old state is useful for drivers that need to perform operations at
> enable time that depend on the transition between the old and new
> states.
>
> While at it, rename the operation to .atomic_enable() to be consistent
> with
On Wed, Jun 28, 2017 at 12:16:21AM +0300, Laurent Pinchart wrote:
> The CRTC .disable() helper operation is deprecated for atomic drivers,
> the new .atomic_disable() helper operation being preferred. Convert all
> atomic drivers to .atomic_disable() to avoid cargo-cult use of
> .disable() in new d
On 06/19/2017 09:58 PM, Philippe CORNU wrote:
Add the STM32 DSI host driver that uses the Synopsys DesignWare
MIPI DSI DRM bridge.
Signed-off-by: Philippe CORNU
Reviewed-by: Neil Armstrong
Reviewed-by: Archit Taneja
---
drivers/gpu/drm/stm/Kconfig | 7 +
drivers/gpu/drm/s
101 - 117 of 117 matches
Mail list logo