Hi Eric and Wladimir,
GPU driver like VC4, Etnaviv and Lima only do rendering and left display
to other DRM display drivers. So there should be a render/display sync
problem for these drivers.
As I know, there are two ways: implicit and explicit described here:
https://bugs.freedesktop.org/show_bug.cgi?id=108771
--- Comment #2 from John ---
This may be a duplicate of https://bugs.freedesktop.org/show_bug.cgi?id=107991
.
--
You are receiving this mail because:
You are the assignee for the bug.___
dri-devel
https://bugs.freedesktop.org/show_bug.cgi?id=105251
--- Comment #60 from Benjamin Hodgetts ---
Created attachment 142505
--> https://bugs.freedesktop.org/attachment.cgi?id=142505=edit
Gallium, UMR, Dmesg Dump Package
Ok, following Andrey Grodzovsky's instructions to get the dumps didn't work
https://bugs.freedesktop.org/show_bug.cgi?id=108778
garththei...@hotmail.com changed:
What|Removed |Added
Priority|medium |high
https://bugs.freedesktop.org/show_bug.cgi?id=105251
--- Comment #59 from Benjamin Hodgetts ---
It's not just Cemu, it looks like it happens in Yuzu too. If you Google for
"VMC page fault" then you'll find people running into that error in various
other programs too.
Personally, this is what I
https://bugs.freedesktop.org/show_bug.cgi?id=108671
--- Comment #9 from Ivan_S ---
Created attachment 142504
--> https://bugs.freedesktop.org/attachment.cgi?id=142504=edit
add xorg.log
--
You are receiving this mail because:
You are the assignee for the
https://bugs.freedesktop.org/show_bug.cgi?id=108671
--- Comment #8 from Ivan_S ---
Created attachment 142503
--> https://bugs.freedesktop.org/attachment.cgi?id=142503=edit
dmesg
add dmesg
--
You are receiving this mail because:
You are the assignee for the
https://bugs.freedesktop.org/show_bug.cgi?id=108671
--- Comment #7 from Ivan_S ---
Created attachment 142502
--> https://bugs.freedesktop.org/attachment.cgi?id=142502=edit
photo of artifact 2
I have this bug too.
Kernel - 4.19.2
Distributive - Fedora 29
--
You are receiving this mail
This adds support for the VK_GOOGLE_display timing extension, which
provides two things:
1) Detailed information about when frames are displayed, including
slack time between GPU execution and display frame.
2) Absolute time control over swapchain queue processing. This allows
the
Michel Dänzer writes:
Thanks for taking time to review this patch!
>> + int64_t refresh = (int64_t) refresh_timing.refreshDuration;
>> + int64_t frames = (delta_nsec + refresh/2) / refresh;
>
> desiredPresentTime has "no sooner than" semantics, so I think this should
https://bugs.freedesktop.org/show_bug.cgi?id=108781
--- Comment #3 from jamespharve...@gmail.com ---
I should add, the screen goes black and system is unresponsive after this.
--
You are receiving this mail because:
You are the assignee for the
https://bugs.freedesktop.org/show_bug.cgi?id=108781
--- Comment #2 from jamespharve...@gmail.com ---
Created attachment 142501
--> https://bugs.freedesktop.org/attachment.cgi?id=142501=edit
dmesg (journalctl) of working on 4.18.16.arch1-1
--
You are receiving this mail because:
You are the
https://bugs.freedesktop.org/show_bug.cgi?id=108781
--- Comment #1 from jamespharve...@gmail.com ---
Created attachment 142500
--> https://bugs.freedesktop.org/attachment.cgi?id=142500=edit
dmesg (journalctl) of failure on 4.19.arch1-1
--
You are receiving this mail because:
You are the
https://bugs.freedesktop.org/show_bug.cgi?id=108781
Bug ID: 108781
Summary: 4.19 Regression - Hawaii (R9 390) boot failure -
Invalid PCC GPIO / invalid powerlevel state / Fatal
error during GPU init
Product: DRI
On Fri 2018-11-16 00:06:45, Sebastian Reichel wrote:
> This adds the required infrastructure for manually updated displays,
> such as DSI command mode panels. While those panels often support
> partial updates we currently always do a full refresh.
>
> The display will be refreshed when something
Hi!
> This prepares framedone interrupt handling for
> manual display update support.
>
> Signed-off-by: Sebastian Reichel
Acked-by: Pavel Machek
> @@ -217,6 +239,9 @@ static irqreturn_t omap_irq_handler(int irq, void *arg)
>
> if (irqstatus &
>
On Fri 2018-11-16 00:06:42, Sebastian Reichel wrote:
> While all display types only forward their VM to the DISPC, this
"While most?"
> is not true for DSI. DSI calculates the VM for DISPC based on its
> own, but its not identical. Actually the DSI VM is not even a valid
"but it is not"
>
On Fri 2018-11-16 00:06:41, Sebastian Reichel wrote:
> After the changes from 4.20 the DSI encoder tries to find the
> attached panel before populating the DSI bus. If the panel is
> not found -EPROBE_DEFER is returned, so the DSI bus is never
> populated and the panel never added.
>
> Fix this
Hi!
> It's time for a new revision of the DSI command mode panel
> patchset. The patches have been rebased to 4.20-rc1 + fixes
> from Laurent and Tony. I dropped the patches for OMAP3 support
> (it needs a workaround for a hardware bug) and for automatic
> display rotation. They should get their
On Fri 2018-11-16 00:06:40, Sebastian Reichel wrote:
> This macro is only used by omapdrm, which should print
> debug messages using the DRIVER category instead of the
> default CORE category.
>
> Signed-off-by: Sebastian Reichel
Acked-by: Pavel Machek
--
(english)
https://bugs.freedesktop.org/show_bug.cgi?id=108780
Bug ID: 108780
Summary: Missing "hainan_mc.bin" firmware reference.
Product: DRI
Version: DRI git
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
https://bugs.freedesktop.org/show_bug.cgi?id=108778
Bug ID: 108778
Summary: [R9 390] amdgpu: Fatal error during GPU init 4.20-rc2
Product: DRI
Version: unspecified
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status:
https://bugs.freedesktop.org/show_bug.cgi?id=108098
--- Comment #8 from Antonio Chirizzi ---
Hello again,
I have been testing my laptop with the AMD Ryzen 7 2700U with latest the Ubuntu
kernel 4.19.0-041900-generic for the last 2 weeks.
It does not freeze and everything works well if I use the
https://bugs.freedesktop.org/show_bug.cgi?id=105733
--- Comment #44 from krutoiles...@gmail.com ---
No mine passes memtest as well, but I was seeing failures on mprime. Also
was on Corsair vengence originally. See if you can borrow a stick to test
from someone.
On Sat, Nov 17, 2018, 06:28
Sometimes tcon attributes like tcon divider, clock rate etc are
needed in interface drivers like DSI. So for such cases interface
driver must probe the respective tcon and get the attributes.
Instead of probing tcon explictly, better export the existing
sun5i_get_tcon0 so-that the relevant
Probe tcon0 during dsi_bind, so-that the tcon attributes like
divider value, clock rate can get whenever it need.
Signed-off-by: Jagan Teki
---
drivers/gpu/drm/sun4i/sun6i_mipi_dsi.c | 7 +++
drivers/gpu/drm/sun4i/sun6i_mipi_dsi.h | 1 +
2 files changed, 8 insertions(+)
diff --git
'info->modes' got allocated with devm_kcalloc in of_get_pxafb_display.
This gives this error message:
./drivers/video/fbdev/pxafb.c:2238:2-7: WARNING: invalid free of devm_
allocated data
Signed-off-by: YueHaibing
---
drivers/video/fbdev/pxafb.c | 4 +---
1 file changed, 1 insertion(+), 3
On Sat, Nov 17, 2018 at 12:26:38PM +0530, Souptick Joarder wrote:
> On Fri, Nov 16, 2018 at 11:59 PM Mike Rapoport wrote:
> > > + * vm_insert_range - insert range of kernel pages into user vma
> > > + * @vma: user vma to map to
> > > + * @addr: target user address of this page
> > > + * @pages:
On 11/16/18 12:15 AM, Souptick Joarder wrote:
> On Fri, Nov 16, 2018 at 12:11 PM Matthew Wilcox wrote:
>>
>> On Fri, Nov 16, 2018 at 11:00:30AM +0530, Souptick Joarder wrote:
>>> On Thu, Nov 15, 2018 at 11:44 PM Randy Dunlap wrote:
On 11/15/18 7:45 AM, Souptick Joarder wrote:
What is
Allwinner MIPI DSI DRQ set value can be varied with respective
video modes.
- burst mode the set value is always 0
- video modes whose front porch greater than 20, the set value
can be computed based front porch and bpp.
- video modes whose front porch is not greater than 20, the set value
is
* Sebastian Reichel [181115 23:07]:
> Hi,
>
> It's time for a new revision of the DSI command mode panel
> patchset. The patches have been rebased to 4.20-rc1 + fixes
> from Laurent and Tony. I dropped the patches for OMAP3 support
> (it needs a workaround for a hardware bug) and for automatic
>
Feiyang FY07024DI26A30-D is 1024x600, 4-lane MIPI-DSI LCD panel.
Add dt-bingings for it.
Signed-off-by: Jagan Teki
Reviewed-by: Rob Herring
---
.../display/panel/feiyang,fy07024di26a30d.txt | 20 +++
1 file changed, 20 insertions(+)
create mode 100644
For 4-lane, burst mode panels would need to enable 2byte trail_fill
along with filling trail_env in dsi base control register.
Similar reference code avialable in BSP (from linux-sunxi/
drivers/video/sunxi/disp2/disp/de/lowlevel_sun50iw1/de_dsi.c)
if (panel->lcd_dsi_lane == 4)
{
Setting up burst mode display would require to compute
- Horizontal timing edge values to fill burst drq register
- Line, sync values to fill burst line register
Since there is no direct documentation for these computations
the edge and line formulas are taken from BSP code (from linux-sunxi/
From: Priit Laes
Even though HDMI connector features hotplug detect pin (HPD), there are
devices that which do not support it. For these devices fall back to
additional check on I2C bus. Of course, there might be also devices
that do not wire DDC pins too, so we don't really know whether cable
Loop N1 instruction delay for burst mode lcd panel are
computed as per BSP code.
Reference code is available in BSP (from linux-sunxi
drivers/video/sunxi/disp2/disp/de/lowlevel_sun50iw1/de_dsi.c)
dsi_dev[sel]->dsi_inst_loop_num.bits.loop_n1=
Horizontal back porch, sync active and sync end bits are
needed to disable for burst mode panel operations.
So, disable them via dsi base control register.
Signed-off-by: Jagan Teki
---
drivers/gpu/drm/sun4i/sun6i_mipi_dsi.c | 12 +---
1 file changed, 9 insertions(+), 3 deletions(-)
On Mon, Oct 08, 2018 at 06:06:21PM +, Leonard Crestez wrote:
> On some chips the PCIE and PCIE_PHY blocks are in separate power domains
> which can be power-gated independently. The pci driver needs to handle
> this by keeping both domain active.
>
> This is intended for imx6sx where PCIE is
Instruction loop selection would require before writing
loop number registers, so enable idle, LP11 bits on
loop selection register.
Reference code available in BSP (from linux-sunxi/
drivers/video/sunxi/disp2/disp/de/lowlevel_sun50iw1/de_dsi.c)
(dsi_dev[sel]->dsi_inst_loop_sel.dwval =
On Thu, Nov 15, 2018 at 09:15:30PM +0530, Souptick Joarder wrote:
> Previouly drivers have their own way of mapping range of
> kernel pages/memory into user vma and this was done by
> invoking vm_insert_page() within a loop.
>
> As this pattern is common across different drivers, it can
> be
Burst mode display timings are different from convectional
video mode so update the horizontal and vertical timings.
Reference code taken from BSP (from linux-sunxi/
drivers/video/sunxi/disp2/disp/de/lowlevel_sun50iw1/de_dsi.c)
dsi_hsa = 0;
dsi_hbp = 0;
dsi_hact = x*dsi_pixel_bits[format]/8;
'dpu_enc' is a member of 'drm_enc'
And 'drm_enc' got allocated with devm_kzalloc in dpu_encoder_init.
This gives this error message:
./drivers/gpu/drm/msm/disp/dpu1/dpu_encoder.c:459:1-6:
WARNING: invalid free of devm_ allocated data
Signed-off-by: YueHaibing
---
Hi Fernando,
On Thu, 2018-11-15 at 23:16 +0100, Fernando Ramos wrote:
> This patch unifies the naming of DRM functions for reference counting as
> requested on Documentation/gpu/todo.rst
>
> Signed-off-by: Fernando Ramos
> ---
> drivers/gpu/drm/arc/arcpgu_drv.c | 4 ++--
For ARCPGU
On Fri, Nov 16, 2018 at 11:59 PM Mike Rapoport wrote:
>
> On Thu, Nov 15, 2018 at 09:15:30PM +0530, Souptick Joarder wrote:
> > Previouly drivers have their own way of mapping range of
> > kernel pages/memory into user vma and this was done by
> > invoking vm_insert_page() within a loop.
> >
> >
On 16/11/2018 12:02 PM, YueHaibing wrote:
'info->modes' got allocated with devm_kcalloc in of_get_pxafb_display.
This gives this error message:
./drivers/video/fbdev/pxafb.c:2238:2-7: WARNING: invalid free of devm_
allocated data
Signed-off-by: YueHaibing
Oh, yes. Thanks for spotting
This series support MIPI-DSI Burst mode on Allwinner platform, which
is tested in burst supported panel in Pine64-LTS board.
Series fixed few code changes commented in previous version[1] and
it depends on A64 MIPI-DSI series[2]
Changes for v2:
- add separate function for setup_inst_delay
On Fri, Nov 16, 2018 at 12:11 PM Matthew Wilcox wrote:
>
> On Fri, Nov 16, 2018 at 11:00:30AM +0530, Souptick Joarder wrote:
> > On Thu, Nov 15, 2018 at 11:44 PM Randy Dunlap wrote:
> > > On 11/15/18 7:45 AM, Souptick Joarder wrote:
> > > What is the opposite of vm_insert_range() or even of
Feiyang FY07024DI26A30-D is 1024x600, 4-lane MIPI-DSI LCD panel.
Add panel driver for it.
Signed-off-by: Jagan Teki
---
MAINTAINERS | 6 +
drivers/gpu/drm/panel/Kconfig | 9 +
drivers/gpu/drm/panel/Makefile| 1 +
On 11/16/18 2:53 PM, a...@linux-foundation.org wrote:
> The mm-of-the-moment snapshot 2018-11-16-14-52 has been uploaded to
>
>http://www.ozlabs.org/~akpm/mmotm/
>
> mmotm-readme.txt says
>
> README for mm-of-the-moment:
>
> http://www.ozlabs.org/~akpm/mmotm/
>
> This is a snapshot of my
Feiyang FY07024DI26A30-D MIPI_DSI panel is desiged to attach with
DSI connector on pine64 boards, enable the same for pine64 LTS.
DSI panel connected via board DSI port with,
- DC1SW as AVDD supply
- DLDO2 as DVDD supply
- DLDO1 as VCC-DSI supply
- PD24 gpio for reset pin
- PH10 gpio for
https://bugs.freedesktop.org/show_bug.cgi?id=102646
--- Comment #40 from tempel.jul...@gmail.com ---
Still having this issue with 2560 x 1440 @ 75Hz and latest 4.21-wip kernel.
Manually forcing a single VRAM clock state eliminates the flicker artifacts. As
soon as there is dynamic VRAM clocking
https://bugs.freedesktop.org/show_bug.cgi?id=105733
--- Comment #43 from Philipp ---
I've got 2x8GB DDR4 Corsair Vengeance LPX RAM (oh dear, those names).
I have run a few rounds of memtest without any errors so far, but I'll run a
few more hours today when I get the chance.
Did you switch your
https://bugs.freedesktop.org/show_bug.cgi?id=108729
--- Comment #4 from Vedran Miletić ---
After upgrading the kernel to 4.19.2:
[0.00] Command line: BOOT_IMAGE=/vmlinuz-4.19.2-300.fc29.x86_64
root=UUID=6721d330-05e1-4b6d-a862-ccc514fd41ff ro rhgb quiet
radeon.cik_support=0
Hi,
[This is an automated email]
This commit has been processed because it contains a -stable tag.
The stable tag indicates that it's relevant for the following trees: all
The bot has tested the following trees: v4.19.2, v4.18.19, v4.14.81, v4.9.137,
v4.4.163, v3.18.125,
v4.19.2: Build OK!
Hi,
[This is an automated email]
This commit has been processed because it contains a -stable tag.
The stable tag indicates that it's relevant for the following trees: all
The bot has tested the following trees: v4.19.2, v4.18.19, v4.14.81, v4.9.137,
v4.4.163, v3.18.125,
v4.19.2: Build OK!
On Fri, Nov 16, 2018 at 3:01 PM Joonas Lahtinen
wrote:
>
> Somebody casually changing the uAPI headers with no consideration
> to the agreed upon rules seems to be a more frequent problem than
> at least I would like it to be.
>
> Might be worthy to condense a checklist to the warning message,
>
56 matches
Mail list logo
