On 2018-10-24 22:09, Matthias Kaehlcke wrote:
Hi Sravanthi,
On Wed, Oct 10, 2018 at 02:54:33PM +0530, Sravanthi Kollukuduru wrote:
The interconnect framework is designed to provide a
standard kernel interface to control the settings of
the interconnects on a SoC.
The interconnect API uses a co
https://bugs.freedesktop.org/show_bug.cgi?id=108606
--- Comment #13 from Samantha McVey ---
Created attachment 142319
--> https://bugs.freedesktop.org/attachment.cgi?id=142319&action=edit
amdgpu.ppfeaturemask=0x3fff resume from suspend lockup
Alex,
So far it seems that I am not getting the
https://bugs.freedesktop.org/show_bug.cgi?id=108606
--- Comment #14 from Samantha McVey ---
Wanted to make sure a few things were clear from my last message:
"I tested again and I still get the gpu lockup without these options (this is
without having any commit reverted)."
- Since I was not gett
On Wed, Oct 31, 2018 at 02:44:24PM -0300, Shayenne da Luz Moura wrote:
> Break line after NULL to decrease the line size.
>
> Signed-off-by: Shayenne da Luz Moura
>
> ---
> Changes in v2:
> - Remove aditional variable added in v1 and add a line break
Applied, thanks.
-Daniel
>
> drivers/gp
When the userspace tries to read the crashstate dump, the read side
implementation in the driver currently ascii85 encodes all the binary
buffers and it does this each time the read system call is called.
A userspace tool like cat typically does a page by page read and the
number of read calls depe
On Thu, Nov 01, 2018 at 12:37:14AM +0100, Noralf Trønnes wrote:
>
> Den 17.10.2018 15.04, skrev 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 Wed, 31 Oct 2018 17:54:34 +
"Kazlauskas, Nicholas" wrote:
> On 10/31/18 12:20 PM, Michel Dänzer wrote:
> > On 2018-10-31 3:41 p.m., Kazlauskas, Nicholas wrote:
> >> On 10/31/18 10:12 AM, Michel Dänzer wrote:
> >>> On 2018-10-31 2:38 p.m., Kazlauskas, Nicholas wrote:
> On 10/30/1
https://bugzilla.kernel.org/show_bug.cgi?id=201139
--- Comment #2 from Aleksandr Mezin (mezin.alexan...@gmail.com) ---
Created attachment 279279
--> https://bugzilla.kernel.org/attachment.cgi?id=279279&action=edit
Kernel log
Today I've seen this issue again on 4.19.
Monitors were turned off by
https://bugzilla.kernel.org/show_bug.cgi?id=201139
Aleksandr Mezin (mezin.alexan...@gmail.com) changed:
What|Removed |Added
Kernel Version|4.19-rc3|4.19
--
Yo
https://bugzilla.kernel.org/show_bug.cgi?id=201139
--- Comment #3 from Aleksandr Mezin (mezin.alexan...@gmail.com) ---
Created attachment 279281
--> https://bugzilla.kernel.org/attachment.cgi?id=279281&action=edit
journalctl --user (Xorg log is here)
--
You are receiving this mail because:
You
On 2018年10月31日 20:07, Chris Wilson wrote:
drivers/gpu/drm/drm_syncobj.c:181:6: warning: no previous prototype for
‘drm_syncobj_add_callback’ [-Wmissing-prototypes]
drivers/gpu/drm/drm_syncobj.c:190:6: warning: no previous prototype for
‘drm_syncobj_remove_callback’ [-Wmissing-prototypes]
Fix
https://bugzilla.kernel.org/show_bug.cgi?id=201139
--- Comment #4 from Aleksandr Mezin (mezin.alexan...@gmail.com) ---
Also tried loggig out & in, restarting GDM, changing display configurations in
Gnome. Even in another VT and in GDM, one monitor was showing only a black
screen. Only reboot made
https://bugs.freedesktop.org/show_bug.cgi?id=108585
--- Comment #16 from Dan Horák ---
Reset on init sounds better to me as the loader kernel (in kexec case) is more
difficult to update than the host kernel.
And for the record - after updating the skiroot kernel firmware version to the
latest th
Hi Jagan,
On Wed, Oct 31, 2018 at 7:58 PM Chen-Yu Tsai wrote:
>
> On Wed, Oct 31, 2018 at 4:53 PM Andrzej Hajda wrote:
> >
> > On 26.10.2018 16:43, Jagan Teki wrote:
> > > Bananapi S070WV20-CT16 ICN6211 is 800x480, 4-lane MIPI-DSI to RGB
> > > bridge panel, which is available on same PCB with 24
On 10/31/2018 8:12 AM, Shawn Guo wrote:
> On Mon, Oct 08, 2018 at 06:06:23PM +, Leonard Crestez wrote:
>> 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":
>>
>>
While adding SiI9022A support to the iwg23s board it came up
that when the HDMI transmitter is in pass through mode the
device is not compliant with the I2C specification anymore,
as it requires a far bigger tbuf due to a delay the HDMI
transmitter is adding when relaying the STOP condition on the
On Tue, Oct 30, 2018 at 6:25 PM Michael Forney wrote:
>
> On 2018-10-29, David Abdurachmanov wrote:
> > On Mon, Oct 29, 2018 at 8:47 PM Michael Forney wrote:
> >>
> >> - Should riscv support ARCH_HAS_SG_CHAIN?
> >
> > Non-expert here, but it looks like ARCH_HAS_SG_CHAIN
> > support is generic, a
On 2018-10-31 17:55, Fabrizio Castro wrote:
> Hello Linus,
>
>> Subject: Re: [RFC] drm/bridge/sii902x: Fix EDID readback
>>
>> Hi Fabrizio,
>>
>> thanks for your patch!
>
> Thank you for your feedback!
>
>>
>> On Wed, Oct 31, 2018 at 1:58 PM Fabrizio Castro
>> wrote:
>>
>>> While adding SiI9022
The firmware.vaddr might be assigned with an error code instead of
NULL, so this patch uses an IS_ERR_OR_NULL check to fix below bug.
Unable to handle kernel paging request at virtual address fff0
[...]
pc : falcon_load_firmware+0x80/0x358 [tegra_drm]
lr : falcon_load_firmware+0x2b4/0x
Hello Linus,
> Subject: Re: [RFC] drm/bridge/sii902x: Fix EDID readback
>
> Hi Fabrizio,
>
> thanks for your patch!
Thank you for your feedback!
>
> On Wed, Oct 31, 2018 at 1:58 PM Fabrizio Castro
> wrote:
>
> > While adding SiI9022A support to the iwg23s board it came up
> > that when the HDMI
On Wed, Oct 31, 2018 at 12:17:50PM +, Leonard Crestez wrote:
> On 10/31/2018 8:12 AM, Shawn Guo wrote:
> > On Mon, Oct 08, 2018 at 06:06:23PM +, Leonard Crestez wrote:
> >> This was implemented in the driver but not actually defined and
> >> referenced in dts. This makes it always on.
> >>
The probe function performs hardware access to read the number of
supported data lanes from a configuration register and thus requires the
device to be active. Ensure this by surrounding the access with
dsi_runtime_get() and dsi_runtime_put() calls.
Additionally we need to introduce a hack in the
Hello,
This series fixes crashes in the omapdss driver at both load and unload
time, due to runtime PM problems related to probe deferral. The bugs got
introduced in v4.20-rc, this should thus be considered as v4.20 fixes.
At the core of the problem comes commit 27d624527d99 ("drm/omap: dss:
Acqu
The bind function performs hardware access (in hdmi4_cec_init()) and
thus requires the device to be active. Ensure this by surrounding the
bind function by hdmi_runtime_get() and hdmi_runtime_put() calls.
Fixes: 27d624527d99 ("drm/omap: dss: Acquire next dssdev at probe time")
Signed-off-by: Laure
The DSS DT node contains children that describe the DSS components
(DISPC and internal encoders). Each of those components is handled by a
platform driver, and thus needs to be backed by a platform device.
The corresponding platform devices are created in arch code by a call to
of_platform_populat
On 2018-10-31 6:54 p.m., Kazlauskas, Nicholas wrote:
> On 10/31/18 12:20 PM, Michel Dänzer wrote:
>> On 2018-10-31 3:41 p.m., Kazlauskas, Nicholas wrote:
>>> On 10/31/18 10:12 AM, Michel Dänzer wrote:
On 2018-10-31 2:38 p.m., Kazlauskas, Nicholas wrote:
> On 10/30/18 11:34 AM, Kazlauskas,
https://bugs.freedesktop.org/show_bug.cgi?id=106175
--- Comment #31 from Michel Dänzer ---
Note that SWcursor completely disables page flipping, at least with
xf86-video-amdgpu, because the two things are fundamentally incompatible with
each other. Does only disabling page flipping also avoid the
On Wed, Oct 31, 2018 at 04:55:53PM +, Fabrizio Castro wrote:
> Having the option of using "unlocked" flavours of reads and writes
> is what we need here, but looking at drivers/base/regmap/regmap-i2c.c
> I couldn't find anything suitable for my case, maybe Mark could advise
> on this one? I am
https://bugs.freedesktop.org/show_bug.cgi?id=108613
--- Comment #1 from Michel Dänzer ---
Please attach the corresponding Xorg log file and output of dmesg.
--
You are receiving this mail because:
You are the assignee for the bug.___
dri-devel mailing
Quoting zhoucm1 (2018-11-01 08:53:02)
>
>
> On 2018年10月31日 20:07, Chris Wilson wrote:
> > drivers/gpu/drm/drm_syncobj.c:181:6: warning: no previous prototype for
> > ‘drm_syncobj_add_callback’ [-Wmissing-prototypes]
> > drivers/gpu/drm/drm_syncobj.c:190:6: warning: no previous prototype for
> >
Hi Laurent,
On 01/11/18 12:25, Laurent Pinchart wrote:
> Hello,
>
> This series fixes crashes in the omapdss driver at both load and unload
> time, due to runtime PM problems related to probe deferral. The bugs got
> introduced in v4.20-rc, this should thus be considered as v4.20 fixes.
>
> At t
https://bugs.freedesktop.org/show_bug.cgi?id=108194
--- Comment #4 from Hadrien Nilsson ---
I'm not sure for bug 104602 as everything else renders correctly.
---
I installed a fresh version of Ubuntu 18.04 on a specific disk and added padoka
unstable ppa for mesa. I got this version:
https://bugzilla.kernel.org/show_bug.cgi?id=201585
Bug ID: 201585
Summary: 144Hz 2560x1440 no longer works (caps at 120Hz)
Product: Drivers
Version: 2.5
Kernel Version: 4.18
Hardware: All
OS: Linux
Tree: Mainl
Ho Tomi,
On Thursday, 1 November 2018 13:47:40 EET Tomi Valkeinen wrote:
> On 01/11/18 12:25, Laurent Pinchart wrote:
> > Hello,
> >
> > This series fixes crashes in the omapdss driver at both load and unload
> > time, due to runtime PM problems related to probe deferral. The bugs got
> > introdu
https://bugs.freedesktop.org/show_bug.cgi?id=108613
--- Comment #2 from tempel.jul...@gmail.com ---
Created attachment 142327
--> https://bugs.freedesktop.org/attachment.cgi?id=142327&action=edit
dmesg.log
--
You are receiving this mail because:
You are the assignee for the bug.___
https://bugs.freedesktop.org/show_bug.cgi?id=108613
--- Comment #3 from tempel.jul...@gmail.com ---
Created attachment 142328
--> https://bugs.freedesktop.org/attachment.cgi?id=142328&action=edit
xorg.log
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=106175
--- Comment #32 from gr...@sub.red ---
(In reply to Michel Dänzer from comment #31)
> Does only disabling page flipping also avoid the problem?
Not from what I can tell.
> Option "EnablePageFlip" "off"
results in
>[ 35496.178] (II) AMDGPU(0)
https://bugs.freedesktop.org/show_bug.cgi?id=106175
--- Comment #33 from tempel.jul...@gmail.com ---
I suppose TearFree forces pageflipping regardless, as we don't see any tearing
with that configuration.
--
You are receiving this mail because:
You are the assignee for the bug.__
https://bugs.freedesktop.org/show_bug.cgi?id=108585
--- Comment #17 from Dan Horák ---
Fedora/ppc64le users can find a pre-built kernel with the patchset at
https://copr.fedorainfracloud.org/coprs/sharkcz/talos-kernel/build/817728/
--
You are receiving this mail because:
You are the assignee fo
Hey Emil,
On 2018-10-31 10:38, Emil Velikov wrote:
Hi Rob,
On Thu, 25 Oct 2018 at 19:38, Robert Foss wrote:
From: Gustavo Padovan
Refactor fence creation to remove the potential allocation failure from
the cmd_submit and atomic_commit paths. Now the fence should be allocated
first and just
On 2018-10-31 10:38, Emil Velikov wrote:
Hi Rob,
On Thu, 25 Oct 2018 at 19:38, Robert Foss wrote:
Add a new field called fence_fd that will be used by userspace to send
in-fences to the kernel and receive out-fences created by the kernel.
This uapi enables virtio to take advantage of expli
On 01/11/18 14:13, Laurent Pinchart wrote:
>> Thanks for debugging this! I have to say I really don't like these
>> (well, 2 is fine), as they feel like hacks.
>
> I assume you also have nothing against the first hunk of patch 3/3.
Yes. And after our discussion, I think 1 is fine too, so the onl
https://bugzilla.kernel.org/show_bug.cgi?id=201139
--- Comment #5 from Harry Wentland (harry.wentl...@amd.com) ---
It looks like link training failed. Can you check on your monitor's OSD whether
DisplayPort or Auto is selected as input? I've seen this behavior on some
monitors when Auto input was
https://bugs.freedesktop.org/show_bug.cgi?id=108098
--- Comment #6 from Antonio Chirizzi ---
Hello fin4478, thanks for the suggestion.
I have tried the latest Manjaro Xfce, it's able to boot but it's not able to
start the graphics environment. I have seen that for the Ryzen 7 2700U (my CPU)
there
https://bugzilla.kernel.org/show_bug.cgi?id=201585
Nicholas Kazlauskas (nicholas.kazlaus...@amd.com) changed:
What|Removed |Added
CC||nichol
https://bugzilla.kernel.org/show_bug.cgi?id=201585
--- Comment #2 from Dan Acristinii (d...@acristinii.com) ---
for which kernel version, 4.18 or 4.19?
--
You are receiving this mail because:
You are watching the assignee of the bug.
___
dri-devel mail
Hi,
Liviu, can I merge this through drm-misc-next.
On Mon, Oct 29, 2018 at 05:14:38PM +, Alexandru-Cosmin Gheorghe wrote:
> Enable the following formats
> - DRM_FORMAT_X0L0: DP650
> - DRM_FORMAT_X0L2: DP550, DP650
>
> Reviewed-by: Brian Starkey
> Signed-off-by: Alexandru Gheorghe
> ---
>
https://bugzilla.kernel.org/show_bug.cgi?id=201585
--- Comment #3 from Nicholas Kazlauskas (nicholas.kazlaus...@amd.com) ---
The kernel you're experiencing the issue on, 4.18.
It might be worth trying 4.19 to see if you can still reproduce the issue
there, however.
--
You are receiving this mai
https://bugzilla.kernel.org/show_bug.cgi?id=201585
--- Comment #4 from Dan Acristinii (d...@acristinii.com) ---
Created attachment 279285
--> https://bugzilla.kernel.org/attachment.cgi?id=279285&action=edit
dmesg.log on 4.18
--
You are receiving this mail because:
You are watching the assignee
https://bugzilla.kernel.org/show_bug.cgi?id=201585
--- Comment #5 from Dan Acristinii (d...@acristinii.com) ---
The issue persists on 4.19
--
You are receiving this mail because:
You are watching the assignee of the bug.
___
dri-devel mailing list
dri-
https://bugzilla.kernel.org/show_bug.cgi?id=201585
--- Comment #6 from Dan Acristinii (d...@acristinii.com) ---
Created attachment 279287
--> https://bugzilla.kernel.org/attachment.cgi?id=279287&action=edit
144Hz working dmesg on 4.17.19
--
You are receiving this mail because:
You are watching
https://bugzilla.kernel.org/show_bug.cgi?id=201585
--- Comment #7 from Nicholas Kazlauskas (nicholas.kazlaus...@amd.com) ---
It may also help to have a dmesg log for 4.18 with drm.debug=4 as part of your
bootline.
Thanks for all the logs.
--
You are receiving this mail because:
You are watching
https://bugs.freedesktop.org/show_bug.cgi?id=108096
--- Comment #25 from Andrey Grodzovsky ---
(In reply to Dieter Nützel from comment #24)
> (In reply to Andrey Grodzovsky from comment #22)
> > (In reply to Andrey Grodzovsky from comment #21)
> > > Please load the driver in debug mode so I can s
Den 25.10.2018 22.13, skrev Noralf Trønnes:
The CMA helper is already using the drm_fb_helper_generic_probe part of
the generic fbdev emulation. This patch makes full use of the generic
fbdev emulation by using its drm_client callbacks. This means that
drm_mode_config_funcs->output_poll_changed
Den 25.10.2018 22.13, skrev Noralf Trønnes:
The CMA helper is already using the drm_fb_helper_generic_probe part of
the generic fbdev emulation. This patch makes full use of the generic
fbdev emulation by using its drm_client callbacks. This means that
drm_mode_config_funcs->output_poll_changed
Den 25.10.2018 22.25, skrev Boris Brezillon:
On Thu, 25 Oct 2018 22:13:37 +0200
Noralf Trønnes wrote:
The CMA helper is already using the drm_fb_helper_generic_probe part of
the generic fbdev emulation. This patch makes full use of the generic
fbdev emulation by using its drm_client callbacks
Den 26.10.2018 10.27, skrev Maxime Ripard:
On Thu, Oct 25, 2018 at 10:13:38PM +0200, Noralf Trønnes wrote:
The CMA helper is already using the drm_fb_helper_generic_probe part of
the generic fbdev emulation. This patch makes full use of the generic
fbdev emulation by using its drm_client callba
Den 29.10.2018 16.55, skrev Jyri Sarha:
On 25/10/18 23:13, Noralf Trønnes wrote:
The CMA helper is already using the drm_fb_helper_generic_probe part of
the generic fbdev emulation. This patch makes full use of the generic
fbdev emulation by using its drm_client callbacks. This means that
drm_m
When the userspace tries to read the crashstate dump, the read side
implementation in the driver currently ascii85 encodes all the binary
buffers and it does this each time the read system call is called.
A userspace tool like cat typically does a page by page read and the
number of read calls depe
On 11/1/18 6:58 AM, Michel Dänzer wrote:
> On 2018-10-31 6:54 p.m., Kazlauskas, Nicholas wrote:
>> On 10/31/18 12:20 PM, Michel Dänzer wrote:
>>> On 2018-10-31 3:41 p.m., Kazlauskas, Nicholas wrote:
On 10/31/18 10:12 AM, Michel Dänzer wrote:
> On 2018-10-31 2:38 p.m., Kazlauskas, Nicholas
On Thu, Nov 01, 2018 at 02:05:41PM +0530, Sharat Masetty wrote:
> When the userspace tries to read the crashstate dump, the read side
> implementation in the driver currently ascii85 encodes all the binary
> buffers and it does this each time the read system call is called.
> A userspace tool like
Basically, just a resend before I merge these patches in
drm-misc-next.
Changes since v6:
- Collected Reviewed-by.
- Fixed author, seems dim it's not smart enough to know "Alexandru
Gheorghe" is the same with Alexandru-Cosmin Gheorghe :).
- Fixed conflicts against latest drm-misc-next.
For some pixel formats .cpp structure in drm_format info it's not
enough to describe the peculiarities of the pixel layout, for example
tiled formats or packed formats at bit level.
What's implemented here is to add three new members to drm_format_info
that could describe such formats:
- char_per
Mali-DP implements a number of tiled yuv formats which are not
currently described in drm_fourcc.h.
This adds those definitions and describes their memory layout by
using the newly added char_per_block, block_w, block_h.
Reviewed-by: Brian Starkey
Reviewed-by: Daniel Vetter
Signed-off-by: Alexan
For formats that are supported only with non-linear modifiers it
doesn't make to much sense to define cpp or char_per_block, so that
will be set to 0.
This patch adds a restriction to force having a modifier attached when
cpp/char_per_block is 0, and to bypass checking the pitch restriction.
This
Add selftests for the following newly added functions:
- drm_format_info_block_width
- drm_format_info_block_height
- drm_format_info_min_pitch
Signed-off-by: Alexandru Gheorghe
Reviewed-by: Daniel Vetter
---
drivers/gpu/drm/selftests/Makefile| 3 +-
.../gpu/drm/selftests/drm_m
Enable the following formats
- DRM_FORMAT_X0L0: DP650
- DRM_FORMAT_X0L2: DP550, DP650
Reviewed-by: Brian Starkey
Signed-off-by: Alexandru Gheorghe
---
drivers/gpu/drm/arm/malidp_hw.c | 14 +++---
drivers/gpu/drm/arm/malidp_planes.c | 28 +---
2 files changed,
If we want to be able to write drmselftests for non-static core
functions that are not intended to be used by drivers we need this
functions to be exported.
This adds a macro that is tied of CONFIG_DRM_DEBUG_SELFTEST, and uses
that to export drm_internal_framebuffer_create, in order for
subsequent
Add tests that verify that drm_internal_framebuffer_create creates
buffers correctly by creating a dummy drm_device with a mock function
for the fb_create callback.
To decide if a buffer has been created or not it just checks if
fb_create callback has been called for the particular drm_mode_fb_cmd
Hi Dave,
Fixes for 4.20. Highlights:
- Fix flickering at low backlight levels on some systems
- Fix some overclocking regressions
- Vega20 updates for
- GPU recovery fixes
- Disable gfxoff on RV as some sbios/fw combinations are not stable yet
The following changes since commit 0af5c656fdb797f74
On Thu, Nov 01, 2018 at 01:31:06PM +, Alexandru-Cosmin Gheorghe wrote:
> Hi,
>
> Liviu, can I merge this through drm-misc-next.
Yeah, that is fine with me.
Best regards,
Liviu
>
> On Mon, Oct 29, 2018 at 05:14:38PM +, Alexandru-Cosmin Gheorghe wrote:
> > Enable the following formats
>
https://bugs.freedesktop.org/show_bug.cgi?id=108098
--- Comment #7 from Michel Dänzer ---
FWIW, I advise against paying too much attention to fin4478. They are not
involved in driver development and known for making rather questionable
suggestions which are definitely not suitable for everyone.
https://bugs.freedesktop.org/show_bug.cgi?id=106175
--- Comment #34 from Michel Dänzer ---
(In reply to tempel.julian from comment #33)
> I suppose TearFree forces pageflipping regardless, as we don't see any
> tearing with that configuration.
Right, you'd have to disable TearFree as well. Can b
https://bugs.freedesktop.org/show_bug.cgi?id=108613
Michel Dänzer changed:
What|Removed |Added
Attachment #142327|text/x-log |text/plain
mime type|
https://bugs.freedesktop.org/show_bug.cgi?id=108613
Michel Dänzer changed:
What|Removed |Added
Attachment #142328|text/x-log |text/plain
mime type|
https://bugs.freedesktop.org/show_bug.cgi?id=108625
Bug ID: 108625
Summary: AMDGPU - Can't even get Xorg to start - Kernel driver
hangs with ring buffer timeout on ARM64
Product: DRI
Version: unspecified
Hardware: ARM
If dma_fence_wait fails to wait for a supplied in-fence in
msm_ioctl_gem_submit, make sure we release that in-fence.
Also remove this dma_fence_put() from the 'out' label.
Signed-off-by: Robert Foss
---
drivers/gpu/drm/msm/msm_gem_submit.c | 10 +-
1 file changed, 5 insertions(+), 5 del
Hi Tony,
On Thursday, 1 November 2018 17:58:56 EET Tony Lindgren wrote:
> * Laurent Pinchart [181101 12:13]:
> > On Thursday, 1 November 2018 13:47:40 EET Tomi Valkeinen wrote:
> > > We do dispc_runtime_get/put in the HDMI driver's suspend/resume too, so
> > > don't we need similar hack (as you a
Quoting Robert Foss (2018-11-01 16:12:28)
> If dma_fence_wait fails to wait for a supplied in-fence in
> msm_ioctl_gem_submit, make sure we release that in-fence.
>
> Also remove this dma_fence_put() from the 'out' label.
>
> Signed-off-by: Robert Foss
> ---
> drivers/gpu/drm/msm/msm_gem_submit
https://bugs.freedesktop.org/show_bug.cgi?id=107221
Martin Peres changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://bugs.freedesktop.org/show_bug.cgi?id=107221
Martin Peres changed:
What|Removed |Added
Status|RESOLVED|CLOSED
--
You are receiving this mail b
https://bugs.freedesktop.org/show_bug.cgi?id=107222
Martin Peres changed:
What|Removed |Added
Status|RESOLVED|CLOSED
--
You are receiving this mail b
https://bugs.freedesktop.org/show_bug.cgi?id=107222
Martin Peres changed:
What|Removed |Added
Resolution|--- |WORKSFORME
Status|NEW
On Wed, Oct 24, 2018 at 03:28:20PM -0700, Manasi Navare wrote:
> This patch defines a new header file for all the DSC 1.2 structures
> and creates a structure for PPS infoframe which will be used to send
> picture parameter set secondary data packet for display stream compression.
> All the PPS inf
On Wed, Oct 24, 2018 at 03:28:23PM -0700, Manasi Navare wrote:
> According to Display Stream compression spec 1.2, the picture
> parameter set metadata is sent from source to sink device
> using the DP Secondary data packet. An infoframe is formed
> for the PPS SDP header and PPS SDP payload bytes.
https://bugs.freedesktop.org/show_bug.cgi?id=102646
--- Comment #39 from bmil...@gmail.com ---
Another interesting info, even with amdgpu.dc=0 I get flickering @75hz.
Difference is the flickering immediatly stops when I switch back to 60hz (no
need to reboot or switch monitor off/on)
--
You are
https://bugs.freedesktop.org/show_bug.cgi?id=108606
--- Comment #15 from Samantha McVey ---
Alex,
The conditions in your patch never get triggered. I added some print statements
in there, and gfx_v9_0_init_rlc_ext_microcode(adev) runs, but
`adev->powerplay.pp_feature &= ~PP_GFXOFF_MASK` never run
On Thu, Nov 01, 2018 at 06:42:17PM +0200, Ville Syrjälä wrote:
> On Wed, Oct 24, 2018 at 03:28:20PM -0700, Manasi Navare wrote:
> > This patch defines a new header file for all the DSC 1.2 structures
> > and creates a structure for PPS infoframe which will be used to send
> > picture parameter set
https://bugs.freedesktop.org/show_bug.cgi?id=107402
Martin Peres changed:
What|Removed |Added
Resolution|--- |WORKSFORME
Status|NEW
https://bugs.freedesktop.org/show_bug.cgi?id=107402
Martin Peres changed:
What|Removed |Added
Status|RESOLVED|CLOSED
--
You are receiving this mail b
For some pixel formats .cpp structure in drm_format info it's not
enough to describe the peculiarities of the pixel layout, for example
tiled formats or packed formats at bit level.
What's implemented here is to add three new members to drm_format_info
that could describe such formats:
- char_per
On 2018-11-01 3:58 p.m., Kazlauskas, Nicholas wrote:
> On 11/1/18 6:58 AM, Michel Dänzer wrote:
>> On 2018-10-31 6:54 p.m., Kazlauskas, Nicholas wrote:
>>> On 10/31/18 12:20 PM, Michel Dänzer wrote:
On 2018-10-31 3:41 p.m., Kazlauskas, Nicholas wrote:
> On 10/31/18 10:12 AM, Michel Dänzer
Hey Chris,
On 2018-11-01 17:26, Chris Wilson wrote:
Quoting Robert Foss (2018-11-01 16:12:28)
If dma_fence_wait fails to wait for a supplied in-fence in
msm_ioctl_gem_submit, make sure we release that in-fence.
Also remove this dma_fence_put() from the 'out' label.
Signed-off-by: Robert Foss
On 11/1/18 1:05 PM, Michel Dänzer wrote:
> On 2018-11-01 3:58 p.m., Kazlauskas, Nicholas wrote:
>> On 11/1/18 6:58 AM, Michel Dänzer wrote:
>>> On 2018-10-31 6:54 p.m., Kazlauskas, Nicholas wrote:
On 10/31/18 12:20 PM, Michel Dänzer wrote:
> On 2018-10-31 3:41 p.m., Kazlauskas, Nicholas wr
https://bugzilla.kernel.org/show_bug.cgi?id=201585
--- Comment #8 from Dan Acristinii (d...@acristinii.com) ---
Created attachment 279289
--> https://bugzilla.kernel.org/attachment.cgi?id=279289&action=edit
4.18 with drm.debug=4
I think I added it in the right way
--
You are receiving this ma
https://bugs.freedesktop.org/show_bug.cgi?id=108606
--- Comment #16 from Samantha McVey ---
Created attachment 142330
--> https://bugs.freedesktop.org/attachment.cgi?id=142330&action=edit
amdgpu.ppfeaturemask=0xfffdbfff lockup during normal usage
I did more testing on amdgpu.ppfeaturemask=0xff
https://bugs.freedesktop.org/show_bug.cgi?id=106175
--- Comment #35 from bmil...@gmail.com ---
(In reply to Michel Dänzer from comment #31)
> Note that SWcursor completely disables page flipping, at least with
> xf86-video-amdgpu, because the two things are fundamentally incompatible
> with each o
https://bugs.freedesktop.org/show_bug.cgi?id=108625
--- Comment #1 from Alex Deucher ---
Please attach your full dmesg output and xorg log if using X.
--
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=106175
--- Comment #36 from bmil...@gmail.com ---
So, to help find the origin of the issue, there are a few options that get rid
of stutter when compositing:
1 - amdgpu.dc=0 - The old DC seems unaffected by the bug.
2 - SWcursor on - Unaffected by bug
https://bugs.freedesktop.org/show_bug.cgi?id=106175
--- Comment #37 from tempel.jul...@gmail.com ---
I think software cursor would also be unusable even if it left pageflipping on.
It causes nasty issues like flickering cursor or other visual corruption.
--
You are receiving this mail because:
Y
1 - 100 of 169 matches
Mail list logo
