From: Sean Paul
__mmap2 isn't supported on all platforms, mmap64 is the right way
to do this in android.
Also folds in a fix from Stéphane Marchesin
to use an offset in bytes not pages, as that's what mmap64 takes.
Cc: Emil Velikov
Cc: Sean Paul
Cc: Alistair Strachan
Cc: Marissa Wall
Clang complains when initializing unions using "= {0}"
so instead use memset.
Cc: Emil Velikov
Cc: Sean Paul
Cc: Alistair Strachan
Cc: Marissa Wall
Signed-off-by: John Stultz
---
amdgpu/amdgpu_cs.c | 9 ++---
1 file changed, 6 insertions(+), 3 deletions(-)
diff --git
From: Hemant Hariyani
Allows mmap on dmabuf fd with MAP_SHARED and PROT_WRITE.
This fixes boot failures caused due to mmap() returning error
Cc: Emil Velikov
Cc: Sean Paul
Cc: Alistair Strachan
Cc: Marissa Wall
Signed-off-by: Hemant Hariyani
[picked and updated commitmsg from
Over the last few days I've been trying to sync the AOSP libdrm
tree with the upstream freedesktop branch.
Thanks to input from Sean, Alistair and Marissa, we've managed
to drop a bunch of stale patches AOSP was carrying, and get
the AOSP libdrm updated to 2.4.97
I've gone through the remaining
From: Adrian Salido
When calling drmModeAtomicAddProperty allocation of memory happens as
needed in increments of 16 elements. This can be very slow if there are
multiple properties to be updated in an Atomic Commit call.
Increase this to as many as can fit in a memory PAGE to avoid having to
From: Prabhanjan Kandula
Avoid additional drm device open and close.
Cc: Emil Velikov
Cc: Sean Paul
Cc: Alistair Strachan
Cc: Marissa Wall
Signed-off-by: John Stultz
---
xf86drm.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/xf86drm.c b/xf86drm.c
index
https://bugs.freedesktop.org/show_bug.cgi?id=110443
--- Comment #5 from Marek Olšák ---
Yes. It can be just 1 function returning both values and it doesn't have to
return boolean.
--
You are receiving this mail because:
You are the assignee for the
On Thu, 18 Apr 2019 09:42:23 -0300
Mauro Carvalho Chehab wrote:
> After thinking a little bit and doing some tests, I think a good solution
> would be to add ":orphan:" markup to the new .rst files that were not
> added yet into the main body (e. g. something like the enclosed example).
Quoting Peter Griffin (2019-04-19 01:32:59)
> This is required to bring Mali450 gpu out of reset. Also
> we now use CLK_OF_DECLARE_DRIVER to probe in both the
> clock and reset drivers. The clock and reset parts have
> been done as one atomic commit to avoid a bisection hole.
>
> Signed-off-by:
On Thu, 18 Apr 2019 10:41:42 +0200
Thomas Gleixner wrote:
> Replace the indirection through struct stack_trace by using the storage
> array based interfaces.
>
> Signed-off-by: Thomas Gleixner
> Cc: Steven Rostedt
Reviewed-by: Steven Rostedt (VMware)
-- Steve
On Thu, 18 Apr 2019 10:41:43 +0200
Thomas Gleixner wrote:
> Simplify the stack retrieval code by using the storage array based
> interface.
>
> Signed-off-by: Thomas Gleixner
Reviewed-by: Steven Rostedt (VMware)
-- Steve
___
dri-devel mailing
To all X.Org Foundation Members:
The round 2 of X.Org Foundation's annual election is now open and will remain
open until 23:59 UTC on 2 May 2019.
Four of the eight director seats are open during this election, with the four
nominees receiving the highest vote totals serving as directors for
Fixes: 5c4923919f01 ("drm/ttm: fix re-init of global structures")
Signed-off-by: kbuild test robot
---
ttm_bo.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/gpu/drm/ttm/ttm_bo.c b/drivers/gpu/drm/ttm/ttm_bo.c
index 2845fce..a7bb5a2 100644
---
tree: git://people.freedesktop.org/~agd5f/linux.git drm-next-5.2-wip
head: a70be09f90c0b211b45bae50eb98617d75713297
commit: 5c4923919f015e80e76d3d88d5743d422d105ff2 [64/66] drm/ttm: fix re-init
of global structures
reproduce:
# apt-get install sparse
git checkout
Add documentation for the interconnect and interconnect-names bindings
for the GPU node as detailed by bindings/interconnect/interconnect.txt.
Signed-off-by: Jordan Crouse
Reviewed-by: Douglas Anderson
Reviewed-by: Rob Herring
Acked-by: Georgi Djakov
---
v4: Fix spelling nits per Georgi
Describe the zap-shader node that defines a reserved memory region
to store the zap shader.
Signed-off-by: Jordan Crouse
---
Documentation/devicetree/bindings/display/msm/gpu.txt | 7 +++
1 file changed, 7 insertions(+)
diff --git a/Documentation/devicetree/bindings/display/msm/gpu.txt
https://bugs.freedesktop.org/show_bug.cgi?id=108521
--- Comment #50 from Dimitar Atanasov ---
There is two windows on this system. Small one below 4GB which is 2.5GB and
bigger one over 4GB which is 64GB. Address space for thunderbolt is only 200
MB. As I know AMDGPU needs 250 MB in low 4GB and
The a6xx GPU powers on in secure mode which restricts what memory it can
write to. To get out of secure mode the GPU driver can write to
REG_A6XX_RBBM_SECVID_TRUST_CNTL but on targets that are "secure" that
register region is blocked and writes will cause the system to go down.
For those targets
a5xx and a6xx both share (mostly) the same code to load the zap shader and
bring the GPU out of secure mode. Move the formerly 5xx specific code to
adreno to make it available for a6xx too.
Signed-off-by: Jordan Crouse
---
drivers/gpu/drm/msm/adreno/a5xx_gpu.c | 111
This patch series adds support for loading the zap shader on a6xx and using it
to get the GPU out of secure mode.
The Adreno a5xx and a6xx GPUs boot in "secure" mode which restricts the memory
the GPU is allowed to use. To get the GPU out of secure mode we need to write
to a register. However
On Thu, Apr 18, 2019 at 8:09 AM Christian König
wrote:
>
> We should be able to do this now after checking all the prerequisites.
>
> v2: fix entrie count in the sgt
>
> Signed-off-by: Christian König
Series is:
Reviewed-by: Alex Deucher
> ---
> drivers/gpu/drm/amd/amdgpu/amdgpu_prime.c|
On Tue, Apr 16, 2019 at 2:39 PM Christian König
wrote:
>
> Add optional explicit pinning callbacks instead of implicitly assume the
> exporter pins the buffer when a mapping is created.
>
> Signed-off-by: Christian König
> ---
> drivers/dma-buf/dma-buf.c | 39
Den 18.04.2019 18.59, skrev Noralf Trønnes:
>
>
> Den 18.04.2019 14.41, skrev Maxime Ripard:
>> Now that the TV margins are properly parsed and filled into
>> drm_cmdline_mode, we just need to initialise the first state at reset to
>> get those values and start using them.
>>
>> Signed-off-by:
On Tue, Apr 16, 2019 at 06:30:25PM -0700, Rob Clark wrote:
> From: Rob Clark
>
> For KHR_robustness, userspace wants to know two things, the count of GPU
> faults globally, and the count of faults attributed to a given context.
> This patch providees the former, and the next patch provides the
On Tue, Apr 16, 2019 at 06:30:24PM -0700, Rob Clark wrote:
> From: Rob Clark
>
> For now it always returns '0' (false), but once the iommu work is in
> place to enable per-process pagetables we can update the value returned.
>
> Userspace needs to know this to make an informed decision about
sync_dump() is an unused, unexported, function that adds 64k to the
kernel image and doesn't even provide locking around the global array it
uses.
add/remove: 0/2 grow/shrink: 0/0 up/down: 0/-65734 (-65734)
Function old new delta
sync_dump
From: Da Lv
The original HiKey (620) board has had a long running issue
where when using a 1080p montior, the display would occasionally
blink and come come back with a horizontal offset (usually also
shifting the colors, depending on the value of the offset%4).
After lots of analysis by HiSi
https://bugs.freedesktop.org/show_bug.cgi?id=110371
--- Comment #6 from babblebo...@gmail.com ---
Will do. Just switched my distro to Gentoo, specifically so I can stay on
kernel 4.18 for as long as necessary to combat the issue and apply a patch when
ready, and cleared all of the cruft out of
It seems this got missed, If no one has any objection I will submit the
patches via drm-mics route.
Deepak
On Tue, 2019-04-09 at 12:49 -0700, Deepak Singh Rawat wrote:
> Hi Daniel/Dave,
>
> The vmwgfx-next changes for 5.2:
> Resource dirtying improvement by Thomas,
> user-space error logging
On Thu, Apr 18, 2019 at 8:09 AM Christian König
wrote:
>
> A lot of root complexes can still do P2P even when PCI devices
> don't share a common upstream bridge.
>
> Start adding a whitelist and allow P2P if both participants are
> attached to known good root complex.
>
> Signed-off-by: Christian
Hi,
On Fri, 2019-04-19 at 09:02 -0700, Chen-Yu Tsai wrote:
> On Fri, Apr 19, 2019 at 1:03 AM Paul Kocialkowski
> wrote:
> > Our components may still be using the DRM device driver (if only to
> > access our driver's private data), so make sure to unbind them before
> > the final drm_dev_put.
> >
On Fri, Apr 19, 2019 at 9:21 AM Emil Velikov wrote:
>
> On Fri, 19 Apr 2019 at 16:57, Marc-André Lureau
> wrote:
> >
> > This patch does more harm than good, as it breaks both Xwayland and
> > gnome-shell with X11.
> >
> > Xwayland requires DRI3 & DRI3 requires PRIME.
> >
> > X11 crash for
On Fri, 19 Apr 2019 at 16:57, Marc-André Lureau
wrote:
>
> This patch does more harm than good, as it breaks both Xwayland and
> gnome-shell with X11.
>
> Xwayland requires DRI3 & DRI3 requires PRIME.
>
> X11 crash for obscure double-free reason which are hard to debug
> (starting X11 by hand
On Fri, Apr 19, 2019 at 11:07:17AM +0200, Peter Zijlstra wrote:
> On Fri, Apr 19, 2019 at 10:32:30AM +0200, Thomas Gleixner wrote:
> > On Fri, 19 Apr 2019, Peter Zijlstra wrote:
> > > On Thu, Apr 18, 2019 at 10:41:47AM +0200, Thomas Gleixner wrote:
> > >
> > > > +typedef bool
This release adds marketing names for AMDGPU devices, a fallback path in
drmDevice for devices lacking OF data and drmIsMaster API, amongst other
changes.
-Emil
Alex Deucher (3):
amdgpu: add some raven marketing names
amdgpu: add marketing name for AMD Radeon VII
amdgpu:
On Fri, Apr 19, 2019 at 1:03 AM Paul Kocialkowski
wrote:
>
> Our components may still be using the DRM device driver (if only to
> access our driver's private data), so make sure to unbind them before
> the final drm_dev_put.
>
> Also release our resserved memory adter unbind to match reverse
This patch does more harm than good, as it breaks both Xwayland and
gnome-shell with X11.
Xwayland requires DRI3 & DRI3 requires PRIME.
X11 crash for obscure double-free reason which are hard to debug
(starting X11 by hand doesn't trigger the crash).
I don't see an apparent problem implementing
On Fri, Apr 19, 2019 at 09:02:11AM +0200, Peter Zijlstra wrote:
> On Thu, Apr 18, 2019 at 05:42:55PM +0200, Thomas Gleixner wrote:
> > On Thu, 18 Apr 2019, Josh Poimboeuf wrote:
>
> > > Another idea I had (but never got a chance to work on) was to extend the
> > > x86 unwind interface to all
On Thu, Apr 18, 2019 at 1:58 PM Mukesh Ojha wrote:
>
>
> On 4/18/2019 3:55 PM, Colin King wrote:
> > From: Colin Ian King
> >
> > There is a spelling mistake in a pr_err message. Fix it.
> >
> > Signed-off-by: Colin Ian King
> Reviewed-by: Mukesh Ojha
Applied. thanks!
Alex
>
> Cheers,
>
On Wed, Apr 17, 2019 at 3:04 AM Mukesh Ojha wrote:
>
>
> On 4/16/2019 5:29 PM, Colin King wrote:
> > From: Colin Ian King
> >
> > There is a spelling mistake in a DRM_INFO message. Fix it.
> >
> > Signed-off-by: Colin Ian King
> Reviewed-by: Mukesh Ojha
Applied. thanks!
Alex
>
> Cheers,
>
Hi Dave, Daniel,
More updates for 5.2:
- Add the amdgpu specific bits for timeline support
- Add internal interfaces for xgmi pstate support
- DC Z ordering fixes for planes
- Add support for NV12 planes in DC
- Add colorspace properties for planes in DC
- eDP optimizations if the GOP driver
https://bugs.freedesktop.org/show_bug.cgi?id=108917
--- Comment #11 from tempel.jul...@gmail.com ---
Is it realistic that the maintainers and firms in charge might manage an effort
to solve this matter across vendors this year?
I unfortunately always notice the performance issue by simply
On Thu, 18 Apr 2019 10:41:41 +0200
Thomas Gleixner wrote:
> It's only used in trace.c and there is absolutely no point in compiling it
> in when user space stack traces are not supported.
>
> Signed-off-by: Thomas Gleixner
> Cc: Steven Rostedt
Funny, these were moved out to global functions
Looks good for me, patch is:
Reviewed-by: Qiang Yu
I'll push this patch to drm-misc-next.
Regards,
Qiang
On Fri, Apr 19, 2019 at 4:35 PM Peter Griffin wrote:
>
> On Hikey board all lima ip blocks are shared with one irq.
> This patch avoids a NULL ptr deref crash on this platform
> on
Which test are you using? Can share?
-David
> -Original Message-
> From: dri-devel On Behalf Of
> Christian K?nig
> Sent: Thursday, April 18, 2019 8:09 PM
> To: dri-devel@lists.freedesktop.org; amd-...@lists.freedesktop.org
> Subject: DMA-buf P2P
>
> Hi guys,
>
> as promised this is
https://bugs.freedesktop.org/show_bug.cgi?id=110214
--- Comment #83 from Michel Dänzer ---
(In reply to Diego Viola from comment #82)
> I found that I can't reproduce this bug with Xephyr -glamor_gles2 (git) but
> it still happens with -glamor.
Presumably the GL_NV_texture_barrier extension
On Fri, Apr 19, 2019 at 10:32:30AM +0200, Thomas Gleixner wrote:
> On Fri, 19 Apr 2019, Peter Zijlstra wrote:
> > On Thu, Apr 18, 2019 at 10:41:47AM +0200, Thomas Gleixner wrote:
> >
> > > +typedef bool (*stack_trace_consume_fn)(void *cookie, unsigned long addr,
> > > +
Hi,
On Thu, 2019-04-18 at 13:40 +1000, Dave Airlie wrote:
> Since Easter is looming for me, I'm just pushing whatever is in my
> tree, I'll see what else turns up and maybe I'll send another pull
> early next week if there is anything.
Note that I submitted some drm/sun4i fixes which looked
Den 18.04.2019 18.50, skrev Noralf Trønnes:
>
>
> Den 18.04.2019 14.41, skrev Maxime Ripard:
>> Properly configuring the overscan properties might be needed for the
>> initial setup of the framebuffer for display that still have overscan.
>> Let's allow for more properties on the kernel
Den 18.04.2019 18.40, skrev Noralf Trønnes:
>
>
> Den 18.04.2019 14.41, skrev Maxime Ripard:
>> Rotations and reflections setup are needed in some scenarios to initialise
>> properly the initial framebuffer. Some drivers already had a bunch of
>> quirks to deal with this, such as either a
Hi,
On Thu, 2019-04-18 at 17:10 -0700, Eric Anholt wrote:
> We were setting the wrong flags to enable PTI errors, so we were
> seeing reads to invalid PTEs show up as write errors. Also, we
> weren't turning on the interrupts. The AXI IDs we were dumping
> included the outstanding write number
Hi,
On Thu, 2019-04-18 at 17:10 -0700, Eric Anholt wrote:
> Looking at a hang recently, I noticed these registers that might tell
> me if something obvious was wrong. They didn't help in this case, but
> keep it around for the future.
Although I don't have docs to check, looks sane:
Hi,
On Thu, 2019-04-18 at 17:10 -0700, Eric Anholt wrote:
> On 7278, we've got 40 bits to work with.
Although I don't have docs to check, looks sane:
Reviewed-by: Paul Kocialkowski
Cheers,
Paul
> Signed-off-by: Eric Anholt
> ---
> drivers/gpu/drm/v3d/v3d_debugfs.c | 1 +
>
Hi,
On Thu, 2019-04-18 at 17:10 -0700, Eric Anholt wrote:
> They're in the hub, not the individual cores.
Although I don't have docs to check, looks sane:
Reviewed-by: Paul Kocialkowski
Cheers,
Paul
> Signed-off-by: Eric Anholt
> ---
> drivers/gpu/drm/v3d/v3d_debugfs.c | 7 ---
> 1
Hi,
On Thu, 2019-04-18 at 20:30 -0400, Nicolas Dufresne wrote:
> Le jeudi 18 avril 2019 à 10:18 +0200, Daniel Vetter a écrit :
> > > It would be cool if both could be used concurrently and not just return
> > > -EBUSY when the device is used with the other subsystem.
> >
> > We live in this
https://bugs.freedesktop.org/show_bug.cgi?id=46711
--- Comment #25 from FiNeX ---
Same problem here.
I'm using latest Linux Kernel (5.0.7) on Arch Linux, with Nvidia drivers
418.56-7, Xorg 1.20.4.
Hardware:
- GPU: NVIDIA GK106 [GeForce GTX 660]
- Mobo: Asus Z87-PRO
- Display: 2x Acer BE270U
Our components may still be using the DRM device driver (if only to
access our driver's private data), so make sure to unbind them before
the final drm_dev_put.
Also release our resserved memory adter unbind to match reverse
creation order.
Fixes: f5a9ed867c83 ("drm/sun4i: Fix component
Hi,
This serie aims at adding the support for rotation on Komeda driver.
This patch series depends on:
- https://patchwork.freedesktop.org/series/54449/
- https://patchwork.freedesktop.org/series/54450/
- https://patchwork.freedesktop.org/series/58710/
-
Komeda series hardware doesn't support Rot90 for AFBC wide block. So
add limitation check to reject it if such configuration has been posted.
Signed-off-by: Lowry Li (Arm Technology China)
---
drivers/gpu/drm/arm/display/komeda/d71/d71_dev.c | 15 +++
- Adds rotation property to plane.
- Komeda display rotation support diverges from the specific formats,
so need to check the user required rotation type with the format caps
and reject the commit if it can not be supported.
- In the layer validate flow, sets the rotation value to the layer
state.
Hi, Jitao:
On Tue, 2019-04-16 at 16:54 +0800, Jitao Shi wrote:
> Add dsi and mipitx nodes to the mt8183
>
> Signed-off-by: Jitao Shi
> ---
> arch/arm64/boot/dts/mediatek/mt8183.dtsi | 25
> 1 file changed, 25 insertions(+)
>
> diff --git
On Thu, Apr 18, 2019 at 10:41:47AM +0200, Thomas Gleixner wrote:
> +typedef bool (*stack_trace_consume_fn)(void *cookie, unsigned long addr,
> + bool reliable);
> +void arch_stack_walk(stack_trace_consume_fn consume_entry, void *cookie,
> +
https://bugs.freedesktop.org/show_bug.cgi?id=110457
--- Comment #5 from jian-h...@endlessm.com ---
Created attachment 144042
--> https://bugs.freedesktop.org/attachment.cgi?id=144042=edit
journal log on Acer TravelMate B114-21
Got more information after wait more time for resuming on Acer
On Thu, Apr 18, 2019 at 05:42:55PM +0200, Thomas Gleixner wrote:
> On Thu, 18 Apr 2019, Josh Poimboeuf wrote:
> > Another idea I had (but never got a chance to work on) was to extend the
> > x86 unwind interface to all arches. So instead of the callbacks, each
> > arch would implement something
64 matches
Mail list logo
