https://bugs.freedesktop.org/show_bug.cgi?id=108521
--- Comment #4 from Robert Strube ---
I decided to apply a hack to 4.19 and see if I could get the eGPU to
initialize. I noticed that this code in /drivers/gpu/drm/amd/amdgpu/atom.c
if ((jiffies_to_msecs(cjiffies) > 5000)) {
DRM_ERROR(
On 10/4/18 9:12 PM, Christian König wrote:
And drop the now superflous extra reservations.
Signed-off-by: Christian König
---
drivers/gpu/drm/amd/amdgpu/amdgpu_cs.c | 4
drivers/gpu/drm/amd/amdgpu/amdgpu_vm.c | 15 ++-
2 files changed, 6 insertions(+), 13 deletions(-)
dif
Patch 3, 5 is
Acked-by: Junwei Zhang
Others are
Reviewed-by: Junwei Zhang
On 10/4/18 9:12 PM, Christian König wrote:
No need for that any more. Just replace the list when there isn't enough
room any more for the additional fence.
Signed-off-by: Christian König
---
drivers/dma-buf/reservat
Christian, I will take a look at them later.
Thanks,
Ray
> -Original Message-
> From: Christian König [mailto:ckoenig.leichtzumer...@gmail.com]
> Sent: Tuesday, October 23, 2018 8:20 PM
> To: amd-...@lists.freedesktop.org; dri-devel@lists.freedesktop.org; linux-
> me...@vger.kernel.org; l
tree: git://people.freedesktop.org/~agd5f/linux.git amd-18.30
head: 7b669e917dcab69f330fab0903d5eb21ba0fb87e
commit: 7b669e917dcab69f330fab0903d5eb21ba0fb87e [1/1] drm/amdgpu:No action
when VCN PG state is unchanged
config: x86_64-allmodconfig (attached as .config)
compiler: gcc-7 (Debian 7.3.
https://bugs.freedesktop.org/show_bug.cgi?id=105251
--- Comment #55 from zzyx...@gmail.com ---
Any updates to this? I can still reproduce with the latest amd-drm-next kernel.
--
You are receiving this mail because:
You are the assignee for the bug.___
From: Lyude
As observed with the latest ThinkPad docks, we unfortunately can't rely
on docks keeping us updated with hotplug events that happened while we
were suspended. On top of that, even if the number of connectors remains
the same between suspend and resume it's still not safe to assume tha
From: Lyude
A follow-up to the previous commit, we skip checking the status of the
MST device and completely reprobe it if drm_dp_mst_topology_mgr_resume()
returns -EINVAL.
Cc: sta...@vger.kernel.org
Signed-off-by: Lyude
Signed-off-by: Juston Li
---
drivers/gpu/drm/i915/intel_dp.c | 7 ++-
Updated and resending these patches from Lyude:
https://lkml.org/lkml/2016/5/19/361
https://lkml.org/lkml/2016/5/19/360
As Lyude explains in patch 1/2, we can't rely on MST hubs to handle
hotplugs during suspend. This patchset will check if any EDID's changed
upon resume and reset the MST connecti
https://bugs.freedesktop.org/show_bug.cgi?id=108533
--- Comment #5 from Dieter Nützel ---
dmesg show this error (all the time):
[ 14.690300] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize
parser !
[ 16.458594] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize
parser !
https://bugs.freedesktop.org/show_bug.cgi?id=108533
Dieter Nützel changed:
What|Removed |Added
Priority|medium |high
--- Comment #4 from Dieter Nützel
https://bugs.freedesktop.org/show_bug.cgi?id=108533
--- Comment #3 from Dieter Nützel ---
Created attachment 142166
--> https://bugs.freedesktop.org/attachment.cgi?id=142166&action=edit
20181024_021334.jpg
--
You are receiving this mail because:
You are the assignee for the bug.__
https://bugs.freedesktop.org/show_bug.cgi?id=108533
--- Comment #2 from Dieter Nützel ---
Created attachment 142165
--> https://bugs.freedesktop.org/attachment.cgi?id=142165&action=edit
20181024_021330.jpg
--
You are receiving this mail because:
You are the assignee for the bug.__
https://bugs.freedesktop.org/show_bug.cgi?id=108533
--- Comment #1 from Dieter Nützel ---
Created attachment 142164
--> https://bugs.freedesktop.org/attachment.cgi?id=142164&action=edit
Xorg.0.log-4.19.0-1.gd04171e-default
--
You are receiving this mail because:
You are the assignee for the b
https://bugs.freedesktop.org/show_bug.cgi?id=108533
Bug ID: 108533
Summary: [Polaris 20] 4.19.0 final unusable with RX580 - SDDM
screen corruption, regression
Product: DRI
Version: unspecified
Hardware: x86-64 (AMD64)
https://bugs.freedesktop.org/show_bug.cgi?id=108096
Dieter Nützel changed:
What|Removed |Added
Summary|[amd-staging-drm-next] SDDM |[amd-staging-drm-next] SDDM
https://bugs.freedesktop.org/show_bug.cgi?id=108096
Dieter Nützel changed:
What|Removed |Added
Severity|normal |critical
--
You are receiving this mai
https://bugs.freedesktop.org/show_bug.cgi?id=107432
--- Comment #12 from Robert Strube ---
Thanks Michel!
I'm currently running 4.19. I'll put my system under memory pressure and see
if things are working OK.
Rob
--
You are receiving this mail because:
You are the assignee for the bug.__
It occurred to me that we never actually check this! So let's start
doing that.
Signed-off-by: Lyude Paul
Cc: Daniel Vetter
---
drivers/gpu/drm/drm_dp_mst_topology.c | 8 +++-
1 file changed, 7 insertions(+), 1 deletion(-)
diff --git a/drivers/gpu/drm/drm_dp_mst_topology.c
b/drivers/gpu/d
Currently, nouveau uses the yolo method of setting up MST displays: it
uses the old VCPI helpers (drm_dp_find_vcpi_slots()) for computing the
display configuration. These helpers don't take care to make sure they
take a reference to the mstb port that they're checking, and
additionally don't actual
Currently; private objects are mostly used just for driver-specific
atomic state, but not entirely. MST also uses private objects for
holding it's atomic state, but in order to make our MST helpers safer
for atomic we need to be able to check that state after the driver has
performed it's own check
Because we have drm_dp_atomic_find_vcpi_slots(), which actually takes
care to update the atomic state of the MST topology, prints valuable
debugging output, and actually takes references to the ports it's
checking! This explains some incorrect usage I've been seeing across the
tree...
Signed-off-b
There's no reason to track the atomic state three times. Unfortunately,
this is currently what we're doing, and even worse is that there is only
one actually correct state pointer: the one in mst_state->base.state.
mgr->state never seems to be used, along with the one in
mst_state->state.
This con
There has been a TODO waiting for quite a long time in
drm_dp_mst_topology.c:
/* We cannot rely on port->vcpi.num_slots to update
* topology_state->avail_slots as the port may not exist if the parent
* branch device was unplugged. This should be fixed by tracking
This patchset does some cleaning up of the atomic VCPI helpers for MST,
and converts nouveau over to using them. I would have included amdgpu in
this patch as well, but at the moment moving them over to the atomic
helpers is nontrivial.
Cc: Daniel Vetter
Lyude Paul (6):
drm/dp_mst: Deprecate d
https://bugs.freedesktop.org/show_bug.cgi?id=108521
--- Comment #3 from Robert Strube ---
Quick question:
Is it possible to completely disable the Vega M using kernel boot parameters.
I did try using pci-stub.ids=: with the PCI hex id for my Vega M
(1002:694e) but amdgpu was still appli
https://bugs.freedesktop.org/show_bug.cgi?id=108323
--- Comment #3 from bmil...@gmail.com ---
Yes, seems like the same issue. It would be useful to know if someone with a
non-Sapphire RX580 has the same problem.
--
You are receiving this mail because:
You are the assignee for the bug.___
On Tue, Oct 23, 2018 at 12:41 PM Sean Paul wrote:
>
> On Mon, Oct 22, 2018 at 08:22:57PM +0100, Chris Wilson wrote:
> > Quoting Mamta Shukla (2018-10-20 18:49:26)
> > > Use DRM_DEV_INFO/ERROR/WARN instead of dev_info/err/debug to generate
> > > drm-formatted specific log messages so that it will b
>-Original Message-
>From: Navare, Manasi D
>Sent: Tuesday, October 23, 2018 11:43 AM
>To: Srivatsa, Anusha
>Cc: intel-...@lists.freedesktop.org; dri-devel@lists.freedesktop.org
>Subject: Re: [Intel-gfx] [PATCH v5 17/28] drm/i915/dsc: Compute Rate Control
>parameters for DSC
>
>On Mon, O
To lower CPU overhead, future userspace will be switching to pinning
iova and avoiding the use of relocs, and only include cmds table entries
for IB1 level cmdstream (but not IB2 or state-groups).
This leaves the kernel unsure what to dump for rd/hangrd cmdstream
dumping. So add a MSM_SUBMIT_BO_
On Mon, Oct 22, 2018 at 04:34:59PM -0700, Srivatsa, Anusha wrote:
>
>
> From: Intel-gfx [intel-gfx-boun...@lists.freedesktop.org] on behalf of Manasi
> Navare [manasi.d.nav...@intel.com]
> Sent: Friday, October 05, 2018 4:22 PM
> To: intel-...@lists.freede
On Thu, 18 Oct 2018 at 21:07, Christian Gmeiner
wrote:
>
> Since kernel 4.17 (drm/etnaviv: remove the need for a gpu-subsystem DT
> node) the etnaviv DRM driver doesn't have an associated DT node
> anymore. This is technically correct, as the etnaviv device is a
> virtual device driving multiple h
https://bugs.freedesktop.org/show_bug.cgi?id=108317
--- Comment #15 from John Galt ---
I've updated the main issue to reflect that this is affects all gcn3 cards
specifically (AI + VI), and no <=gcn2 or gcn5 cards.
--
You are receiving this mail because:
You are the assignee for the bug.___
https://bugzilla.kernel.org/show_bug.cgi?id=201497
Bug ID: 201497
Summary: [amdgpu]: '*ERROR* No EDID read' is back in 4.19
Product: Drivers
Version: 2.5
Kernel Version: 4.19
Hardware: All
OS: Linux
Tree: Main
https://bugs.freedesktop.org/show_bug.cgi?id=108317
John Galt changed:
What|Removed |Added
Summary|[Polaris] Black Textures|[GCN3] Black Textures only
https://bugs.freedesktop.org/show_bug.cgi?id=108514
--- Comment #5 from Werner Lueckel ---
Created attachment 142156
--> https://bugs.freedesktop.org/attachment.cgi?id=142156&action=edit
dmesg Ubuntu14.04, Kernel4.4.0-133, radeon 2.43.0, screen flickering
... and I found out that the screen-fl
On 10/23/18 18:35, Emil Velikov wrote:
> From: Emil Velikov
>
> A while back we removed it, yet that lead to regressions. At some later
> point, I've attempted to remove it again without fully grasping the
> unique (pun intended) situation that virtio is in.
pun appreciated :)
>
> Add a bulky
https://bugs.freedesktop.org/show_bug.cgi?id=108514
--- Comment #4 from Werner Lueckel ---
- I attached 2 dmesg-listings;
booting Ubuntu14.04, Kernel3.13 -> screen is o.k.; no flickering
booting Ubuntu18.04, Kernel4.15 -> screen flickers.
- no Xorg log since the flickering happens already in
https://bugs.freedesktop.org/show_bug.cgi?id=108330
Michel Dänzer changed:
What|Removed |Added
Blocks||108530
Referenced Bugs:
https://bugs.
On Mon, Oct 22, 2018 at 08:22:57PM +0100, Chris Wilson wrote:
> Quoting Mamta Shukla (2018-10-20 18:49:26)
> > Use DRM_DEV_INFO/ERROR/WARN instead of dev_info/err/debug to generate
> > drm-formatted specific log messages so that it will be easy to
> > differentiate in case of multiple instances of
From: Emil Velikov
A while back we removed it, yet that lead to regressions. At some later
point, I've attempted to remove it again without fully grasping the
unique (pun intended) situation that virtio is in.
Add a bulky comment to document any the call should stay as-is, for the
next person wh
From: Emil Velikov
Previous commit removed the only reason why we were allowing NULL as
a parent device. With that resolved, we can enforce nobody else does
that mistake.
With that we can drop the ugly drm_dev_set_unique workaround.
v2: rebase, silence checkpatch "== NULL" warning
Cc: Daniel V
From: Deepak Sharma
Modify vgem_init to take platform dev as parent in drm_dev_init.
This will make drm device available at "/sys/devices/platform/vgem"
in x86 chromebook.
v2: rebase, address checkpatch typo and line over 80 characters
Cc: Daniel Vetter
Signed-off-by: Deepak Sharma
Reviewed-b
https://bugs.freedesktop.org/show_bug.cgi?id=108514
--- Comment #3 from Werner Lueckel ---
Created attachment 142155
--> https://bugs.freedesktop.org/attachment.cgi?id=142155&action=edit
dmesg Ubuntu18.04, Kernel4.15.0-36, radeon 2.50.0, screen flickering
--
You are receiving this mail becaus
https://bugs.freedesktop.org/show_bug.cgi?id=108514
--- Comment #2 from Werner Lueckel ---
Created attachment 142154
--> https://bugs.freedesktop.org/attachment.cgi?id=142154&action=edit
dmesg Ubuntu14.04, Kernel3.13.0-160, radeon 2.36.0, screen O.K.
--
You are receiving this mail because:
Yo
https://bugs.freedesktop.org/show_bug.cgi?id=108493
--- Comment #8 from Timur Kristóf ---
Upgraded to kernel 4.18.16 and mesa 18.2.3 which is supposed to fix a GPU hang.
Did not help, the problem is still there.
--
You are receiving this mail because:
You are the assignee for the bug.__
https://bugs.freedesktop.org/show_bug.cgi?id=108493
--- Comment #7 from Timur Kristóf ---
1. It was suggested that this is a thermal issue. So I monitored the GPU
temperatures with GALLIUM_HUD and it was about 40 Celsius when the crash
happened.
2. It was also suggested that this is a VRAM memor
https://bugs.freedesktop.org/show_bug.cgi?id=108521
Robert Strube changed:
What|Removed |Added
Attachment #142151|dmesg log booting system|dmesg log booting system
descrip
https://bugs.freedesktop.org/show_bug.cgi?id=108521
--- Comment #2 from Robert Strube ---
Created attachment 142151
--> https://bugs.freedesktop.org/attachment.cgi?id=142151&action=edit
dmesg log booting system with eGPU attched and powered
Starting at line:
[ 11.192733] ATOM BIOS: 401815-1
On Tue, 23 Oct 2018 at 16:14, Emil Velikov wrote:
>
> From: Emil Velikov
>
> Simply make use of the function, instead of duplicating it.
>
Please ignore this and the other three DIM patches. Seemingly git
workspaces cannot have different sendemail.to :-\
-Emil
___
From: Emil Velikov
Seems like some of my existing URLs had a trailing forward slash.
This confused url_to_remote(), resulting in adding the exact same repo
again.
Signed-off-by: Emil Velikov
---
dim | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/dim b/dim
index 93e90a4f96d
From: Emil Velikov
Currently we check for $DIM_CONFIG, falling back to $HOME/.dimrc.
Instead of always setting DIM_CONFIG, add support for XDG_CONFIG_HOME
aka ~/.config.
Now we get $DIM_CONFIG > $XDG_CONFIG_HOME/dim/config > $HOME/.dimrc
Ideally in the future we'll:
a) warn and kill off the l
From: Emil Velikov
Simply make use of the function, instead of duplicating it.
Signed-off-by: Emil Velikov
---
dim | 7 +--
1 file changed, 1 insertion(+), 6 deletions(-)
diff --git a/dim b/dim
index 8be504e46995..21e1e0d6ed45 100755
--- a/dim
+++ b/dim
@@ -2026,12 +2026,7 @@ function dim
On Mon, Oct 22, 2018 at 9:46 PM Koenig, Christian
wrote:
>
> Am 18.10.18 um 17:37 schrieb :
> > If the hardware queue for a scheduler is empty then we don't
> > need to the shift the entities from their current scheduler
> > as they are not getting scheduled because of some dependency.
>
> That is
Le lun. 15 oct. 2018 à 13:15, Benjamin Gaignard
a écrit :
>
> Le lun. 24 sept. 2018 à 13:59, Yannick Fertré a écrit
> :
> >
> > Add missing flags for pixel clock & data enable polarities.
> > These flags are similar to other synchronization signals (hsync, vsync...).
> >
> > Signed-off-by: Yanni
https://bugs.freedesktop.org/show_bug.cgi?id=108521
--- Comment #1 from Alex Deucher ---
Please attach your dmesg output.
--
You are receiving this mail because:
You are the assignee for the bug.___
dri-devel mailing list
dri-devel@lists.freedesktop.o
On 10/22/2018 05:33 AM, Koenig, Christian wrote:
> Am 19.10.18 um 22:52 schrieb Andrey Grodzovsky:
>> Problem:
>> A particular scheduler may become unsuable (underlying HW) after
>> some event (e.g. GPU reset). If it's later chosen by
>> the get free sched. policy a command will fail to be
>> sub
On 10/23/2018 05:23 AM, Christian König wrote:
> Am 22.10.18 um 22:46 schrieb Andrey Grodzovsky:
>> Start using drm_gpu_scheduler.ready isntead.
>>
>> v3:
>> Add helper function to run ring test and set
>> sched.ready flag status accordingly, clean explicit
>> sched.ready sets from the IP specifi
Hi Daniel,
On Tuesday, 23 October 2018 16:40:41 EEST Daniel Vetter wrote:
> On Mon, Oct 22, 2018 at 01:51:35PM +0530, Souptick Joarder wrote:
> > On Thu, Oct 11, 2018 at 1:48 PM Daniel Vetter wrote:
> >> On Mon, Oct 08, 2018 at 09:57:52PM +0530, Souptick Joarder wrote:
> >>> On Mon, Oct 1, 2018 a
https://bugzilla.kernel.org/show_bug.cgi?id=201273
--- Comment #7 from quirin.blae...@freenet.de ---
Bug is still alive. v4.19
--
You are receiving this mail because:
You are watching the assignee of the bug.
___
dri-devel mailing list
dri-devel@lists.
On Tue, Oct 23, 2018 at 08:54:36AM -0400, Sean Paul wrote:
> On Thu, Oct 18, 2018 at 7:11 PM Mamta Shukla wrote:
> >
> > Use PTR_ERR_OR_ZERO rather than if(IS_ERR(...)) + PTR_ERR because its
> > better to have inlined function rather than code-opened implementation.
> >
> > Signed-off-by: Mamta Sh
On Tue, Oct 23, 2018 at 09:32:22AM +0530, Souptick Joarder wrote:
> Replace dma_alloc_coherent + memset with dma_zalloc_coherent.
>
> Signed-off-by: Souptick Joarder
Applied, thanks for your patch.
-Daniel
> ---
> drivers/gpu/drm/drm_pci.c | 5 ++---
> 1 file changed, 2 insertions(+), 3 deleti
https://bugs.freedesktop.org/show_bug.cgi?id=108329
--- Comment #5 from John Galt ---
(In reply to Nicholas Kazlauskas from comment #4)
> 1. Is the high pitch audio loud relative to the rest of the output?
> 2. If you're using speakers, are they internal to the TV/monitor?
> 3. Does the high pitc
On Mon, Oct 22, 2018 at 11:32:10AM +0100, Alexandru-Cosmin Gheorghe wrote:
> On Fri, Oct 19, 2018 at 05:29:15PM +0200, Daniel Vetter wrote:
> > On Fri, Oct 19, 2018 at 11:57:52AM +0100, Alexandru Gheorghe wrote:
> > > Add selftests for the following newly added functions:
> > > - drm_format_info_b
On Mon, Oct 22, 2018 at 04:15:48PM +0200, Noralf Trønnes wrote:
>
> Den 17.10.2018 17.46, skrev Daniel Vetter:
> > On Wed, Oct 17, 2018 at 03:04:53PM +0200, Noralf Trønnes wrote:
> > > This adds a library for shmem backed GEM objects.
> > >
> > > v5:
> > > - Drop drm_gem_shmem_prime_mmap() (Danie
On Mon, Oct 22, 2018 at 02:57:28PM +0200, Christian König wrote:
> Am 17.10.18 um 15:04 schrieb Noralf Trønnes:
> > This adds an optional function table on GEM objects.
> > The main benefit is for drivers that support more than one type of
> > memory (shmem,vram,cma) for their buffers depending on
On Tue, Oct 23, 2018 at 09:55:08AM +0200, Boris Brezillon wrote:
> Hi Daniel,
>
> On Tue, 16 Oct 2018 14:57:43 +0200
> Daniel Vetter wrote:
>
> > On Tue, Oct 16, 2018 at 11:40:45AM +0200, Boris Brezillon wrote:
> > > The HVS block is supposed to fill the pixelvalve FIFOs fast enough to
> > > mee
On Tue, Oct 23, 2018 at 11:01:14AM +, Eugeniy Paltsev wrote:
> Hi David,
>
> Maybe you have any comments or remarks about this patch?
> And if you don't could you please apply it. Thanks!
Hm I hoped Sean would pick this up. I stuffed it into drm-misc-next now,
and Sean owes me one. Generally
On 2018-10-23 2:20 p.m., Christian König wrote:
> Ping once more! Adding a few more AMD people.
>
> Any comments on this?
Patches 1 & 3 are a bit over my head I'm afraid.
Patches 2, 4, 6-8 are
Reviewed-by: Michel Dänzer
--
Earthling Michel Dänzer | http://www.am
On Mon, Oct 22, 2018 at 01:51:35PM +0530, Souptick Joarder wrote:
> Hi Laurent,
>
> On Thu, Oct 11, 2018 at 1:48 PM Daniel Vetter wrote:
> >
> > On Mon, Oct 08, 2018 at 09:57:52PM +0530, Souptick Joarder wrote:
> > > Hi Laurent,
> > > On Mon, Oct 1, 2018 at 6:12 PM Noralf Trønnes wrote:
> > > >
On 2018-10-04 3:12 p.m., Christian König wrote:
> It is perfectly possible that the BO list is created before the BO is
> exported. While at it cleanup setting shared to one instead of true.
"clean up"
> v2: add comment and simplify logic
>
> Signed-off-by: Christian König
As this is a bug fi
https://bugs.freedesktop.org/show_bug.cgi?id=108486
Andi changed:
What|Removed |Added
Status|RESOLVED|VERIFIED
--- Comment #4 from Andi ---
I tested
https://bugs.freedesktop.org/show_bug.cgi?id=108329
--- Comment #4 from Nicholas Kazlauskas ---
1. Is the high pitch audio loud relative to the rest of the output?
2. If you're using speakers, are they internal to the TV/monitor?
3. Does the high pitch audio also occur during desktop idle?
--
Y
On Thu, Oct 18, 2018 at 7:11 PM Mamta Shukla wrote:
>
> Use PTR_ERR_OR_ZERO rather than if(IS_ERR(...)) + PTR_ERR because its
> better to have inlined function rather than code-opened implementation.
>
> Signed-off-by: Mamta Shukla
Reviewed-by: Sean Paul
> ---
> drivers/gpu/drm/msm/adreno/a5x
On Tue, 23 Oct 2018 at 00:57, Rodrigo Siqueira
wrote:
>
> On 10/22, Emil Velikov wrote:
> > Hi all,
>
> Hi Emil,
>
> Thanks for your feedback.
>
> > On Tue, 22 May 2018 at 02:07, Rodrigo Siqueira
> > wrote:
> >
> > > +// SPDX-License-Identifier: GPL-2.0
> >
> > This
> >
> > > +/*
> > > + * This p
Ping once more! Adding a few more AMD people.
Any comments on this?
Thanks,
Christian.
Am 12.10.18 um 10:22 schrieb Christian König:
Ping! Adding a few people directly and more mailing lists.
Can I get an acked-by/rb for this? It's only a cleanup and not much
functional change.
Regards,
Ch
Am 23.10.18 um 11:37 schrieb Chunming Zhou:
> v2:
> add a mutex between sync_cb execution and free.
> v3:
> clearly separating the roles for pt_lock and cb_mutex (Chris)
> v4:
> the cb_mutex should be taken outside of the pt_lock around
> this if() block. (Chris)
> v5:
> fix a corner case
> v6:
> t
https://bugs.freedesktop.org/show_bug.cgi?id=108323
--- Comment #2 from Christian Widmer ---
This is most likely the same issue I encountered some time ago with my RX 580,
which is also a Sapphire Nitro+ (Special Edition but that should not matter). I
opened a bug report on the kernel bugzilla ba
On Tue, 2018-10-23 at 13:39 +0200, Maarten Lankhorst wrote:
>
> Op 02-10-18 om 13:15 schreef Stanislav Lisovskiy:
> > PLANE_CTL_FORMAT_AYUV is already supported, according to hardware
> > specification.
> >
> > v2: Edited commit message, removed redundant whitespaces.
> >
> > v3: Fixed fallthrou
Op 02-10-18 om 13:15 schreef Stanislav Lisovskiy:
> PLANE_CTL_FORMAT_AYUV is already supported, according to hardware
> specification.
>
> v2: Edited commit message, removed redundant whitespaces.
>
> v3: Fixed fallthrough logic for the format switch cases.
>
> v4: Yet again fixed fallthrough log
Hi David,
Maybe you have any comments or remarks about this patch?
And if you don't could you please apply it. Thanks!
On Fri, 2018-09-28 at 17:41 +0300, Eugeniy Paltsev wrote:
> UDL doesn't support vblank functionality so we don't need to
> initialize vblank here (we are able to send page flip
>
https://bugs.freedesktop.org/show_bug.cgi?id=108486
Petri Latvala changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://bugs.freedesktop.org/show_bug.cgi?id=108347
--- Comment #4 from Nicolai Hähnle ---
Thanks for keeping an eye out for performance :)
The difference in settings isn't only about nir, but also sisched and noerror.
Still a curious observation.
That said, with default settings, the patch see
Hi,
Le mercredi 10 octobre 2018 à 16:58 +0200, Maxime Ripard a écrit :
> On Wed, Oct 10, 2018 at 01:41:32PM +0200, Paul Kocialkowski wrote:
> > This adds support for the 3.5" LCD panel from Lemaker, sold for use with
> > BananaPi boards. It comes with a 24-bit RGB888 parallel interface and
> > req
On Tue, 23 Oct 2018, Souptick Joarder wrote:
> On Fri, Oct 19, 2018 at 9:30 PM Sabyasachi Gupta
> wrote:
>>
>> Replaced kmem_cache_alloc + memset with kmem_cache_zalloc
>
> Put a new line gap in between these two lines and send v2.
Nah, the maintainers can trivially add the newline while
applyin
v2:
add a mutex between sync_cb execution and free.
v3:
clearly separating the roles for pt_lock and cb_mutex (Chris)
v4:
the cb_mutex should be taken outside of the pt_lock around
this if() block. (Chris)
v5:
fix a corner case
v6:
tidy drm_syncobj_fence_get_or_add_callback up. (Chris)
Tested by s
Hi,
Le mercredi 10 octobre 2018 à 16:57 +0200, Maxime Ripard a écrit :
> On Wed, Oct 10, 2018 at 01:41:31PM +0200, Paul Kocialkowski wrote:
> > Some panels need an active-low data enable (DE) signal for the RGB
> > interface. This requires flipping a bit in the TCON0 polarity register
> > when set
Am 23.10.18 um 11:11 schrieb Chris Wilson:
> Quoting zhoucm1 (2018-10-23 10:09:01)
>>
>> On 2018年10月23日 17:01, Chris Wilson wrote:
>>> Quoting Chunming Zhou (2018-10-23 08:57:54)
v2:
add a mutex between sync_cb execution and free.
v3:
clearly separating the roles for pt_lock and
Am 22.10.18 um 22:46 schrieb Andrey Grodzovsky:
Start using drm_gpu_scheduler.ready isntead.
v3:
Add helper function to run ring test and set
sched.ready flag status accordingly, clean explicit
sched.ready sets from the IP specific files.
Signed-off-by: Andrey Grodzovsky
---
[SNIP]
+
+int a
Am 23.10.18 um 08:22 schrieb Thomas Zimmermann:
Hi Christian
Am 19.10.18 um 18:41 schrieb Christian König:
As the name says we only need one global instance of ttm_mem_global.
Drop all the driver initialization and just use a single exported
instance which is initialized during BO global initi
Quoting zhoucm1 (2018-10-23 10:09:01)
>
>
> On 2018年10月23日 17:01, Chris Wilson wrote:
> > Quoting Chunming Zhou (2018-10-23 08:57:54)
> >> v2:
> >> add a mutex between sync_cb execution and free.
> >> v3:
> >> clearly separating the roles for pt_lock and cb_mutex (Chris)
> >> v4:
> >> the cb_mute
On 2018年10月23日 17:01, Chris Wilson wrote:
Quoting Chunming Zhou (2018-10-23 08:57:54)
v2:
add a mutex between sync_cb execution and free.
v3:
clearly separating the roles for pt_lock and cb_mutex (Chris)
v4:
the cb_mutex should be taken outside of the pt_lock around this if() block.
(Chris)
v
Quoting Chunming Zhou (2018-10-23 08:57:54)
> v2:
> add a mutex between sync_cb execution and free.
> v3:
> clearly separating the roles for pt_lock and cb_mutex (Chris)
> v4:
> the cb_mutex should be taken outside of the pt_lock around this if() block.
> (Chris)
> v5:
> fix a corner case
>
> Tes
Quoting zhoucm1 (2018-10-23 09:00:26)
>
>
> On 2018年10月23日 15:51, Chris Wilson wrote:
> > Quoting Chunming Zhou (2018-10-23 02:50:08)
> >> v2:
> >> add a mutex between sync_cb execution and free.
> >> v3:
> >> clearly separating the roles for pt_lock and cb_mutex (Chris)
> >> v4:
> >> the cb_mute
https://bugs.freedesktop.org/show_bug.cgi?id=107334
--- Comment #9 from Christian Widmer ---
Out of curiosity I just tested it with kernel 4.18.14 and could not reproduce
the issue there, either. This most likely means it was some other update in the
meantime. I recently updated libdrm from versi
On 2018年10月23日 15:51, Chris Wilson wrote:
Quoting Chunming Zhou (2018-10-23 02:50:08)
v2:
add a mutex between sync_cb execution and free.
v3:
clearly separating the roles for pt_lock and cb_mutex (Chris)
v4:
the cb_mutex should be taken outside of the pt_lock around this if() block.
(Chris)
v2:
add a mutex between sync_cb execution and free.
v3:
clearly separating the roles for pt_lock and cb_mutex (Chris)
v4:
the cb_mutex should be taken outside of the pt_lock around this if() block.
(Chris)
v5:
fix a corner case
Tested by syncobj_basic and syncobj_wait of igt.
Signed-off-by: Chun
Hi Daniel,
On Tue, 16 Oct 2018 14:57:43 +0200
Daniel Vetter wrote:
> On Tue, Oct 16, 2018 at 11:40:45AM +0200, Boris Brezillon wrote:
> > The HVS block is supposed to fill the pixelvalve FIFOs fast enough to
> > meet the requested framerate. The problem is, the HVS and memory bus
> > bandwidths
Quoting Chunming Zhou (2018-10-23 02:50:08)
> v2:
> add a mutex between sync_cb execution and free.
> v3:
> clearly separating the roles for pt_lock and cb_mutex (Chris)
> v4:
> the cb_mutex should be taken outside of the pt_lock around this if() block.
> (Chris)
>
> Tested by syncobj_basic and s
This adds the device tree bindings for the Samsung S6D16D0
panel. This is a command mode only panel using DSI.
Cc: devicet...@vger.kernel.org
Cc: Andrzej Hajda
Acked-by: Sam Ravnborg
Reviewed-by: Rob Herring
Signed-off-by: Linus Walleij
---
ChangeLog v2->v3:
- Collected Sam's ACK.
- Collected
1 - 100 of 116 matches
Mail list logo
