On 2018-10-09 11:07, Sean Paul wrote:
On Mon, Oct 08, 2018 at 09:27:18PM -0700, Jeykumar Sankaran wrote:
Layer mixer/pingpong block counts and hw ctl block counts
will not be same for all the topologies (e.g. layer
mixer muxing to single interface)
Use the encoder's split_role info to retrieve
https://bugs.freedesktop.org/show_bug.cgi?id=108309
Bug ID: 108309
Summary: Raven Ridge 2700U system lock-up on multiple games
Product: DRI
Version: unspecified
Hardware: Other
OS: All
Status: NEW
https://bugs.freedesktop.org/show_bug.cgi?id=108307
--- Comment #4 from Samantha McVey ---
I just tested on the latest git (v4.19-rc7-15-g64c5e530ac2c) and I didn't see
any issues. So the issue has been either fixed between 4.19-rc7 and latest git
or something in the kernel config is different.
Hi Sravanthi,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on robclark/msm-next]
[also build test ERROR on next-20181009]
[cannot apply to v4.19-rc7]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https
Hi Jeykumar,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on robclark/msm-next]
[also build test ERROR on next-20181009]
[cannot apply to v4.19-rc7]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https
https://bugs.freedesktop.org/show_bug.cgi?id=108014
Lyude Paul changed:
What|Removed |Added
Summary|AMD WX4150 - MST is |AMD WX4150 - Hotplugging on
https://bugs.freedesktop.org/show_bug.cgi?id=108307
--- Comment #3 from Samantha McVey ---
I was able to get something on the screen when I added "pci=noacpi" (this was
without blacklisting amdgpu).
[Firmware Bug]: AMD-Vi: No southbridge IOAPIC fonud
AMD-Vi: Disabling interrupt remapping
https://bugs.freedesktop.org/show_bug.cgi?id=108307
--- Comment #2 from Samantha McVey ---
Created attachment 141966
--> https://bugs.freedesktop.org/attachment.cgi?id=141966=edit
Booting with pci noacpi
--
You are receiving this mail because:
You are the assignee for the
https://bugs.freedesktop.org/show_bug.cgi?id=108307
--- Comment #1 from Alex Deucher ---
Can you bisect? If you set modprobe.blacklist=amdgpu on the kernel command
line in grub and you are still getting a problem, it's an issue outside of the
graphics driver. If so, does setting pci=noacpi
https://bugs.freedesktop.org/show_bug.cgi?id=108307
Bug ID: 108307
Summary: Regression: Raven Ridge 2700U does not boot with
4.19-rc7
Product: DRI
Version: XOrg git
Hardware: Other
OS: All
> drivers/gpu/drm/selftests/drm_damage_helper_selftests.h
> > create mode 100644 drivers/gpu/drm/selftests/test-
> drm_damage_helper.c
> >
> > diff --git a/drivers/gpu/drm/selftests/Makefile
> b/drivers/gpu/drm/selftests/Makefile
> > index 9fc349fa18e9..88ac216f5962 100644
> > ---
On Tue, 2018-10-09 at 15:20 -0700, Manasi Navare wrote:
> On Fri, Oct 05, 2018 at 07:34:35PM -0400, Lyude Paul wrote:
> > On Fri, 2018-10-05 at 16:23 -0700, Manasi Navare wrote:
> > > DSC can be supported per DP connector. This patch adds a per connector
> > > debugfs node to expose DSC support
On Fri, Oct 05, 2018 at 07:34:35PM -0400, Lyude Paul wrote:
> On Fri, 2018-10-05 at 16:23 -0700, Manasi Navare wrote:
> > DSC can be supported per DP connector. This patch adds a per connector
> > debugfs node to expose DSC support capability by the kernel.
> > The same node can be used from
Hi Jeykumar,
Thank you for the patch! Perhaps something to improve:
[auto build test WARNING on robclark/msm-next]
[also build test WARNING on next-20181009]
[cannot apply to v4.19-rc7]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url
https://bugzilla.kernel.org/show_bug.cgi?id=201273
--- Comment #2 from quirin.blae...@freenet.de ---
Created attachment 278973
--> https://bugzilla.kernel.org/attachment.cgi?id=278973=edit
dmesg old + new
The RX560 is new. Error happens only from time to time and only at bootup and i
have to
Add optional cleanup function on master level. This allows the
master to call framework level cleanup functions in case binding
of any component failed before the previously successfully bound
components get unbound.
Signed-off-by: Stefan Agner
---
Hi,
This is an attempt to fix the issue
In situations where a component fails to bind, a previously
successfully bound component might already registered itself
with the DRM framework (e.g. an encoder). When the master
component then calls drm_mode_config_cleanup, we end up in a
use after free sitution.
Use the cleanup callback to make
On Tue, Oct 09, 2018 at 01:56:04PM -0400, Ilia Mirkin wrote:
> On Tue, Oct 9, 2018 at 1:40 PM Laurent Pinchart
> wrote:
> > commit 9c305eb442f3b371fc722ade827bbf673514123e
> > Author: Neil Armstrong
> > Date: Fri Feb 23 12:44:37 2018 +0100
> >
> > drm: bridge: dw-hdmi: Fix overflow
On Mon, Oct 08, 2018 at 09:27:24PM -0700, Jeykumar Sankaran wrote:
> DPU maintained reservation lists to cache assigned
> HW blocks for the display and a retrieval mechanism for
> the individual DRM components to query their respective
> HW blocks.
>
> This patch uses the sub-classed CRTC state
https://bugs.freedesktop.org/show_bug.cgi?id=108139
--- Comment #3 from Duncan Roe ---
Created attachment 141963
--> https://bugs.freedesktop.org/attachment.cgi?id=141963=edit
dmesg output as requested
Added dmesg output as requested
--
You are receiving this mail because:
You are the
It appears when testing my previous fix for some of the legacy
modesetting issues with MST, I misattributed some kernel splats that
started appearing on my machine after a rebase as being from upstream.
But it appears they actually came from my patch series:
[2.980512]
On Mon, Oct 08, 2018 at 09:27:39PM -0700, Jeykumar Sankaran wrote:
> Instead of letting encoder make a centralized reservation for
> all of its display DRM components, this path splits the
> responsibility between CRTC and Encoder, each requesting
> RM for the HW mapping of its own domain.
>
>
On Mon, Oct 08, 2018 at 09:27:23PM -0700, Jeykumar Sankaran wrote:
> struct dpu_hw_blk has hw block type info. Remove duplicate
> type tracking in struct dpu_rm_hw_blk.
>
> Signed-off-by: Jeykumar Sankaran
> ---
> drivers/gpu/drm/msm/disp/dpu1/dpu_rm.c | 17 -
> 1 file changed,
On Tue, Oct 9, 2018 at 5:56 AM Maxime Ripard wrote:
>
> On Fri, Oct 05, 2018 at 12:02:22PM -0400, Sean Paul wrote:
> > Unfortunately Gustavo has decided to step down as drm-misc maintainer to
> > focus on other projects. Thanks Gustavo for your dedication and hard work!
> >
> > Fortunately for
From: Sean Paul
state->connector is just a backpointer to conn with the added risk of
state being NULL.
Signed-off-by: Sean Paul
---
drivers/gpu/drm/msm/disp/dpu1/dpu_encoder.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/gpu/drm/msm/disp/dpu1/dpu_encoder.c
On Mon, Oct 08, 2018 at 09:27:22PM -0700, Jeykumar Sankaran wrote:
> Not actively used. Clean up the crtc mixer struct.
>
> Signed-off-by: Jeykumar Sankaran
Reviewed-by: Sean Paul
> ---
> drivers/gpu/drm/msm/disp/dpu1/dpu_crtc.c | 2 --
> drivers/gpu/drm/msm/disp/dpu1/dpu_crtc.h | 2 --
> 2
On Mon, Oct 08, 2018 at 09:27:21PM -0700, Jeykumar Sankaran wrote:
> Definition was removed already. Clean up header declaration.
>
> Signed-off-by: Jeykumar Sankaran
Reviewed-by: Sean Paul
> ---
> drivers/gpu/drm/msm/disp/dpu1/dpu_rm.h | 8
> 1 file changed, 8 deletions(-)
>
>
Hi Dave,
Fix for armv7 u64 division
The following changes since commit 3ce36b4542b585ed0231b175aee31020b2f289c2:
drm/msm/a6xx: Remove CP perfcounter selects from the protected list
(2018-10-07 14:40:28 -0400)
are available in the Git repository at:
On Mon, Oct 08, 2018 at 09:27:20PM -0700, Jeykumar Sankaran wrote:
> Not used. Remove from RM.
>
> Signed-off-by: Jeykumar Sankaran
Reviewed-by: Sean Paul
> ---
> drivers/gpu/drm/msm/disp/dpu1/dpu_kms.c | 3 +--
> drivers/gpu/drm/msm/disp/dpu1/dpu_rm.c | 7 ++-
>
On Mon, Oct 08, 2018 at 09:27:19PM -0700, Jeykumar Sankaran wrote:
> RM was equipped with reservation tracking structure RSVP
> to cache HW reservation of displays for certain clients
> where atomic_checks (atomic commit with TEST_ONLY) for all
> the displays are called before their respective
On Mon, Oct 08, 2018 at 09:27:41PM -0700, Jeykumar Sankaran wrote:
> Since HW reservations are happening through atomic_check
> and all the display commits are catered by a single commit thread,
> it is not necessary to protect the interfaces by a separate
> mutex.
>
> Signed-off-by: Jeykumar
Boris Brezillon writes:
> When vc4_plane_state is duplicated ->is_yuv is left assigned to its
> previous value, and we never set it back to false when switching to
> a non-YUV format.
>
> Fix that by setting ->is_yuv to false in the 'num_planes == 1' branch
> of the
Hi Linus.
Few comments below, nothing serious.
On Mon, Oct 08, 2018 at 12:58:52PM +0200, Linus Walleij wrote:
> The Samsung S6D16D0 is a simple comman mode only DSI display
s/comman/command/
> that is used on the ST-Ericsson Ux500 reference design
> TVK1281618 user interface board (UIB).
>
>
On Tue, Oct 09, 2018 at 05:32:49PM +0300, Jani Nikula wrote:
> On Tue, 09 Oct 2018, Ville Syrjälä wrote:
> > On Mon, Oct 08, 2018 at 05:23:51PM -0700, Manasi Navare wrote:
> >> VESA eDP 1.4 specification has separate fields defined in
> >> EDP_DPCD_REV for eDP 1.4a and 1.4b eDP revisions.
> >>
On Tue, Oct 09, 2018 at 04:43:51PM +0300, Ville Syrjälä wrote:
> On Mon, Oct 08, 2018 at 05:23:51PM -0700, Manasi Navare wrote:
> > VESA eDP 1.4 specification has separate fields defined in
> > EDP_DPCD_REV for eDP 1.4a and 1.4b eDP revisions.
> > This patch defines those. Found this when one of
On Mon, Oct 08, 2018 at 09:27:17PM -0700, Jeykumar Sankaran wrote:
> Submitting series of patches to clean up DPU resource manager (RM)
> of complicated hw iterations, redundant data maintenence and eventually
> modifying the DPU to reserve display HW blocks only in atomic check
> and caching the
On Mon, Oct 08, 2018 at 01:00:05PM +0200, Linus Walleij wrote:
> 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
> Signed-off-by: Linus Walleij
> ---
> .../display/panel/samsung,s6d16d0.txt
Thanks for the review.
Pushed to drm-misc.
Manasi
On Wed, Oct 03, 2018 at 09:32:49PM +0200, Daniel Vetter wrote:
> On Tue, Oct 02, 2018 at 02:50:55PM -0700, Manasi Navare wrote:
> > This patch explains the DRM_MODE_PROP_IMMUTABLE flag a bit better
> > by telling which function to call if kernel
https://bugs.freedesktop.org/show_bug.cgi?id=106519
--- Comment #26 from Cristian Ciupitu ---
For what it's worth, the name of the Xorg driver package is xorg-x11-drv-amdgpu
on Fedora.
--
You are receiving this mail because:
You are the assignee for the
On Tue, Oct 9, 2018 at 10:29 AM Andrzej Hajda wrote:
> On 08.10.2018 12:58, Linus Walleij wrote:
> > +static const struct drm_display_mode samsung_s6d16d0_mode = {
> > + .clock = 420160, /* HS 420160kHz, LP 19200kHz */
> > + .hdisplay = 864,
> > + .hsync_start = 864 + 154,
> > +
Hi,
I need to setup a three monitor system on an Intel based
touchscreen POS machine using separate X screens so standalone
fullscreen apps can be shown on each screen.
Using the Intel driver with two Section "Device" with Driver "intel"
and different ZaphodHeads settings work so I can have
https://bugzilla.kernel.org/show_bug.cgi?id=201275
Cristian Aravena Romero (carav...@gmail.com) changed:
What|Removed |Added
CC|
On 2018-10-09 09:50, Jordan Crouse wrote:
On Mon, Oct 08, 2018 at 09:27:35PM -0700, Jeykumar Sankaran wrote:
we don't have enough reasons why the HW block looping's
cannot happen in the same function. So merge them.
looping's -> looping. So there are reasons one might break them out
but not
On 2018-10-09 07:24, Sean Paul wrote:
On Mon, Oct 08, 2018 at 04:55:45PM -0700, Jeykumar Sankaran wrote:
While creating display and event threads per crtc, validate
them before setting their priorities.
changes in v2:
- use dev_warn (Abhinav Kumar)
changes in v3:
- fix
On Mon, Oct 08, 2018 at 09:27:18PM -0700, Jeykumar Sankaran wrote:
> Layer mixer/pingpong block counts and hw ctl block counts
> will not be same for all the topologies (e.g. layer
> mixer muxing to single interface)
>
> Use the encoder's split_role info to retrieve the
> respective control path
On Tue, Oct 9, 2018 at 1:40 PM Laurent Pinchart
wrote:
>
> Hi Jernej,
>
> Thank you for the patch.
>
> On Sunday, 7 October 2018 12:38:51 EEST Jernej Skrabec wrote:
> > It turns out that even new DW HDMI controllers exhibits same magenta
> > line issues as older versions.
> >
> > Enable
https://bugs.freedesktop.org/show_bug.cgi?id=108272
--- Comment #8 from Jan Vesely ---
(In reply to jamespharvey20 from comment #7)
> Regarding Luxmark, do you know with MAX_GLOBAL_BUFFERS set to 32, is it
> merely that many pixels will be shown wrong? Are the benchmark results
> valid, or with
Hi Jernej,
Thank you for the patch.
On Sunday, 7 October 2018 12:38:51 EEST Jernej Skrabec wrote:
> It turns out that even new DW HDMI controllers exhibits same magenta
> line issues as older versions.
>
> Enable workaround for v2.12a.
This doesn't affect the platforms I maintain, so I can't
https://bugzilla.kernel.org/show_bug.cgi?id=201273
Alex Deucher (alexdeuc...@gmail.com) changed:
What|Removed |Added
CC|
On Mon, Oct 08, 2018 at 07:24:30PM -0400, Lyude Paul wrote:
> With the exception of modesets which would switch the DPMS state of a
> connector from on to off, we want to make sure that we disallow all
> modesets which would result in enabling a new monitor or a new mode
> configuration on a
On Mon, Oct 08, 2018 at 05:44:08PM +0800, Bin Meng wrote:
> On Thu, Oct 4, 2018 at 4:12 AM Bjorn Helgaas wrote:
> > On Thu, Sep 27, 2018 at 10:10:07AM +0800, Bin Meng wrote:
> > > On Thu, Sep 27, 2018 at 12:57 AM Bjorn Helgaas wrote:
> > > > On Wed, Sep 26, 2018 at 08:14:01AM -0700, Bin Meng
On Mon, Oct 08, 2018 at 09:27:35PM -0700, Jeykumar Sankaran wrote:
> we don't have enough reasons why the HW block looping's
> cannot happen in the same function. So merge them.
looping's -> looping. So there are reasons one might break them out
but not interesting ones?
> Signed-off-by:
On Mon, Oct 08, 2018 at 09:27:27PM -0700, Jeykumar Sankaran wrote:
> hw_mdp block is common for displays. No need
> to reserve per display.
>
> Signed-off-by: Jeykumar Sankaran
> ---
> drivers/gpu/drm/msm/disp/dpu1/dpu_kms.c | 7 ++-
> drivers/gpu/drm/msm/disp/dpu1/dpu_rm.c | 20
On Tue, Oct 9, 2018 at 8:20 PM Christian König
wrote:
>
> We need to make sure that we don't race between job completion and
> timeout.
>
> v2: put revert label after calling the handling manually
>
> Signed-off-by: Christian König
Reviewed-by: Nayan Deshmukh
> ---
>
On Tue, Oct 9, 2018 at 8:20 PM Christian König
wrote:
>
> Cleanup starting the timeout a bit.
>
> Signed-off-by: Christian König
Reviewed-by: Nayan Deshmukh
> ---
> drivers/gpu/drm/scheduler/sched_main.c | 29 +
> 1 file changed, 17 insertions(+), 12 deletions(-)
>
On Mon, Oct 08, 2018 at 09:27:18PM -0700, Jeykumar Sankaran wrote:
> Layer mixer/pingpong block counts and hw ctl block counts
> will not be same for all the topologies (e.g. layer
> mixer muxing to single interface)
>
> Use the encoder's split_role info to retrieve the
> respective control path
On Mon, Oct 08, 2018 at 04:28:41PM +0200, Jernej Škrabec wrote:
> Dne ponedeljek, 08. oktober 2018 ob 12:18:28 CEST je Maxime Ripard napisal(a):
> > Hi,
> >
> > On Sun, Oct 07, 2018 at 11:38:46AM +0200, Jernej Skrabec wrote:
> > > In preparation to introduce DE3 support, change prefix from
Hi Jeykumar,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on robclark/msm-next]
[also build test ERROR on v4.19-rc7 next-20181009]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day-ci
https://bugs.freedesktop.org/show_bug.cgi?id=108130
Martin Peres changed:
What|Removed |Added
Status|RESOLVED|CLOSED
--- Comment #3 from Martin Peres
Hi Bart,
CC debian-68k, linux-m68k
On Tue, Oct 9, 2018 at 5:00 PM Bart Van Assche wrote:
> On Tue, 2018-10-09 at 13:51 +, Christophe Leroy wrote:
> > _PAGE_WRITETHRU is a target specific flag. Prefer generic functions.
> >
> > Acked-by: Geert Uytterhoeven
> > Signed-off-by: Christophe
On Tue, 09 Oct 2018, Ville Syrjälä wrote:
> On Mon, Oct 08, 2018 at 05:23:51PM -0700, Manasi Navare wrote:
>> VESA eDP 1.4 specification has separate fields defined in
>> EDP_DPCD_REV for eDP 1.4a and 1.4b eDP revisions.
>> This patch defines those. Found this when one of my eDP panels
>>
On Mon, Oct 08, 2018 at 04:55:45PM -0700, Jeykumar Sankaran wrote:
> While creating display and event threads per crtc, validate
> them before setting their priorities.
>
> changes in v2:
> - use dev_warn (Abhinav Kumar)
> changes in v3:
> - fix compilation error
>
> Change-Id:
https://bugs.freedesktop.org/show_bug.cgi?id=107978
--- Comment #8 from Shmerl ---
Created attachment 141960
--> https://bugs.freedesktop.org/attachment.cgi?id=141960=edit
dmesg with drm.debug=4 and Xorg.0.log
Attaching logs.
--
You are receiving this mail because:
You are the assignee for
https://bugs.freedesktop.org/show_bug.cgi?id=107978
--- Comment #7 from Shmerl ---
I'm using KDE Plasma 5.13.5, current Debian testing x86_64. Can you try it with
Debian? Ubuntu stack is not that close anymore.
I also noticed one detail. When screen mode is chaning (like before sddm comes
up),
On Mon, Oct 08, 2018 at 05:23:51PM -0700, Manasi Navare wrote:
> VESA eDP 1.4 specification has separate fields defined in
> EDP_DPCD_REV for eDP 1.4a and 1.4b eDP revisions.
> This patch defines those. Found this when one of my eDP panels
> advertises eDP 1.4a (04h) in the EDP_DPCD_REV DPCD
On Fri, 28 Sep 2018 16:21:26 -0700
Eric Anholt wrote:
> Fixes an oops reading this debugfs entry on BCM7278.
>
You probably want to add:
Fixes: 57692c94dcbe ("drm/v3d: Introduce a new DRM driver for Broadcom V3D
V3.x+")
Cc:
> Signed-off-by: Eric Anholt
In any case, this is
Reviewed-by:
https://bugs.freedesktop.org/show_bug.cgi?id=108302
Michel Dänzer changed:
What|Removed |Added
See Also||https://bugzilla.kernel.org
On Fri, 28 Sep 2018 16:21:25 -0700
Eric Anholt wrote:
> Since this is UAPI, it's good to document what exactly the guarantees
> we're providing are.
>
> Signed-off-by: Eric Anholt
Reviewed-by: Boris Brezillon
> ---
> include/uapi/drm/v3d_drm.h | 10 ++
> 1 file changed, 10
On Fri, 28 Sep 2018 16:21:24 -0700
Eric Anholt wrote:
> This adds just enough performance counter support to measure the
> clock. We don't have linux kernel drivers for the clock driving the
> HW, and this was useful for determining that the V3D HW is running on
> a slow clock, not that the
When vc4_plane_state is duplicated ->is_yuv is left assigned to its
previous value, and we never set it back to false when switching to
a non-YUV format.
Fix that by setting ->is_yuv to false in the 'num_planes == 1' branch
of the vc4_plane_setup_clipping_and_scaling() function.
Fixes:
https://bugs.freedesktop.org/show_bug.cgi?id=107978
Nicholas Kazlauskas changed:
What|Removed |Added
CC||nicholas.kazlaus...@amd.com
---
https://bugzilla.kernel.org/show_bug.cgi?id=201273
quirin.blae...@freenet.de changed:
What|Removed |Added
Hardware|x86-64 |S390-31
https://bugs.freedesktop.org/show_bug.cgi?id=108139
--- Comment #2 from Nicholas Kazlauskas ---
Do you mind posting a full dmesg log for your 4.18 kernel? It would probably
help to have drm.debug=4 in your boot parameters as well for this.
--
You are receiving this mail because:
You are the
On 10/05/2018 06:10 PM, Manasi Navare wrote:
On Fri, Oct 05, 2018 at 04:39:46PM -0400, Nicholas Kazlauskas wrote:
Modern display hardware is capable of supporting variable refresh rates.
This patch introduces the "vrr_capable" property on the connector to
allow userspace to query support for
On 2018-10-08 14:57, Sravanthi Kollukuduru wrote:
Since the upstream interconnect bus framework has landed
upstream, the existing references of custom bus scaling
needs to be cleaned up.
Signed-off-by: Sravanthi Kollukuduru
---
drivers/gpu/drm/msm/disp/dpu1/dpu_core_perf.c| 157
https://bugs.freedesktop.org/show_bug.cgi?id=108302
Bug ID: 108302
Summary: High GPU temperature after kernel 4.18.0.9.10 on AMD
RX460
Product: DRI
Version: XOrg git
Hardware: Other
OS: All
Cleanup starting the timeout a bit.
Signed-off-by: Christian König
---
drivers/gpu/drm/scheduler/sched_main.c | 29 +
1 file changed, 17 insertions(+), 12 deletions(-)
diff --git a/drivers/gpu/drm/scheduler/sched_main.c
b/drivers/gpu/drm/scheduler/sched_main.c
We need to make sure that we don't race between job completion and
timeout.
v2: put revert label after calling the handling manually
Signed-off-by: Christian König
---
drivers/gpu/drm/scheduler/sched_main.c | 30 +-
1 file changed, 29 insertions(+), 1 deletion(-)
On Mon, Oct 08, 2018 at 05:22:28PM +0100, Colin King wrote:
> From: Colin Ian King
>
> There are several switch statements that are missing break statements.
> Add missing breaks to handle any fall-throughs corner cases.
>
> Detected by CoverityScan, CID#1457175 ("Missing break in switch")
>
>
https://bugs.freedesktop.org/show_bug.cgi?id=107432
--- Comment #11 from Michel Dänzer ---
The patch landed in 4.19-rc1.
--
You are receiving this mail because:
You are the assignee for the bug.___
dri-devel mailing list
On Thu, 27 Sep 2018, Krzysztof Kozlowski wrote:
> The driver for LD9040 AMOLED LCD panel was superseded with DRM driver
> panel-samsung-ld9040.c. It does not support DeviceTree and respective
> possible user (Exynos4210 Universal C210) is DeviceTree-only and uses
> DRM version of driver.
>
>
On Thu, 27 Sep 2018, Krzysztof Kozlowski wrote:
> The driver for S6E63M0 AMOLED LCD panel is not used. It does not
> support DeviceTree and respective possible users (S5Pv210 Aquila and
> Goni boards) are DeviceTree-only.
>
> Suggested-by: Marek Szyprowski
> Cc: Marek Szyprowski
> Cc: Inki
On Fri, Oct 05, 2018 at 12:02:22PM -0400, Sean Paul wrote:
> Unfortunately Gustavo has decided to step down as drm-misc maintainer to
> focus on other projects. Thanks Gustavo for your dedication and hard work!
>
> Fortunately for us, we have a wealth of people qualified to assume a
> -misc
On Mon, Oct 08, 2018 at 05:09:42PM +0200, Jernej Škrabec wrote:
> Dne ponedeljek, 08. oktober 2018 ob 11:14:06 CEST je Maxime Ripard napisal(a):
> > Hi,
> >
> > On Sun, Oct 07, 2018 at 11:38:54AM +0200, Jernej Skrabec wrote:
> > > It turns out that H6 HDMI BSP kernel driver doesn't change TMDS
On Fri, 21 Sep 2018, Nathan Chancellor wrote:
> Clang warns that the address of a pointer will always evaluated as true
> in a boolean context.
>
> drivers/video/backlight/lm3639_bl.c:403:14: warning: address of
> 'pchip->cdev_torch' will always evaluate to 'true'
> [-Wpointer-bool-conversion]
>
Commit d49cd15550d9d4495f6187425318c245d58cb63f ("OMAPDSS: DISPC: lock
access to DISPC_CONTROL & DISPC_CONFIG") added locking to
mgr_fld_write(). This was needed in omapfb times due to lack of good
locking, especially in the case of both V4L2 and fbdev layers using the
DSS driver.
This is not
Signed-off-by: Chunming Zhou
---
drivers/gpu/drm/amd/amdgpu/amdgpu_drv.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/drivers/gpu/drm/amd/amdgpu/amdgpu_drv.c
b/drivers/gpu/drm/amd/amdgpu/amdgpu_drv.c
index 6870909da926..58cba492ba55 100644
---
syncobj wait/signal operation is appending in command submission.
v2: separate to two kinds in/out_deps functions
Signed-off-by: Chunming Zhou
---
drivers/gpu/drm/amd/amdgpu/amdgpu.h| 8 +-
drivers/gpu/drm/amd/amdgpu/amdgpu_cs.c | 111 +
user mode can query timeline payload.
v2: check return value of copy_to_user
Signed-off-by: Chunming Zhou
---
drivers/gpu/drm/drm_internal.h | 2 ++
drivers/gpu/drm/drm_ioctl.c| 2 ++
drivers/gpu/drm/drm_syncobj.c | 52 ++
include/uapi/drm/drm.h |
points array is one-to-one match with syncobjs array.
v2:
add seperate ioctl for timeline point wait, otherwise break uapi.
v3:
userspace can specify two kinds waits::
a. Wait for time point to be completed.
b. and wait for time point to become available
Signed-off-by: Chunming Zhou
---
This patch is for VK_KHR_timeline_semaphore extension, semaphore is called
syncobj in kernel side:
This extension introduces a new type of syncobj that has an integer payload
identifying a point in a timeline. Such timeline syncobjs support the
following operations:
* CPU query - A host
flags can be used by driver to decide whether need to block wait submission.
Signed-off-by: Chunming Zhou
---
drivers/gpu/drm/amd/amdgpu/amdgpu_cs.c | 2 +-
drivers/gpu/drm/drm_syncobj.c | 4 ++--
drivers/gpu/drm/v3d/v3d_gem.c | 4 ++--
drivers/gpu/drm/vc4/vc4_gem.c |
https://bugs.freedesktop.org/show_bug.cgi?id=108272
--- Comment #7 from jamespharve...@gmail.com ---
Regarding Luxmark, do you know with MAX_GLOBAL_BUFFERS set to 32, is it merely
that many pixels will be shown wrong? Are the benchmark results valid, or with
the wrong pixels, are the results
https://bugs.freedesktop.org/show_bug.cgi?id=108272
--- Comment #6 from jamespharve...@gmail.com ---
Understood about Luxmark.
Doesn't look like it links against LLVM directly, but it links against libGL,
libGLX, and libGLdispatch.
Arch is on LLVM 7.0.0-1, and I wouldn't be surprised if that is
On 08.10.2018 12:58, Linus Walleij wrote:
> The Samsung S6D16D0 is a simple comman mode only DSI display
> that is used on the ST-Ericsson Ux500 reference design
> TVK1281618 user interface board (UIB).
>
> Signed-off-by: Linus Walleij
> ---
> drivers/gpu/drm/panel/Kconfig | 7
https://bugs.freedesktop.org/show_bug.cgi?id=108294
--- Comment #1 from jamespharve...@gmail.com ---
For searchability, here's a few of the lines I think are most useful. Again,
the full dmesg section is attached to the original report.
[163437.787090] [drm] DM_MST: stopping TM on aconnector:
https://bugs.freedesktop.org/show_bug.cgi?id=108294
Bug ID: 108294
Summary: Turning off monitor via DisplayPort causes Kernel
warning + stack trace
Product: DRI
Version: unspecified
Hardware: x86-64 (AMD64)
This was implemented in the driver but not actually defined and
referenced in dts. This makes it always on.
From reference manual in section "10.4.1.4.1 Power Distribution":
"Display domain - The DISPLAY domain contains GIS, CSI, PXP, LCDIF,
PCIe, DCIC, and LDB. It is supplied by internal
Hi Philipp,
On 10/05/2018 02:44 AM, Philipp Zabel wrote:
Hi Steve,
On Thu, 2018-10-04 at 11:53 -0700, Steve Longerbeam wrote:
+
+ /* framelines for NTSC / PAL */
+ height = (std & V4L2_STD_525_60) ? 525 : 625;
I think this is a bit convoluted. Instead of
Hello,
This patch series adds two new configurable properties
to exynos_drm_fimd.
Patch 1 add window alpha property.
Patch 2 add pixel blend mode property.
Regards,
Chris
Christoph Manszewski (2):
drm/exynos: fimd: Make plane alpha configurable
drm/exynos: fimd: Make pixel blend mode
1 - 100 of 133 matches
Mail list logo
