What about
"Enable recursive locking at swapout time to make it possible to swap
out BOs that share the same reservation object."
Is "per VM BOs" an AMD specific name? In that case, I'd avoid using it
in the TTM code since most people have no idea what they are and why the
need specific
Quoting Dave Airlie (2017-12-21 02:42:56)
> > @@ -494,12 +473,11 @@ static int drm_syncobj_fd_to_handle(struct drm_file
> > *file_private,
> > spin_unlock(_private->syncobj_table_lock);
> > idr_preload_end();
> >
> > - if (ret < 0) {
> > - fput(syncobj->file);
On 12/20/2017 11:35 AM, Roger He wrote:
extract this function since eviction and swapout share same logic
But it's only used in eviction?
Change-Id: I80a475a93fceed8d66d74a1832c815a0756341ac
Signed-off-by: Roger He
---
drivers/gpu/drm/ttm/ttm_bo.c | 29
Roger,
5 out of 7 patches in this series are completely lacking a commit log
message, and thats not OK. Really.
https://www.kernel.org/doc/html/v4.12/process/submitting-patches.html#describe-your-changes
I'll review these, but IIRC the no_wait in the memory accounting code is
different in
https://bugzilla.kernel.org/show_bug.cgi?id=198221
--- Comment #3 from Petr Vandrovec (p...@vandrovec.name) ---
Created attachment 261285
--> https://bugzilla.kernel.org/attachment.cgi?id=261285=edit
Bandaid to prevent processing of works not fully set up
I've attached bandaid that seems to
Patch bd36d3bab2e3d08f80766c86487090dbceed4651 fixed a deadlock in the
failure path of drm_lease_create. This made the partially initialized
lease object visible for a short window of time.
To avoid having the lessee state appear transiently, I've rearranged
the code so that the lessor fields are
On Wed, 20 Dec 2017, Dhinakaran Pandiyan wrote:
> Occasionally there are LINK_ADDRESS sideband messages timing out with the
> Lenovo MST dock + Dell MST monitor(w/ in-built branch) setup I have. These
> failures lead to the display not coming up on boot. Power
Occasionally there are LINK_ADDRESS sideband messages timing out with the
Lenovo MST dock + Dell MST monitor(w/ in-built branch) setup I have. These
failures lead to the display not coming up on boot. Power cycling the port
corresponding to the MST monitor's branch device and resending the message
These ioctls replace drmWaitVBlank and add ns time resolution and
64-bit sequence numbers to comply with the Vulkan API specifications.
The tests were derived from the existing kms_vblank tests with the
'wait' variant elided as the new API doesn't provide a mechanism for
blocking in the kernel.
Both of these APIs are now in the kernel; it would be nice to have the
tests integrated into the test suite.
This includes an updated version of the kms_lease patch (v3) which
adapts to the final kernel API changes.
___
dri-devel mailing list
Validate that the leasing API creates leases that allow access to a
subset of the available resources and that lease revocation works.
v2: from Dave Airlie
* Update ioctl numbers to latest proposed values.
* Fix commit message
* Add tests for get_lease and list_lessees
With the addition of "private_objs" in drm_atomic_state, we no longer
need to subclass drm_atomic_state to store state of share resources
that don't perfectly fit within planes/crtc/connector state information.
We can now save this state within drm_atomic_state itself using
the private objects.
It's been recommended that we use drm_private_objs embedded in
drm_atomic_state to hold shared resources instead of subclassing
drm_atomic_state.
This will also help us in getting one step closer to using the
atomic commit helpers instead of the msm_atomic_commit() funcs
in msm_atomic.c
I've
Global shared resources (hwpipes, hwmixers and SMP) for MDP5 are
implemented as a part of atomic state by subclassing drm_atomic_state.
The preferred approach is to use the drm_private_obj infrastructure
available in the atomic core.
mdp5_global_state is introduced as a drm atomic private
This replaces the usage of the subclassed atomic state (mdp5_state)
with a private_obj state embedded within drm_atomic_state. The latter
method is the preferred approach, since it's simpler to implement
and less prone to errors.
The new API replaces the older and equivalent mdp5_state usage in
-Original Message-
From: Christian König [mailto:ckoenig.leichtzumer...@gmail.com]
Sent: Wednesday, December 20, 2017 9:36 PM
To: He, Roger ; amd-...@lists.freedesktop.org;
dri-devel@lists.freedesktop.org
Subject: Re: [PATCH 3/7] drm/ttm: use an operation ctx for
Hi all,
Commits
bb5cdf8d1c76 ("drm: omapdrm: Remove filename from header and fix copyright
tag")
d66c36a3ee79 ("drm: omapdrm: Simplify platform registration")
are missing a Signed-off-by from their committer.
--
Cheers,
Stephen Rothwell
___
https://bugzilla.kernel.org/show_bug.cgi?id=198221
Petr Vandrovec (p...@vandrovec.name) changed:
What|Removed |Added
Regression|No |Yes
--- Comment
> @@ -494,12 +473,11 @@ static int drm_syncobj_fd_to_handle(struct drm_file
> *file_private,
> spin_unlock(_private->syncobj_table_lock);
> idr_preload_end();
>
> - if (ret < 0) {
> - fput(syncobj->file);
> - return ret;
> - }
> -
https://bugzilla.kernel.org/show_bug.cgi?id=198221
Ilia Mirkin (imir...@alum.mit.edu) changed:
What|Removed |Added
CC||imir...@alum.mit.edu
On Wed, Dec 20, 2017 at 6:22 PM, Kristian Kristensen
wrote:
> On Wed, Dec 20, 2017 at 12:41 PM, Miguel Angel Vico
> wrote:
>> On Wed, 20 Dec 2017 11:54:10 -0800
>> Kristian Høgsberg wrote:
>> > I'd like to see concrete examples of
On Wed, Dec 20, 2017 at 11:32:23AM +, Guillaume Tucker wrote:
> When neither HDMI nor DP is supported such as on the tegra124, the
> sor->clk_out is not initialised and remains NULL. In this case, the
> parent clock can't be assigned to it so revert to the previous
> behaviour of assigning it
https://bugs.freedesktop.org/show_bug.cgi?id=102130
--- Comment #5 from Alex Deucher ---
Is this still an issue?
--
You are receiving this mail because:
You are the assignee for the bug.___
dri-devel mailing list
https://bugs.freedesktop.org/show_bug.cgi?id=97471
Alex Deucher changed:
What|Removed |Added
Status|NEW |RESOLVED
https://bugs.freedesktop.org/show_bug.cgi?id=94973
--- Comment #2 from Alex Deucher ---
Is this still an issue?
--
You are receiving this mail because:
You are the assignee for the bug.___
dri-devel mailing list
https://bugs.freedesktop.org/show_bug.cgi?id=97993
Alex Deucher changed:
What|Removed |Added
Status|NEW |RESOLVED
On Wed, Dec 20, 2017 at 06:46:11PM +0300, Dmitry Osipenko wrote:
> Commit 7772fdaef939 ("drm/tegra: Support ARGB and ABGR formats") broke
> DRM's MODE_ADDFB IOCTL on Tegra20/30, because IOCTL uses XRGB format if
> requested FB depth is 24bpp. As a result, Xorg doesn't work anymore with
> both
https://bugs.freedesktop.org/show_bug.cgi?id=96866
Alex Deucher changed:
What|Removed |Added
Status|NEW |RESOLVED
https://bugs.freedesktop.org/show_bug.cgi?id=104347
--- Comment #2 from Michel Dänzer ---
Please attach the corresponding glxinfo output.
Did this not happen with an older version of Mesa / LLVM? If so, can you
bisect?
--
You are receiving this mail because:
You are the
Ping... can someone please review this patch?
Samuel Li
> -Original Message-
> From: amd-gfx [mailto:amd-gfx-boun...@lists.freedesktop.org] On Behalf
> Of Samuel Li
> Sent: Friday, December 15, 2017 11:28 AM
> To: dri-devel@lists.freedesktop.org; amd-...@lists.freedesktop.org
> Cc:
https://bugs.freedesktop.org/show_bug.cgi?id=104347
--- Comment #1 from network...@rkmail.ru ---
I had the same issue with my RX480, but it does not happen on hd7950 with
amdgpu.
--
You are receiving this mail because:
You are the assignee for the
On 12/20/2017 04:35 PM, Ray Strode wrote:
> Hi,
>
>> Actually, I don't want that :)
>>
>> This was a design decision that I've made to keep the code small and simple
>> to audit.
>> As it is, the simple bootsplash code will make 99% of people happy.
> You think only 1% of linux users have more
On 12/20/2017 04:21 PM, Ray Strode wrote:
> If we've reached the scenario you're discussing above, the real
> failure is that the KMS
> driver took too long to load. DRM is the platform graphics api. If
> it's not loading
> timely enough to show graphics then that's the problem! It sounds
> like
On 12/20/2017 04:19 PM, Daniel Vetter wrote:
> On Wed, Dec 20, 2017 at 4:11 PM, Daniel Vetter wrote:
>> On Wed, Dec 20, 2017 at 3:55 PM, Max Staudt wrote:
>>> On 12/20/2017 11:14 AM, Daniel Vetter wrote:
btw since I'm probably sounding a bit too grumpy
On 12/20/2017 04:11 PM, Daniel Vetter wrote:
> So fundamentally I don't think an in-kernel bootsplash is a bad idea.
> But most likely you want this on a highly embedded system, which
> probably is compiled for your exact hw, with pretty much everything
> built in. Also, no fbcon, maybe even no vt
Hi,
> Actually, I don't want that :)
>
> This was a design decision that I've made to keep the code small and simple
> to audit.
> As it is, the simple bootsplash code will make 99% of people happy.
You think only 1% of linux users have more than one monitor or a 4k screen?
> I've made this
On Wed, Dec 20, 2017 at 4:19 PM, Daniel Vetter wrote:
> On Wed, Dec 20, 2017 at 4:11 PM, Daniel Vetter wrote:
>> On Wed, Dec 20, 2017 at 3:55 PM, Max Staudt wrote:
>>> On 12/20/2017 11:14 AM, Daniel Vetter wrote:
btw since I'm probably
Hi,
> The problem that I am stumbling upon is different:
> - the system starts with an FB driver
> - after the ShowDelay time, Plymouth opens /dev/fb0
> - the system finally loads the DRM driver, which tries to kick the previous
> FB driver
> - loading the DRM driver fails because Plymouth
On Wed, Dec 20, 2017 at 4:11 PM, Daniel Vetter wrote:
> On Wed, Dec 20, 2017 at 3:55 PM, Max Staudt wrote:
>> On 12/20/2017 11:14 AM, Daniel Vetter wrote:
>>> btw since I'm probably sounding a bit too grumpy here: I'd very much
>>> support this. I think
On Wed, Dec 20, 2017 at 3:55 PM, Max Staudt wrote:
> On 12/20/2017 11:14 AM, Daniel Vetter wrote:
>> btw since I'm probably sounding a bit too grumpy here: I'd very much
>> support this. I think bootsplash in kernel has a bunch of uses, and it
>> shouldn't be hard to get non-suse
On 12/20/2017 11:14 AM, Daniel Vetter wrote:
> btw since I'm probably sounding a bit too grumpy here: I'd very much
> support this. I think bootsplash in kernel has a bunch of uses, and it
> shouldn't be hard to get non-suse people to cheer for it (makes merging
> easier if it's not just a one-off
https://bugs.freedesktop.org/show_bug.cgi?id=104275
--- Comment #9 from Harry Wentland ---
Created attachment 136321
--> https://bugs.freedesktop.org/attachment.cgi?id=136321=edit
DC scatter gather patch
You'll need this DC patch.
--
You are receiving this mail
Am 20.12.2017 um 11:34 schrieb Roger He:
Change-Id: I803ea52d11e5c06add0dffab836c3aecc00b56dd
Signed-off-by: Roger He
Commit message! And please double check the coding style of
ast_ttm_tt_populate.
With that fixed that patch is Reviewed-by: Christian König
On 12/20/2017 11:06 AM, Neil Armstrong wrote:
> My 2cents about this patchset:
> You did a good job about all the animation and splash logic, but for me all
> this fbcon
> stuff is a huge hack, please use a standard and modern display subsystem en
> leave fbcon
> die alone
Thanks for the
On 12/20/2017 10:43 AM, Daniel Vetter wrote:
> On Tue, Dec 19, 2017 at 07:40:12PM +0100, Max Staudt wrote:
>> On 12/19/2017 06:26 PM, Daniel Vetter wrote:
>>> So essentially you're telling me that on a current general purpose
>>> distro the gfx driver loading is a dumpster fire, and we're fixing
On Wed, Dec 20, 2017 at 11:50:17AM +0100, Hans de Goede wrote:
> At least on the Chuwi Vi8 (non pro/plus) the LCD panel will show an image
> shifted aprox. 20% to the left (with wraparound) and sometimes also wrong
> colors, showing that the panel controller is starting with sampling the
>
Den 15.12.2017 18.51, skrev Noralf Trønnes:
Hi,
This is a new attempt at simplifying fbdev setup/teardown in drivers.
Only doc changes in this version based on feedback from Daniel.
Noralf.
Changes since version 1:
- Document a case where drm_fb_helper_fbdev_setup() can't be used:
Commit message!
Am 20.12.2017 um 11:34 schrieb Roger He:
Change-Id: I4104a12e09a374b6477a0dd5a8fce26dce27a746
Signed-off-by: Roger He
---
drivers/gpu/drm/ttm/ttm_memory.c | 15 ---
drivers/gpu/drm/ttm/ttm_page_alloc.c | 6 +-
Commit message needed! Something like:
Forward the operation context to ttm_mem_global_alloc as well.
Am 20.12.2017 um 11:34 schrieb Roger He:
Change-Id: I5279b5cd3560c4082b00f822219575a5f9c3808a
Signed-off-by: Roger He
With the commit message fixed, patch is Reviewed-by:
Am 20.12.2017 um 11:34 schrieb Roger He:
then remove superfluous functions
We need a better commit message. Something like:
Remove the extra indirection, cause we have only one implementation anyway.
Change-Id: Iea020f0e30a239e0265e7a1500168c7d7f819bd9
Signed-off-by: Roger He
On Wed, 20 Dec 2017, Joe Perches wrote:
> On Wed, 2017-12-20 at 10:59 +0100, Greg Kroah-Hartman wrote:
> > > > Why you didn't send that patch to the sysfs maintainer is a bit odd...
> > > > :)
> > >
> > > So here's an opportunity for you:
> > >
> > > The sysfs maintainer hasn't added
On 12/19/2017 10:01 PM, Ray Strode wrote:
> Hi,
>
> On Tue, Dec 19, 2017 at 10:41 AM, Max Staudt wrote:
>> I'm hooking into the in-kernel terminal emulator, because the bootsplash is a
>> functional extension of that. It just happens that fbcon sits on top of FB,
>> so I
>>
On 12/19/2017 09:30 PM, Ray Strode wrote:
> Hi,
>
>> For example, having a userspace splash that starts as early as it can
>> (thus on vesafb/efifb on a PC) will cause the KMS driver to fail
>> reserving the entirety of video RAM, and thus fail loading. This cannot be
>> fixed.
> well the fix
Hi Dave, seasons greetings, just a few small fixes.
BR,
Jani.
The following changes since commit 2cf654db8d7eafb973d28eb3cddf043d353e1345:
drm/i915/fence: Use rcu to defer freeing of irq_work (2017-12-14 10:58:59
+0200)
are available in the git repository at:
Hi Daniel,
On Tue, Dec 19, 2017 at 11:05:04AM +0100, Daniel Vetter wrote:
> On Mon, Dec 18, 2017 at 08:50:46AM +0100, Maxime Ripard wrote:
> > Hi,
> >
> > On Fri, Dec 15, 2017 at 06:06:32PM +0100, Daniel Vetter wrote:
> > > On Fri, Dec 15, 2017 at 05:46:19PM +0100, Hans Verkuil wrote:
> > > >
This patch was initially sent along with another one to fix a
first hang in the nouveau drm driver[1]. I'm now sending it
again as a separate patch as it's to fix a second hang which is
not strictly related. It is hidden by the first hang though, as
this happens later on during the driver
When neither HDMI nor DP is supported such as on the tegra124, the
sor->clk_out is not initialised and remains NULL. In this case, the
parent clock can't be assigned to it so revert to the previous
behaviour of assigning it to the main sor->clk instead.
This fixes a kernel hang on tegra124 and
https://bugs.freedesktop.org/show_bug.cgi?id=104347
Bug ID: 104347
Summary: AMD RX 580: Hide/Show window sometimes corrupts screen
(see screenshot)
Product: Mesa
Version: 17.3
Hardware: x86-64 (AMD64)
OS:
On 19.12.2017 12:42, Marc Zyngier wrote:
> On 19/12/17 07:55, Andrzej Hajda wrote:
>> On 18.12.2017 12:28, Marc Zyngier wrote:
>>> Stopping the X display manager on a kevin platform results in the
>>> following crash:
>>>
>>> [ 674.833536] Synchronous External Abort: synchronous external abort
Hi Johannes,
On 20 December 2017 at 11:08, Johannes Thumshirn wrote:
> On Tue, Dec 19, 2017 at 05:16:30PM +0100, Daniel Vetter wrote:
>> Ok I've realized that my assumptions about why you need this aren't
>> So from reading these patches it sounded like you want an in-kernel
https://bugzilla.kernel.org/show_bug.cgi?id=196197
--- Comment #17 from Andreas Brogle (an...@ok.de) ---
What do you suggest ?
Who is the maintainer for fixing this bug ?
--
You are receiving this mail because:
You are watching the assignee of the bug.
On Wed, 2017-12-20 at 10:59 +0100, Greg Kroah-Hartman wrote:
> > > Why you didn't send that patch to the sysfs maintainer is a bit odd... :)
> >
> > So here's an opportunity for you:
> >
> > The sysfs maintainer hasn't added include/linux/sysfs.h to
> > the list of maintained files...
> >
> >
https://bugzilla.kernel.org/show_bug.cgi?id=196197
--- Comment #16 from Michel Dänzer (mic...@daenzer.net) ---
(In reply to Andreas Brogle from comment #14)
> 60e8d3e11645a1b9c4197d9786df3894332c1685 (BAD)
> 190c3ee06a0f0660839785b7ad8a830e832d9481 (GOOD)
There are only PCI subsystem changes
https://bugs.freedesktop.org/show_bug.cgi?id=104345
--- Comment #3 from Michel Dänzer ---
Please attach the output of glxinfo and vdpauinfo.
--
You are receiving this mail because:
You are the assignee for the bug.___
dri-devel
extract this function since eviction and swapout share same logic
Change-Id: I80a475a93fceed8d66d74a1832c815a0756341ac
Signed-off-by: Roger He
---
drivers/gpu/drm/ttm/ttm_bo.c | 29 +++--
1 file changed, 19 insertions(+), 10 deletions(-)
diff --git
Change-Id: I1e87954564f38ad298bf6e4ff88c9f26f291a62d
Signed-off-by: Roger He
---
drivers/gpu/drm/ttm/ttm_bo.c | 15 +++
drivers/gpu/drm/ttm/ttm_memory.c | 12
include/drm/ttm/ttm_bo_api.h | 3 ++-
3 files changed, 21 insertions(+), 9
Change-Id: I42a7df8c50e1ce3b527ee9cb78809f8e58136f07
Signed-off-by: Roger He
---
drivers/gpu/drm/amd/amdgpu/amdgpu_ttm.c | 2 +-
drivers/gpu/drm/nouveau/nouveau_bo.c| 2 +-
drivers/gpu/drm/radeon/radeon_ttm.c | 2 +-
drivers/gpu/drm/ttm/ttm_bo.c| 2 +-
Change-Id: I803ea52d11e5c06add0dffab836c3aecc00b56dd
Signed-off-by: Roger He
---
drivers/gpu/drm/amd/amdgpu/amdgpu_ttm.c | 7 ---
drivers/gpu/drm/ast/ast_ttm.c| 5 +++--
drivers/gpu/drm/cirrus/cirrus_ttm.c | 5 +++--
https://bugs.freedesktop.org/show_bug.cgi?id=104345
--- Comment #2 from bernhardu ---
(In reply to Michel Dänzer from comment #1)
> It's more likely a Mesa or maybe LLVM issue. Did this start happening after
> you upgraded Mesa and/or LLVM, or maybe another component such
Change-Id: I5279b5cd3560c4082b00f822219575a5f9c3808a
Signed-off-by: Roger He
---
drivers/gpu/drm/ttm/ttm_bo.c| 2 +-
drivers/gpu/drm/ttm/ttm_memory.c| 15 +--
drivers/gpu/drm/ttm/ttm_object.c| 13 ++---
Change-Id: I4104a12e09a374b6477a0dd5a8fce26dce27a746
Signed-off-by: Roger He
---
drivers/gpu/drm/ttm/ttm_memory.c | 15 ---
drivers/gpu/drm/ttm/ttm_page_alloc.c | 6 +-
drivers/gpu/drm/ttm/ttm_page_alloc_dma.c | 8 ++--
then remove superfluous functions
Change-Id: Iea020f0e30a239e0265e7a1500168c7d7f819bd9
Signed-off-by: Roger He
---
drivers/gpu/drm/ttm/ttm_bo.c | 21 +++-
drivers/gpu/drm/ttm/ttm_memory.c | 12 ++-
include/drm/ttm/ttm_bo_api.h | 1 +
On Wed, Dec 20, 2017 at 10:35:45AM +0100, Maarten Lankhorst wrote:
> From: Ville Syrjälä
>
> We don't need any active planes during load detection, so just disable
> them all. This saves us from having to come up with a suitable
> framebuffer. And we also avoid
On Wed, Dec 20, 2017 at 10:35:44AM +0100, Maarten Lankhorst wrote:
> This is is very useful to finding sources of leaked framebufers.
> The fbcon fb is annotated with [fbcon], to give it a better name
> than kworker.
>
> Signed-off-by: Maarten Lankhorst
I
On Wed, Dec 20, 2017 at 10:35:43AM +0100, Maarten Lankhorst wrote:
> lock_all_ctx in setplane_internal may return -EINTR, and
> __setplane_internal could return -EDEADLK. Making more
> special cases for fb would make the code even harder to
> read, so the easiest solution is not taking over the fb
On Wed, Dec 20, 2017 at 11:06:34AM +0100, Neil Armstrong wrote:
> On 20/12/2017 10:43, Daniel Vetter wrote:
> > On Tue, Dec 19, 2017 at 07:40:12PM +0100, Max Staudt wrote:
> >> On 12/19/2017 06:26 PM, Daniel Vetter wrote:
> >>> On Tue, Dec 19, 2017 at 6:04 PM, Max Staudt wrote:
>
https://bugs.freedesktop.org/show_bug.cgi?id=104345
Michel Dänzer changed:
What|Removed |Added
QA Contact|
On 20/12/2017 10:43, Daniel Vetter wrote:
> On Tue, Dec 19, 2017 at 07:40:12PM +0100, Max Staudt wrote:
>> On 12/19/2017 06:26 PM, Daniel Vetter wrote:
>>> On Tue, Dec 19, 2017 at 6:04 PM, Max Staudt wrote:
Well, those could enable fbcon if they want the bootsplash.
https://bugs.freedesktop.org/show_bug.cgi?id=104345
Bug ID: 104345
Summary: Playing video hangs X-Server with showing scrambled
picture, sound still playing.
Product: DRI
Version: unspecified
Hardware: x86-64 (AMD64)
https://bugs.freedesktop.org/show_bug.cgi?id=104331
--- Comment #5 from Michel Dänzer ---
(In reply to MWATTT from comment #2)
> However, the demo does not render properly(I don't know if I should make
> another report for that).
Please do.
--
You are receiving this mail
On Tue, Dec 19, 2017 at 03:27:31PM -0800, Dongwon Kim wrote:
> I forgot to include this brief information about this patch series.
>
> This patch series contains the implementation of a new device driver,
> hyper_dmabuf, which provides a method for DMA-BUF sharing across
> different OSes running
On Wed, Dec 20, 2017 at 01:54:41AM -0800, Joe Perches wrote:
> On Wed, 2017-12-20 at 10:32 +0100, Greg Kroah-Hartman wrote:
> > On Wed, Dec 20, 2017 at 01:24:44AM -0800, Joe Perches wrote:
> > > On Wed, 2017-12-20 at 10:34 +0200, Jarkko Nikula wrote:
> > > > On Tue, Dec 19, 2017 at 10:15:07AM
https://bugs.freedesktop.org/show_bug.cgi?id=104275
--- Comment #8 from Michel Dänzer ---
(In reply to Alex_Zhang1 from comment #7)
Without the patch referenced in comment 3, a buffer must be pinned to VRAM
before it can be scanned out (displayed). The problem described in
On Wed, 2017-12-20 at 10:32 +0100, Greg Kroah-Hartman wrote:
> On Wed, Dec 20, 2017 at 01:24:44AM -0800, Joe Perches wrote:
> > On Wed, 2017-12-20 at 10:34 +0200, Jarkko Nikula wrote:
> > > On Tue, Dec 19, 2017 at 10:15:07AM -0800, Joe Perches wrote:
> > > > Convert DEVICE_ATTR uses to
On Tue, Dec 19, 2017 at 05:23:52PM +0100, Max Staudt wrote:
> On 12/19/2017 05:02 PM, Daniel Vetter wrote:
> > On Tue, Dec 19, 2017 at 4:41 PM, Max Staudt wrote:
> >> On 12/19/2017 02:57 PM, Daniel Vetter wrote:
> >>> The problem is that defio is totally not how a real driver
On Tue, Dec 19, 2017 at 07:40:12PM +0100, Max Staudt wrote:
> On 12/19/2017 06:26 PM, Daniel Vetter wrote:
> > On Tue, Dec 19, 2017 at 6:04 PM, Max Staudt wrote:
> >> Well, those could enable fbcon if they want the bootsplash. Shouldn't make
> >> a difference anyway if they're
lock_all_ctx in setplane_internal may return -EINTR, and
__setplane_internal could return -EDEADLK. Making more
special cases for fb would make the code even harder to
read, so the easiest solution is not taking over the fb
refcount, and making callers responsible for dropping
the ref.
Bugzilla:
From: Ville Syrjälä
We don't need any active planes during load detection, so just disable
them all. This saves us from having to come up with a suitable
framebuffer. And we also avoid leaving sprite/cursor planes on and
potentially presenting them at a peculiar
This is is very useful to finding sources of leaked framebufers.
The fbcon fb is annotated with [fbcon], to give it a better name
than kworker.
Signed-off-by: Maarten Lankhorst
---
drivers/gpu/drm/drm_fb_helper.c | 1 +
drivers/gpu/drm/drm_framebuffer.c | 2
There's a small leak excerbated by interruptible waiting in setplane_internal,
which was triggered by kms_atomic. Another leak is in load detection, and easily
plugged by just removing the fb handling.
Maarten Lankhorst (2):
drm/plane: Make framebuffer refcounting the responsibility of
https://bugzilla.kernel.org/show_bug.cgi?id=197925
--- Comment #11 from Charles (ylang-yl...@libertysurf.fr) ---
Hi team,
Just to say... same error :
[drm:hwss_wait_for_blank_complete [amdgpu]] *ERROR* DC: failed to blank crtc!
with 4.15-rc4
(on the same noteboook)
--
You are receiving this
On Wed, Dec 20, 2017 at 01:24:44AM -0800, Joe Perches wrote:
> On Wed, 2017-12-20 at 10:34 +0200, Jarkko Nikula wrote:
> > On Tue, Dec 19, 2017 at 10:15:07AM -0800, Joe Perches wrote:
> > > Convert DEVICE_ATTR uses to DEVICE_ATTR_RW where possible.
> []
> > > diff --git a/sound/soc/omap/mcbsp.c
On Wed, 2017-12-20 at 10:34 +0200, Jarkko Nikula wrote:
> On Tue, Dec 19, 2017 at 10:15:07AM -0800, Joe Perches wrote:
> > Convert DEVICE_ATTR uses to DEVICE_ATTR_RW where possible.
[]
> > diff --git a/sound/soc/omap/mcbsp.c b/sound/soc/omap/mcbsp.c
[]
> > @@ -854,7 +854,7 @@ static ssize_t
On 12/19/2017 12:15 PM, Joe Perches wrote:
drivers/char/ipmi/ipmi_msghandler.c| 17 +++---
For ipmi:
Acked-by: Corey Minyard
___
dri-devel mailing list
dri-devel@lists.freedesktop.org
On 20/12/17 00:27, Dongwon Kim wrote:
> I forgot to include this brief information about this patch series.
>
> This patch series contains the implementation of a new device driver,
> hyper_dmabuf, which provides a method for DMA-BUF sharing across
> different OSes running on the same virtual OS
Em Sun, 17 Dec 2017 16:28:44 -0800
Joe Perches escreveu:
> Some functions definitions have either the initial open brace and/or
> the closing brace outside of column 1.
>
> Move those braces to column 1.
>
> This allows various function analyzers like gnu complexity to work
>
On 2017-12-18 12:37, Michel Dänzer wrote:
>
> Following up by e-mail, since I can't find Peter Rosin in the kernel
> bugzilla.
>
>
> On 2017-12-16 02:41 AM, bugzilla-dae...@bugzilla.kernel.org wrote:
>> https://bugzilla.kernel.org/show_bug.cgi?id=198123
>>
>> --- Comment #8 from Deposite Pirate
* Tomi Valkeinen [171219 10:51]:
> On 11/12/17 17:22, Tony Lindgren wrote:
> > * H. Nikolaus Schaller [171201 07:44]:
> > > Official vendor string is now "tpo" and not "toppoly".
> > >
> > > Requires patch "omapdrm: panel: fix compatible vendor string
On 12/19/2017 6:59 PM, Daniel Vetter wrote:
On Mon, Dec 18, 2017 at 09:42:13AM -0800, Linus Torvalds wrote:
On Sun, Dec 17, 2017 at 11:11 PM, Daniel Vetter wrote:
This didn't seem to have made it into -rc4. Anything needed to get it
going?
Do you actually see the problem
On 19/12/17 07:55, Andrzej Hajda wrote:
> On 18.12.2017 12:28, Marc Zyngier wrote:
>> Stopping the X display manager on a kevin platform results in the
>> following crash:
>>
>> [ 674.833536] Synchronous External Abort: synchronous external abort
>> (0x9610) at 0x0c970640
>> [
1 - 100 of 103 matches
Mail list logo