https://bugs.freedesktop.org/show_bug.cgi?id=109554
Bug ID: 109554
Summary: Regression: short time display corruption during
resume
Product: DRI
Version: XOrg git
Hardware: x86-64 (AMD64)
OS: Linux (All)
On Mon, Feb 4, 2019 at 1:07 AM Daniel Vetter wrote:
>
> On Mon, Feb 04, 2019 at 10:57:24AM +0200, Joonas Lahtinen wrote:
> > Quoting Joonas Lahtinen (2019-01-15 16:47:27)
> > > Hi all,
> > >
> > > I would like to have some Acked-by's from you, the distro media
> > > folks Cc'd here, to document
https://bugs.freedesktop.org/show_bug.cgi?id=105733
--- Comment #69 from jake.hed...@yahoo.com ---
Hi Alex, comment 64 did not resolve the issue. It did seem to delay the crash,
but ultimately did not resolve it. I will test the idle=nomwait param now and
begin testing. If I am still stuck, I
On Sat, 2 Feb 2019 at 10:20, Lyude Paul wrote:
>
> Atomic checks should never modify anything outside of the state that
> they're passed in. Unfortunately this appears to be exactly what we're
> doing in nv50_msto_atomic_check() where we update mstc->pbn every time
> the function is called. This
https://bugs.freedesktop.org/show_bug.cgi?id=109548
--- Comment #2 from spause+bugzi...@gmail.com ---
It seems like this issue is maybe the same as this one associated with Intel
driver here - https://bugs.freedesktop.org/show_bug.cgi?id=104536
But I may be misunderstanding.
I will say that
https://bugs.freedesktop.org/show_bug.cgi?id=109548
--- Comment #1 from spause+bugzi...@gmail.com ---
Created attachment 143293
--> https://bugs.freedesktop.org/attachment.cgi?id=143293=edit
video (no issues) properties
--
You are receiving this mail because:
You are the assignee for the
https://bugs.freedesktop.org/show_bug.cgi?id=109548
Bug ID: 109548
Summary: Seeing visual corruption in totem after installing
amdgpu 18.50 in Ubuntu 18.04.1
Product: DRI
Version: unspecified
Hardware: Other
https://bugs.freedesktop.org/show_bug.cgi?id=109539
--- Comment #5 from jon ---
Created attachment 143291
--> https://bugs.freedesktop.org/attachment.cgi?id=143291=edit
Xorg.0.log
xorg log from ~/.local/
--
You are receiving this mail because:
You are the assignee for the
https://bugs.freedesktop.org/show_bug.cgi?id=109539
--- Comment #4 from jon ---
Created attachment 143290
--> https://bugs.freedesktop.org/attachment.cgi?id=143290=edit
dmesg output
dmesg output (direct code disabled)
--
You are receiving this mail because:
You are the assignee for the
https://bugs.freedesktop.org/show_bug.cgi?id=109539
--- Comment #3 from jon ---
>The freezing doesn't seem to be necessarily caused by by something in amdgpu
>>from a glance at your log.
I thought the same thing, but after disabling direct code I went from the
system freezing up to 5 or 6
This patch adds appropiate kernel documentation for DRM DP helpers
used for enabling Display Stream compression functionality in
drm_dp_helper.h and drm_dp_helper.c as well as for the DSC spec
related structure definitions and helpers in drm_dsc.c and drm_dsc.h
Also add links between the functions
Ville Syrjälä wrote:
> Kevin Strasser wrote:
> > Ville Syrjälä wrote:
> > > is_hdr_plane() is around now, please use it.
> >
> > I don't think I can use icl_is_hdr_plane here without some refactoring. It
> > requires the plane->base to be initialized through drm_universal_plane_init,
> > which
On Mon, Feb 4, 2019 at 7:49 PM Sam Ravnborg wrote:
>
> Hi Daniel
>
> On Mon, Feb 04, 2019 at 11:31:13AM +0100, Daniel Vetter wrote:
> > The compiler already clears this for us.
> >
> > More important, someone might look what this is actually used for,
> > and freak out about the dragon staring
On Fri, Feb 01, 2019 at 09:38:57PM +, Strasser, Kevin wrote:
> Ville Syrjälä wrote:
> > > @@ -1774,6 +1776,45 @@ static const u32 skl_planar_formats[] = {
> > >DRM_FORMAT_NV12,
> > > };
> > >
> > > +static const uint32_t icl_hdr_plane_formats[] = {
> >
> > Please switch to u32 & co.
On Mon, Feb 4, 2019 at 2:26 PM Vasily Khoruzhick wrote:
>
> On Mon, Feb 4, 2019 at 12:23 PM Rob Herring wrote:
>
> > > simple-panel would probably work if you stuck in some mostly compatible
> > > string and provided a ddc-i2c-bus property in the device tree node. The
> > > generic-ish fallback
On Mon, Feb 4, 2019 at 10:56 AM Thierry Reding wrote:
>
> On Mon, Feb 04, 2019 at 10:27:09AM -0600, Rob Herring wrote:
> > On Mon, Feb 4, 2019 at 2:24 AM Thierry Reding
> > wrote:
> > >
> > > On Mon, Feb 04, 2019 at 12:13:55AM -0800, Vasily Khoruzhick wrote:
> > > > On Sun, Feb 3, 2019 at 11:43
https://bugs.freedesktop.org/show_bug.cgi?id=109539
--- Comment #2 from Alex Deucher ---
Does adding idle=nomwait to the kernel command line in grub help?
--
You are receiving this mail because:
You are the assignee for the bug.___
dri-devel mailing
Hi Daniel
On Mon, Feb 04, 2019 at 11:31:14AM +0100, Daniel Vetter wrote:
> Noticed why wonder what vboxvideo is using the ->master_set/drop hooks
> for.
Can you improve the gammar a little, I find it hard to read.
>
> Signed-off-by: Daniel Vetter
> Cc: Greg Kroah-Hartman
> Cc: Fabio Rafael da
On Tue, 5 Feb 2019 at 04:35, Alex Deucher wrote:
>
> On Sun, Feb 3, 2019 at 11:57 PM Dave Airlie wrote:
> >
> > On Mon, 4 Feb 2019 at 13:27, Dave Airlie wrote:
> > >
> > > On Sat, 26 Jan 2019 at 09:15, Alex Deucher wrote:
> > > >
> > > > Hi Dave, Daniel,
> > > >
> > > > New stuff for 5.1.
> >
Hi Daniel
On Mon, Feb 04, 2019 at 11:31:13AM +0100, Daniel Vetter wrote:
> The compiler already clears this for us.
>
> More important, someone might look what this is actually used for,
> and freak out about the dragon staring back at them.
>
> Signed-off-by: Daniel Vetter
> Cc: Greg
Hi Joe.
> My preference would also convert all the
> DRM_DEV_ uses to drm_dev_ eventually.
>
> Also, the macros themselves could change to use a
> more consistent mechanism.
>
> This would make the drm logging mechanisms more like
> other logging mechanisms used in the kernel.
>
> Something
https://bugs.freedesktop.org/show_bug.cgi?id=105733
--- Comment #68 from Alex Deucher ---
(In reply to jake.hedges from comment #66)
> It really did not take too long to crash it with even with the params. I
> back to square one. Thinking I will at least try a few different distros
> and
ttm_fbdev_mmap() just doesn't work. It appears to work fine, mmap()
returns success, but any attempt to actually access the mapping causes a
SIGBUS.
We can just use drm_gem_prime_mmap() instead. Almost. We have to copy
over the start offset from the ttm_buffer_object vm_node to the
https://bugs.freedesktop.org/show_bug.cgi?id=105733
--- Comment #66 from jake.hed...@yahoo.com ---
It really did not take too long to crash it with even with the params. I back
to square one. Thinking I will at least try a few different distros and
possibly upgrade some hardware though I am not
On Sun, Feb 3, 2019 at 11:57 PM Dave Airlie wrote:
>
> On Mon, 4 Feb 2019 at 13:27, Dave Airlie wrote:
> >
> > On Sat, 26 Jan 2019 at 09:15, Alex Deucher wrote:
> > >
> > > Hi Dave, Daniel,
> > >
> > > New stuff for 5.1.
> > > amdgpu:
> > > - DC bandwidth formula updates
> > > - Support for DCC
On 02/02/2019 08:07, Rodrigo Vivi wrote:
Straight copy from the kernel file.
Add more PCI Device IDs for Coffee Lake, Ice Lake,
and Amber Lake. It also include a reorg on Whiskey Lake IDs.
Align with kernel commits:
5e0f5a58b167 ("drm/i915/cfl: Adding another PCI Device ID.")
03ca3cf8e9aa
>-Original Message-
>From: dri-devel [mailto:dri-devel-boun...@lists.freedesktop.org] On Behalf Of
>Ville Syrjälä
>Sent: Monday, February 4, 2019 10:54 PM
>To: Shankar, Uma
>Cc: intel-...@lists.freedesktop.org; Syrjala, Ville ;
>dri-
>de...@lists.freedesktop.org; Lankhorst, Maarten
>
On Thu, Jan 31, 2019 at 07:17:02PM +0100, Greg Kroah-Hartman wrote:
> On Thu, Jan 31, 2019 at 09:59:26AM -0800, Rodrigo Vivi wrote:
> > On Thu, Jan 31, 2019 at 02:15:07PM +0100, Greg Kroah-Hartman wrote:
> > > When calling debugfs functions, they can now return error values if
> > > something went
Den 04.02.2019 16.41, skrev Daniel Vetter:
> On Sun, Feb 03, 2019 at 04:41:56PM +0100, Noralf Trønnes wrote:
>> The only thing now that makes drm_dev_unplug() special is that it sets
>> drm_device->unplugged. Move this code to drm_dev_unregister() so that we
>> can remove drm_dev_unplug().
>>
>>
On Mon, Feb 04, 2019 at 05:08:40PM +, Shankar, Uma wrote:
>
>
> >-Original Message-
> >From: Ville Syrjälä [mailto:ville.syrj...@linux.intel.com]
> >Sent: Monday, February 4, 2019 8:55 PM
> >To: Shankar, Uma
> >Cc: intel-...@lists.freedesktop.org; Syrjala, Ville
> >;
> >Lankhorst,
>-Original Message-
>From: dri-devel [mailto:dri-devel-boun...@lists.freedesktop.org] On Behalf Of
>Ville Syrjälä
>Sent: Saturday, February 2, 2019 12:31 AM
>To: Shankar, Uma
>Cc: intel-...@lists.freedesktop.org; Syrjala, Ville ;
>Lankhorst, Maarten ; dri-
>de...@lists.freedesktop.org
>-Original Message-
>From: dri-devel [mailto:dri-devel-boun...@lists.freedesktop.org] On Behalf Of
>Ville Syrjälä
>Sent: Saturday, February 2, 2019 12:48 AM
>To: Shankar, Uma
>Cc: emil.l.veli...@gmail.com; intel-...@lists.freedesktop.org; Syrjala, Ville
>; Lankhorst, Maarten ;
>-Original Message-
>From: Ville Syrjälä [mailto:ville.syrj...@linux.intel.com]
>Sent: Monday, February 4, 2019 8:55 PM
>To: Shankar, Uma
>Cc: intel-...@lists.freedesktop.org; Syrjala, Ville ;
>Lankhorst, Maarten ; dri-
>de...@lists.freedesktop.org
>Subject: Re: [Intel-gfx] [v10 1/3]
On Mon, Feb 04, 2019 at 10:27:09AM -0600, Rob Herring wrote:
> On Mon, Feb 4, 2019 at 2:24 AM Thierry Reding
> wrote:
> >
> > On Mon, Feb 04, 2019 at 12:13:55AM -0800, Vasily Khoruzhick wrote:
> > > On Sun, Feb 3, 2019 at 11:43 PM Thierry Reding
> > > wrote:
> > > >
> > > > On Sun, Feb 03,
https://bugs.freedesktop.org/show_bug.cgi?id=108893
supercoolem...@seznam.cz changed:
What|Removed |Added
Resolution|--- |INVALID
https://bugs.freedesktop.org/show_bug.cgi?id=108893
--- Comment #3 from supercoolem...@seznam.cz ---
This led me to another round of testing with LIGL_ALWAYS_SOFTWARE=0. Not so
surprisingly, this is also product of random chance, so this is after all
probably Wine bug.
--
You are receiving this
On Mon, Feb 4, 2019 at 9:01 AM Rob Herring wrote:
>
> On Sat, Feb 2, 2019 at 12:22 PM Noralf Trønnes wrote:
> > Den 02.02.2019 18.07, skrev Rob Herring:
> > > Other than using a rockchip_gem_object directly, the Rockchip fbdev
> > > setup has nothing special and can be converted to use the
https://bugs.freedesktop.org/show_bug.cgi?id=108893
--- Comment #2 from supercoolem...@seznam.cz ---
(In reply to supercoolemail from comment #1)
> Suprisingly, enabling GALLIUM_HUD="GPU-load;fps;cpu" workarounds this too
> and lowers the delay to HUD update step.
Ok, it does not. The delay just
On Mon, Feb 4, 2019 at 10:11 AM Vasily Khoruzhick wrote:
>
> On Mon, Feb 4, 2019 at 12:24 AM Thierry Reding
> wrote:
> > >
> > > Pinebook used several 768p panels that have slightly different timings
> > > and recent batch uses 1080p panel.
> > >
> > > What panel descriptor should I use as
>-Original Message-
>From: C, Ramalingam
>Sent: Thursday, January 31, 2019 12:30 PM
>To: intel-...@lists.freedesktop.org; dri-devel@lists.freedesktop.org;
>daniel.vet...@ffwll.ch; Winkler, Tomas ; Shankar,
>Uma
>Cc: C, Ramalingam
>Subject: [PATCH v10 38/40] drm/i915: Fix KBL HDCP2.2
https://bugs.freedesktop.org/show_bug.cgi?id=108893
supercoolem...@seznam.cz changed:
What|Removed |Added
Version|18.2|18.3
--
You are receiving
https://bugs.freedesktop.org/show_bug.cgi?id=108893
--- Comment #1 from supercoolem...@seznam.cz ---
Suprisingly, enabling GALLIUM_HUD="GPU-load;fps;cpu" workarounds this too and
lowers the delay to HUD update step.
--
You are receiving this mail because:
You are the assignee for the
https://bugzilla.kernel.org/show_bug.cgi?id=202445
--- Comment #15 from Clément Guérin (li...@protonmail.com) ---
Created attachment 280949
--> https://bugzilla.kernel.org/attachment.cgi?id=280949=edit
dmesg drm.debug=4
Here's the dmesg output as requested. I'm running gnome-shell 3.30.2.
--
>-Original Message-
>From: C, Ramalingam
>Sent: Thursday, January 31, 2019 12:30 PM
>To: intel-...@lists.freedesktop.org; dri-devel@lists.freedesktop.org;
>daniel.vet...@ffwll.ch; Winkler, Tomas ; Shankar,
>Uma
>Cc: C, Ramalingam
>Subject: [PATCH v10 36/40] misc/mei/hdcp: Component
On Mon, Feb 4, 2019 at 2:24 AM Thierry Reding wrote:
>
> On Mon, Feb 04, 2019 at 12:13:55AM -0800, Vasily Khoruzhick wrote:
> > On Sun, Feb 3, 2019 at 11:43 PM Thierry Reding
> > wrote:
> > >
> > > On Sun, Feb 03, 2019 at 10:54:57AM -0800, Vasily Khoruzhick wrote:
> > > > eDP panels usually
On Mon, Feb 04, 2019 at 08:11:05AM -0800, Vasily Khoruzhick wrote:
> On Mon, Feb 4, 2019 at 12:24 AM Thierry Reding
> wrote:
> > >
> > > Pinebook used several 768p panels that have slightly different timings
> > > and recent batch uses 1080p panel.
> > >
> > > What panel descriptor should I use
On Mon, Feb 04, 2019 at 04:59:09PM +0100, Daniel Vetter wrote:
> On Mon, Feb 04, 2019 at 12:22:18PM +0100, Thierry Reding wrote:
> > On Mon, Feb 04, 2019 at 10:40:12AM +0100, Daniel Vetter wrote:
> > > On Mon, Feb 04, 2019 at 09:23:59AM +0100, Thierry Reding wrote:
> > > > On Mon, Feb 04, 2019 at
>-Original Message-
>From: C, Ramalingam
>Sent: Thursday, January 31, 2019 12:30 PM
>To: intel-...@lists.freedesktop.org; dri-devel@lists.freedesktop.org;
>daniel.vet...@ffwll.ch; Winkler, Tomas ; Shankar,
>Uma
>Cc: C, Ramalingam
>Subject: [PATCH v10 35/40] misc/mei/hdcp: Closing wired
>-Original Message-
>From: C, Ramalingam
>Sent: Thursday, January 31, 2019 12:30 PM
>To: intel-...@lists.freedesktop.org; dri-devel@lists.freedesktop.org;
>daniel.vet...@ffwll.ch; Winkler, Tomas ; Shankar,
>Uma
>Cc: C, Ramalingam
>Subject: [PATCH v10 34/40] misc/mei/hdcp: Enabling the
>-Original Message-
>From: C, Ramalingam
>Sent: Thursday, January 31, 2019 12:30 PM
>To: intel-...@lists.freedesktop.org; dri-devel@lists.freedesktop.org;
>daniel.vet...@ffwll.ch; Winkler, Tomas ; Shankar,
>Uma
>Cc: C, Ramalingam
>Subject: [PATCH v10 33/40] misc/mei/hdcp: Verify
>-Original Message-
>From: C, Ramalingam
>Sent: Thursday, January 31, 2019 12:30 PM
>To: intel-...@lists.freedesktop.org; dri-devel@lists.freedesktop.org;
>daniel.vet...@ffwll.ch; Winkler, Tomas ; Shankar,
>Uma
>Cc: C, Ramalingam
>Subject: [PATCH v10 32/40] misc/mei/hdcp: Repeater
>-Original Message-
>From: C, Ramalingam
>Sent: Thursday, January 31, 2019 12:30 PM
>To: intel-...@lists.freedesktop.org; dri-devel@lists.freedesktop.org;
>daniel.vet...@ffwll.ch; Winkler, Tomas ; Shankar,
>Uma
>Cc: C, Ramalingam
>Subject: [PATCH v10 31/40] misc/mei/hdcp: Prepare
>-Original Message-
>From: C, Ramalingam
>Sent: Thursday, January 31, 2019 12:30 PM
>To: intel-...@lists.freedesktop.org; dri-devel@lists.freedesktop.org;
>daniel.vet...@ffwll.ch; Winkler, Tomas ; Shankar,
>Uma
>Cc: C, Ramalingam
>Subject: [PATCH v10 30/40] misc/mei/hdcp: Verify
>-Original Message-
>From: C, Ramalingam
>Sent: Thursday, January 31, 2019 12:30 PM
>To: intel-...@lists.freedesktop.org; dri-devel@lists.freedesktop.org;
>daniel.vet...@ffwll.ch; Winkler, Tomas ; Shankar,
>Uma
>Cc: C, Ramalingam
>Subject: [PATCH v10 29/40] misc/mei/hdcp: Initiate
99.999% of the time during normal operation the GMU is responsible
for power and clock control on the GX domain and the CPU remains
blissfully unaware. However, there is one situation where the CPU
needs to get involved:
The power sequencing rules dictate that the GX needs to be turned
off before
The HFI tasklet was removed in df0dff1 ("drm/msm/a6xx: Poll for HFI
responses") but the tasklet_struct was accidentally left behind.
Signed-off-by: Jordan Crouse
---
drivers/gpu/drm/msm/adreno/a6xx_gmu.h | 1 -
1 file changed, 1 deletion(-)
diff --git a/drivers/gpu/drm/msm/adreno/a6xx_gmu.h
The GMU should have two power domains defined: "cx" and "gx". "cx" is the
actual power domain for the device and "gx" will be attached at runtime
to manage reference counting on the GPU device in case of a GMU crash.
Signed-off-by: Jordan Crouse
---
The GMU code currently has some misguided code to try to work around
a hardware quirk that requires the power domains on the GPU be
collapsed in a certain order. Upcoming patches will do this the
right way so get rid of the unused and unwanted regulator
code.
Signed-off-by: Jordan Crouse
---
This is a stack of changes for 5.1 (if I'm not already too late). The bulk of
the changes implement a better GMU reset sequence using the new gpucc power
domain added in 5.0. If a GMU fault occurs during runtime we try to do a
standard GPU recovery and if the fault happens during GMU start then
Now that the GX domain is sorted we can wire up a working GMU reset.
IF a GMU hang was detected then try to forcefully shut down the GMU
in the power down sequence which should ensure that it can recover
normally on the next power up.
Signed-off-by: Jordan Crouse
---
Currently if the GMU resume function fails all we try to do is clear the
BOOT_SLUMBER oob which usually times out and ends up in a cycle of death.
If the resume function fails at any point remove any RPMh votes that might
have been added and try to shut down the GMU hardware cleanly.
>-Original Message-
>From: dri-devel [mailto:dri-devel-boun...@lists.freedesktop.org] On Behalf Of
>Ramalingam C
>Sent: Thursday, January 31, 2019 12:30 PM
>To: intel-...@lists.freedesktop.org; dri-devel@lists.freedesktop.org;
>daniel.vet...@ffwll.ch; Winkler, Tomas ; Shankar,
>Uma
>-Original Message-
>From: C, Ramalingam
>Sent: Thursday, January 31, 2019 12:30 PM
>To: intel-...@lists.freedesktop.org; dri-devel@lists.freedesktop.org;
>daniel.vet...@ffwll.ch; Winkler, Tomas ; Shankar,
>Uma
>Cc: C, Ramalingam
>Subject: [PATCH v10 27/40] misc/mei/hdcp: Verify
On 2/4/2019 9:34 PM, Winkler, Tomas wrote:
On HDMI connector init, intel_hdcp_init is passed with a flag for hdcp2.2
support based on the platform capability.
v2:
Rebased.
v3:
Collected the reviewed-by received.
Signed-off-by: Ramalingam C
Reviewed-by: Uma Shankar
---
>-Original Message-
>From: C, Ramalingam
>Sent: Thursday, January 31, 2019 12:30 PM
>To: intel-...@lists.freedesktop.org; dri-devel@lists.freedesktop.org;
>daniel.vet...@ffwll.ch; Winkler, Tomas ; Shankar,
>Uma
>Cc: C, Ramalingam
>Subject: [PATCH v10 26/40] misc/mei/hdcp: Verify
>-Original Message-
>From: C, Ramalingam
>Sent: Thursday, January 31, 2019 12:30 PM
>To: intel-...@lists.freedesktop.org; dri-devel@lists.freedesktop.org;
>daniel.vet...@ffwll.ch; Winkler, Tomas ; Shankar,
>Uma
>Cc: C, Ramalingam
>Subject: [PATCH v10 25/40] misc/mei/hdcp: Initiate
> -Original Message-
> From: C, Ramalingam
> Sent: Thursday, January 31, 2019 09:00
> To: intel-...@lists.freedesktop.org; dri-devel@lists.freedesktop.org;
> daniel.vet...@ffwll.ch; Winkler, Tomas ; Shankar,
> Uma
> Cc: C, Ramalingam
> Subject: [PATCH v10 19/40] drm/i915: Add HDCP2.2
>-Original Message-
>From: C, Ramalingam
>Sent: Thursday, January 31, 2019 12:30 PM
>To: intel-...@lists.freedesktop.org; dri-devel@lists.freedesktop.org;
>daniel.vet...@ffwll.ch; Winkler, Tomas ; Shankar,
>Uma
>Cc: C, Ramalingam
>Subject: [PATCH v10 24/40] misc/mei/hdcp: Define ME FW
>
> On HDMI connector init, intel_hdcp_init is passed with a flag for hdcp2.2
> support based on the platform capability.
>
> v2:
> Rebased.
> v3:
> Collected the reviewed-by received.
>
> Signed-off-by: Ramalingam C
> Reviewed-by: Uma Shankar
> ---
> drivers/gpu/drm/i915/intel_hdmi.c |
>-Original Message-
>From: C, Ramalingam
>Sent: Thursday, January 31, 2019 12:30 PM
>To: intel-...@lists.freedesktop.org; dri-devel@lists.freedesktop.org;
>daniel.vet...@ffwll.ch; Winkler, Tomas ; Shankar,
>Uma
>Cc: C, Ramalingam
>Subject: [PATCH v10 17/40] drm/i915: Implement the
>-Original Message-
>From: C, Ramalingam
>Sent: Thursday, January 31, 2019 12:30 PM
>To: intel-...@lists.freedesktop.org; dri-devel@lists.freedesktop.org;
>daniel.vet...@ffwll.ch; Winkler, Tomas ; Shankar,
>Uma
>Cc: C, Ramalingam
>Subject: [PATCH v10 16/40] drm/i915: Implement the
On Thu, Jan 31, 2019 at 03:46:40PM +0100, Daniel Vetter wrote:
> Component framework is extended to support multiple components for
> a struct device. These will be matched with different masters based on
> its sub component value.
>
> We are introducing this, as I915 needs two different
On Mon, Feb 04, 2019 at 12:22:18PM +0100, Thierry Reding wrote:
> On Mon, Feb 04, 2019 at 10:40:12AM +0100, Daniel Vetter wrote:
> > On Mon, Feb 04, 2019 at 09:23:59AM +0100, Thierry Reding wrote:
> > > On Mon, Feb 04, 2019 at 12:13:55AM -0800, Vasily Khoruzhick wrote:
> > > > On Sun, Feb 3, 2019
Den 04.02.2019 16.01, skrev Rob Herring:
> On Sat, Feb 2, 2019 at 12:22 PM Noralf Trønnes wrote:
>> Den 02.02.2019 18.07, skrev Rob Herring:
>>> Other than using a rockchip_gem_object directly, the Rockchip fbdev
>>> setup has nothing special and can be converted to use the generic fbdev
>>>
https://bugzilla.kernel.org/show_bug.cgi?id=202445
--- Comment #14 from Nicholas Kazlauskas (nicholas.kazlaus...@amd.com) ---
FreeSync not working on WINE is a Mesa issue I believe.
I don't think the backend WINE goes through is DRI3 which is required to use
the present extension / support
On Fri, 1 Feb 2019 at 14:15, Lucas Stach wrote:
>
> Hi Emil,
>
> > > For reference with this patch drmdevice and other drmDevice API users
> > > list:
> > > - VGEM, needs "drm/vgem: Fix vgem_init to get drm device available."
> > > - in v5.0 only :'-(
> > > - etnaviv, after "drm/etnaviv:
On Sun, Feb 03, 2019 at 04:41:56PM +0100, Noralf Trønnes wrote:
> The only thing now that makes drm_dev_unplug() special is that it sets
> drm_device->unplugged. Move this code to drm_dev_unregister() so that we
> can remove drm_dev_unplug().
>
> Signed-off-by: Noralf Trønnes
> ---
>
> Maybe
https://bugs.freedesktop.org/show_bug.cgi?id=109539
--- Comment #1 from Nicholas Kazlauskas ---
The freezing doesn't seem to be necessarily caused by by something in amdgpu
from a glance at your log.
There are some DC warnings/errors that describe what you're seeing with your
monitor not waking
daniel,
Could you please review this patch too.? Already Updated this as per
your previous review comment.
--Ram
On 1/31/2019 12:29 PM, Ramalingam C wrote:
Implement the required WA sequence for KBL to fix the
incorrect positioning of the window of oppurtunity and enc_en
signalling.
v2:
https://bugs.freedesktop.org/show_bug.cgi?id=108037
--- Comment #12 from Öyvind Saether ---
Created attachment 143286
--> https://bugs.freedesktop.org/attachment.cgi?id=143286=edit
Kernel 5.0.0-rc5 still has this problem
[27295.165873] Call Trace:
On Fri, Feb 01, 2019 at 08:50:11PM +0200, Ville Syrjälä wrote:
> On Wed, Jan 30, 2019 at 06:24:24PM +0530, Uma Shankar wrote:
> > Create a new connector property to program colorspace to sink
> > devices. Modern sink devices support more than 1 type of
> > colorspace like 601, 709, BT2020 etc.
On Mon, 04 Feb 2019 16:00:18 +0100,
Daniel Vetter wrote:
>
> On Thu, Jan 31, 2019 at 12:29:18PM +0530, Ramalingam C wrote:
> > From: Daniel Vetter
> >
> > Since we need multiple components for I915 for different purposes
> > (Audio & Mei_hdcp), we adopt the subcomponents methodology introduced
Reviewed-by: Lionel Landwerlin
On 02/02/2019 08:07, Rodrigo Vivi wrote:
Align with kernel commits:
5e0f5a58b167 ("drm/i915/cfl: Adding another PCI Device ID.")
03ca3cf8e9aa ("drm/i915/icl: Adding few more device IDs for Ice Lake")
Cc: José Roberto de Souza
Cc: Kenneth Graunke
Cc: Anuj
On Sat, Feb 2, 2019 at 12:22 PM Noralf Trønnes wrote:
> Den 02.02.2019 18.07, skrev Rob Herring:
> > Other than using a rockchip_gem_object directly, the Rockchip fbdev
> > setup has nothing special and can be converted to use the generic fbdev
> > emulation instead.
[...]
> > -static int
On Thu, Jan 31, 2019 at 12:29:18PM +0530, Ramalingam C wrote:
> From: Daniel Vetter
>
> Since we need multiple components for I915 for different purposes
> (Audio & Mei_hdcp), we adopt the subcomponents methodology introduced
> by the previous patch (mentioned below).
>
> Author: Daniel
On 2/4/2019 7:54 PM, Shankar, Uma wrote:
-Original Message-
From: C, Ramalingam
Sent: Thursday, January 31, 2019 12:29 PM
To: intel-...@lists.freedesktop.org; dri-devel@lists.freedesktop.org;
daniel.vet...@ffwll.ch; Winkler, Tomas ; Shankar,
Uma
Cc: C, Ramalingam
Subject: [PATCH
On 2/4/2019 7:39 PM, Shankar, Uma wrote:
-Original Message-
From: C, Ramalingam
Sent: Thursday, January 31, 2019 12:29 PM
To: intel-...@lists.freedesktop.org; dri-devel@lists.freedesktop.org;
daniel.vet...@ffwll.ch; Winkler, Tomas ; Shankar,
Uma
Cc: C, Ramalingam
Subject: [PATCH
>-Original Message-
>From: C, Ramalingam
>Sent: Thursday, January 31, 2019 12:30 PM
>To: intel-...@lists.freedesktop.org; dri-devel@lists.freedesktop.org;
>daniel.vet...@ffwll.ch; Winkler, Tomas ; Shankar,
>Uma
>Cc: C, Ramalingam
>Subject: [PATCH v10 15/40] drm: removing the DP Errata
>-Original Message-
>From: C, Ramalingam
>Sent: Thursday, January 31, 2019 12:30 PM
>To: intel-...@lists.freedesktop.org; dri-devel@lists.freedesktop.org;
>daniel.vet...@ffwll.ch; Winkler, Tomas ; Shankar,
>Uma
>Cc: C, Ramalingam
>Subject: [PATCH v10 14/40] drm/i915: Handle HDCP2.2
>-Original Message-
>From: C, Ramalingam
>Sent: Thursday, January 31, 2019 12:29 PM
>To: intel-...@lists.freedesktop.org; dri-devel@lists.freedesktop.org;
>daniel.vet...@ffwll.ch; Winkler, Tomas ; Shankar,
>Uma
>Cc: C, Ramalingam
>Subject: [PATCH v10 13/40] drm/i915: Implement HDCP2.2
>-Original Message-
>From: C, Ramalingam
>Sent: Thursday, January 31, 2019 12:29 PM
>To: intel-...@lists.freedesktop.org; dri-devel@lists.freedesktop.org;
>daniel.vet...@ffwll.ch; Winkler, Tomas ; Shankar,
>Uma
>Cc: C, Ramalingam
>Subject: [PATCH v10 12/40] drm: HDCP2.2 link check
>-Original Message-
>From: C, Ramalingam
>Sent: Thursday, January 31, 2019 12:29 PM
>To: intel-...@lists.freedesktop.org; dri-devel@lists.freedesktop.org;
>daniel.vet...@ffwll.ch; Winkler, Tomas ; Shankar,
>Uma
>Cc: C, Ramalingam
>Subject: [PATCH v10 11/40] drm/i915: Implement HDCP2.2
>-Original Message-
>From: C, Ramalingam
>Sent: Thursday, January 31, 2019 12:29 PM
>To: intel-...@lists.freedesktop.org; dri-devel@lists.freedesktop.org;
>daniel.vet...@ffwll.ch; Winkler, Tomas ; Shankar,
>Uma
>Cc: C, Ramalingam
>Subject: [PATCH v10 10/40] drm: helper functions for
Hi,
On Sun, Feb 03, 2019 at 10:54:55AM -0800, Vasily Khoruzhick wrote:
> Clock rate check that was added in commit bb43d40d7c83 ("drm/sun4i: rgb:
> Validate the clock rate") prevents some panel and bridges from working with
> sun4i driver.
>
> Unfortunately, dotclock frequency for some modes are
>-Original Message-
>From: C, Ramalingam
>Sent: Thursday, January 31, 2019 12:29 PM
>To: intel-...@lists.freedesktop.org; dri-devel@lists.freedesktop.org;
>daniel.vet...@ffwll.ch; Winkler, Tomas ; Shankar,
>Uma
>Cc: C, Ramalingam
>Subject: [PATCH v10 09/40] drm/i915: Implement HDCP2.2
>-Original Message-
>From: dri-devel [mailto:dri-devel-boun...@lists.freedesktop.org] On Behalf Of
>Ramalingam C
>Sent: Thursday, January 31, 2019 12:29 PM
>To: intel-...@lists.freedesktop.org; dri-devel@lists.freedesktop.org;
>daniel.vet...@ffwll.ch; Winkler, Tomas ; Shankar,
>Uma
https://bugs.freedesktop.org/show_bug.cgi?id=109545
Lionel Landwerlin changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
>-Original Message-
>From: C, Ramalingam
>Sent: Thursday, January 31, 2019 12:29 PM
>To: intel-...@lists.freedesktop.org; dri-devel@lists.freedesktop.org;
>daniel.vet...@ffwll.ch; Winkler, Tomas ; Shankar,
>Uma
>Cc: C, Ramalingam
>Subject: [PATCH v10 07/40] drm/i915: hdcp1.4 CP_IRQ
https://bugs.freedesktop.org/show_bug.cgi?id=109545
andrey.or...@intel.com changed:
What|Removed |Added
Priority|medium |high
--
You are receiving
https://bugs.freedesktop.org/show_bug.cgi?id=109545
Bug ID: 109545
Summary: intel_gt(dev_id) function returns wrong gt size on
some device IDs
Product: DRI
Version: XOrg git
Hardware: x86-64 (AMD64)
OS: All
1 - 100 of 164 matches
Mail list logo
